Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "VCard vocabulary usage"

(UML Overview)
(Other classes)
Line 41: Line 41:
 
*v:logo  
 
*v:logo  
 
*v:tel
 
*v:tel
 +
 +
=== Home ===
 +
 +
* subClassOf: Address
 +
* 0..1 p:owner
 +
* 0..1 p:renter
  
 
=== Other classes ===
 
=== Other classes ===
  
*v:Home
+
*Work
*v:Work
+
*Also used: Parcel, Dom, Intl, Pref, Postal
*Also used: vParcel, v:Dom, v:Intl, v:Pref, v:Postal
+
*Also used: BBS...Voice as shown above
*Also used: vBBS...v:Voice as shown above
+
  
 
== Classes Not Used  ==
 
== Classes Not Used  ==

Revision as of 18:20, 16 August 2011

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

The Persona vocabulary imports vCard (http://www.w3.org/2006/vcard/ns) and uses most of it as is, but with a few tweaks described below.

UML Overview

We show below the aspect of the Persona vocabulary that builds on the vCard vocabulary. Attribute names and class names imported from other, non-vcard vocabularies are shown in italics. Classes from other vocabularies are shown in grey.

Vcard 2.0.114b.png

Classes and Attributes Used

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

v:Address

  • p:addressNote *
  • 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

Home

  • subClassOf: Address
  • 0..1 p:owner
  • 0..1 p:renter

Other classes

  • Work
  • Also used: Parcel, Dom, Intl, Pref, Postal
  • Also used: BBS...Voice as shown above

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

Other conventions

Whereas by inference a p:Person node that has a v:adr or v:n etc link is a v:VCard, we add the following constraints (that are not present in usual VCards) on p:Persons using these complex attributes:

  1. A single p:Person instance has a maximum of one v:adr, one v:n, one v:org

The implication of #1 above is that if a person has N addresses, then N separate p:Person nodes must be instantiated. If it is desired to indicate the time period for which the person lived at a given address, the h:start..h:end attributes on the p:Person node are used.

Links

Back to the top