NOTE-vcard-rdf-20010222.1 26.9 KB

Raw Blame History Permalink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML lang="en">
<HEAD>
<TITLE>Representing vCard Objects in RDF/XML</TITLE>
<LINK href="http://www.w3.org/StyleSheets/TR/W3C-NOTE.css" type="text/css" rel="stylesheet">
</HEAD>
<BODY>
<DIV class=head><A href="http://www.w3.org/"><IMG height=48 alt=W3C
src="http://www.w3.org/Icons/w3c_home" width=72></A>
<H1>Representing vCard Objects in RDF/XML</H1>
<H2>W3C Note 22 February 2001</H2>
<DL>
  <DT>This version:
  <DD><A href="http://www.w3.org/TR/2001/NOTE-vcard-rdf-20010222">http://www.w3.org/TR/2001/NOTE-vcard-rdf-20010222</A>

  <DT>Latest version:
  <DD><A href="http://www.w3.org/TR/vcard-rdf">http://www.w3.org/TR/vcard-rdf</A>
  <DT>Author:
  <DD><A href="mailto:renato@iprsystems.com">Renato Iannella</A>, IPR Systems </DD>
</DL>

<P class=copyright>Copyright <A href="http://www.iprsystems.com/">IPR Systems</A> 2001.
Distribution policies are governed by the W3C intellectual property
<a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">terms</a>.
</P>
<HR title="Separator from Header">
</DIV>
<H2><A name=abstract>Abstract</A></H2>
<P>
This note specifies a Resource Description Framework (RDF) encoding of the vCard profile defined by RFC 2426 and to provide equivalent functionality to its standard format.
The motivation is to enable the common and consistent description of persons (using the existing semantics of vCard) and to encode these in RDF/XML.
</P>
<H2><A name=status>Status of this document</A></H2>
<p>This document is a submission to the World Wide Web Consortium from
IPR Systems Pty Ltd (see <a href="/Submission/2001/04/">Submission Request</a>, <a href="/Submission/2001/04/Comment">W3C Staff Comment</a>). For a full list of all acknowledged Submissions, please see <a href="http://www.w3.org/Submission/">Acknowledged Submissions to W3C</a>.</p>

<P>This document is a NOTE made available by the W3C for discussion only.
Publication of this Note by W3C indicates no endorsement by W3C or the W3C
Team, or any W3C Members. W3C has had no editorial control over the
preparation of this Note. This document is a work in progress and may be
updated, replaced, or rendered obsolete by other documents at any
time.</P>

<P>Comments on this document may be sent to the author or to the publicly
archived <a href="http://www.w3.org/RDF/Interest/">RDF Interest Group</a>
distribution list,
<a href="mailto:www-rdf-interest@w3.org">www-rdf-interest@w3.org</a>
[<a href="http://lists.w3.org/Archives/Public/www-rdf-interest/">archive</a>].
</P>

<P>A list of current W3C technical documents can be found at the <A HREF="/TR">Technical Reports</A> page.</P>
<H2><A name=contents>Table of contents</A></H2>
<OL>
  <LI><A href="#1">Introduction</A>
  <LI><A href="#2">RDF vCard Namespace</A>
  <LI><A href="#3">RDF vCard Specification</A>
  <LI><A href="#4">RDF vCard Language</A>
  <LI><A href="#5">RDF vCard Examples</A>
  <LI><A href="#6">vCard in XML</A>
  <LI><A href="#7">Acknowledgements</A>
  <LI><A href="#8">References</A>

</OL>


<h2><A name="1"></A>1. Introduction </h2>
<p>
   This note specifies a Resource Description Framework (RDF) <a href="#RDF">[RDF]</a> expression
   that corresponds to the vCard electronic business card profile defined by
   RFC 2426 <a href="#VCARD">[VCARD]</a>. This specification provides equivalent functionality to
   the standard format defined by <a href="#VCARD">[VCARD]</a> Version 3.0. RDF is an application of the    Extensible Markup Language <a href="#XML">[XML]</a>. Documents structured in accordance with
   this RDF/XML encoding may also be known as 'RDF vCard' documents.
