This page is for discussion and development of an OWL Ontology for vCard.
The latest IETF vCard V.4 is documented in RFC6350
The lasted Working Draft is http://www.w3.org/TR/vcard-rdf/
The corresponding RDF/OWL Ontology
Discussion is undertaken on the SWIG email list.
Feedback/Updates (to be addressed in next release)
In the examples of RDFa, Turtle and JSON-LD in section 3, vcard:hasValue has a literal value which should be a URI (as an ObjectProperty)
Update JSON text and link to json file to serve (see http://lists.w3.org/Archives/Public/semantic-web/2013Nov/0002.html).
Add lang (en) to all labels and comments also add a rdfs:definedBy pointing the ontology itself to every concept
Remove the deprecated statements, add comment that they have consistently named equivalents, along with equivalentProperty/equivalentClass axioms (only deprecate Agent, Class, long, lat, mailer)
Feedback/Updates (addressed in Sept 2013 WD)
Include JSON Example 
If we keep the same URI namespace, add equivalent properties/classes (where it makes sense)  Add Appendix with a mapping to old terms (and a rationale) and deprecated terms
Add a "+" before the country code in the telephone examples Change datatype for telephone to union of xsd:string and xsd:anyURI so both can appear (Michael Angstadt, ietf)
Add more description for the purpose of the relational (v direct) properties. See  Remove the Domains from all the direct properties Remove the dp: op: class: prefixes from the Tables Section discussing the relationship between this and existing vocabularies such as foaf and ORG. Fix up all labels...especially "has"
Add descriptive text to the Examples explaining why we used the relations/direct approach  Remove mailto: from the Examples
Fix Location class - geo and/or address properties
Fix OrganizationName label 
Explicit link to RDFS/OWL version (as Turtle and RDF/XML) - independent of namespace issue.