Copyright © 2014 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. W3C liability, trademark and document use rules apply.
The document describes a mapping of the vCard specification (RFC6350) to RDF/OWL. The goal is to promote the use of vCard for the description of people and organisations utilising semantic web techniques and allowing compatibility with traditional vCard implementations.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
This document was published by the Semantic Web Interest Group as an Interest Group Note. If you wish to make comments regarding this document, please send them to semantic-web@w3.org (subscribe, archives).
This document updates the W3C Member Submission on vCard RDF [VCARD-MEMBER] to align with the new semantics of IETF RFC6350 [RFC6350] as developed by the IETF vCard Working Group. Note that RFC6350 obsoletes the previous RFC2426 [RF2426] that the W3 Member Submission was based on.
Publication as an Interest Group Note does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
The disclosure obligations of the Participants of this group are described in the charter.
vCard is a specification developed by the IETF for the description of people and organisations. Recently, vCard has been significantly updated to Version 4 as documented in [RFC6350]. Typically, vCard objects are encoded in its own defined text-based syntax or XML renderings.
The objective of this document is to provide an equivalent representation of vCard utilizing the Semantic Web representations of RDF/OWL. The goal is to allow compatible representations between RFC6350 and this vCard Ontololgy.
Previous vCard ontologies, such as the W3C Member Submission on Representing vCard Objects in RDF [VCARD-MEMBER] covered vCard version 3.0 as defined in RFC2426 [RFC2426]. RFC2426 has been obsoleted by RFC6350 and it is recommeded that this vCard Ontology be used for any vCard semantic representations. RFC6350 has introduced many additional changes such as new structures and properties (for example, Kind, Gender, Language, Anniversary, Calendaring attributes), additional parameters, and removed features (for example, some Address types, inline vCards, Label). See Appendix A of [RFC6350] for complete details.
The current vCard Ontology (See Section 4) has continued to use the
http://www.w3.org/2006/vcard/ns# namespace URI that was used by the previous W3C Member Submission
on Representing vCard Objects in RDF [VCARD-MEMBER].
This will support backwards compatibility. Please note some of the
equivalent/deprecated terms from the previous ontology in Section 2.12.
In addition, this namespace URI will also serve the JSON-LD context.
The vCard specifications have a long history and were first proposed in 1995 and then standardized by the IETF in 1998. Since then, new vocabularies, such as the FOAF Vocabulary Specification (2005), and the The Organisation Ontology (2013) have appeared. The vCard Ontology has also focused on describing people and organisations, including location information and groups of such entities. The FOAF ontology focuses more on the relationships between people, agents, things and social web entities, and the ORG ontology focuses on organizational structures, roles, and activities. There are some overlaps between the three ontologies, but they can provide useful vocabularies individually, and also can provided enhanced information when used collaboratively.
In order to create the OWL ontology mapping from RFC6350, some changes and enhancements are required to reflect and support RDF/OWL features, linked data principles, and support ontology reuse. No semantics are changed in the mapping from RFC6350 to the vCard Ontology. All the data types defined in RFC6350 are fully supported as XML Schema dataypes.
The model informing the mapping from RFC6350 to OWL has been to
create OWL object properties for all things that would typically be
resources (e.g. identified with a URI) and OWL data properties for all
things
that would typically be literals (e.g. strings and dates). The model
includes naming all the object properties with a "hasX" name pattern,
and the data properties with just the "x" name pattern. However, in
some circumstances (see examples in Property Relation Mechanisms) the
data property may use its equivalent object property to support
vCard's property parameters.
All versions of vCard supported additional property parameters that could be used with any of the descriptive properties. For example the sort-string and geography property parameters could be associated with any of the vCard properties to provide further meta-information. To support vCard's property parameters, a new object property (hasValue) and data property (value) have been defined that relates both the property and parameter to the vCard kind.
Consider the following simple example that only includes direct property relationships:
<vcard:Individual rdf:about="http://example.com/me/corky">
<vcard:fn>Corky Crystal</vcard:fn>
<vcard:nickname>Corks</vcard:nickname>
<vcard:hasEmail rdf:resource="mailto:corky@example.com"/>
</vcard:Individual>
If we wanted to add a sort-as property parameter to the nickname (data) property and a type property parameter (to indicate a home email address) to the hasEmail (object) property, then we need to use the hasNickname object property with the value data property and the hasValue object property with the hasEmail object property to capture these n-ary relationships, as shown below:
<vcard:Individual rdf:about="http://example.com/me/corky">
<vcard:fn>Corky Crystal</vcard:fn>
<vcard:hasNickname rdf:parseType="Resource">
<vcard:value>Corks</vcard:value>
<vcard:sort-string>cork</vcard:sort-string>
</vcard:hasNickname>
<vcard:hasEmail rdf:parseType="Resource">
<vcard:hasValue rdf:resource="mailto:corky@example.com"/>
<rdf:type rdf:resource="http://www.w3.org/2006/vcard/ns#Home"/>
</vcard:hasEmail>
</vcard:Individual>
In previous vCard/RDF specifications, the use of rdf:value was recommended to support vCard property parameters. The use of rdf:value is now deprecated in favour of the above mechanism. Additionally, this enables the current vCard Ontology to support OWL-DL.
The following sections outlines the mapping from RFC6350 to the vCard Ontology showing both the n-ary Relation and Direct properties.
These properties can apply to most vCard properties.
| RFC Property | Note | Ontology Property |
|---|---|---|
| LANGUAGE | The human language used in the related property (from RFC5646) | language |
| VALUE | Not required as this is implicit in the ontology datatypes |
|
| PREF | Recommended to use rdf:Seq to support ordered preferences
|
|
| ALTID | Recommended to use rdf:Alt to support alternative values
|
|
| PID | Recommended to use rdf:ID to support identified properties
|
|
| TYPE | Recommended to use rdf:type to indicate type. See Section 2.11 for list of vCard Type
values.
|
|
| MEDIATYPE | Not required |
|
| CALSCALE | Assume the default Gregorian system for datetimes |
|
| SORT-AS | The string used for sorting the property | sort-string |
| GEO | The geographic location related to the property value (expressed as a geo URI) | hasGeo |
| TZ | The timezone related to the property value | tz |
| RFC Property | Note | Ontology Class | Ontology Property |
|---|---|---|---|
| BEGIN | Not required |
|
|
| END | Not required |
|
|
| SOURCE | The orginal source of the vCard information |
| hasSource |
| KIND | vCard defines "Kinds" to represent the types of objects to be represented by vCard: | Kind |
|
|
| Individual - To represent people | Individual |
|
|
| Organization - To represent organisations | Organization |
|
|
| Group - To represent groups of vCard objects | Group |
|
|
| Location - To represent location objects | Location |
|
| XML | Not required |
|
|
| RFC Property | Note | Ontology Property | N-Ary Property |
|---|---|---|---|
| FN | The full name of the object (as a single string). This is the only mandatory property. | fn | hasFN |
| N | The name of the object represented in structured parts | hasName (range of class Name) given-name family-name additional-name honorific-prefix honorific-suffix | hasGivenName hasFamilyName hasAdditionalName hasHonorificPrefix hasHonorifixSuffix |
| NICKNAME | A nickname for the object | nickname | hasNickname |
| PHOTO |
| hasPhoto | |
| BDAY | Birth date of the object. Should only apply to Individual. |
bday | |
| ANNIVERSARY | Should only apply to Individual | anniversary | |
| GENDER | Should only apply to Individual. See Gender Codes in Section 2.11. | hasGender |
| RFC Property | Note | Ontology Property | N-Ary Property |
|---|---|---|---|
| ADR | The address of the object represented in structured parts | hasAddress (range of class Address) street-address locality region country-name postal-code | hasStreetAddress hasLocality hasRegion hasCountryName hasPostalCode |
| RFC Property | Note | Ontology Property | N-Ary Property |
|---|---|---|---|
| TEL | The telephone number as a tel URI. Recommended to use rdf:type to indicate the Telephone Type.See Section 2.11 for list of Telephone Type values. | hasTelephone | |
| The email address as a mailto URI | hasEmail | | |
| IMPP | The IMPP instant messaging contact information | hasInstantMessage | |
| LANG | The language of the object | language | hasLanguage |
| RFC Property | Note | Ontology Property |
|---|---|---|
| TZ | The timezone of the object | tz
|
| GEO | The geographical coordinates of the object (geo URI) | hasGeo |
| RFC Property | Note | Ontology Property | N-Ary Property |
|---|---|---|---|
| TITLE | The title of the object | title | hasTitle |
| ROLE | The role of the object | role | hasRole |
| LOGO | The logo of the object (data URI) | hasLogo | |
| ORG | The organisation related to the object | organization-name | hasOrganizationName |
| ORGUNIT | The organisational unit related to the object | organizational-unit | hasOrganizationalUnit |
| MEMBER | Can only be used for Group Kind objects. Must point to other Individual or Organization objects. | hasMember |
|
| RELATED | Link to related objects. Recommended to use rdf:type to indicate the Related Type.See Section 2.11 for list of Related Type values. | hasRelated | |
| RFC Property | Note | Ontology Property | N-Ary Property |
|---|---|---|---|
| CATEGORIES | The categories of the object | category | hasCategory |
| NOTE | Notes about the object | note | hasNote |
| PRODID | The identifier of the product that created the vCard object | prodid | |
| REV | The revision datetime of the vCard object | rev | |
| SOUND | Audio related to the object (data URI) | hasSound | |
| UID | A unique identifier for the object |
hasUID | |
| CLIENTPIDMAP | Not required |
|
|
| URL | Any URL related to the object | hasURL | |
| VERSION | Not required (namespace will capture this) |
|
|
| RFC Property | Note | Ontology Property |
|---|---|---|
| KEY | The security key of the object | hasKey |
| RFC Property | Note | Ontology Property |
|---|---|---|
| FBURL | Calendar Busy Time of the object | hasCalendarBusy |
| CALADURI | Calendar Request of the object | hasCalendarRequest |
| CALURI | Calendar Link of the object | hasCalendarLink |
| RFC Property | OWL Class |
|---|---|
| vCard Type |
Home Work |
| Gender |
Female Male None Other Unknown |
| Telephone Type |
Cell (mobile) Fax Pager Text (sms) TextPhone Video Voice |
| Related Type |
Acquaintance Agent Child Colleague Contact Coresident Coworker Crush Date Emergency Friend Kin Me Met Muse Neighbor Parent Sibling Spouse Sweetheart |
The following concepts from the previous vCard Ontology have the following mappings in the current vCard Ontology
| Previous Ontology | Equivalent (Current Ontology) |
|---|---|
| VCard (Class) | Kind |
| BBS (Class) | NOTE: This concept has been deprecated |
| Car (Class) | NOTE: This concept has been deprecated |
| Dom (Class) | NOTE: This concept has been deprecated |
| Email (Class) | NOTE: This concept has been deprecated |
| ISDN (Class) | NOTE: This concept has been deprecated |
| Internet (Class) | NOTE: This concept has been deprecated |
| Intl (Class) | NOTE: This concept has been deprecated |
| Label (Class) | NOTE: This concept has been deprecated |
| Modem (Class) | NOTE: This concept has been deprecated |
| Msg (Class) | NOTE: This concept has been deprecated |
| PCS (Class) | NOTE: This concept has been deprecated |
| Parcel (Class) | NOTE: This concept has been deprecated |
| Postal (Class) | NOTE: This concept has been deprecated |
| Pref (Class) | NOTE: This concept has been deprecated |
| Tel (Class) | NOTE: This concept has been deprecated |
| X400 (Class) | NOTE: This concept has been deprecated |
| adr (object property) | hasAddress |
| email (object property) |
hasEmail |
| geo (object property) | hasGeo |
| key (object property) | hasKey |
| logo (object property) | hasLogo |
| n (object property) | hasName |
| org (object property) | organization-name |
| photo (object property) | hasPhoto |
| sound (object property) | hasSound |
| tel (object property) | hasTelephone |
| url (object property) | hasURL |
| agent (object property) |
NOTE: This concept has been deprecated |
| class (data property) |
NOTE: This concept has been deprecated |
| extended-address (data property) | NOTE: This concept has been deprecated |
| label (data property) | NOTE: This concept has been deprecated |
| latitude (data property) | NOTE: This concept has been deprecated |
| longitude (data property) | NOTE: This concept has been deprecated |
| mailer (data property) | NOTE: This concept has been deprecated |
| post-office-box (data property) | NOTE: This concept has been deprecated |
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:vcard="http://www.w3.org/2006/vcard/ns#">
<vcard:Individual rdf:about="http://example.com/me/corky">
<vcard:fn>Corky Crystal</vcard:fn>
<vcard:nickname>Corks</vcard:nickname>
<vcard:hasTelephone rdf:parseType="Resource">
<vcard:hasValue rdf:resource="tel:+61755555555"/>
<rdf:type rdf:resource="http://www.w3.org/2006/vcard/ns#Home"/>
<rdf:type rdf:resource="http://www.w3.org/2006/vcard/ns#Voice"/>
</vcard:hasTelephone>
<vcard:hasEmail rdf:resource="mailto:corky@example.com"/>
<vcard:hasAddress rdf:parseType="Resource">
<vcard:street-address>111 Lake Drive</vcard:street-address>
<vcard:locality>WonderCity</vcard:locality>
<vcard:postal-code>5555</vcard:postal-code>
<vcard:country-name>Australia</vcard:country-name>
<rdf:type rdf:resource="http://www.w3.org/2006/vcard/ns#Home"/>
</vcard:hasAddress>
</vcard:Individual>
</rdf:RDF>
<div vocab="http://www.w3.org/2006/vcard/ns#"
resource="http://example.com/me/corky" typeof="Individual">
<span property="fn">Corky Crystal</span>
<span property="nickname">Corks</span>
<span property="hasTelephone" typeof="Home Voice">
<span property="hasValue" href="tel:+61755555555"/>
</span>
<link property="hasEmail" href="mailto:corky@example.com"/>
<span property="hasAddress" typeof="Home">
<span property="street-address">111 Lake Drive</span>
<span property="locality">WonderCity</span>
<span property="postal-code">5555</span>
<span property="country-name">Australia</span>
</span>
</div>
@prefix vcard: <http://www.w3.org/2006/vcard/ns#> .
@prefix rdfa: <http://www.w3.org/ns/rdfa#> .
<http://example.com/me/corky> a vcard:Individual;
vcard:hasEmail <mailto:corky@example.com>;
vcard:fn "Corky Crystal";
vcard:hasAddress [ a vcard:Home;
vcard:country-name "Australia";
vcard:locality "WonderCity";
vcard:postal-code "5555";
vcard:street-address "111 Lake Drive" ];
vcard:hasTelephone [ a vcard:Home,
vcard:Voice;
vcard:hasValue <tel:+61755555555> ];
vcard:nickname "Corks" .
{
"@context": "http://www.w3.org/2006/vcard/ns",
"@id": "http://example.com/me/corky",
"@type": "Individual",
"fn": "Corky Crystal",
"nickname": "Corks",
"hasEmail": "mailto:corky@example.com",
"hasAddress": {
"@type": "Home",
"country-name": "Australia",
"locality": "WonderCity",
"postal-code": "5555",
"street-address": "111 Lake Drive"
},
"hasTelephone": {
"@type": [ "Home", "Voice" ],
"hasValue": "tel:+61755555555"
}
}
IRI: http://www.w3.org/2006/vcard/ns#Acquaintance
IRI: http://www.w3.org/2006/vcard/ns#Address
IRI: http://www.w3.org/2006/vcard/ns#Agent
IRI: http://www.w3.org/2006/vcard/ns#BBS
This class is deprecated
IRI: http://www.w3.org/2006/vcard/ns#Car
This class is deprecated
IRI: http://www.w3.org/2006/vcard/ns#Cell
Also called mobile telephone
IRI: http://www.w3.org/2006/vcard/ns#Child
IRI: http://www.w3.org/2006/vcard/ns#Colleague
IRI: http://www.w3.org/2006/vcard/ns#Contact
IRI: http://www.w3.org/2006/vcard/ns#Coresident
IRI: http://www.w3.org/2006/vcard/ns#Coworker
IRI: http://www.w3.org/2006/vcard/ns#Crush
IRI: http://www.w3.org/2006/vcard/ns#Date
IRI: http://www.w3.org/2006/vcard/ns#Dom
This class is deprecated
IRI: http://www.w3.org/2006/vcard/ns#Email
To specify the electronic mail address for communication with the object the vCard represents. Use the hasEmail object property.
IRI: http://www.w3.org/2006/vcard/ns#Emergency
IRI: http://www.w3.org/2006/vcard/ns#Fax
IRI: http://www.w3.org/2006/vcard/ns#Female
IRI: http://www.w3.org/2006/vcard/ns#Friend
IRI: http://www.w3.org/2006/vcard/ns#Gender
Used for gender codes. The URI of the gender code must be used as the value for Gender.
IRI: http://www.w3.org/2006/vcard/ns#Group
Object representing a group of persons or entities. A group object will usually contain hasMember properties to specify the members of the group.
IRI: http://www.w3.org/2006/vcard/ns#Home
This implies that the property is related to an individual's personal life
IRI: http://www.w3.org/2006/vcard/ns#Individual
An object representing a single person or entity
IRI: http://www.w3.org/2006/vcard/ns#Internet
This class is deprecated
IRI: http://www.w3.org/2006/vcard/ns#Intl
This class is deprecated
IRI: http://www.w3.org/2006/vcard/ns#ISDN
This class is deprecated
IRI: http://www.w3.org/2006/vcard/ns#Kin
IRI: http://www.w3.org/2006/vcard/ns#Kind
The parent class for all objects
IRI: http://www.w3.org/2006/vcard/ns#Label
This class is deprecated
IRI: http://www.w3.org/2006/vcard/ns#Location
An object representing a named geographical place
IRI: http://www.w3.org/2006/vcard/ns#Male
IRI: http://www.w3.org/2006/vcard/ns#Me
IRI: http://www.w3.org/2006/vcard/ns#Met
IRI: http://www.w3.org/2006/vcard/ns#Modem
This class is deprecated
IRI: http://www.w3.org/2006/vcard/ns#Msg
This class is deprecated
IRI: http://www.w3.org/2006/vcard/ns#Muse
IRI: http://www.w3.org/2006/vcard/ns#Name
To specify the components of the name of the object
IRI: http://www.w3.org/2006/vcard/ns#Neighbor
IRI: http://www.w3.org/2006/vcard/ns#None
IRI: http://www.w3.org/2006/vcard/ns#Organization
An object representing an organization. An organization is a single entity, and might represent a business or government, a department or division within a business or government, a club, an association, or the like.
IRI: http://www.w3.org/2006/vcard/ns#Other
IRI: http://www.w3.org/2006/vcard/ns#Pager
IRI: http://www.w3.org/2006/vcard/ns#Parcel
This class is deprecated
IRI: http://www.w3.org/2006/vcard/ns#Parent
IRI: http://www.w3.org/2006/vcard/ns#PCS
This class is deprecated
IRI: http://www.w3.org/2006/vcard/ns#TelephoneType
Used for telephone type codes. The URI of the telephone type code must be used as the value for the Telephone Type.
IRI: http://www.w3.org/2006/vcard/ns#Postal
This class is deprecated
IRI: http://www.w3.org/2006/vcard/ns#Pref
This class is deprecated
IRI: http://www.w3.org/2006/vcard/ns#RelatedType
Used for relation type codes. The URI of the relation type code must be used as the value for the Relation Type.
IRI: http://www.w3.org/2006/vcard/ns#Sibling
IRI: http://www.w3.org/2006/vcard/ns#Spouse
IRI: http://www.w3.org/2006/vcard/ns#Sweetheart
IRI: http://www.w3.org/2006/vcard/ns#Tel
This class is deprecated. Use the hasTelephone object property.
IRI: http://www.w3.org/2006/vcard/ns#Text
Also called sms telephone
IRI: http://www.w3.org/2006/vcard/ns#TextPhone
IRI: http://www.w3.org/2006/vcard/ns#Type
Used for type codes. The URI of the type code must be used as the value for Type.
IRI: http://www.w3.org/2006/vcard/ns#Unknown
IRI: http://www.w3.org/2006/vcard/ns#VCard
The vCard class is equivalent to the new Kind class, which is the parent for the four explicit types of vCards (Individual, Organization, Location, Group)
IRI: http://www.w3.org/2006/vcard/ns#Video
IRI: http://www.w3.org/2006/vcard/ns#Voice
IRI: http://www.w3.org/2006/vcard/ns#Work
This implies that the property is related to an individual's work place
IRI: http://www.w3.org/2006/vcard/ns#X400
This class is deprecated
IRI: http://www.w3.org/2006/vcard/ns#adr
This object property has been mapped
IRI: http://www.w3.org/2006/vcard/ns#agent
This object property has been deprecated
IRI: http://www.w3.org/2006/vcard/ns#email
This object property has been mapped
IRI: http://www.w3.org/2006/vcard/ns#geo
This object property has been mapped
IRI: http://www.w3.org/2006/vcard/ns#hasAdditionalName
Used to support property parameters for the additional name data property
IRI: http://www.w3.org/2006/vcard/ns#hasAddress
To specify the components of the delivery address for the object
IRI: http://www.w3.org/2006/vcard/ns#hasCalendarBusy
To specify the busy time associated with the object. (Was called FBURL in RFC6350)
IRI: http://www.w3.org/2006/vcard/ns#hasCalendarLink
To specify the calendar associated with the object. (Was called CALURI in RFC6350)
IRI: http://www.w3.org/2006/vcard/ns#hasCalendarRequest
To specify the calendar user address to which a scheduling request be sent for the object. (Was called CALADRURI in RFC6350)
IRI: http://www.w3.org/2006/vcard/ns#hasCategory
Used to support property parameters for the category data property
IRI: http://www.w3.org/2006/vcard/ns#hasCountryName
Used to support property parameters for the country name data property
IRI: http://www.w3.org/2006/vcard/ns#hasEmail
To specify the electronic mail address for communication with the object
IRI: http://www.w3.org/2006/vcard/ns#hasFamilyName
Used to support property parameters for the family name data property
IRI: http://www.w3.org/2006/vcard/ns#hasFN
Used to support property parameters for the formatted name data property
IRI: http://www.w3.org/2006/vcard/ns#hasGender
To specify the sex or gender identity of the object. URIs are recommended to enable interoperable sex and gender codes to be used.
IRI: http://www.w3.org/2006/vcard/ns#hasGeo
To specify information related to the global positioning of the object. May also be used as a property parameter.
IRI: http://www.w3.org/2006/vcard/ns#hasGivenName
Used to support property parameters for the given name data property
IRI: http://www.w3.org/2006/vcard/ns#hasHonorificPrefix
Used to support property parameters for the honorific prefix data property
IRI: http://www.w3.org/2006/vcard/ns#hasHonorificSuffix
Used to support property parameters for the honorific suffix data property
IRI: http://www.w3.org/2006/vcard/ns#hasKey
To specify a public key or authentication certificate associated with the object
IRI: http://www.w3.org/2006/vcard/ns#hasLanguage
Used to support property parameters for the language data property
IRI: http://www.w3.org/2006/vcard/ns#hasLocality
Used to support property parameters for the locality data property
IRI: http://www.w3.org/2006/vcard/ns#hasLogo
To specify a graphic image of a logo associated with the object
IRI: http://www.w3.org/2006/vcard/ns#hasMember
To include a member in the group this object represents. (This property can only be used by Group individuals)
IRI: http://www.w3.org/2006/vcard/ns#hasInstantMessage
To specify the instant messaging and presence protocol communications with the object. (Was called IMPP in RFC6350)
IRI: http://www.w3.org/2006/vcard/ns#hasName
To specify the components of the name of the object
IRI: http://www.w3.org/2006/vcard/ns#hasNickname
Used to support property parameters for the nickname data property
IRI: http://www.w3.org/2006/vcard/ns#hasNote
Used to support property parameters for the note data property
IRI: http://www.w3.org/2006/vcard/ns#hasOrganizationName
Used to support property parameters for the organization name data property
IRI: http://www.w3.org/2006/vcard/ns#hasOrganizationUnit
Used to support property parameters for the organization unit name data property
IRI: http://www.w3.org/2006/vcard/ns#hasPhoto
To specify an image or photograph information that annotates some aspect of the object
IRI: http://www.w3.org/2006/vcard/ns#hasPostalCode
Used to support property parameters for the postal code data property
IRI: http://www.w3.org/2006/vcard/ns#hasRegion
Used to support property parameters for the region data property
IRI: http://www.w3.org/2006/vcard/ns#hasRelated
To specify a relationship between another entity and the entity represented by this object
IRI: http://www.w3.org/2006/vcard/ns#hasRole
Used to support property parameters for the role data property
IRI: http://www.w3.org/2006/vcard/ns#hasSound
To specify a digital sound content information that annotates some aspect of the object
IRI: http://www.w3.org/2006/vcard/ns#hasSource
To identify the source of directory information of the object
IRI: http://www.w3.org/2006/vcard/ns#hasStreetAddress
Used to support property parameters for the street address data property
IRI: http://www.w3.org/2006/vcard/ns#hasTelephone
To specify the telephone number for telephony communication with the object
IRI: http://www.w3.org/2006/vcard/ns#hasTitle
Used to support property parameters for the title data property
IRI: http://www.w3.org/2006/vcard/ns#hasUID
To specify a value that represents a globally unique identifier corresponding to the object
IRI: http://www.w3.org/2006/vcard/ns#hasURL
To specify a uniform resource locator associated with the object
IRI: http://www.w3.org/2006/vcard/ns#hasValue
Used to indicate the resource value of an object property that requires property parameters
IRI: http://www.w3.org/2006/vcard/ns#key
This object property has been mapped
IRI: http://www.w3.org/2006/vcard/ns#logo
This object property has been mapped
IRI: http://www.w3.org/2006/vcard/ns#n
This object property has been mapped
IRI: http://www.w3.org/2006/vcard/ns#org
This object property has been mapped. Use the organization-name data property.
IRI: http://www.w3.org/2006/vcard/ns#photo
This object property has been mapped
IRI: http://www.w3.org/2006/vcard/ns#sound
This object property has been mapped
IRI: http://www.w3.org/2006/vcard/ns#tel
This object property has been mapped
IRI: http://www.w3.org/2006/vcard/ns#url
This object property has been mapped
IRI: http://www.w3.org/2006/vcard/ns#additional-name
The additional name associated with the object
IRI: http://www.w3.org/2006/vcard/ns#anniversary
The date of marriage, or equivalent, of the object
IRI: http://www.w3.org/2006/vcard/ns#bday
To specify the birth date of the object
IRI: http://www.w3.org/2006/vcard/ns#category
The category information about the object, also known as tags
IRI: http://www.w3.org/2006/vcard/ns#class
This data property has been deprecated
IRI: http://www.w3.org/2006/vcard/ns#country-name
The country name associated with the address of the object
IRI: http://www.w3.org/2006/vcard/ns#extended-address
This data property has been deprecated
IRI: http://www.w3.org/2006/vcard/ns#family-name
The family name associated with the object
IRI: http://www.w3.org/2006/vcard/ns#fn
The formatted text corresponding to the name of the object
IRI: http://www.w3.org/2006/vcard/ns#given-name
The given name associated with the object
IRI: http://www.w3.org/2006/vcard/ns#honorific-prefix
The honorific prefix of the name associated with the object
IRI: http://www.w3.org/2006/vcard/ns#honorific-suffix
The honorific suffix of the name associated with the object
IRI: http://www.w3.org/2006/vcard/ns#label
This data property has been deprecated
IRI: http://www.w3.org/2006/vcard/ns#language
To specify the language that may be used for contacting the object. May also be used as a property parameter.
IRI: http://www.w3.org/2006/vcard/ns#latitude
This data property has been deprecated. See hasGeo
IRI: http://www.w3.org/2006/vcard/ns#locality
The locality (e.g. city or town) associated with the address of the object
IRI: http://www.w3.org/2006/vcard/ns#longitude
This data property has been deprecated. See hasGeo
IRI: http://www.w3.org/2006/vcard/ns#mailer
This data property has been deprecated
IRI: http://www.w3.org/2006/vcard/ns#nickname
The nick name associated with the object
IRI: http://www.w3.org/2006/vcard/ns#note
A note associated with the object
IRI: http://www.w3.org/2006/vcard/ns#organization-name
To specify the organizational name associated with the object
IRI: http://www.w3.org/2006/vcard/ns#organization-unit
To specify the organizational unit name associated with the object
IRI: http://www.w3.org/2006/vcard/ns#post-office-box
This data property has been deprecated
IRI: http://www.w3.org/2006/vcard/ns#postal-code
The postal code associated with the address of the object
IRI: http://www.w3.org/2006/vcard/ns#prodid
To specify the identifier for the product that created the object
IRI: http://www.w3.org/2006/vcard/ns#region
The region (e.g. state or province) associated with the address of the object
IRI: http://www.w3.org/2006/vcard/ns#rev
To specify revision information about the object
IRI: http://www.w3.org/2006/vcard/ns#role
To specify the function or part played in a particular situation by the object
IRI: http://www.w3.org/2006/vcard/ns#sort-string
To specify the string to be used for national-language-specific sorting. Used as a property parameter only.
IRI: http://www.w3.org/2006/vcard/ns#street-address
The street address associated with the address of the object
IRI: http://www.w3.org/2006/vcard/ns#tz
To indicate time zone information that is specific to the object. May also be used as a property parameter.
IRI: http://www.w3.org/2006/vcard/ns#title
To specify the position or job of the object
IRI: http://www.w3.org/2006/vcard/ns#value
Used to indicate the literal value of a data property that requires property parameters
Changes since Previous Version (Working Draft 24 Sept 2013)
Thanks to member of the W3C Semantic Web Interest Group and the IETF vCard Working Group for valuable feedback and suggestions; Dan Brickley, Ivan Herman, Michael Angstadt, Adrian Pohl, Dave Reynolds, Brian McBride, Martin Hepp, and Shahim Essaid.
Special thanks to Masahide Kanzaki for feedback on the OWL Ontology and Markus Lanthaler for providing the JSON-LD schema.
The ontology HTML section was obtained by processing the OWL ontology source code through LODE, Live OWL Documentation Environment, developed by Silvio Peroni.
To specify the components of the delivery address for the object