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

VCard vocabulary usage

{{#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.117b.png

Classes and Attributes Used

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

persona:Person

The following attributes are used on p:Person objects:

  • 0..1 bday
  • 0..1 title
  • 0..1 logo
  • 0..1 tel
  • 0..1 n
  • 0..1 adr
  • 0..1 org

Address

  • 0..1 address
  • 0..1 extended-address
  • 0..1 post-office-box
  • 0..1 locality
  • 0..1 region
  • 0..1 postal-code

Note:

  • country-name is not used; use p:country instead

Email

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

Attributes Not Used

  • agent - use hasAgent
  • category
  • class
  • fn - use skos:prefLabel
  • geo - use geo:location
  • key
  • mailer - not sure what this is
  • photo - use foaf:thumbnail
  • prodid
  • rev
  • sort-string
  • sound
  • tz - not sure syntax of range/value
  • uid - use entityId
  • url - use foaf:page (and sub-attributes)

Other conventions

Whereas by inference a p:Person node that has a adr or n etc link is a 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 adr, one n, one 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