Persona Attribute List

{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}

This page describes the mapping rules from a human-readable description of an attribute to the equivalent PDM attribute(s). The mapping is usually 1:1 but there will be exceptions.

Introduction

Since getting the entire world to commit to a single, rich ontology will never happen, the next best thing is to define a rich, fine-grained internal ontology (as we have done in Persona Data Model 2.0 (PDM) and then define mapping rules into and out from it.

One of the sub-parts of PDM is an ontology to describe these mapping functions and some supporting concepts. It is called mapping.owl and is described briefly on the main PDM page.

Mapping in or out of another vocabulary can be thought of as involving two steps. First a human needs to look at an attribute in some target vocabulary T classify it as some concept C. The rows in the tables on this page describe the mapping from C to entities and attribute instances in a concrete instance of the PDM model. For example, if in vocabulary T we saw a term that we'd classify as a person's given (aka first) name then we search for a row by that name on this page and then lookup the function and arguments on that row. The functions represent paths through a PDM-conforming object graph. In the case of given name we'd find the following matching row:

Attribute	Function	Arg1	Arg2	Arg3	Arg4	Comment
Given Name	rolePathLiteral	RP	v:n	v:given-name

The function to be applied called rolePathLiteral. Its name is a hint as to how it operates. This function takes three arguments (RP, v:n, v:given-name). The rolePathLiteral starts at the root of the Persona graph (the RootMe node) and breadth-first following p:subCorrelation links searches for the first persona node that is tagged with a role that matches the role of the overall mapping context.

Let's take a moment to explain what this means. Since a single person is represented in PDM as multiple persona nodes (facets) when trying to map "given-name" we need to understand the broad, overall context of the interaction. Depending on the context a person might answer differently. For example if the context was a virtual world like Second Life, the person's given name is almost always not their "real world" given name. Persona nodes in PDM carry a number of "role" tags that indicate appropriateness/use in one of these overall contexts. (We're using the word context generically here, we are not (for once!) referring to Higgins Contexts.

So to continue our example, let's assume that the overall context is "eCommerce". The rolePathLiteral function will start at the root RootMe node and breadth-first find the first Persona node that has a matching role value of "eCommerce". If none are found then the first Person found that matches the rest of the criteria we're about to explain, will be used.

The rest of the criteria are that the persona node must have a "path" (we're done with "role" we're now onto "path"), that is, a complex-valued attribute (aka link) of type v:n (from the vcard vocabulary). Further, it must have a simple-valued attribute of type v:given-name. The value of this literal attribute is the result of mapping the human concept of "given name."

Account

Attribute	Function	Arg1	Arg2	Arg3	Arg4	Comment
Account Username	rolePathLiteral	RP	foaf:account	foaf:accountName
Account Password	rolePathLiteral	"	"	p:password
Account Confirm Password	rolePathLiteral	"	"	"
Account Username Email	roleObject	"	foaf:mbox
Account Username Email Confirm	roleObject	"	"

Names

Attribute	Function	Arg1	Arg2	Arg3	Arg4	Comment
Honorific Prefix	rolePathLiteralInitial	RP	v:n	v:honorific-prefix
Given Name	rolePathLiteral	"	"	v:given-name
Additional Names	rolePathLiteral	"	"	v:additional-name
Additional Names - Initial	rolePathLiteralInitial	"	"	v:additional-name
Family Name	rolePathLiteral	"	"	v:family-name
Honorific Suffix	rolePathLiteralInitial	"	"	v:honorific-suffix
Formatted Name	TBD
Recipient Honorific Prefix	rolePathLiteralInitial	RP, p:Recipient	v:n	v:honorific-prefix
Recipient Given Name	rolePathLiteral	"	"	v:given-name
Recipient Additional Names	rolePathLiteral	"	"	v:additional-name
Recipient Additional Names - Initial	rolePathLiteralInitial	"	"	v:additional-name
Recipient Family Name	rolePathLiteral	"	"	v:family-name
Recipient Honorific Suffix	rolePathLiteralInitial	"	"	v:honorific-suffix
Recipient Formatted Name	TBD
Billing Honorific Prefix	rolePathLiteralInitial	RP, p:Buyer	v:n	v:honorific-prefix
Billing Given Name	rolePathLiteral	"	"	v:given-name
Billing Additional Names	rolePathLiteral	"	"	v:additional-name
Billing Additional Names - Initial	rolePathLiteralInitial	"	"	v:additional-name
Billing Family Name	rolePathLiteral	"	"	v:family-name
Billing Honorific Suffix	rolePathLiteralInitial	"	"	v:honorific-suffix
Billing Formatted Name	TBD

Addresses

Attribute	Function	Arg1	Arg2	Arg3	Arg4	Comment
Recipient Address	rolePathLiteral	RP p:Recipient	v:adr	v:street-address
Recipient Extended Address	"	"	"	v:extended-address
Recipient Locality	"	"	"	v:locality
Recipient Region	"	"	"	v:region
Recipient Postal Code	"	"	"	v:postal-code
Recipient 4 Digit Extension Zip	TBD	"	"	v:postal-code
Recipient Home Address	rolePathLiteral	RP p:Recipient p:Home	v:adr	v:street-address
Recipient Home Extended Address	"	"	"	v:extended-address
Recipient Home Locality	"	"	"	v:locality
Recipient Home Region	"	"	"	v:region
Recipient Home Postal Code	"	"	"	v:postal-code
Recipient Home 4 Digit Extension Zip	TBD	"	"	v:postal-code
Billing Address	rolePathLiteral	RP p:Buyer	v:adr	v:street-address
Billing Extended Address	"	"	"	v:extended-address
Billing Locality	"	"	"	v:locality
Billing Region	"	"	"	v:region
Billing Postal Code	"	"	"	v:postal-code
Billing 4 Digit Extension Zip	TBD	"	"	v:postal-code

Birthday

Attribute	Function	Arg1	Arg2	Arg3	Arg4	Comment
Year of Birth	roleYear	RP	v:bday
Buyer Year of Birth	roleYear	RP, p:Buyer	v:bday
Month of Birth	roleMonth	RP	"
Day of Birth	roleDay	"	"

Payment Related

Attribute	Function	Arg1	Arg2	Arg3	Arg4	Comment
Credit Card Type	TBD
Credit Card Number	rolePathClassLiteral	RP, p:Buyer	pay:payment	pay:CreditCard	pay:ccNumber
Credit Card Expiration Date - Month	rolePathClassMonth	"	"	"	pay:ccExpiration
Credit Card Expiration Date - Year	rolePathClassYear	"	"	"	pay:ccExpiration
Credit Card Name	rolePathClassLiteral	"	"	"	pay:ccName
Credit Card Number	rolePathClassLiteral	RP, p:Home	"	"	pay:ccCID

Telephone Numbers

Attribute	Function	Arg1	Arg2	Arg3	Arg4	Comment
Daytime Phone - Area Code	rolePathAreaCode	RP, p:Daytime	v:tel
Daytime Phone Number - Less Area Code	rolePathSevenDigits	"	"
Daytime Phone Number - First Three	rolePathFirstThree	"	"
Daytime Phone Number - Last Four	rolePathLastFour	"	"
Daytime Phone Number - Extension	rolePathExtension	"	"
Home Phone Number - Area Code	rolePathAreaCode	RP, p:Home	"
Home Phone Number - First Three	rolePathFirstThree	"	"
Home Phone Number - Last Four	rolePathLastFour	"	"
Home Phone Number - Extension	rolePathExtension	"	"
Recipient Daytime Phone - Area Code	rolePathAreaCode	RP, p:Recipient, p:Daytime	"
Recipient Daytime Phone Number - Less Area Code	rolePathSevenDigits	"	"
Recipient Daytime Phone Number - First Three	rolePathFirstThree	"	"
Recipient Daytime Phone Number - Last Four	rolePathLastFour	"	"
Recipient Daytime Phone Number - Extension	rolePathExtension	"	"
Recipient Phone Number - Area Code	rolePathAreaCode	RP, p:Recipient	"
Recipient Phone Number - First Three	rolePathFirstThree	"	"
Recipient Phone Number - Last Four	rolePathLastFour	"	"
Recipient Phone Number - Extension	rolePathExtension	"	"
Recipient Phone Number	rolePathLiteral	RP, p:Recipient	"

Misc

Attribute	Function	Arg1	Arg2	Arg3	Arg4	Comment
Country	rolePathLiteral	RP	v:adr	v:country
Gender	roleLiteral	"	foaf:gender
Buyer Gender	roleLiteral	", p:Buyer	foaf:gender
Company Name	rolePathLiteral	RP, p:Work	v:org	v:organization-name
Title	rolePathLiteral	"	"	v:title
Timezone	TBD
Employment Status	TBD		"
Biography	TBD
Language	TBD