idnits 2.17.1 draft-li-vcarddav-vcard-id-property-extensions-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (December 29, 2010) is 4867 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) == Outdated reference: A later version (-22) exists of draft-ietf-vcarddav-vcardrev-15 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 vcarddav K. Li 3 Internet-Draft B. Leiba 4 Intended status: Standards Track Huawei Technologies 5 Expires: July 2, 2011 December 29, 2010 7 vCard Format Extensions : DDAY, BIRTH, and DEATH 8 draft-li-vcarddav-vcard-id-property-extensions-00 10 Abstract 12 This document defines an extension to the vCard data format for 13 representing and exchanging information about the date of death, the 14 place of birth, and the place of death of the object the vCard 15 represents. 17 Note 19 Discussion and suggestions for improvement are requested, and should 20 be sent to vcarddav@ietf.org. 22 Status of this Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on July 2, 2011. 39 Copyright Notice 41 Copyright (c) 2010 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 2. Terminology Used in This Document . . . . . . . . . . . . . . . 3 58 3. Identification Property Extensions . . . . . . . . . . . . . . 3 59 3.1. Property: DDAY . . . . . . . . . . . . . . . . . . . . . . 3 60 3.2. Property: BIRTH . . . . . . . . . . . . . . . . . . . . . . 4 61 3.3. Property: DEATH . . . . . . . . . . . . . . . . . . . . . . 4 62 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 63 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 64 5.1. Registration of 'DDAY' property . . . . . . . . . . . . . . 5 65 5.2. Registration of 'BIRTH' property . . . . . . . . . . . . . 5 66 5.3. Registration of 'DEATH' property . . . . . . . . . . . . . 6 67 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 68 7. Normative References . . . . . . . . . . . . . . . . . . . . . 7 69 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 71 1. Introduction 73 This specification adds three new properties to vCard 4.0: DDAY to 74 specify the date of death, BIRTH to specify the place of birth, DEATH 75 to specify the place of death, of the object the vCard represents. 77 2. Terminology Used in This Document 79 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 80 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 81 document are to be interpreted as described in [RFC2119]. 83 Syntax specifications shown here use the augmented Backus-Naur Form 84 (ABNF) as described in [RFC5234], and are specified as in the base 85 vcard specification [I-D.ietf-vcarddav-vcardrev]. 87 3. Identification Property Extensions 89 3.1. Property: DDAY 91 Purpose: To specify the date of death of the object the vCard 92 represents. 94 Value type: The default is a single date-and-or-time value. It can 95 also be reset to a single text value. 97 Cardinality: *1 99 ABNF: 100 DDAY-param = DDAY-param-date / DDAY-param-text 101 DDAY-value = date-and-or-time / text 102 ; Value and parameter MUST match. 104 DDAY-param-date = "VALUE=date-and-or-time" 105 DDAY-param-text = "VALUE=text" / language-param 107 DDAY-param =/ altid-param / calscale-param / any-param 108 ; calscale-param can only be present when DDAY-value is 109 ; date-and-or-time and actually contains a date or date-time. 111 Examples: 112 DDAY:19960415 113 DDAY:--0415 114 DDAY;19531015T231000Z 115 DDAY;VALUE=text:circa 1800 117 3.2. Property: BIRTH 119 Purpose: To specify the place of birth of the object the vCard 120 represents. 122 Value type: A single text value (default) or a single URI value. 124 Cardinality: *1 126 ABNF: 127 BIRTH-param = "VALUE=" / ("text" / "uri") 128 BIRTH-value = text / uri 129 ; Value and parameter MUST match. 131 BIRTH-param =/ altid-param / language-param / any-param 133 Examples: 134 BIRTH:Babies'R'Us Hospital 135 BIRTH;VALUE=uri:http://example.com/hospitals/babiesrus.vcf 136 BIRTH;VALUE=uri:geo:46.769307,-71.283079 138 3.3. Property: DEATH 140 Purpose: To specify the place of death of the object the vCard 141 represents. 143 Value type: A single text value (default) or a single URI value. 145 Cardinality: *1 147 ABNF: 148 DEATH-param = "VALUE=" / ("text" / "uri") 149 DEATH-value = text / uri 150 ; Value and parameter MUST match. 152 DEATH-param =/ altid-param / language-param / any-param 154 Examples: 155 DEATH:Aboard the Titanic\, near Newfoundland 156 DEATH;VALUE=uri:http://example.com/ships/titanic.vcf 157 DEATH;VALUE=uri:41.731944,-49.945833 159 4. Security Considerations 161 This presents no security considerations beyond those in section 9 of 162 the base vcard specification [I-D.ietf-vcarddav-vcardrev]. 164 5. IANA Considerations 166 Registrations are requested for the three properties (DDAY, BIRTH, 167 DEATH), according to the instructions in section 10.2.3 of the base 168 vcard specification [I-D.ietf-vcarddav-vcardrev]. 170 5.1. Registration of 'DDAY' property 172 Namespace: 174 Property name: DDAY 176 Purpose: The date of death of the object the vCard represents. 178 Value type: The default is a single date-and-or-time value. It can 179 also be reset to a single text value. 181 Cardinality: *1 183 Property parameters: VALUE, CALSCALE, LANGUAGE 184 CALSCALE can only be present when the value is a 185 date-and-or-time value and actually contains a date or date-time. 186 LANGUAGE can only b present when the value is text. 188 Description: 190 Format definition: 191 DDAY-param = DDAY-param-date / DDAY-param-text 192 DDAY-value = date-and-or-time / text 193 ; Value and parameter MUST match. 195 DDAY-param-date = "VALUE=date-and-or-time" 196 DDAY-param-text = "VALUE=text" / language-param 198 DDAY-param =/ altid-param / calscale-param / any-param 199 ; calscale-param can only be present when DDAY-value is 200 ; date-and-or-time and actually contains a date or date-time. 202 Example(s): 203 DDAY:19960415 204 DDAY:--0415 205 DDAY;19531015T231000Z 206 DDAY;VALUE=text:circa 1800 208 5.2. Registration of 'BIRTH' property 209 Namespace: 211 Property name: BIRTH 213 Purpose: The place of birth of the object the vCard represents. 215 Value type: A single text value (default) or a single URI value. 217 Cardinality: *1 219 Property parameters: VALUE, LANGUAGE 221 Description: 223 Format definition: 224 BIRTH-param = "VALUE=" / ("text" / "uri") 225 BIRTH-value = text / uri 226 ; Value and parameter MUST match. 228 BIRTH-param =/ altid-param / language-param / any-param 230 Example(s): 231 BIRTH:Babies'R'Us Hospital 232 BIRTH;VALUE=uri:http://example.com/hospitals/babiesrus.vcf 233 BIRTH;VALUE=uri:geo:46.769307,-71.283079 235 5.3. Registration of 'DEATH' property 237 Namespace: 239 Property name: DEATH 241 Purpose: The place of death of the object the vCard represents. 243 Value type: A single text value (default) or a single URI value. 245 Cardinality: *1 247 Property parameters: VALUE, LANGUAGE 249 Description: 251 Format definition: 252 DEATH-param = "VALUE=" / ("text" / "uri") 253 DEATH-value = text / uri 254 ; Value and parameter MUST match. 256 DEATH-param =/ altid-param / language-param / any-param 258 Example(s): 259 DEATH:Aboard the Titanic\, near Newfoundland 260 DEATH;VALUE=uri:http://example.com/ships/titanic.vcf 261 DEATH;VALUE=uri:41.731944,-49.945833 263 6. Acknowledgements 265 The author of this draft would like thank the authors of 266 draft-ietf-vcarddav-vcardrev-13, because most of the texts are copied 267 from there. 269 7. Normative References 271 [I-D.ietf-vcarddav-vcardrev] 272 Perreault, S. and P. Resnick, "vCard Format 273 Specification", draft-ietf-vcarddav-vcardrev-15 (work in 274 progress), December 2010. 276 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 277 Requirement Levels", BCP 14, RFC 2119, March 1997. 279 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 280 Specifications: ABNF", STD 68, RFC 5234, January 2008. 282 Authors' Addresses 284 Kepeng Li 285 Huawei Technologies 286 Huawei Base, Bantian, Longgang District 287 Shenzhen, Guangdong 518129 288 P. R. China 290 Phone: +86-755-28974289 291 Email: likepeng@huawei.com 292 Barry Leiba 293 Huawei Technologies 295 Phone: +1 646 827 0648 296 Email: barryleiba@computer.org 297 URI: http://internetmessagingtechnology.org/