Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Persona Data Model 2.0"

(UML Overview)
(Persona.owl)
Line 177: Line 177:
 
*The value <code>http://!self</code> - the user has explicitly asserted entities &amp; attributes in this context  
 
*The value <code>http://!self</code> - the user has explicitly asserted entities &amp; attributes in this context  
 
*The value <code>http://!derived</code> - the active client has derived entities &amp; attributes in this context based on observed behavior and/or assertions made by the user in other contexts
 
*The value <code>http://!derived</code> - the active client has derived entities &amp; attributes in this context based on observed behavior and/or assertions made by the user in other contexts
 
==== <code>p:verification</code>  ====
 
Verification information about some entity in this context
 
* used by: h:Context
 
* value: p:Verification
 
 
==== <code>p:verifiedAt</code>  ====
 
When this verification was performed
 
* used by: p:Verification
 
* value: dateTime
 
 
==== <code>p:verifiedObject</code>  ====
 
The entity that has been verified
 
* used by: p:Verification
 
* value: an entity
 
  
 
== Imported Ontologies  ==
 
== Imported Ontologies  ==

Revision as of 21:54, 24 August 2010

{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
Higgins logo 76Wx100H.jpg

The Persona Data Model 2.0 (PDM) is builds on Higgins Data Model 2.0 and a number of other models (aka schemas, vocabularies, ontologies). It used by Personal Data Store 2.0 and will likely be used by future Higgins web services.

Contents

TODO

  • add mapping.owl section
  • add owl section

Introduction

The Persona Data Model 2.0 is an ontology about people. It is based on the Higgins Data Model 2.0 which is in turn based on Context Data Model 2.0 (aka CDM 2.0). This page provides an informal overview.

Restrictions on CDM 2.0 EntityIds

The PDM 2.0 uses a restricted set of the full capabilities of CDM 2.0. The restriction is in the area of EntityIds. PDM 2.0 adds the following constraints:

  1. All entityIds MUST be URIs
  2. All entityId values MUST be Linked Data URIs or XRI 2.0 URIs
  3. All entityIds within a given context MUST be either (a) relative to a "base" URI of the context or (b) absolute
  4. Whether or not an entityID is relative or absolute MUST be able to be determined by inspection of its syntax
  5. Absolute entityIds MAY be globally resolvable
  6. Globally resolvable entityIds resolve to an entity (resource description) within exactly one context

A graph of Persona nodes

A person is represented as a graph of p:Persona class Entity nodes (vertices) interconnected by links (edges). Each node represents a different facet of the user (person). Each node is an entity (i.e. a set of attributes & values). These attributes may be simple literals (e.g. the user's first name) or they may be other entities. These latter complex attributes are rendered a as links (edges) to other nodes, but these edges and nodes are not considered part of the graph.

The graph is a logical abstraction. The data behind these nodes may be physically located anywhere on the Internet.

Typically each node in the Persona graph is located in its own Context. The root node lies in a special context (for each user) called the root context.

All of the main persona entities can be reached by traversing links of the following kinds, (although in addition other links may also exist (e.g. foaf:knows, etc.)):

  • h:correlation
  • h:relation
  • h:indeterminate
  • p:subCorrelation

p:subCorrelation and Access Control

PDM adds p:subCorrelation, a specialized (directed) h:correlation. It is a relation between two Personas 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 typically larger than the intended audience for the source entity. It is a non-symmetric attribute of an entity. The value of this attribute is another entity.

SubCorrelation allows us to construct a directed graph of entities radiating out from the root node. The root node's attributes are the most privileged information about a person. Below is an example of a directed graph. We have displayed a reasonable "default" access control policy for each "level" (i.e. number of hops from the root) of the graph.

Subcorr.png

More detailed example graph

A more detailed example graph is shown below. Many details in this diagram will be explained further on:

Root 2.0.114.png

Note: in order to simplify the above diagram we follow a convention whereby the links are drawn between contexts whereas in reality the links are between the main p:persona objects within each of these contexts. Further, these main persona entities may well themselves have complex attributes (i.e. links to other entities). These have also been omitted.

profile/personaSubCorrelation

For performance reasons, the PDM has added the following link types (sub-attributes of p:subCorrelation): p:personaSubCorrelation and p:profileSubCorrelation. When the links from the root p:Persona node are enumerated, the potentially hundreds of links to p:Persona entities that live in p:PersonaContexts can be differentiated by inspection from the handful of of links to p:Persona entities that live in p:ProfileContexts.

Kinds of Contexts

There are three special kinds of Contexts:

Persona Context
A context containing a Persona instance (shown in the tinted areas above). This Persona represents a broad role that a person plays in interacting with multiple other people, websites/organizations. Typical examples of PersonaContexts would be Work, Home & Friends, Citizen, Health and Anonymous. For example, the Work Persona's attributes are common across multiple kinds of interactions related to one's employment.
Profile Context
A context that contains a Persona instance. This Persona represents a specific profile (set of attributes) used with ONE external person or website/organization.
Root Context
A singleton context that contains the "root" Persona node of the Persona graph.

Schemas

In the above example all of the contexts except one express their contents using the Persona data model (shown as red "P"s above). The exception is the managed i-card from Equifax which uses attribute (aka claim) URIs defined by the OASIS IMI TC and by the ICF's (Information Card Foundation) schema working group.

Representing Social Graphs

h:relation

HDM defines a h:relation complex attribute that is used in PDM to link one Person node to another where each Persona node represents a different person. No symmetry is implied in this thus the statement (A h:relation B) is akin to saying person A "knows of" person B.

Shown below are two social graph examples. One uses foaf:knows links and and (unrelated to this) shows each node in its own context. The other uses h:relation links and (unrelated) shows all persona nodes in a single context. In the Work context we see that the user knows three colleagues but doesn't know how they know one another. In the Home & Family context we see that the user knows two people and that everyone knows one another. The foaf:knows links are shown in both directions although logically this is redundant since foaf:knows is what is a called a symmetric relation.

Nodes that represent the user are shown in purple. Nodes that represent a person other than the user are shown in red.

Social graph 2.0.102.png

foaf:knows

To indicate that a person A "knows" person B where some level of reciprocated interaction between the parties is implied, we use foaf:knows.

Since foaf:knows is a broader concept than h:relation, foaf:knows is not a sub-attribute of h:relation. Thus if we had the statement "A h:relation B" then we might later add a second statement "A foaf:knows B" to add the stronger, broader (and symmetric) concept of "knowing."

h:indeterminate

HDM also defines h:indeterminate link attribute on node A to indicates that its value(s) may or may not represent the same thing as is represented by A.

Implementation Note

Consumers of the HDM may traverse h:relation, h:correlation and h:indeterminate attribute links and (despite ignoring all other links) traverse the entire graph of h:Persona nodes.

Persona.owl

Persona.owl is the main ontology that imports and builds upon many other Higgins-defined and external ontologies as will be described later.

UML Overview

Persona 2.0.106d.png

Classes

Persona

A contextualized aspect (aka facet) of a person.

  • 0..N role
  • 0..N subCorrelation
  • 0..N hasAgent

Role

Abstract concept of a role that a p:Persona plays.

Internal roles that a person may play:

  • 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.

External roles are imposed on you by the nature of the broad outer context. E.g. an eCommerce website "imposes" an eCommerce role on you, whereas a gaming site imposes broading a gaming role on you. These External roles are defined:

  • 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

Attributes

eyeColor

  • class: Persona
  • value: xsd:string oneOf(green, blue, brown)

subCorrelation

A relation between two Personas 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.

  • class: Persona
  • value: Persona

role

A role that this person plays. Multiple values are allowed: e.g. p:Home and p:Buyer indicates that this person is playing the role of both (a) themself in their home/family/personal life and (b) the person who will receive credit card bills and pay them.

  • class: Persona
  • value: Role

hasAgent

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

  • value: p:Persona

neverRememberPassword

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

  • class: p:Persona
  • value: xsd:boolean

password

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

  • class: foaf:OnlineAccount
  • value: xsd:string

p: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

Imported Ontologies

The PDM 2.0 is defined persona.owl and the ontologies it build on. At the heart of the PDM model is the p:Persona class and related attributes. In the following sections we describe the concepts that have been adopted by PDM that have been defined in vCard, FOAF and other ontologies.

Persona imports 2.0.106.jpg

Higgins-Defined

External

vCard

Persona imports vCard, uses most of it as is, but with a few tweaks described below.

UML Overview

We show below the aspect of PDM that builds on the vCard ontology. The heart of the PDM model is the p:Persona class. Concepts from vCard are shown in italics. Item in non-italics are defined in persona.owl discussed further on.

Vcard 2.0107.png

Classes

Note: Additional attributes from persona.owl are shown in bold below.

v:Address

  • p:addressNote *
  • p:start ..1
  • p:end ..1
  • v:address ..1
  • v:extended-address ..1
  • v:post-office-box ..1
  • v:locality ..1
  • v:region ..1
  • v:postal-code ..1
  • v:country-name ..1

v:Name

  • v:honorific-prefix ..1
  • v:given-name ..1
  • v:additional-name *
  • v:family-name ..1
  • v:honorific-suffix ..1

v:Organization

  • v:organization-name ..1
  • v:organization-unit ..1

Other attributes

  • v:logo
  • v:tel

Other vCard classes

  • v:Label (disjoint with v:Tel) - not used (don't yet understand what it is)
  • v:Tel - not used; we use foaf:phone instead

Attributes

The following attributes are not used:

  • v:street-address - we use the more granular p:street, p:houseName, p:houseNumber, p:apartment instead
  • v:category
  • v:class
  • v:email - we use foaf:mbox instead
  • v:fn
  • v:agent - we use hasAgent instead
  • v:geo - we use geo:location instead
  • v:key
  • v:mailer - not sure what this is
  • v:photo - we use foaf:thumbnail instead
  • v:prodid
  • v:rev
  • v:sort-string
  • v:sound
  • v:tz - not sure syntax of range/value
  • v:uid - we use entityId instead
  • v:url - we use foaf:page (and sub-attributes) instead

FOAF

Persona.owl imports FOAF and uses some of the classes and attributes it defines.

UML Overview

We show below the aspect of PDM that builds on the FOAF ontology:

Foaf 2.0.113.png

Classes

  • foaf:OnlineAccount
  • foaf:OnlineEcommerceAccount
  • foaf:OnlineGamingAccount
  • foaf:OnlineChatAccount
  • foaf:Document
  • foaf:PersonalProfileDocument
  • foaf:Image

Attributes

  • foaf:account
  • foaf:accountName
  • foaf:status
  • foaf:myersBriggs
  • foaf:geekcode
  • foaf:geekcode
  • foaf:aimChatID
  • foaf:skypeId
  • foaf:skypID
  • foaf icqChatID
  • foaf:yahooID
  • foaf:msnChatID
  • foaf:made
  • foaf:maker
  • foaf:mbox
  • foaf:mbox_sha1sum
  • foaf:depicts
  • foaf:depiction
  • foaf:knows
  • foaf:gender
  • foaf:thumbnail
  • foaf:page
  • foaf:homepage
  • foaf:weblog
  • foaf:openid
  • foaf:tipjar
  • foaf:schoolHomepage
  • foaf:workplaceHomepage
  • foaf:workInfoHomepage

WSG84

Persona.owl imports WGS84 and uses some of its classes and attributes.

UML Overview

We show below the aspect of PDM that builds on the geospatial ontology:

Geo2.0.106.png

Classes

Attributes

SKOS

Person.owl imports the SKOS ontology and uses a few of its classes and attributes.

Classes

Concept

A concept in a concept hierarchy

Attributes

skos:concept

  • used to annotate persona.owl attributes
  • value: skos:Concept

skos:broader

  • value: skos:Concept

Concept Scheme

Persona.owl includes a concept hierarchy defined using SKOS. This hierarchy can be used by visual editors (e.g. a persona editor) to help organize the UI. Attributes defined in persona.owl include skos:concept annotations to indicate the category of concept the attribute belongs to.

Conceptsv5.png

Which is represented as:

Persona-concept-hierarchy.png

Note: see Higgins Data Model 2.0 for more information on concept schemes.

Example of Use

@@@@TODO


event.owl

Overview

Event 2.0.100.png

Classes

Event

Attribute

Subclasses of Attribute:

  • Get
  • Modify
  • Delete
  • Add

Verification

Attributes

event

mapping.owl

@@@TODO

payment.owl

Overview

Payment.png

Classes

PaymentMethod

Method of payment including credit cards, paypal, etc.

ByBankTransferInAdvance

  • subclassOf: PaymentMethod

Cash

  • subclassOf: PaymentMethod

CheckInAdvance

  • subclassOf: PaymentMethod

COD

  • subclassOf: PaymentMethod

CreditCard

  • subclassOf: PaymentMethod
  • 1..1 ccCid
  • 1..1 ccExpiration
  • 1..1 ccNumber

AMEX

  • subclassOf: CreditCard

DinersClub

  • subclassOf: CreditCard

Discover

  • subclassOf: CreditCard

MasterCard

  • subclassOf: CreditCard

VISA

  • subclassOf: CreditCard

DirectDebit

  • subclassOf: PaymentMethod

PayPal

  • subclassOf: PaymentMethod

Attributes

ccCid

  • class: CreditCard
  • value: xsd:string

ccExpiration

  • class: CreditCard
  • value: xsd:date

ccNumber

  • class: CreditCard
  • value: xsd:string

paymentMethod

  • class: Persona
  • value: PaymentMethod

icard.owl

Information Card (aka i-card) technology is defined by the OASIS IMI TC. It is a standard way to represent a person's digital identities using a card metaphor, XML card formats, and associated SOAP and HTTP network protocols. See also I-Card.

Before we introduce the I-Card classes, remember that in CDM multiple inheritance is allowed: any single entity may be a member of multiple classes simultaneously. In this section we leverage this characteristic.

Classes

I-Card

Abstract class

  • subclassOf: h:Context.
  • 1..1 cardId (xsd:string) - a unique identifier for the card
  • 1..1 image - an image bitmap for the background of the card when it is displayed
  • ... others.

P-Card

An OASIS IMI Personal card

  • subclassOf: I-Card

M-Card

An OASIS IMI Managed card

  • subclassOf: I-Card

P-Card Attributes

The attributes that define a personal card are taken directly from the OASIS IMI specification. An example p-card is shown here:

Personal-i-card-example.png

M-Card Attributes

Shown below is an example of an instance of an m-card. For simplicity this m-card has only a single supported claim, "LastName". The entity shown in the center of the card is a cache of what is returned by the STS in response to a request for a display token.

M-card-explained.png

Note: There is an error in the above diagram the DisplayTokenEntity should have been modeled in the Persona data model (thus identity:surname would have been transformed into its equivalent in PDM.


Card Axioms

  1. For any M-Card: The value of any of the above "supported" claims attributes is considered to be a cache of the most recent value of these claims as fetched from the m-card's STS


rcard.owl

R-Card ontology.

Classes

R-Card

A Higgins relationship card. Which is really a profile of an IMI managed or personal i-card

  • subClassOf i-card:I-Card
  • 1..1 resource-udr

AppCard

An r-card that supports a Javascript app. It's resource-udr is a reference to a target entity. This target entity and its surrounding context are described by the app-data ontology.

  • subClassOf: R-Card

Attributes

resource-udr

Representation of the http://schemas.informationcard.net/@ics/resource-udr/2009-03 claim type.

  • class: R-Card
  • value: xsd:anyURI - UDI reference

Personal R-Card Example

From a structural point of view, the presence of the resource-udr claim on a P-Card or an M-Card makes it be considered an R-Card. Here is an example of a personal R-Card:

Example-r-pcard-v2.png

ERRATA: the above image is incorrect for PDM 2.0. As above the card is a context. The entity (in this case referenced by the value of the resource_udr claim) would be a free standing Persona entity (as above) and described in the PDM 1.1 model. Also icf: prefix should be removed along with ...2008... suffix.

Managed R-Card

The final type of card is the managed r-card. The presence of the resource-udr claim makes an ordinary M-Card into an R-Card. Here is an example of a managed R-Card:

Managed-r-card.png

ERRATA: The image above needs to be replaced.

app-data.owl

Provides the classes and attributes to represent the "target" entity pointed to by an app-card, as well as this entity's surrounding context.

Classes

AppData

Abstract superclass. A kind of h:Context used to store the information about an app. This information is "pointed" to by an app-card (ako r-card)

  • subClassOf: h:Context
  • 1..1 appId
  • 1..1 appDescription
  • 1..1 appVersion
  • 0..N appSites
  • 0..N appEntityParam
  • 0..1 appParams
  • 1..1 appAdmin

Fetched

An AppData describing an app wherein the Javascript is fetched from an external service.

  • subClassOf: app-data:AppData
  • 1..1 appServiceType - the type of service from which the Javascript is fetched
  • 1..1 appService - the Javascript service URL

Embedded

An AppData describing an app where the Javascript is retrieved from the value of the appJS attribute.

  • subClassOf: app-data:AppData
  • 1..1 appJS - the Javascript to run

AppParams

An AppParams instance is the value of an AppCard's appParams attribute. It is a set of attributes and values used to initialize the app. Note: these attribute/values are combined with those derived from the AppCard's appEntityParam.

AppData Attributes

appId

Uniquely identifies the app within the "developerId" (i.e. the card issuer) namespace. In other words the combination of the devID and the appId is globally unique. When using Kynetx KNS this is the ruleID with special constraint that this ruleID is globally unique.

  • used by: AppData
  • value: string

appDescription

A human readable description of the app. Note: If appServer == http(s)://init.kobj.net, then the KNS "describe" API can be used by a context provider implementation to provide this attribute value.

  • used by: AppData
  • value: string

appVersion

A human readable version of the app. Note: If appServer == http(s)://init.kobj.net, then the Kynetx KNS "describe" API can be used by a context Provider implementation to provide this attribute value.

  • used by: AppData
  • value: string

appAdminURL

The URL of a webapp to load into an active client's "dashboard" (admin) UI.

  • used by: AppData
  • value: xsd:anyURI

appSites

This is not a list of specific URIs, it is a list of strings to match in the domain name part of a URI. So urn:google would fire on maps.google.com, www.google.com, www.googleismyfavoritesite.com. For Kynetx-powered cards (i.e. if appServer = http[s]://init.kobj.net"), the values of this attribute should be dynamically fetched using the 'dispatch' method at URL: [1]<appId>.

  • used by: AppData
  • value: string

appParams

A set of attributes used to initialize the app.

  • used by: AppData
  • value: AppParams

appEntityParam

The value is the (URI) name of an attribute on the AppCard's target entity. This referenced attribute and its value should be used to initialize the app.

  • used by: AppData
  • value: URI name of an attribute

appEntityParam

The name of an attribute (e.g. p:postal-code) of the "target" entity of the app-card. The value of this named attribute of the target entity is used as a parameter to the app-card's app.

  • used by: AppData
  • value: URI

Fetched AppData Attributes

appService

The URI giving the endpoint from which the Javascript should be fetched.

  • used by: Fetched
  • value: URI

appServiceType

If value is "kynetx" then the browser extension that will inject the Javascript for this app-card should construct a Kynetx-compatible <script> block and call an initialization URL based on the value of the appService attribute.

  • used by: Fetched
  • value: string whose value is oneof ("kynetx").

Embedded AppData Attributes

appJS

The Javascript of the app. There must either be an appJS or an appService attribute and apptype (but not both)

  • used by: Embedded
  • value: base64encoded block of Javascript

Other Attributes

appEnabled

  • used by the target entity to which the underlying r-card's resource-udr points. If true the Javascript of this card is enabled to run.
  • value: boolean

Example AppCard (context) and it's associated AppData (context)

Note: Not shown is a r-card:resource-udr link from the AppCard in the upper diagram to the Persona_1 entity in the lower diagram.

Here is the AppCard:

Appcard v2.jpg

Note: missing from the above diagram is the list of supported claims. This list would include the ICF's resource-udr claim type.

Here is the AppData:

Appdata v1.png

Shown above is an example Embedded AppData context (shown as CreditBureauAppData above). Within this context is an entity, Persona_1. The CreditBureauAppData object has a number of attributes described above.

Of particular interest is the app-card:appParams attribute whose value is the AppParams_1 object. The AppParams_1 in turn has two app initialization attributes, randomAttribute1 and 2.

Note: Since "appEnabled" = true attribute/value is not present on Persona_1 its value is assumed to be false and the card is thus disabled at present.

See Also

Proposed extensions:

Use cases:

Back to the top