Skip to main content
Jump to: navigation, search

Difference between revisions of "Persona Data Model 2.0"

(Supporting Contexts)
(Supporting Contexts)
Line 19: Line 19:
 
== Supporting Contexts ==
 
== Supporting Contexts ==
  
Each regular context (e.g. each of the contexts shown above) has links to three kinds of supporting contexts: template, control and vocabulary.
+
Each regular context (e.g. each of the contexts shown above) has the following links:
 +
* a single-valued p:template link
 +
* a single-valued p:control link
 +
* a single-valued h:vocabulary link
  
[[Image:Supporting 2.0.111.png|center]]
+
[[Image:Supporting 2.0.112.png|center]]
  
 
=== Template Context ===
 
=== Template Context ===
Each regular context may have up to one associated template context (pointed to by p:template attribute). This template context (see [[Template vocabulary]]) may contain one or more of the following:
+
Each regular context may have up to one associated template context (pointed to by p:template attribute). This template context may be shared by multiple regular contexts. This template context (see [[Template vocabulary]]) may contain one or more of the following:
 
* [[View-builder vocabulary | view information]] that describes how to logically organize a presentation interface for the associated regular context
 
* [[View-builder vocabulary | view information]] that describes how to logically organize a presentation interface for the associated regular context
 
* a p:Person subclass that has a set of mapping rules written in the [[Mapping vocabulary]]
 
* a p:Person subclass that has a set of mapping rules written in the [[Mapping vocabulary]]
Line 30: Line 33:
  
 
=== Control Context ===
 
=== Control Context ===
Each regular context is associated with up to one "control" context (linked to by h:context) that contains meta information including:
+
Each regular context is associated with one "control" context (linked to by h:context). A control context is associated with one regular context. The control context contains meta information including:
 
* date-time when the regular context was created and modified
 
* date-time when the regular context was created and modified
 
* access control lists:
 
* access control lists:
Line 38: Line 41:
  
 
=== Vocabulary Context ===
 
=== Vocabulary Context ===
Each regular context has an h:vocabulary link to a context holding the vocabulary it uses to describe its contents. The value of this link is usually a reference to the context holding persona.owl (see [[Persona vocabulary]]).
+
Each regular context has an h:vocabulary link to a context holding the vocabulary it uses to describe its contents. Multiple regular contexts may share links to the same vocabulary context. The value of this link is usually a reference to the context holding persona.owl (see [[Persona vocabulary]]).
  
 
== Inbox Context ==
 
== Inbox Context ==

Revision as of 16:28, 15 May 2011

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

Person graph

A natural, human person is represented as a graph of p:Person entities (nodes, or vertices) interconnected by links (edges). Each node represents a different facet of the user (person). Each of these facets is held in a separate (graph) container called a Context.

