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"

(Classes Not Used)
(Attributes Not Used)
Line 63: Line 63:
 
The following attributes are '''not''' used:  
 
The following attributes are '''not''' used:  
  
*v:category  
+
* category  
*v:class  
+
* class  
*v:email - we use foaf:mbox instead  
+
* email - we use foaf:mbox instead  
*v:fn  
+
* fn  
*v:agent - we use hasAgent instead  
+
* agent - we use hasAgent instead  
*v:geo - we use geo:location instead  
+
* geo - we use geo:location instead  
*v:key  
+
* key  
*v:mailer - not sure what this is  
+
* mailer - not sure what this is  
*v:photo - we use foaf:thumbnail instead  
+
* photo - we use foaf:thumbnail instead  
*v:prodid  
+
* prodid  
*v:rev  
+
* rev  
*v:sort-string  
+
* sort-string  
*v:sound  
+
* sound  
*v:tz - not sure syntax of range/value  
+
* tz - not sure syntax of range/value  
*v:uid - we use entityId instead  
+
* uid - we use entityId instead  
*v:url - we use foaf:page (and sub-attributes) instead
+
* url - we use foaf:page (and sub-attributes) instead
  
 
== Other conventions ==
 
== Other conventions ==

Revision as of 18:23, 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.

Address

  • 0..N p:addressNote
  • 0..1 address
  • 0..1 extended-address
  • 0..1 post-office-box
  • 0..1 locality
  • 0..1 region
  • 0..1 postal-code
  • 0..1 country-name

Name

  • 0..1 honorific-prefix
  • 0..1 given-name
  • 0..N additional-name
  • 0..1 family-name
  • 0..1 honorific-suffix

Organization

  • 0..1 organization-name
  • 0..1 organization-unit

Other attributes

  • 0..1 logo
  • 0..1 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

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

Attributes Not Used

The following attributes are not used:

  • category
  • class
  • email - we use foaf:mbox instead
  • fn
  • agent - we use hasAgent instead
  • geo - we use geo:location instead
  • key
  • mailer - not sure what this is
  • photo - we use foaf:thumbnail instead
  • prodid
  • rev
  • sort-string
  • sound
  • tz - not sure syntax of range/value
  • uid - we use entityId instead
  • 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