</p>
<p>
   This specification is in no way intended to create a separate definition
   for the vCard schema. The sole purpose for this note is to define an
   alternative RDF/XML encoding for the format defined by <a href="#VCARD">[VCARD]</a>.
</p>
<p>
   The RDF vCard does not introduce any capability not expressible in
   the format defined by <a href="#VCARD">[VCARD]</a>. However, an attempt has been made to
   leverage the capabilities of the XML and RDF syntax to better articulate
   the original intent of the vCard authors. </p>

<h2><A name="2"></A>2. RDF vCard Namespace </h2>
<p>
   RDF uses the XML Namespace <a href="#XMLNS">[XMLNS]</a> to uniquely identify the
   metadata schema and version. For vCard, the following URI <a href="#URI">[URI]</a> is
   defined to be vCard Namespace:
</p>
<dl>
<dd>        http://www.w3.org/2001/vcard-rdf/3.0#  </dd>
</dl>
<p>
   The explicit use of this XML Namespace in RDF means that there is no
   need to support the VCARD Profile and VERSION type.
</p>

<p>
This namespace name (URI) will only be used to refer to this version
of this specification: different URIs will be used for any and all new
versions of the specification except as follows.</p>

<ol>
 <li>This namespace name may be reused in any update of the
  specification which is made for the purpose of clarification or bug
  fixes. These changes will be minor in that they do not (a) change the
  meaning or validity of existing documents written using the
  namespace, or (b) affect the operation of existing software written
  to process such documents.</li>
</ol>

<p>
   Examples used in this note will use "vCard" as the prefix for the vCard XML Namespace
  and "rdf" for the RDF XML Namespace.
</p>

<h2><A name="3"></A>3. RDF vCard Specification</h2>

<h3>3.1 Basic Properties</h3>
<p>
   The RDF vCard equally promotes all vCard types into RDF property
   types. Some of the vCard types, for example BEGIN, END, PROFILE,
   and VERSION, are not required to be expressed as these are implicitly
   provided by RDF.
</p>
<p>
   With RDF, statements are made about a resource. The resource in
   question is identified with a URI. This has similar semantics to    the vCard UID type. Hence, RDF descriptions should use the vCard
   UID as the RDF "about" value when the UID is expressed as a
   machine-resolvable URI.
</p>
<p>
   The majority of the vCard property types have strings as their values
   (objects of statements) and are simply represented by their    property type name and value as specified in the vCard specification
   <a href="#VCARD">[VCARD]</a>. These include:
</p>
<dl>
<dd>     FN </dd>
<dd>     NICKNAME </dd>
<dd>    BDAY </dd>
<dd>     MAILER </dd>
<dd>    GEO </dd>
<dd>     TITLE </dd>
<dd>     ROLE </dd>
<dd>     CATEGORIES </dd>
<dd>     NAME </dd>
<dd>     SOURCE </dd>
<dd>    NOTE </dd>
<dd>     PRODID </dd>
<dd>     REV </dd>
<dd>     SORT-STRING </dd>
 <dd>    CLASS </dd>
</dl>
 <p>
   For example, the following shows sample RDF vCard encodings:
</p>
<pre>
      &lt;vCard:FN> Corky Crystal &lt;/vCard:FN>
      &lt;vCard:BDAY> 1980-01-01 &lt;/vCard:BDAY>
      &lt;vCard:TITLE> Computer Officer Class 3 &lt;/vCard:TITLE>
      &lt;vCard:ROLE> Programmer &lt;/vCard:ROLE>
</pre>
<p>
   There are special cases to be noted for the SOURCE and NAME property
   types. SOURCE maps to the RDF "about" URI and should be used to    indicate the unique identifier for the person object. NAME is a
   human-displayable text about the vCard record itself (not the person).
   If NAME is required, then it should be represented as a Statement about
   Statements (see Section 4 of the RDF Syntax specification <a href="#RDF">[RDF]</a>.)
</p>

<h3>3.2 Grouping and Ordering</h3>
<p>
   To have multiple values of a vCard property type, RDF provides three
   mechanisms; Bags, Sequences, and Alternatives.
