Difference between revisions of "Persona vocabulary"

Revision as of 17:12, 25 April 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
• 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)

Context

A context as used in the Persona data model

• subClassOf: h:Context
• 0..1 h:control
• 0..1 template
• 1..1 skos:prefLabel

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

Role

Abstract concept of a role that a Person plays.

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

RootContext

A tagging subclass indicating that this context is the "root" context for this user. There should only be one instance of RootContext for each user.

• subClassOf: Context

Person 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

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

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

shareAnonMeWithSites

If true user is willing to share their anonymous profile data (usually the p:Person in a separate "anonymous me" context) with publisher websites

• domain: Person
• value: xsd:boolean

Context Attributes

issuer

The entity (e.g. a business) that defines this context: defines the schema used, defines the meaning of the attributes of the schema, defines the interaction context withing which these attributes gain values. The issuer is often, but not necessarily the entity that makes the attribute value assertions (claims). If the issuer is Equifax, then indeed Equifax is making the claim that the "bearer" of this context is, say, over 21 years of age. As a counter example, the issuer of a context might be Facebook. In this case the values are asserted by the Facebook user, yet Facebook is considered the issuer. This is a required attribute of all Contexts.

• domain: Context
• value: 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

template

• domain: Context
• value: instance of template:TemplateContext

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