idnits 2.17.1 

draft-dawson-vcard-xml-dtd-02.txt:

  Checking boilerplate required by RFC 5378 and the IETF Trust (see
  https://trustee.ietf.org/license-info):
  ----------------------------------------------------------------------------

  ** Looks like you're using RFC 2026 boilerplate.  This must be updated to
     follow RFC 3978/3979, as updated by RFC 4748.


  Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
  ----------------------------------------------------------------------------

  ** Missing expiration date.  The document expiration date should appear on
     the first and last page.

  ** The document seems to lack a 1id_guidelines paragraph about
     Internet-Drafts being working documents. 

  ** The document seems to lack a 1id_guidelines paragraph about 6 months
     document validity -- however, there's a paragraph with a matching
     beginning. Boilerplate error?

  ** The document seems to lack a 1id_guidelines paragraph about the list of
     current Internet-Drafts. 

  ** The document seems to lack a 1id_guidelines paragraph about the list of
     Shadow Directories. 

  == No 'Intended status' indicated for this document; assuming Proposed
     Standard

  == The page length should not exceed 58 lines per page, but there was 17
     longer pages, the longest (page 2) being 62 lines


  Checking nits according to https://www.ietf.org/id-info/checklist :
  ----------------------------------------------------------------------------

  ** The document seems to lack an IANA Considerations section.  (See Section
     2.2 of https://www.ietf.org/id-info/checklist for how to handle the case
     when there are no actions for IANA.)

  ** The abstract seems to contain references ([RFC2119], [VCARD], [XML]),
     which it shouldn't.  Please replace those with straight textual mentions
     of the documents in question.

  ** The document seems to lack a both a reference to RFC 2119 and the
     recommended RFC 2119 boilerplate, even if it appears to use RFC 2119
     keywords. 

     RFC 2119 keyword, line 108: '...es not support namespaces MAY omit the...'
     RFC 2119 keyword, line 331: '...   <!-- value MUST be "DATE" for a dat...'
     RFC 2119 keyword, line 443: '...   <!-- value MUST be "VCARD" for a "v...'
     RFC 2119 keyword, line 844: '...the Internet Standards process MUST be...'


  Miscellaneous warnings:
  ----------------------------------------------------------------------------

  == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not
     match the current year

  -- The document seems to lack a disclaimer for pre-RFC5378 work, but may
     have content which was first submitted before 10 November 2008.  If you
     have contacted all the original authors and they are all willing to grant
     the BCP78 rights to the IETF Trust, then this is fine, and you can ignore
     this comment.  If not, you may need to add the pre-RFC5378 disclaimer. 
     (See the Legal Provisions document at
     https://trustee.ietf.org/license-info for more information.)

  -- The document date (November 15, 1998) is 9287 days in the past.  Is this
     intentional?


  Checking references for intended status: Proposed Standard
  ----------------------------------------------------------------------------

     (See RFCs 3967 and 4897 for information about using normative references
     to lower-maturity documents in RFCs)

  -- Missing reference section? 'XML' on line 787 looks like a reference

  -- Missing reference section? 'VCARD' on line 784 looks like a reference

  -- Missing reference section? 'RFC 2119' on line 776 looks like a reference

  -- Missing reference section? 'RFC 2146' on line 103 looks like a reference

  -- Missing reference section? 'NSPACE' on line 780 looks like a reference

  -- Missing reference section? 'FPI' on line 763 looks like a reference

  -- Missing reference section? 'ISO9070' on line 767 looks like a reference

  -- Missing reference section? 'RFC 2045' on line 772 looks like a reference


     Summary: 9 errors (**), 0 flaws (~~), 3 warnings (==), 10 comments (--).

     Run idnits with the --verbose option for more detailed information about
     the items above.

--------------------------------------------------------------------------------


2	Network Working Group                               Frank Dawson, Lotus
3	Internet Draft                                        Paul Hoffman, IMC
4	<draft-dawson-vcard-xml-dtd-02.txt
5	Expires six months after:                             November 15, 1998

7	                         The vCard v3.0 XML DTD

9	Status of this Memo

11	   This document is an Internet-Draft. Internet-Drafts are working
12	   documents of the Internet Engineering Task Force (IETF), its areas,
13	   and its working groups. Note that other groups may also distribute
14	   working documents as Internet-Drafts.

16	   Internet-Drafts are draft documents valid for a maximum of six
17	   months. Internet-Drafts may be updated, replaced, or made obsolete by
18	   other documents at any time. It is not appropriate to use Internet-
19	   Drafts as reference material or to cite them other than as a "working
20	   draft" or "work in progress".

22	   To view the entire list of current Internet-Drafts, please check the
23	   "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
24	   Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern
25	   Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific
26	   Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast).

28	   Distribution of this document is unlimited.

30	   Copyright (C) The Internet Society 1998. All Rights Reserved.

32	Abstract

34	   This memo defines a [XML] Document Type Definition (DTD) that
35	   corresponds to the vCard, electronic business card format defined by
36	   [VCARD]. This DTD provides equivalent functionality to the standard
37	   format defined by [VCARD]. Documents structured in accordance with
38	   this DTD may also be know as 'XML vCard' documents.

40	   The mailing list for discussion of this memo is 'ietf-vcard-
41	   xml@imc.org'. Send an email to ' ietf-vcard-xml-request@imc.org' with
42	   the message 'SUBSCRIBE' to add your email address to this mailing
43	   list. Send an email to ' ietf-vcard-xml-request@imc.org' with the
44	   message 'UNSUBSCRIBE' to remove your email address from this mailing
45	   list.

47	   The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT',
48	   'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY' and 'OPTIONAL' in this
49	   document are to be interpreted as described in [RFC 2119].

51	Table of Contents

53	1. Introduction........................................................3
54	2. vCard XML Document Type Definition..................................3
55	3. vCard v3.0 Notation................................................11
56	4. Example Usage......................................................11
57	 4.1 Simple vCard ....................................................11
58	 4.2 vCard with non-standard extension ...............................11
59	 4.3 vCard with photo element ........................................12
60	 4.4 vCard with an agent element .....................................13
61	 4.5 Document with multiple vCards ...................................13
62	 4.6 Document utilizing vCard namespace ..............................13
63	 4.7 XML document reference to a non-XML vCard .......................14
64	5. Namespace..........................................................14
65	6. Acknowledgments....................................................15
66	7. Security Considerations............................................15
67	8. Bibliography.......................................................16
68	9. Author's Address...................................................16
69	10. Full Copyright Statement..........................................17
70	1.      Introduction

72	   The Extended Markup Language (XML) as defined in [XML] is gaining
73	   widespread attention as a "web friendly" syntax for encoding and
74	   exchanging documents and data on the Internet. This interest includes
75	   requests for and discussion of possible document type definitions
76	   (DTD) for IETF standards such at the vCard, electronic business card
77	   format defined by [VCARD].

79	   This XML DTD is in no way intended to create a separate definition
80	   for the vCard schema. The sole purpose for this memo is to define an
81	   alternative XML encoding for the format defined by [VCARD].

83	   The vCard DTD does not introduce any capability not expressible in
84	   the format defined by [VCARD]. However, an attempt has been made to
85	   leverage the capabilities of the XML syntax to better articulate the
86	   original intent of the vCard authors. For example, the notation
87	   attribute is used to declare the strong data typing intended for each
88	   of the properties in a vCard. It is the responsibility of the XML
89	   application supporting this DTD to make sure that the content
90	   information is formatted consistently with the notation declared for
91	   each element.

93	   The vCard DTD promotes a number of vCard properties into attributes
94	   on the "vCard" element. This has been done to express these
95	   properties as "global attributes" for the vCard object, as a whole.
96	   For example, the VERSION, REV, PRODID, UID, CLASS properties have
97	   been "mapped" into attributes on the vCard object.

99	   Binary content in the PHOTO, LOGO, SOUND and KEY properties may
100	   either be specified through an external entity reference to the non-
101	   XML image or sound content or may be included in the content after
102	   first encoding the binary information using the BASE64 encoding of
103	   [RFC 2146].

105	   XML namespaces are described in [NSPACE]. A namespace is a collection
106	   of names identified by a URI. This specification includes the
107	   definition for a default namespace for the vCard DTD elements. A
108	   vCard application that does not support namespaces MAY omit the
109	   namespace declaration in the vCard definition.

111	   It is expected that the DTD defined in this memo will not normally be
112	   included with vCards that are distributed. Instead, this DTD will be
113	   externally referenced. This means that such Cards will be well-formed
114	   but not valid, as defined in [XML].

116	2.      vCard XML Document Type Definition

118	   The following DTD conforms to XML version 1.0, as specified by [XML].

120	   <?xml version="1.0" encoding="UTF-8"?>

122	   <!-- ******************************************** -->
123	   <!-- Entity declarations and references -->
124	   <!-- ******************************************** -->

126	   <!ENTITY % attr.lang "
127	        lang CDATA #IMPLIED
128	   ">
129	   <!-- lang value is a valid RFC 1766 language string -->

131	   <!ENTITY % attr.del "
132	        del.type NMTOKENS 'INTL POSTAL PARCEL WORK'
133	   ">
134	   <!-- Valid name tokens are "INTL", "DOM", "POSTAL", "PARCEL"
135	        "WORK", "HOME" -->

137	   <!ENTITY % attr.tel "
138	        tel.type NMTOKENS 'VOICE'
139	   ">
140	   <!-- Valid name tokens are "HOME", "WORK", "MSG", "PREF"
141	        "VOICE", "FAX", "CELL", "VIDEO", "PAGER", "BBS", "MODEM"
142	        "CAR", "ISDN", "PCS" -->

144	   <!ENTITY % attr.email "
145	        email.type NMTOKENS 'INTERNET'
146	   ">
147	   <!-- Valid name tokens are "INTERNET", "X.400", "PREF" -->

149	   <!ENTITY % attr.img "
150	        img.type CDATA #REQUIRED
151	   ">
152	   <!-- img.type value is an IANA registered image type -->

154	   <!ENTITY % attr.aud "
155	        aud.type CDATA #REQUIRED
156	   ">
157	   <!-- aud.type value is an IANA registered audio type -->

159	   <!-- The mandatory properties in any vCard -->
160	   <!ENTITY % prop.man "
161	        (fn, n)
162	   ">

164	   <!-- Identification properties -->
165	   <!ENTITY % prop.id "
166	        (nickname | photo | bday)
167	   ">

169	   <!-- Delivery addressing properties -->
170	   <!ENTITY % prop.del "
171	        (adr | label)
172	   ">

174	   <!-- Telecommunications addressing properties -->
175	   <!ENTITY % prop.tel "
176	        (tel | email | mailer)
177	   ">

179	   <!-- Geographical properties -->
180	   <!ENTITY % prop.geo "
181	        (tz | geo)
182	   ">

184	   <!-- Organizational properties -->
185	   <!ENTITY % prop.org "
186	        (title | role | logo | agent | org)
187	   ">

189	   <!-- Explanatory propeties -->
190	   <!ENTITY % prop.exp "
191	        (categories | note | sort | sound | url)
192	   ">

194	   <!-- Security properties -->
195	   <!ENTITY % prop.sec "
196	        (key)
197	   ">

199	   <!-- The optional properties in a vCard -->
200	   <!ENTITY % prop.opt "
201	        %prop.id; | %prop.del; | %prop.tel; | %prop.geo; |
202	        %prop.org; | %prop.exp; | %prop.sec;
203	   ">

205	   <!-- ******************************************** -->
206	   <!-- vCard value type notation declarations -->
207	   <!-- ******************************************** -->

209	   <!NOTATION URI PUBLIC "-//IETF/vCard version 3.0//NOTATION Value Type
210	   URI//EN">

212	   <!NOTATION TEXT PUBLIC "-//IETF/vCard version 3.0//NOTATION Value
213	   Type Text//EN">

215	   <!NOTATION DATE PUBLIC "-//IETF/vCard version 3.0//NOTATION Value
216	   Type Date//EN">

218	   <!NOTATION TIME PUBLIC "-//IETF/vCard version 3.0//NOTATION Value
219	   Type Time//EN">

221	   <!NOTATION DATE-TIME PUBLIC "-//IETF/vCard version 3.0//NOTATION
222	   Value Type Date-Time//EN">

224	   <!NOTATION INTEGER PUBLIC "-//IETF/vCard version 3.0//NOTATION Value
225	   Type Integer//EN">

227	   <!NOTATION BOOLEAN PUBLIC "-//IETF/vCard version 3.0//NOTATION Value
228	   Type Boolean//EN">
229	   <!NOTATION FLOAT PUBLIC "-//IETF/vCard version 3.0//NOTATION Value
230	   Type Float//EN">

232	   <!NOTATION X-NAME PUBLIC "-//IETF/vCard version 3.0//NOTATION Value
233	   Type X-Name//EN">

235	   <!NOTATION BINARY PUBLIC "-//IETF/vCard version 3.0//NOTATION Value
236	   Type Binary//EN">

238	   <!NOTATION VCARD PUBLIC "-//IETF/vCard version 3.0//NOTATION Value
239	   Type vCard//EN">

241	   <!NOTATION PHONE-NUMBER PUBLIC "-//IETF/vCard version 3.0//NOTATION
242	   Value Type Phone-Number//EN">

244	   <!NOTATION UTC-OFFSET PUBLIC "-//IETF/vCard version 3.0//NOTATION
245	   Value Type UTC-Offset//EN">

247	   <!-- ******************************************** -->
248	   <!-- vCard element and attribute declarations -->
249	   <!-- ******************************************** -->

251	   <!ELEMENT vCardSet (vCard*)>
252	   <!ATTLIST vCardSet name CDATA #IMPLIED>

254	   <!ELEMENT vCard      (%prop.man;, (%prop.opt;)*)>

256	   <!ATTLIST vCard
257	        %attr.lang;
258	        xmlns CDATA #FIXED 'http://www.ietf.org/internet-drafts/draft-
259	   dawson-vcard-xml-dtd-02.txt'
260	        xmlns:vcf CDATA #FIXED 'http://www.ietf.org/internet-
261	   drafts/draft-dawson-vcard-xml-dtd-02.txt'
262	        version CDATA #REQUIRED
263	        rev CDATA #IMPLIED
264	        uid CDATA #IMPLIED
265	        prodid CDATA #IMPLIED
266	        class (PUBLIC | PRIVATE | CONFIDENTIAL) "PUBLIC"
267	        value NOTATION (VCARD) #IMPLIED>
268	   <!-- version - Must be "3.0" if document conforms to this spec -->
269	   <!-- rev - ISO 8601 formatted date or date/time string -->
270	   <!-- uid - UID associated with the object described by the vCard -->
271	   <!-- prodid - ISO 9070 FPI for product that generated vCard -->
272	   <!-- class - Security classification for vCard information -->

274	   <!-- Identification properties -->
275	   <!-- Element and attribute declarations -->
276	   <!ELEMENT fn (#PCDATA)>
277	   <!ATTLIST fn
278	        %attr.lang;
279	        value NOTATION (TEXT) #IMPLIED>

281	   <!ELEMENT n (family*, given*, other*, prefix*, suffix*)>
282	   <!ELEMENT family (#PCDATA)>
283	   <!ATTLIST family
284	        %attr.lang;
285	        value NOTATION (TEXT) #IMPLIED>

287	   <!ELEMENT given (#PCDATA)>
288	   <!ATTLIST given
289	        %attr.lang;
290	        value NOTATION (TEXT) #IMPLIED>

292	   <!ELEMENT other (#PCDATA)>
293	   <!ATTLIST other
294	        %attr.lang;
295	        value NOTATION (TEXT) #IMPLIED>

297	   <!ELEMENT prefix (#PCDATA)>
298	   <!ATTLIST prefix
299	        %attr.lang;
300	        value NOTATION (TEXT) #IMPLIED>

302	   <!ELEMENT suffix (#PCDATA)>
303	   <!ATTLIST suffix
304	        %attr.lang;
305	        value NOTATION (TEXT) #IMPLIED>

307	   <!ELEMENT nickname (#PCDATA)>
308	   <!ATTLIST nickname
309	        %attr.lang;
310	        value NOTATION (TEXT) #IMPLIED>

312	   <!ELEMENT photo (extref | b64bin)>
313	   <!ATTLIST photo
314	        %attr.img;>

316	   <!-- extref holds a reference to an external entity that -->
317	   <!-- has the photo. b64bin holds the inline BASE64 encoded -->
318	   <!-- binary data for the photo as defined in RFC 2045. -->

320	   <!ELEMENT extref EMPTY>
321	   <!ATTLIST extref
322	        uri ENTITY #REQUIRED>

324	   <!ELEMENT b64bin (#PCDATA)>
325	   <!ATTLIST b64bin value NOTATION (BINARY) #IMPLIED>

327	   <!ELEMENT bday (#PCDATA)>
328	   <!ATTLIST bday value NOTATION (DATE | DATE-TIME) #IMPLIED>

330	   <!-- bday holds a ISO 8601 formatted date or date/time string -->
331	   <!-- value MUST be "DATE" for a date string and "DATE-TIME" for -->
332	   <!--   date/time string. -->

334	   <!-- Delivery addressing properties -->
335	   <!-- Element and attribute declarations -->
336	   <!ELEMENT adr (pobox*, extadd*, street*, locality*, region*,
337	                pcode*, country*)>
338	   <!ATTLIST adr
339	        %attr.del; >

341	   <!ELEMENT pobox (#PCDATA)>
342	   <!ATTLIST pobox
343	        %attr.lang;
344	        value NOTATION (TEXT) #IMPLIED>

346	   <!ELEMENT extadd (#PCDATA)>
347	   <!ATTLIST extadd
348	        %attr.lang;
349	        value NOTATION (TEXT) #IMPLIED>

351	   <!ELEMENT street (#PCDATA)>
352	   <!ATTLIST street
353	        %attr.lang;
354	        value NOTATION (TEXT) #IMPLIED>

356	   <!ELEMENT locality (#PCDATA)>
357	   <!ATTLIST locality
358	        %attr.lang;
359	        value NOTATION (TEXT) #IMPLIED>

361	   <!ELEMENT region (#PCDATA)>
362	   <!ATTLIST region
363	        %attr.lang;
364	        value NOTATION (TEXT) #IMPLIED>

366	   <!ELEMENT pcode (#PCDATA)>
367	   <!ATTLIST pcode
368	        %attr.lang;
369	        value NOTATION (TEXT) #IMPLIED>

371	   <!ELEMENT country (#PCDATA)>
372	   <!ATTLIST country
373	        %attr.lang;
374	        value NOTATION (TEXT) #IMPLIED>

376	   <!ELEMENT label (#PCDATA | br)*>
377	   <!ATTLIST label
378	        %attr.del;
379	        %attr.lang;
380	        value NOTATION (TEXT) #IMPLIED>

382	   <!ELEMENT br EMPTY>
383	   <!-- Signifies a new line in the content information -->

385	   <!-- Telecommunications addressing properties -->
386	   <!-- Element and attribute declarations -->

388	   <!ELEMENT tel (#PCDATA)>
389	   <!-- A valid ITU standard telephone numbers string. -->
390	   <!ATTLIST tel
391	        %attr.tel;
392	        value NOTATION (PHONE-NUMBER) #IMPLIED>

394	   <!ELEMENT email (#PCDATA)>
395	   <!ATTLIST email
396	        %attr.email;
397	        value NOTATION (TEXT) #IMPLIED>

399	   <!ELEMENT mailer (#PCDATA)>
400	   <!ATTLIST mailer
401	        %attr.lang;
402	        value NOTATION (TEXT) #IMPLIED>

404	   <!-- Geographical properties -->
405	   <!-- Element and attribute declarations -->

407	   <!ELEMENT tz (#PCDATA)>
408	   <!ATTLIST tz value NOTATION (UTC-OFFSET) #IMPLIED>
409	   <!-- tz holds an ISO 8601 formatted time zone offset. -->

411	   <!ELEMENT geo (lat, lon)>

413	   <!ELEMENT lat (#PCDATA)>
414	   <!ATTLIST lat value NOTATION (FLOAT) #IMPLIED>
415	   <!-- A decimal degree float number to 6 decimal places -->

417	   <!ELEMENT lon (#PCDATA)>
418	   <!ATTLIST lon value NOTATION (FLOAT) #IMPLIED>
419	   <!-- A decimal degree float number to 6 decimal places -->

421	   <!-- Organizational properties -->
422	   <!-- Element and attribute declarations -->

424	   <!ELEMENT title (#PCDATA)>
425	   <!ATTLIST title
426	        %attr.lang;
427	        value NOTATION (TEXT) #IMPLIED>

429	   <!ELEMENT role (#PCDATA)>
430	   <!ATTLIST role
431	        %attr.lang;
432	        value NOTATION (TEXT) #IMPLIED>

434	   <!ELEMENT logo (extref | b64bin)>
435	   <!ATTLIST logo
436	        %attr.img;>

438	   <!-- extref holds a reference to an external entity that -->
439	   <!-- has the logo. b64bin holds the inline BASE64 encoded -->
440	   <!-- binary data for the logo as defined in RFC 2045. -->

442	   <!ELEMENT agent (vCard | extref)>
443	   <!-- value MUST be "VCARD" for a "vCard" content model and -->
444	   <!--   "URI" for a "extref" content model. -->

446	   <!ELEMENT org (orgnam, orgunit*)>

448	   <!ELEMENT orgnam (#PCDATA)>
449	   <!ATTLIST orgnam
450	        %attr.lang;
451	        value NOTATION (TEXT) #IMPLIED>
452	   <!ELEMENT orgunit (#PCDATA)>
453	   <!ATTLIST orgunit
454	        %attr.lang;
455	        value NOTATION (TEXT) #IMPLIED>

457	   <!-- Explanatory properties -->
458	   <!-- Element and attribute declarations -->

460	   <!ELEMENT categories (item)*>

462	   <!ELEMENT item (#PCDATA)>
463	   <!ATTLIST item
464	        %attr.lang;
465	        value NOTATION (TEXT) #IMPLIED>

467	   <!ELEMENT note (#PCDATA | br)*>
468	   <!ATTLIST note
469	        %attr.lang;
470	        value NOTATION (TEXT) #IMPLIED>

472	   <!ELEMENT sort (#PCDATA)>
473	   <!ATTLIST sort
474	        %attr.lang;
475	        value NOTATION (TEXT) #IMPLIED>

477	   <!ELEMENT sound (extref | b64bin)>
478	   <!ATTLIST sound
479	        %attr.aud;>

481	   <!-- extref holds a reference to an external entity that -->
482	   <!-- has the sound. b64bin holds the inline BASE64 encoded -->
483	   <!-- binary data for the sound as defined in RFC 2045. -->

485	   <!ELEMENT url EMPTY>
486	   <!ATTLIST url
487	        uri ENTITY #REQUIRED>
488	   <!-- url holds a RFC 1738 formatted Uniform Resource Locator -->

490	   <!-- Security properties -->
491	   <!-- Element and attribute declarations -->

493	   <!ELEMENT key (extref | b64bin)>

495	   <!-- extref holds a reference to an external entity that -->
496	   <!--   has the key or cert. base64-data has the actual data for -->
497	   <!--   the key or cert, encoded with Base64 as defined in the -->
498	   <!--   MIME spec. -->

500	3.      vCard v3.0 Notation

502	   The formal public identifier (FPI) for the DTD described in this
503	   specification is "-//IETF//DTD vCard v3.0//EN".

505	   A XML document can reference an external non-XML entity containing a
506	   vCard v3.0 object, as specified by [VCARD]. The vCard v3.0 object,
507	   while encoded in the standard, non-XML format can be referenced in an
508	   external entity reference that identifies the [VCARD] format in a
509	   notation declaration. The [VCARD] format is identified by the formal
510	   public identifier "-//IETF//NONSGML vCard version 3.0//EN", as
511	   defined in [FPI].

513	4.      Example Usage

515	4.1     Simple vCard

517	   The following is a simple example of a XML document using this DTD.

519	   <?xml version="1.0" encoding="UTF-8"?>
520	   <!DOCTYPE vCard PUBLIC "-//IETF//DTD vCard v3.0//EN">

522	   <vCard
523	        version="3.0">
524	   <fn>Frank Dawson</fn>
525	   <n><family>Dawson</family> <given>Frank</given></n>
526	   <tel tel.type="WORK MSG PREF">+1-617-693-8728</tel>
527	   <tel tel.type="WORK MSG">+1-919-676-9515</tel>
528	   <adr del.type="POSTAL PARCEL WORK">
529	        <street>6544 Battleford Drive</street>
530	        <locality>Raleigh</locality> <region>NC</region>
531	        <pcode>27613-3502</pcode> <country>US</country></adr>
532	   <label del.type="POSTAL PARCEL WORK">6544 Battleford
533	   Drive<br/>Raleigh,NC 27613-3502<br/>US</label>
534	   <email email.type="INTERNET">Frank_Dawson@Lotus.com</email>
535	   </vCard>

537	4.2     vCard with non-standard extension

539	   The following is an example of vCard that also includes a non-
540	   standard extension.

542	   <?xml version="1.0" encoding="UTF-8"?>
543	   <!DOCTYPE vCard PUBLIC "-//IETF//DTD vCard v3.0//EN"
544	   [
545	   <!ELEMENT vCard      (%prop.man;, (%prop.opt; |
546	   x-lotus-blood-type)+)>
547	   <!ELEMENT x-lotus-blood-type (#PCDATA)>
548	   <!ATTLIST x-lotus-blood-type value NOTATION(X-NAME) #IMPLIED>
549	   ]>

551	   <vCard
552	        version="3.0"
553	        prodid="-//HandGen//NONSGML vGen v1.0//EN">
554	   <fn>Frank Dawson</fn>
555	   <n>  <family>Dawson</family>
556	        <given>Frank</given></n>
557	   <tel tel.type="WORK MSG">+1-617-693-8728</tel>
558	   <x-lotus-blood-type>O+</x-lotus-blood-type>
559	   </vCard>

561	4.3     vCard with photo element

563	   The following is an example of a vCard that also includes an external
564	   reference to a photo. Similar structure would be used to represent a
565	   vCard with an external reference to a logo, sound or public
566	   key/certificate.

568	   <?xml version="1.0" encoding="UTF-8"?>
569	   <!DOCTYPE vCard PUBLIC "-//IETF//DTD vCard v3.0//EN"
570	   [
571	   <!ENTITY photo1 SYSTEM "http://host.com/pub/photos/frd-photo.jpg"
572	   NDATA JPEG>
573	   <!NOTATION JPEG PUBLIC "ISO/IEC 10918:1993//NOTATION Digital
574	   Compression and Coding of Continuous-tone Still Images (JPEG)//EN" >
575	   ]>

577	   <vCard
578	        version="3.0"
579	        prodid="-//HandGen//NONSGML vGen v1.0//EN">
580	   <fn>Frank Dawson</fn>
581	   <n>  <family>Dawson</family>
582	        <given>Frank</given></n>
583	   <tel tel.type="WORK MSG">+1-617-693-8728</tel>
584	   <photo img.type="JPEG"><extref uri="photo1" /></photo>
585	   <email email.type="INTERNET">Frank_Dawson@Lotus.com</email>
586	   </vCard>

588	   The following is an example of a vCard that includes a photo element
589	   as inline binary content.

591	   <?xml version="1.0" encoding="UTF-8"?>
592	   <!DOCTYPE vCard PUBLIC "-//IETF//DTD vCard v3.0//EN">

594	   <vCard version="3.0">
595	   <fn>Frank Dawson</fn>
596	   <n><family>Dawson</family><given>Frank</given></n>
597	   <photo img.type="JPEG"><b64bin>MIICajCCAdOgAwIBAgICBEUwDQ
598	   EEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bmlj
599	   YXRpb25z...and so on...IENvcnBvc==</b64bin></photo>
600	   </vCard>
601	4.4     vCard with an agent element

603	   The following is an example of a vCard that includes an agent
604	   element. The content of the agent element is another vCard.

606	   <?xml version="1.0" encoding="UTF-8"?>
607	   <!DOCTYPE vCard PUBLIC "-//IETF//DTD vCard v3.0//EN">

609	   <vCard
610	        version="3.0"
611	        prodid="-//HandGen//NONSGML vGen v1.0//EN">
612	   <fn>Frank Dawson</fn>
613	   <n>  <family>Dawson</family>
614	        <given>Frank</given></n>
615	   <tel tel.type="WORK MSG">+1.617.693.8728</tel>
616	   <agent><vCard
617	        version="3.0"
618	        prodid="-//HandGen//NONSGML vGen v1.0//EN">
619	        <fn>Kathie Collins</fn>
620	        <n> <family>Collins</family>
621	            <given>Kathie</given></n>
622	        <tel tel.type="WORK MSG">+1.617.693-5660</tel>
623	        <email email.type="INTERNET">Kathie_Collins@Lotus.com</email>
624	        </vCard></agent>
625	   <email email.type="INTERNET">Frank_Dawson@Lotus.com</email>
626	   </vCard>

628	4.5     Document with multiple vCards

630	   The following is an example of a vCard document that includes more
631	   than one vCard.

633	   <?xml version="1.0" encoding="UTF-8"?>
634	   <!DOCTYPE vCard PUBLIC "-//IETF//DTD vCard v3.0//EN">

636	   <vCardSet name="Mailing List">
637	   <vCard version="3.0">
638	   <fn>John Smith</fn>
639	   <n>  <family>Smith</family>
640	        <given>John</given>
641	   <email email.type="INTERNET">jsmith@host.com</email>
642	   </vCard>
643	   <vCard version="3.0">
644	   <fn>Fred Stone</fn>
645	   <n>  <family>Stone</family>
646	        <given>Fred</given>
647	   <email email.type="INTERNET">fstone@host1.com</email>
648	   </vCard>
649	   </vCardSet>

651	4.6     Document utilizing vCard namespace

653	   The following is an example of a XML document that declares the vCard
654	   namespace as it's default namespace.

656	   <?xml version="1.0" encoding="UTF-8"?>

658	   <vCard version="3.0" xmlns="http://www.ietf.org/internet-drafts/
659	   draft-dawson-vcard-xml-dtd-02.txt">
660	   <fn>Frank Dawson</fn>
661	   <n>  <family>Dawson</family> <given>Frank</given>
662	   <email email.type="INTERNET">fdawson@host1.com</email>
663	   </vCard>

665	   The following is an example of a XML document that includes elements
666	   from the vCard namespace.

668	   <?xml version="1.0" encoding="UTF-8"?>

670	   <x   xmlns:vcf="http://www.ietf.org/internet-drafts/
671	   draft-dawson-vcard-xml-dtd-02.txt"
672	        xmlns:pdi="http://pdi.org/schema">
673	   <vcf:fn>John Smith</vcf:fn>
674	   <vcf:tel tel.type="WORK">+1-919-555-1234</vcf:tel>
675	   <pdi:idnum>1234567</pdi:idnum>
676	   <pdi:usage>999.99</pdi:usage>
677	   </x>

679	4.7     XML document reference to a non-XML vCard

681	   The following is an example of a XML document with a proper reference
682	   to a non-XML entity containing a vCard object in the format defined
683	   by [VCARD]. This example shows how existing vCard objects can be
684	   integrated into XML documents using the XML structure defined in this
685	   document.

687	   <?xml version="1.0" encoding="UTF-8"?>
688	   <!DOCTYPE loanappl SYSTEM "http://host.finance.com/loanappl.dtd"
689	   [
690	   <!ENTITY fdawson SYSTEM "http://fdawson.com/myvcard.vcf"
691	   NDATA vCard>

693	   <!NOTATION vCard PUBLIC "-//IETF//NOTATION vCard version 3.0//EN">

695	   ]>

697	   <loan>
698	        <pd vcard=fdawson></pd>
699	        <acct name=CFCU id="http://www.cfu.org">01234-56789</acct>
700	        <amt need="immediate">$1,000,000</amt>
701	   </loan>

703	5.      Namespace

705	   [NSPACE] defines "XML namespaces" to be a collection of names,
706	   identified by a URI, which are used in XML documents as element types
707	   and attribute names. XML namespaces allow multiple markup vocabulary
708	   in a single document. Considering the utility of the vCard properties
709	   in other applications, it is important for the vCard XML DTD to
710	   define a namespace for the vCard element types.

712	   This memo includes the definition of both a qualified name for the
713	   vCard namespace and also a default namespace. The namespace
714	   declaration is specified by attributes on the "vCard" element. The
715	   default namespace is specified with the "xmlns" attribute and the
716	   qualified name for the vCard namespace is specified with the
717	   "xmlns:vcf" attribute.

719	   The default namespace attribute is useful in XML documents that are
720	   based on the vCard document types. The qualified name for the vCard
721	   namespace is useful in XML documents that partially consist of vCard
722	   elements types but also consist of element types from other schemas.

724	   The following is an example of the a vCard namespace declaration
725	   using the qualified namespace:

727	   <?xml version="1.0" encoding="UTF-8"?>
728	   <vcf:vCard version="3.0" xmlns:vcf="http://www.ietf.org/internet-
729	   drafts/
730	   draft-dawson-vcard-xml-dtd-02.txt">

732	   <!-- Remainder of the XML document, each vCard element prefaced -->
733	   <!-- with the "vcf:" prefix... -->

735	   </vcf:vCard>

737	   The following is an example of a vCard namespace declaration using
738	   the default namespace:

740	   <?xml version="1.0" encoding="UTF-8"?>
741	   <x xmlns="http://www.ietf.org/internet-drafts/
742	   draft-dawson-vcard-xml-dtd-02.txt">

744	   <!-- Remainder of the XML document, each vCard element prefaced -->
745	   <!-- with the "vcf:" prefix... -->

747	   </x>

749	6.      Acknowledgments

751	   The following have participated in the drafting and discussion of
752	   this memo:

754	   Scott Boag, Dean Burton, Charles Goldfarb, Alex Hoppman, Sean
755	   McGrath, Noah Mendelsohn, Thomas Rowe

757	7.      Security Considerations

759	   Security issues are not currently discussed in this memo.

761	8.      Bibliography

763	   [FPI] F. Dawson and P. Hoffman, "vCard v3.0 Formal Public
764	   Identifier", Internet Draft, http://www.internic.net/internet-
765	   drafts/draft-dawson-vcard-fpi-00.txt, July 1998.

767	   [ISO9070] "Information Technology_SGML Support Facilities_
768	   Registration Procedures for Public Text Owner Identifiers", ISO/IEC
769	   9070, Second Edition, International Organization for Standardization,
770	   April, 1991.

772	   [RFC 2045] N. Freed, N. Borenstein, "Multipurpose Internet Mail
773	   Extensions (MIME) - Part One: Format of Internet Message Bodies", RFC
774	   2045, November 1996.

776	   [RFC 2119] S. Bradner, "Key words for use in RFCs to Indicate
777	   Requirement Levels", RFC 2119, ftp://ftp.isi.edu/in-notes/
778	   rfc2119.txt, March 1997.

780	   [NSPACE] T. Bray, D. Hollander, A. Layman, "Namespaces in XML", WD-
781	   xml-names-19980916, http://www.w3.org/TR/1998/WD-xml-names-19980916,
782	   Septebmer 1998.

784	   [VCARD] F. Dawson and T. Howes, "vCard MIME Directory Profile", RFC
785	   2426, ftp://ftp.isi.edu/in-notes/rfc2426.txt, September 1998.

787	   [XML] "Extensible Markup Language (XML)", Worldwid Web Consortium,
788	   http://www.w3.org/TR/PR-xml-971208, December 1997.

790	9.      Author's Address

792	   The following address information is provided in a vCard XML DTD
793	   electronic business card, format.

795	   <vCard
796	        version="3.0"
797	        prodid="-//HandGen//NONSGML vGen v1.0//EN">
798	   <fn>Frank Dawson</fn>
799	   <n>  <family>Dawson</family>
800	        <given>Frank</given></n>
801	   <org><orgname>Lotus Development Corporation</orgname>
802	   <adr adr.type="WORK POSTAL PARCEL">
803	        <street>6544 Battleford Drive</street>
804	        <locality>Raleigh</locality>
805	        <region>NC</region>
806	        <pcode>27613-3502</pcode>
807	        <countryUSA</country></adr>
808	   <tel tel.type="PREF WORK MSG">+1-617-693-8728</tel>
809	   <tel tel.type="WORK MSG">+1-919-676-9515</tel>
810	   <email email.type="PREF INTERNET">Frank_Dawson@Lotus.com</email>
811	   <email email.type="INTERNET">fdawson@earthlink.net</email>
812	   </vCard>
813	   <vCard
814	        version="3.0"
815	        prodid="-//HandGen//NONSGML vGen v1.0//EN">
816	   <fn>Paul Hoffman</fn>
817	   <n>  <family>Hoffman</family>
818	        <given>Paul</given>
819	   <org><orgname>Internet Mail Consortium<orgname></org>
820	   <adr adr.type="WORK POSTAL PARCEL">
821	        <street>127 Segre Place</street>
822	        <locality>Santa Cruz</locality>
823	        <region>CA</region>
824	        <pcode>95060</pcode>
825	        <country>US</country></adr>
826	   <tel tel.type="WORK MSG">+1-408-426-9827</tel>
827	   <email email.type="INTERNET">phoffman@imc.org</email>
828	   </vCard>

830	10.     Full Copyright Statement

832	   "Copyright (C) The Internet Society (1998).All Rights Reserved.

834	   This document and translations of it may be copied and furnished to
835	   others, and derivative works that comment on or otherwise explain it
836	   or assist in its implmentation may be prepared, copied, published and
837	   distributed, in whole or in part, without restriction of any kind,
838	   provided that the above copyright notice and this paragraph are
839	   included on all such copies and derivative works.However, this
840	   document itself may not be modified in any way, such as by removing
841	   the copyright notice or references to the Internet Society or other
842	   Internet organizations, except as needed for the purpose of
843	   developing Internet standards in which case the procedures for
844	   copyrights defined in the Internet Standards process MUST be
845	   followed, or as required to translate it into languages other than
846	   English.

848	   The limited permissions granted above are perpetual and will not be
849	   revoked by the Internet Society or its successors or assigns.

851	   This document and the information contained herein is provided on an
852	   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
853	   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
854	   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
855	   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
856	   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.