Difference between revisions of "Persona vocabulary"

Revision as of 15:23, 8 February 2011

This is the main vocabulary at the heart of the Persona Data Model 2.0

Files

• Most recently published
• SVN source: persona.owl.

Vocabularies Imported by persona.owl

Higgins-defined

• onb: Online-behavior vocabulary
• osoc: OpenSocial overlay vocabulary
• media: Media vocabulary
• event: Event vocabulary
• pay: Payment vocabulary
• app-data: App-data vocabulary
• r-card: R-Card vocabulary
• i-card: I-Card vocabulary
• mapping: Mapping vocabulary
• template: Template vocabulary
• h: Higgins Data Model 2.0

External

• v: VCard vocabulary usage
• geo: GeoLocation vocabulary usage
• foaf: FOAF vocabulary usage
• skos: SKOS vocabulary usage
• spl: SPL, spin: SPIN, sp: SP
• dc: Dublin Core
• owl: OWL 2, RDFS, RDF

UML Overview

Classes

TODO: add the newly added IdentificationDoc, Passport and VehicleLicense classes to this section TODO: add the newly added SourceLink classes to this section (and p:sourceLink to the attributes section)

External

Roles defined by the context of your interaction. E.g. an eCommerce website "imposes" an eCommerce role on you, whereas a gaming site imposes broading a gaming role on you.

• subClassOf Role

Defined instances:

• Ecommerce: A role imposed by eCommerce interactions, e.g. with an eCommerce website
• Gaming: A role imposed by gaming-related interactions, e.g. with a gaming website like world of warcraft
• SocialNetworking: A role imposed by social interactions, e.g. with a social networking site

Internal

Roles that a person may play

• subClassOf Role

Defined instances:

• Work: A work-related role.
• Home: Acting in a personal, non-professional capacity.
• Buyer: A person who is physically able to receive a bill and pay a bill. This person must be "contactable" to play this role. They must have a v:adr and v:n and optionally other information so that the bill/invoice can be physically delivered to them. Further, they must be able to pay this bill.
• Recipient: A person who is physically able to receive a letter, parcel or delivery. This person must be "contactable" to play this role. That is, they must have a v:adr and v:n and optionally other information so that the delivery can be physically routed to them.

Person

A contextualized aspect (aka facet) of a person.

• subClassOf h:Person
• subClassOf geo:SpatialThing

• 0..N subCorrelation
• 0..N hasAgent
• 0..N sourceLink

ProfileContext

• subClassOf h:Context

A context that stores the following kinds of attributes:

1. One or more p:Person nodes each with RP-specific attributes
   • e.g. united.com frequent flyer number and account balance
   • foaf:OnlineAccount instance (including p:password)
2. Disclosure events
   • Events that record what attributes have been disclosed to an RP.

Role

Abstract concept of a role that a Person plays.

• 1..1 skos:prefLabel - display label for UI

RootContext

A singleton context that contains the "root" Person node of the Person graph.

• subClassOf h:Context

Attributes

acceptTermsAndConditions

Person has accepted the terms and conditions of this context current at the time of acceptance.

• domain: p:Person
• value: xsd:dateTime

allowEmailContact

Allow email contact from any other entity (or the context issuer that may not be explicitly represented as an entity) in this context.

• domain: p:Person
• value: xsd:boolean

allowSMSContact

Allow SMS contact from any other entity (or the context issuer that may not be explicitly represented as an entity) in this context.

• domain: p:Person
• value: xsd:boolean

consumer

Inverse of p:source link.

• domain: p:Person
• value: p:Person - consumer

hasAgent

A person other than the user to whom some authority to act on the user's behalf has been delegated.

• domain: p:Person
• value: p:Person

issuer

In the Higgins Data Model 2.0 all Context attributes are optional. However in the Persona Data Model 2.0 we have this requirement:

• All contexts that are made available by a third party (e.g. the government, a bank, etc.) MUST have a p:issuer attribute
• The attribute value is a URI
• The URI is either the domain name that is the authority behind the attribute assertions or
• The value http://!self - the user has explicitly asserted entities & attributes in this context
• The value http://!derived - the active client has derived entities & attributes in this context based on observed behavior and/or assertions made by the user in other contexts

neverRememberPassword

Remember whether or not the person wants password managers to capture the password entered into a login form. Only used in Profile Contexts.

• domain: p:Person
• value: xsd:boolean

password

The value of the password that a person might enter into a login form. Only used in Profile Contexts

• domain: foaf:OnlineAccount
• value: xsd:string

role

A role played by a Person

• domain: Person
• value: Role

subCorrelation

A relation between two p:Person nodes in different contexts that are asserted to be representing the same person and such that the value entity is used in a broader scope (with generally more relaxed access control policies). The size of the intended "audience" for the value entity is larger than the intended audience for the source entity.

• domain: Person
• value: Person

Attributes from higgins.owl

h:end

Time instant before which this p:Person is valid (see also h:start)

• domain: p:Person
• value: xsd:dateTime

h:start

Time instant after which this p:Person is valid (see also h:end)

• domain: p:Person
• value: xsd:dateTime

Links

• Persona Data Model 2.0