</p>
<p>
   An RDF Bag is used when there is more than one value and the order
   is not important. For example:
</p>
<pre>
      &lt;vCard:ROLE>          &lt;rdf:bag>
            &lt;rdf:li> Programmer &lt;/rdf:li>
            &lt;rdf:li> Fire Warden &lt;/rdf:li>
         &lt;/rdf:bag>
     &lt;/vCard:ROLE>
</pre>
<p>
   If order is important, then an RDF Sequence can be used. For example:
</p>
<pre>
      &lt;vCard:TITLE>          &lt;rdf:seq>
            &lt;rdf:li> Principal Research Scientist &lt;/rdf:li>
            &lt;rdf:li> Visiting Professor &lt;/rdf:li>
         &lt;/rdf:seq>
     &lt;/vCard:TITLE>
</pre>
<p>
   An RDF Alternative is used when there is a choice of values available
   for a property, with each value being valid but dependent on some other
   externally defined factor. The first value is the default. For example,
   a vCard resource may have a number of aliases for their email address.
   In essence, these are all different representations of the same email
   addresses. This would be encoded as:
</p>
<pre>
     &lt;vCard:EMAIL>          &lt;rdf:alt>
            &lt;rdf:li> corky@qqqfoo.com &lt;/rdf:li>
            &lt;rdf:li> info@qqqfoo.com &lt;/rdf:li>
            &lt;rdf:li> corky2000cool@hotmail.com &lt;/rdf:li>
         &lt;/rdf:alt>
     &lt;/vCard:EMAIL>
</pre>
<p>
   The vCard specification also allows properties to be arbitrarily grouped. For RDF
   to support this, we need to define a new vCard  property to capture
   this. We call this new vCard property "GROUP".   </p>
<p>
   For example, to group two NICKNAME and NOTE properties:
</p>
<pre>
   &lt;vCard:GROUP>
     &lt;rdf:bag>
       &lt;rdf:li rdf:parseType="Resource">
         &lt;vCard:NICKNAME> Corky Porky &lt;/vCard:NICKNAME>
         &lt;vCard:NOTE> Only used by close friends &lt;/vCard:NOTE>
       &lt;/rdf:li>        &lt;rdf:li rdf:parseType="Resource">
         &lt;vCard:NICKNAME> Princess Corky &lt;/vCard:NICKNAME>
         &lt;vCard:NOTE> Only used by my Mother &lt;/vCard:NOTE>
       &lt;/rdf:li>
     &lt;/rdf:bag>
   &lt;/vCard:GROUP>
</pre>
<p>
  Note: The "rdf:parseType=Resource" indicates that the &lt;rdf:li> content
  should be treated as if it were the content of an &lt;rdf:Description>   element.
</p>
<p>
  Some of these grouping and ordering features are unique to RDF,
  so it is important to realise that the conversion from RDF to   native vCard format may result in some loss of information.
  However, it should not be a critical loss of semantics.
</p>

<h3>3.3 Properties with Attributes</h3>
<p>
  A number of vCard properties include the ability to indicate one or more
  "type parameters" of a value. For example, to indicate that a Telephone
  number is a Fax number, or that a particular email address is the preferred
  value.
</p>
<p>
  To represent this in RDF, we utilise the &lt;rdf:type> property which
  allows us to specify the type of a resource by indicating a URI that
  represents this type. The URI will be:
</p>
<dl>
<dd>             http://www.w3.org/2001/vcard-rdf/3.0#<i>&lt;type> </i></dd>
</dl>
<p>
  where <i>&lt;type></i> will be one of the officially defined vCard type parameters.
</p>
<p>
  Also, the property value must now be given by using the &lt;rdf:value>
  property. For example:
<p>
<pre>
   &lt;vCard:TEL rdf:parseType="Resource">
    &lt;rdf:value> +61 7 555 5555 &lt;/rdf:value>
    &lt;rdf:type rdf:resource="http://www.w3.org/2001/vcard-rdf/3.0#work"/>
    &lt;rdf:type rdf:resource="http://www.w3.org/2001/vcard-rdf/3.0#voice"/>
   &lt;/vCard:TEL>
