Difference between revisions of "VCard vocabulary usage"

Revision as of 00:04, 14 October 2010

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:Person class. Concepts from vCard are shown in italics. Item in non-italics are defined in persona.owl discussed further on.

Classes Used

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

v:Address

• p:addressNote *
• h:start ..1
• h: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

Classes Not Used

• 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 Not Used

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

Links

• Persona Data Model 2.0