Each Person node is a set of attributes and values. These attributes may be simple literals (e.g. the user's first name) or they may be other entities (which we call complex attributes). These latter attributes are shown in diagrams a as links to other nodes.

Typically each node in the person 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 person entities can be reached by traversing links of the following kinds, (although other links may also exist (e.g. p:source, foaf:knows, etc.):

  • h:correlation
  • h:relation
  • h:indeterminate
Root context 2.0.124.png

Supporting Contexts

Each regular context (e.g. each of the contexts shown above) has the following links:

  • a single-valued p:template link
  • a single-valued p:control link
  • a single-valued h:vocabulary link
Supporting 2.0.112.png

Template Context

Each regular context may have up to one associated template context (pointed to by p:template attribute). This template context may be shared by multiple regular contexts. This template context (see Template vocabulary) may contain one or more of the following:

  • view information that describes how to logically organize a presentation interface for the associated regular context
  • a p:Person subclass that has a set of mapping rules written in the Mapping vocabulary
  • template information about how to dynamically create the associated regular context

Control Context

Each regular context is associated with one "control" context (linked to by h:context). A control context is associated with one regular context. The control context contains meta information including:

  • date-time when the regular context was created and modified
  • access control lists:
    • list of parties (currently PDS account ids) that may read the regular context
    • list of parties that may write the regular context
    • list of parties that may append to the regular context

Vocabulary Context

Each regular context has an h:vocabulary link to a context holding the vocabulary it uses to describe its contents. Multiple regular contexts may share links to the same vocabulary context. The value of this link is usually a reference to the context holding persona.owl (see Persona vocabulary).

Inbox Context

In order to bootstrap sharing, each PDS user has an inbox context that is globally append-able. This allows users to append invites to other users. See the Data Sharing With Alice And Bob scenario.

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 Person 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 person 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.

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

Social graphs 2.0.103b.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 Person nodes.

Vocabularies

Contexts may describe their contents in any vocabulary they wish so long as it builds on the Persona vocabulary. In the person graph example above all of the contexts except one describe their contents using the Persona Data Model (vocabulary) (shown as purple "PDM"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.

Infocard related vocabularies:

Naming Conventions

Context Naming

User Context Naming

User contexts inside an ADS are are named according to the following pattern:

  http://<servername>/<username>/<context-name>/<meta-type>
  

If <meta-type> is missing this implies that this is the id of a "regular" user context, else <meta-type> may be one of these values:

  • twin

Examples wherein servername is my.azigo.com:

  http://my.azigo.com/ptrevithick/awp - anonymous web profile
  http://my.azigo.com/ptrevithick/staples.com - paul's profile at staples.com
  http://my.azigo.com/ptrevithick/staples.com/twin - what staples says about paul
  http://my.azigo.com/ptrevithick/browsing - browsing history

Reserved Usernames

Any username with 4 or less characters is reserved. Examples of reserved usernames:

  • sys
  • root
  • blog

If the username is 4 or less characters this is the id of a system context (see next section)

System Context Naming

  http://<servername>/<reserved-username>/<meta-type>/<context-name>

The <meta-type> may be one of these values:

  • template
  • ontology
  • data

Example

  http://my.azigo.com/sys/template/awp - the template for a user's regular "awp" context
  http://my.azigo.com/sys/ontology/tracker-catalog
  http://my.azigo.com/sys/data/trackers

Entity Naming

The root entity in most contexts has a local name of "me".

Example:

  http://my.azigo.com/ptrevithick/awp#me

Examples

Imagine a root context containing a p:Person entity locally named "me". This root node could have h:correlation links pointing to the root "me" entities in two contexts, a web profile context, and a alice-staples context.

The web profile context might look like this:

Webprofile.png

The staples context (the profile of the user at staples.com) might look like this:

Alice-staples2.png


Viewing & Editing Contexts

This section discusses how present (e.g. in a user interface) the contents of a context that is represented using the Persona vocabulary. To construct a data-driven presentation metadata about the attributes of the context is needed. These metadata attributes may live in a number of places. Metadata attributes may:

  • Be attributes of the attribute's class definition (rdf:Property)
  • Be attributes of the an entity class (e.g. persona:Person, vcard:Address)

Further, these metadata attribute statements may be stored either one or the other (or both) places:

  • The context that holds the Persona vocabulary or one of the vocabularies that it imports
  • The template context that holds information to help build a presentation of contexts (see the View-builder vocabulary)

Note: the fact that the metadata may be stored in more than one context has an implication that the lookup APIs should search across ALL contexts for these statements.

Here are some of those metadata attributes:

UI widget label 
This is stored in an internationalized string value of the skos:prefLabel metadata attribute. An example of a UI label might be the string "Zipcode" for the person's postal-code attribute.
Cardinality 
The min..max number of values of the attribute. This is an attribute of the class of the entity (e.g. persona:Person, vcard:Address). Min=0 and Max=1 is an example of an attribute that has one optional value.
Example value 
The example value is the value of the skos:example attribute. For example "name@domain.com" might be an example of an example value.
Hover text 
The string description of the attribute is the value of the skos:description attribute.
Type 
The type of an attribute is the value of the rdf:type attribute
Allowed values 
For literal-valued attributes an enumerated list of values is provided. This is represented as attributes of the attribute's rdf:range attribute. For example for eye-color the allowed attribute values might be "blue", "green" and "brown".
Syntax restrictions 
@@@@TBD

Links

Rough notes; a bit long in the tooth:

Back to the top