</pre>
<p>
  Note: The "rdf:parseType=Resource" simply indicates properties within
  the two &lt;vCard:Tel> tags, should be considered as the entire value for
  the &lt;vCard:Tel> property. </p>
<p>
  The vCard properties that have a type parameter are listed here with
  their possible values: </p>
<pre>      vCard Property  Type Parameter Values
   --------------  -----------------------------------------------
    TEL            home, msg, work, pref, voice, fax, cell, video,
                   pager, bbs, modem, car, isdn, pcs
    EMAIL          internet, x400, pref
    ADR            dom, intl, postal, parcel, home, work, pref
    LABEL          dom, intl, postal, parcel, home, work, pref
    TZ             text
</pre>
<p>
  In cases where the type parameter has been defined by an external
  body (ie: not defined by the vCard specification), we must use   a "vCard:TYPE" attribute in the property since we have no control
  over the potential size of this list.
</p>
<p>
  For example, to indicate that the value for the UID property is   of type "United States Social Security Number":
</p>
<pre>      &lt;vCard:UID vCard:TYPE="US-SSN">
       987-65-4320
    &lt;/vCard:UID>
</pre>
<p>
  The vCard  properties that have uncontrolled type parameters are
  listed here:
</p>
<pre>
   vCard Property  Type Parameter Values
   --------------  -----------------------------------------------
    UID            Any IANA registered or non-standard identifier formats
    LOGO           Any IANA registered or non-standard image formats
    PHOTO          Any IANA registered or non-standard image formats
    SOUND          Any IANA registered or non-standard audio formats
</pre>
<p>
  There are two special cases to be noted:
</p>
<ol>
 <li>
   The URL property can only have a valid URI as its value. RDF
       provides a short-hand mechanism to encode this with the
       "rdf:resource"  attribute. For example:
<pre>
   &lt;vCard:URL rdf:resource="http://qqqfoo.com/me.html"/>
</pre>
</li>
<li>
   The LABEL property has a value that is formatted text which
       may include XML statements. To indicate that the value should
       not be interpreted, we use the "rdf:parseType" attribute set
       to "Literal". For example:
<pre>
  &lt;vCard:LABEL rdf:parseType="Resource">
    &lt;rdf:type rdf:resource="http://www.w3.org/2001/vcard-rdf/3.0#postal"/>
    &lt;rdf:value rdf:parseType="Literal">
      Corky Crystal&lt;br/>
      &lt;b>qqqfoo.com Pty Ltd&lt;/b>&lt;br/>
      PO Box 555&lt;br/>
      Coolville, AUSTRALIA
    &lt;/rdf:value>
  &lt;/vCard:LABEL>
</pre>
</li>
</ol>


<H3>3.4 Structured Properties</h3>

<p>
   A number of vCard properties define sub-structure. For example,
   the N property has Family Name, Given Names, and Honorific. It
   is important to preserve and express this structure and it is
   fully-supported in the RDF model. For example:
</p>
<pre>
     &lt;vCard:N rdf:parseType="Resource">
        &lt;vCard:Family> Crystal &lt;/vCard:Family>
        &lt;vCard:Given>  Corky &lt;/vCard:Given>
        &lt;vCard:Other>  Jacky &lt;/vCard:Other>
        &lt;vCard:Prefix> Dr &lt;/vCard:Prefix>
        &lt;vCard:Suffix> III &lt;/vCard:Suffix>
     &lt;/vCard:N>
</pre>
<p>
   The properties that have defined sub-structure are listed here
   with the names of the property types.
</p>
<pre>
    vCard Property  Substructure Name      Property Type Name
    --------------  --------------------   ------------------
     N              Family Name            Family
                    Given Name             Given
                    Additional Names       Other
                    Honorific Prefixes     Prefix
                    Honorific Suffixes     Suffix
        ADR            Post Office Box        Pobox
                    Extended Address       Extadd
                    Street Address         Street
                    Locality               Locality
                    Region                 Region
                    Postal Code            Pcode
                    Country                Country

     ORG            Organisation Name      Orgname
                    Organisation Unit      Orgunit
</pre>
<p>
   There are two special cases to be noted:
</p>
<ol>
<li>
   Even though the LABEL property has the same substructure
       defined by N and ADR, we do not use them in specifying its
       value. This is because the value of LABEL is formatted text
       that is not intended to be interpreted.
</li>
<li>
   There is an implied ordering for Organisational Units
       (higher to lower). This can be supported by using the        &lt;rdf:seq> mechanism. An example is given in Section 5.
</li>
</ol>

<h3>3.5 Binary Values</h3>
<p>
   A number of vCard properties allow for inline binary values (encoded
   in BASE64) or external references via a URI. These include:
</p>
<dl>
   <dd>  PHOTO </dd>
   <dd>  LOGO </dd>
   <dd>  SOUND </dd>
   <dd>  KEY </dd>
</dl>
<p>
   In the case of binary values, we can represent the property with
   a "vCard:ENCODING" attribute indicating the content value ("b").
   For example:
</p>
<pre>
     &lt;vCard:PHOTO vCard:ENCODING="b" vCard:TYPE="image/jpeg">
          MSJD9s99DS(S@W99329(#9....
     &lt;/vCard:PHOTO>
</pre>
<p>
   In the case of an external reference, RDF provides a convenient
   encoding with the "rdf:resource" construct. For example:
 </p>
<pre>
     &lt;vCard:PHOTO vCard:TYPE="image/gif"
                  rdf:resource="http://qqqfoo.com/me.gif"/>
</pre>

<h3>3.6 Agent Property</h3>
<p>
  The Agent property allows the specification or identification of
  another vCard resource. RDF allows for the Agent vCard resource
  to be inline with an existing vCard resource. For example:
</p>
<pre>
      &lt;vCard:FN> Corky Crystal &lt;/vCard:FN>
      &lt;vCard:TITLE> Research Director &lt;/vCard:TITLE>
      &lt;vCard:AGENT rdf:parseType="Resource">
         &lt;vCard:FN>    John Mutton &lt;/vCard:FN>
         &lt;vCard:TITLE> Personal Assistant &lt;/vCard:TITLE>
         &lt;vCard:EMAIL> john@qqqfoo.com &lt;/vCard:EMAIL>
      &lt;/vCard:AGENT>
 </pre>
<p>
  To refer to an external identifiers (via a URI) of the
  Agent resource, RDF supports encoding with the "rdf:resource" construct.
  For example:
</p>
<pre>
      &lt;vCard:FN> Corky Crystal &lt;/vCard:FN>
      &lt;vCard:TITLE> Research Director &lt;/vCard:TITLE>
      &lt;vCard:AGENT rdf:resource="http://qqqfoo.com/staff/mutton/"/>
</pre>

<h2><A name="4"></A>4. RDF vCard Language</h2>

<p>
  To express the human language encoding of vCard property values, XML   provides a convenient "xml:lang" attribute. The values are defined   in RFC 1766. For example:
<p>
<pre>
      &lt;vCard:FN xml:lang="en"> Corky Crystal &lt;/vCard:FN>
      &lt;vCard:TITLE xml:lang="en"> Computer Officer Class 3 &lt;/vCard:TITLE>
      &lt;vCard:ROLE xml:lang="en"> Programmer &lt;/vCard:ROLE>
</pre>
<p>
  In cases where a single vCard property is expressed with multiple
  language values, the RDF Alternative construct should be used.
  For example:
</p>
<pre>
     &lt;vCard:ROLE>          &lt;rdf:alt>
            &lt;rdf:li xml:lang="en"> Programmer &lt;/rdf:li>
            &lt;rdf:li xml:lang="fr"> Programmeur &lt;/rdf:li>
            &lt;rdf:li xml:lang="it"> Programmatore &lt;/rdf:li>
         &lt;/rdf:alt>
     &lt;/vCard:ROLE>
</pre>

<h2><A name="5"></A>5. RDF vCard Examples</H2>
<p>
   It is important to note that since XML is case-sensitive, the
   property and attribute names used in this specification and the
   below examples, should be taken literally. </p>
<p>
   The following is a complete example of an RDF encoded vCard:
</p>


<pre>
  &lt;?xml version="1.0"?>
  &lt;rdf:RDF xmlns:rdf = "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
           xmlns:vCard = "http://www.w3.org/2001/vcard-rdf/3.0#">

    &lt;rdf:Description rdf:about = "http://qqqfoo.com/staff/corky" >
      &lt;vCard:FN> Corky Crystal &lt;/vCard:FN>
      &lt;vCard:N rdf:parseType="Resource">
        &lt;vCard:Family> Crystal &lt;/vCard:Family>
        &lt;vCard:Given>  Corky &lt;/vCard:Given>
        &lt;vCard:Other>  Jacky &lt;/vCard:Other>
        &lt;vCard:Prefix> Dr &lt;/vCard:Prefix>
      &lt;/vCard:N>
      &lt;vCard:BDAY> 1980-01-01 &lt;/vCard:BDAY>
      &lt;vCard:TITLE> Computer Officer Class 3 &lt;/vCard:TITLE>
      &lt;vCard:ROLE> Programmer &lt;/vCard:ROLE>
      &lt;vCard:TEL rdf:parseType="Resource">
        &lt;rdf:value> +61 7 555 5555 &lt;/rdf:value>
        &lt;rdf:type rdf:resource="http://www.w3.org/2001/vcard-rdf/3.0#work"/>
        &lt;rdf:type rdf:resource="http://www.w3.org/2001/vcard-rdf/3.0#voice"/>
      &lt;/vCard:TEL>
      &lt;vCard:EMAIL rdf:parseType="Resource">
        &lt;rdf:value> corky@qqqfoo.com &lt;/rdf:value>
        &lt;rdf:type rdf:resource="http://www.w3.org/2001/vcard-rdf/3.0#internet"/>
      &lt;/vCard:EMAIL>
      &lt;vCard:ADR rdf:parseType="Resource">
        &lt;vCard:Street>   111 Lake Drive &lt;/vCard:Street>
        &lt;vCard:Locality> WonderCity &lt;/vCard:Locality>
        &lt;vCard:Pcode>    5555 &lt;/vCard:Pcode>
        &lt;vCard:Country>  Australia &lt;/vCard:Country>
      &lt;/vCard:ADR>
    &lt;/rdf:Description>
  &lt;/rdf:RDF>
</pre>
<p>
   The following is an example of an RDF vCard that includes a photo element
   as inline binary content.
</p>
<pre>
  &lt;?xml version="1.0"?>
  &lt;rdf:RDF xmlns:rdf = "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
           xmlns:vCard = "http://www.w3.org/2001/vcard-rdf/3.0#" >

    &lt;rdf:Description rdf:about = "http://qqqfoo.com/staff/corky">
      &lt;vCard:FN> Corky Crystal &lt;/vCard:FN>
      &lt;vCard:N rdf:parseType="Resource">
        &lt;vCard:Family> Crystal &lt;/vCard:Family>
        &lt;vCard:Given>  Corky &lt;/vCard:Given>
      &lt;/vCard:N>
      &lt;vCard:EMAIL rdf:parseType="Resource">
        &lt;rdf:value> corky@qqqfoo.com &lt;/rdf:value>
        &lt;rdf:type rdf:resource="http://www.w3.org/2001/vcard-rdf/3.0#internet"/>
      &lt;/vCard:EMAIL>
      &lt;vCard:URL rdf:resource="http://qqqfoo.com/staff/corky-home.html"/>
      &lt;vCard:PHOTO vCard:ENCODING="b" vCard:TYPE="image/jpeg">
        MIICajCCAdOgAwIBAgICBEUwDQEEBQAwdzELMAkGA1UEBhMCVVMxLDA
        qBgNVBAoTI05ldHNjYXBlIENvbW11bmljYXRpb25z.....W992WW329
      &lt;/vCard:PHOTO>
    &lt;/rdf:Description>
  &lt;/rdf:RDF>
</pre>
<p>
   This example shows how an RDF vCard objects can be integrated with
   other metadata standards and encoded with RDF. In this example, the
   Dublin Core Metadata Element Set <a href="#DCMES">[DCMES]</a> standard is used.
   (Please refer to [DCMES] for namespace and encoding recommendations.)
</p>
<pre>
  &lt;?xml version="1.0"?>
  &lt;rdf:RDF xmlns:rdf   = "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
           xmlns:DC   = "http://purl.org/dc/elements/1.1/"
           xmlns:vCard = "http://www.w3.org/2001/vcard-rdf/3.0#" >

   &lt;rdf:Description rdf:about = "http://qqqfoo.com/annual-report.html" >
    &lt;DC:title> Annual Report 1999/2000 &lt;/DC:title>
    &lt;DC:creator rdf:parseType="Resource">
      &lt;vCard:FN> Corky Crystal &lt;/vCard:FN>
      &lt;vCard:N rdf:parseType="Resource">
        &lt;vCard:Family> Crystal &lt;/vCard:Family>
        &lt;vCard:Given>  Corky &lt;/vCard:Given>
      &lt;/vCard:N>
      &lt;vCard:EMAIL rdf:parseType="Resource">
        &lt;rdf:value> corky@qqqfoo.com &lt;/rdf:value>
        &lt;rdf:type rdf:resource="http://www.w3.org/2001/vcard-rdf/3.0#internet"/>
      &lt;/vCard:EMAIL>
    &lt;/DC:creator>
    &lt;DC:date> 2000-10-01 &lt;/DC:date>
    &lt;DC:subject> Company Report, Outcomes, Objectives &lt;/DC:subject>
    &lt;DC:publisher> qqqfoo.com Pty Ltd &lt;/DC:publisher>
    &lt;DC:rights> Copyright 2000 &lt;/DC:rights>
   &lt;/rdf:Description>
  &lt;/rdf:RDF>
</pre>
<p>
  The following is an example of an RDF vCard that includes structured
  Organisation information:
</p>
<pre>
  &lt;?xml version="1.0"?>
  &lt;rdf:RDF xmlns:rdf = "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
           xmlns:vCard = "http://www.w3.org/2001/vcard-rdf/3.0#" >

    &lt;rdf:Description rdf:about = "http://qqqfoo.com/staff/corky">
      &lt;vCard:FN> Corky Crystal &lt;/vCard:FN>
      &lt;vCard:N rdf:parseType="Resource">
        &lt;vCard:Family> Crystal &lt;/vCard:Family>
        &lt;vCard:Given>  Corky &lt;/vCard:Given>
      &lt;/vCard:N>
      &lt;vCard:EMAIL rdf:parseType="Resource">
        &lt;rdf:value> corky@qqqfoo.com &lt;/rdf:value>
        &lt;rdf:type rdf:resource="http://www.w3.org/2001/vcard-rdf/3.0#internet"/>
      &lt;/vCard:EMAIL>
      &lt;vCard:ORG rdf:parseType="Resource">
        &lt;vCard:Orgname> qqqfoo.com Pty Ltd &lt;/vCard:Orgname>
        &lt;vCard:Orgunit>
          &lt;rdf:seq>
                   &lt;rdf:li> Commercialisation Division &lt;/rdf:li>
                   &lt;rdf:li> Engineering Office &lt;/rdf:li>
                   &lt;rdf:li> Java Unit &lt;/rdf:li>
          &lt;/rdf:seq>
       &lt;/vCard:Orgunit>
      &lt;/vCard:ORG>
    &lt;/rdf:Description>
  &lt;/rdf:RDF>
</pre>


<h2><A name="6"></A>6. vCard in XML</h2>
<p>
It is also possible to encode vCard in XML without the RDF expressions (although this is
<i>out of scope</i> for this note). This would enable XML expressions to be generated without the
need to support RDF. However, there will be some features then lacking and unable to
be represented in standard XML.
</p>
<p>
For example, the following is a standard XML expression of last example in the previous section:
</P>
<pre>
  &lt;?xml version="1.0"?>
  &lt;myns:myElement xmlns:myns = "http://www.qqqfoo.com/my-namespace#"
           xmlns:vCard = "http://www.w3.org/2001/vcard-rdf/3.0#" >

      &lt;vCard:FN> Corky Crystal &lt;/vCard:FN>
      &lt;vCard:N>
        &lt;vCard:Family> Crystal &lt;/vCard:Family>
        &lt;vCard:Given>  Corky &lt;/vCard:Given>
      &lt;/vCard:N>
      &lt;vCard:EMAIL vcard:TYPE="http://www.w3.org/2001/vcard-rdf/3.0#internet">
           corky@qqqfoo.com       &lt;/vCard:EMAIL>
      &lt;vCard:ORG>
        &lt;vCard:Orgname> qqqfoo.com Pty Ltd &lt;/vCard:Orgname>
        &lt;vCard:Orgunit> Commercialisation Division &lt;/vCard:Orgunit>
        &lt;vCard:Orgunit> Engineering Office &lt;/vCard:Orgunit>
        &lt;vCard:Orgunit> Java Unit &lt;/vCard:Orgunit>
      &lt;/vCard:ORG>
  &lt;/myns:myElement >
</pre>
<p>
Note that all of the RDF grouping mechanisms and attributes can no longer be used. The vCard:TYPE attribute (only one) can be used
for all vCard attributes/types.
</p>


<h2><A name="7"></A>7. Acknowledgments</h2>
<p>
   Thanks to Dave Beckett (Uni Kent), Roland Schwaenzl (Uni Osnabrueck),    Ron Daniel (DATAFUSION), Eric Miller (OCLC), and Hoylen Sue (DSTC) for    their valuable feedback and comments on drafts of this document. </p>
<p>
   Early versions of the work reported in this paper has been funded in part by the
   Cooperative Research Centres Program through the Department of the Prime
   Minister and Cabinet of Australia, whilst the Author was an employee of DSTC.
</p>


<h2><A name="8"></A>8. References</h2>
<dl>
   <dt><A name="DCMES"> </A>[DCMES]</dt>
  <dd>Dublin Core Metadata Element Set, Version 1.1.    <a href="http://purl.org/DC/documents/rec-dces-19990702.htm">&lt;http://purl.org/DC/documents/rec-dces-19990702.htm> </a> </dd>


   <dt><A name="XMLNS"> </A>[XMLNS]</dt>
   <dd>Namespaces in XML, World Wide Web Consortium, January 1999.
   <a href="http://www.w3.org/TR/REC-xml-names">&lt;http://www.w3.org/TR/REC-xml-names > </a> </dd>

   <dt><A name="RDF"> </A>[RDF]</dt>
  <dd>  Resource Description Framework (RDF) Model and Syntax Specification
   World Wide Web Consortium, February 1999.
   <a href="http://www.w3.org/TR/REC-rdf-syntax/"> &lt;http://www.w3.org/TR/REC-rdf-syntax/> </a>  </dd>

   <dt><A name="URI"> </A>[URI]</dt>
   <dd>Uniform Resource Identifiers (URI): Generic Syntax, Berners-Lee,
   Fielding, Masinter, Internet Draft Standard, August 1998.
    <a href="ftp://ftp.isi.edu/in-notes/rfc2396.txt"> &lt;ftp://ftp.isi.edu/in-notes/rfc2396.txt> </a> </dd>

   <dt><A name="VCARD"> </A>[VCARD] </dt>
   <dd>vCard MIME Directory Profile, F. Dawson and T. Howes, Internet
   RFC 2426, September 1998.
    <a href="ftp://ftp.isi.edu/in-notes/rfc2426.txt"> &lt;ftp://ftp.isi.edu/in-notes/rfc2426.txt></a> </dd>

   <dt><A name="XML"> </A>[XML]</dt>
    <dd>Extensible Markup Language (XML) 1.0, World Wide Web Consortium,
   February 1998. <a href="http://www.w3.org/TR/REC-xml"> &lt;http://www.w3.org/TR/REC-xml></a></dd>

</dl>
</body>
</html>