idnits 2.17.1 draft-ietf-jcardcal-jcard-04.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 seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document date (July 03, 2013) is 3947 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 (-10) exists of draft-ietf-jcardcal-jcal-00 == Outdated reference: A later version (-06) exists of draft-sheffer-running-code-02 -- Obsolete informational reference (is this intentional?): RFC 4627 (Obsoleted by RFC 7158, RFC 7159) Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 JSON data formats for vCard and iCalendar P. Kewisch 3 Internet-Draft Mozilla 4 Intended status: Standards Track July 03, 2013 5 Expires: January 04, 2014 7 jCard: The JSON format for vCard 8 draft-ietf-jcardcal-jcard-04 10 Abstract 12 This specification defines "jCard", a JSON format for vCard data. 14 Status of This Memo 16 This Internet-Draft is submitted in full conformance with the 17 provisions of BCP 78 and BCP 79. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF). Note that other groups may also distribute 21 working documents as Internet-Drafts. The list of current Internet- 22 Drafts is at http://datatracker.ietf.org/drafts/current/. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 This Internet-Draft will expire on January 04, 2014. 31 Copyright Notice 33 Copyright (c) 2013 IETF Trust and the persons identified as the 34 document authors. All rights reserved. 36 This document is subject to BCP 78 and the IETF Trust's Legal 37 Provisions Relating to IETF Documents 38 (http://trustee.ietf.org/license-info) in effect on the date of 39 publication of this document. Please review these documents 40 carefully, as they describe your rights and restrictions with respect 41 to this document. Code Components extracted from this document must 42 include Simplified BSD License text as described in Section 4.e of 43 the Trust Legal Provisions and are provided without warranty as 44 described in the Simplified BSD License. 46 Table of Contents 48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 49 2. Conventions Used in This Document . . . . . . . . . . . . . . 3 50 3. Converting from vCard to jCard . . . . . . . . . . . . . . . 4 51 3.1. Pre-processing . . . . . . . . . . . . . . . . . . . . . 4 52 3.2. Properties (RFC6350 section 6) . . . . . . . . . . . . . 5 53 3.2.1. Special Cases for Properties . . . . . . . . . . . . 6 54 3.2.1.1. The VERSION Property . . . . . . . . . . . . . . 6 55 3.2.1.2. Multi-valued Properties . . . . . . . . . . . . . 6 56 3.2.1.3. Grouping of Properties . . . . . . . . . . . . . 6 57 3.2.1.4. Structured Property Values . . . . . . . . . . . 7 58 3.3. Parameters (RFC6350 Section 5) . . . . . . . . . . . . . 9 59 3.3.1. VALUE parameter . . . . . . . . . . . . . . . . . . . 10 60 3.3.2. Multi-value Parameters . . . . . . . . . . . . . . . 10 61 3.4. Values (RFC6350 Section 4) . . . . . . . . . . . . . . . 10 62 3.4.1. Text (RFC6350 Section 4.1) . . . . . . . . . . . . . 11 63 3.4.2. URI (RFC6350 Section 4.2) . . . . . . . . . . . . . . 11 64 3.4.3. Date (RFC6350 Section 4.3.1) . . . . . . . . . . . . 11 65 3.4.4. Time (RFC6350 Section 4.3.2) . . . . . . . . . . . . 12 66 3.4.5. Date-Time (RFC6350 Section 4.3.3) . . . . . . . . . . 13 67 3.4.6. Date and/or Time (RFC6350 Section 4.3.4) . . . . . . 15 68 3.4.7. Timestamp (RFC6350 Section 4.3.5) . . . . . . . . . . 15 69 3.4.8. Boolean (RFC6350 Section 4.4) . . . . . . . . . . . . 16 70 3.4.9. Integer (RFC6350 Section 4.5) . . . . . . . . . . . . 16 71 3.4.10. Float (RFC6350 Section 4.6) . . . . . . . . . . . . . 16 72 3.4.11. UTC Offset (RFC6350 Section 4.7) . . . . . . . . . . 16 73 3.4.12. Language Tag (RFC6350 Section 4.8) . . . . . . . . . 17 74 3.5. Extensions (RFC6350 Section 6.10) . . . . . . . . . . . . 17 75 4. Converting from jCard into vCard . . . . . . . . . . . . . . 17 76 5. Handling Unrecognized Properties or Parameters . . . . . . . 18 77 5.1. Converting vCard into jCard . . . . . . . . . . . . . . . 19 78 5.2. Converting jCard into vCard . . . . . . . . . . . . . . . 19 79 5.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . 19 80 6. Implementation Status (to be removed prior to publication as 81 an RFC) . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 82 7. Security Considerations . . . . . . . . . . . . . . . . . . . 21 83 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 84 8.1. GROUP vCard Parameter . . . . . . . . . . . . . . . . . . 22 85 8.2. UNKNOWN vCard Value Data Type . . . . . . . . . . . . . . 23 86 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23 87 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 23 88 10.1. Normative References . . . . . . . . . . . . . . . . . . 23 89 10.2. Informative References . . . . . . . . . . . . . . . . . 24 90 Appendix A. ABNF Schema . . . . . . . . . . . . . . . . . . . . 24 91 Appendix B. Examples . . . . . . . . . . . . . . . . . . . . . . 26 92 B.1. Example: vCard of the author of RFC6350 . . . . . . . . . 26 93 B.1.1. vCard Data . . . . . . . . . . . . . . . . . . . . . 26 94 B.1.2. jCard Data . . . . . . . . . . . . . . . . . . . . . 27 95 Appendix C. Change History (to be removed prior to publication 96 as an RFC) . . . . . . . . . . . . . . . . . . . . . 28 98 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 29 100 1. Introduction 102 The vCard data format [RFC6350] provides for the capture and exchange 103 of information normally stored within an address book or directory 104 application. The vCard format has gone through multiple revisions, 105 most recently vCard 4. The purpose of this specification is to 106 define "jCard", a JSON format for vCard data. One main advantage to 107 using a JSON-based format as defined in [RFC4627] over the classic 108 vCard format is easier processing for JavaScript based widgets and 109 libraries, especially in the scope of web-based applications. 111 As certain similarities exist between vCard and the iCalendar data 112 format [RFC5545], there is also an effort to define a JSON-based data 113 format for calendar information called jCal [I-D.ietf-jcardcal-jcal] 114 that parallels the format defined in this specification. 116 The purpose of this specification is to define "jCard", a JSON format 117 for vCard data. One main advantage to using a JSON-based format as 118 defined in [RFC4627] over the classic vCard format is easier 119 processing for JavaScript based widgets and libraries, especially in 120 the scope of web-based applications. 122 The key design considerations are essentially the same as those for 123 [I-D.ietf-jcardcal-jcal] and [RFC6321], that is: 125 Round-tripping (converting a vCard instance to jCard and back) 126 will give the same semantic result as the starting point. For 127 example, all components, properties and property parameters are 128 guaranteed to be preserved. 130 Ordering of elements will not necessarily be preserved. 132 Preserve the semantics of the vCard data. While a simple consumer 133 can easily browse the data in jCard, a full understanding of vCard 134 is still required in order to modify and/or fully comprehend the 135 directory data. 137 Ability to handle many extensions to the underlying vCard 138 specification without requiring an update to this document. 140 2. Conventions Used in This Document 142 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 143 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 144 document are to be interpreted as described in [RFC2119]. 146 The underlying format used for jCard is JSON. Consequently, the 147 terms "object" and "array" as well as the four primitive types are to 148 be interpreted as described in Section 1 of [RFC4627]. 150 Some examples in this document contain "partial" JSON documents used 151 for illustrative purposes. In these examples, three periods "..." 152 are used to indicate a portion of the document that has been removed 153 for compactness. 155 3. Converting from vCard to jCard 157 This section describes how vCard objects are converted to jCard using 158 a simple mapping between the vCard data model and JSON elements. 160 In [RFC6350], vCard objects are comprised of a set of "properties", 161 "parameters" and "values". The top level of a vCard object contains 162 "properties". A "property" has a "value" and a set of zero or more 163 "parameters". Each of these entities have a representation in jCard, 164 defined in the following sections. The representation of a vCard 165 object in JSON will be named "jCard component" throughout this 166 document. 168 3.1. Pre-processing 170 vCard uses a line folding mechanism to limit lines of data to a 171 maximum line length (typically 72 characters) to ensure maximum 172 likelihood of preserving data integrity as it is transported via 173 various means (e.g., email) - see Section 3.2 of [RFC6350]. Prior to 174 converting vCard data into jCard all folded lines MUST be unfolded. 176 vCard data uses an "escape" character sequence for text values and 177 property parameter values. See Section 3.4 of [RFC6350] as well as 178 [RFC6868]. When such text elements are converted into jCard, the 179 vCard escaping MUST be removed first. The only escaping that may be 180 applied is any escaping mandated by JSON. 182 One key difference in the formatting of values used in vCard and 183 jCard is that in jCard the specification uses date/time values 184 aligned with the extended format of [ISO.8601.2004]. The sections of 185 this document describing the various date and time formats contain 186 more information on the use of the complete representation, reduced 187 accuracy or truncated representation. 189 3.2. Properties (RFC6350 section 6) 191 Each individual vCard property is represented in jCard by an array 192 with three fixed elements, followed by one or more additional 193 elements, depending on if the property is a multi-value property as 194 described in Section 3.3 of [RFC6350]. 196 The array consists of the following fixed elements: 198 1. The name of the property as a string, but in lowercase. 200 2. An object containing the parameters as described in Section 3.3. 202 3. The type identifier string of the value, in lowercase. 204 The remaining elements of the array are used for the value of the 205 property. For single-value properties, the array MUST have exactly 206 four elements, for multi-valued properties as described in 207 Section 3.2.1.2 there can be any number of additional elements. 209 The array describing the property can then be inserted into the array 210 designated for properties in the jCard component. 212 Example: 214 ["vcard", 215 [ 216 ["version", {}, "text", "4.0"], 217 ["fn", {}, "text", "John Doe"], 218 ["gender", {}, "text", "M"], 219 ... 220 ] 221 ] 223 The property parameters in the second element of the property array 224 associate a set of parameter names with their respective value. 225 Parameters are further described in Section 3.3. 227 To allow for a cleaner implementation, the parameter object MUST be 228 present even if there are no parameters. In this case, an empty 229 object MUST be used. 231 As described in Section 3.2.1.4, it is important for a parser check 232 the data type of the value even if it is assumed to be a string in 233 most cases. The value could turn out to be a structured value, in 234 which case the data type is an array. 236 3.2.1. Special Cases for Properties 238 This section describes some properties that have special handling 239 when converting to jCard. 241 3.2.1.1. The VERSION Property 243 The vCard format is versioned. [RFC6350] defines the VERSION 244 property to be mandatory, therefore a "version" property MUST also be 245 specified in a jCard component. Similarly, the value of the version 246 property MUST be "4.0". 248 3.2.1.2. Multi-valued Properties 250 Various vCard properties defined in [RFC6350], for example the 251 "CATEGORIES" property, are defined as multi-valued properties. In 252 jCal these properties are added as further members of the array 253 describing the property. 255 Note that additional multi-valued properties may be added in 256 extensions to the iCalendar format. 258 Example: 260 ["vcard", 261 [ 262 ["categories", {}, "text", "computers", "cameras"], 263 ... 264 ] 265 ] 267 3.2.1.3. Grouping of Properties 269 [RFC6350] Section 3.3 defines a grouping construct that is used to 270 group related properties together. To eliminate the need for an 271 extra group syntax in jCard, thus unifying the general syntax with 272 that of jCal, this specification introduces a "group" parameter, that 273 holds the group name. The parameter MUST NOT be used in vCard as per 274 [RFC6350], it is merely registered to reserve the parameter, avoiding 275 collisions. 277 Namespace: 279 Parameter name: GROUP 281 Purpose: To simplify the jCard format. 283 Description: The GROUP parameter is reserved for the exclusive use 284 of the jCard format RFCTODO. It MUST NOT be used in plain vCard 285 [RFC6350], nor in xCard [RFC6351]. 287 Format definition: (Not applicable) 289 Example: As this registration serves as a reservation of the GROUP 290 parameter so that it is not used in vCard, there is no applicable 291 vCard example. For examples of its usage in jCard, see RFCTODO 293 3.2.1.3.1. Group Conversion Rules 295 In jCard, the parameter's value is a single opaque string. 296 Conversion rules are as follows: 298 o From vCard to jCard, the group construct (see [RFC6350], 299 Section 3.3, Page 7) is removed. In its place, the GROUP 300 parameter is added (lowercased, as any other parameter). Its 301 value is a string corresponding to the group name. The name's 302 case MUST be preserved intact. 304 o From jCard to vCard, the reverse procedure is performed. The 305 GROUP parameter MUST NOT appear in the resulting vCard. 307 Example: 309 CONTACT.FN:Mr. John Q. Public\, Esq. 311 is equivalent to: 313 [ "fn", { "group": "CONTACT" }, "text", "Mr. John Q. Public, Esq." ] 315 3.2.1.4. Structured Property Values 317 The vCard specification defines properties with structured values, 318 for example GENDER or ADR. A structured value is defined as a value 319 that contains multiple text components, delimited by the SEMICOLON 320 character. In jCard, the property value is an array containing one 321 element for each text component. 323 vCard Example: 325 ADR:;;123 Main Street;Any Town;CA;91921-1234;U.S.A. 327 jCard Example: 329 ["adr", {}, "text", 330 [ 331 "", "", "123 Main Street", 332 "Any Town", "CA", "91921-1234", "U.S.A." 333 ] 334 ] 336 Some vCard properties, for example ADR, also allow a structured value 337 element that itself has multiple values. In this case, the element 338 of the array describing the structured value is itself an array with 339 one element for each of the component's multiple values. 341 vCard Example: 343 ADR:;;My Street,Left Side,Second Shack;Hometown;PA;18252;U.S.A. 345 jCard Example: 347 ["adr", {}, "text", 348 [ 349 "", "", 350 ["My Street", "Left Side", "Second Shack"], 351 "Hometown", "PA", "18252", "U.S.A." 352 ] 353 ] 355 In both cases, the array element values MUST have the primitive type 356 that matches the jCard type identifier. In [RFC6350], there are only 357 structured text values and thus only JSON strings are used. 358 Extensions may for example define structured number or boolean 359 values, where JSON number or boolean types MUST be used. 361 If a multi-valued text component is changed to hold only one value, 362 the text component SHOULD be represented as a single primitive value, 363 dropping the array completely. Nevertheless, a more simple 364 implementation might choose to retain the array, with a single 365 primitive value as its element. 367 Similarly, structured values that consist of two text components with 368 one being optional (for example, GENDER) can be represented as a 369 single text value. Therefore, parsers of jCard data SHOULD check 370 even known property values for structured information by considering 371 the JSON data type of the value, which can be an array or a primitive 372 value. This is especially important for languages where accessing 373 array members is done by the same construct as accessing characters 374 of a string. 376 Examples: 378 ["gender", {}, "text", ["F", "grrrl"] ], 379 ["gender", {}, "text", "M" ] 381 Per [RFC6350] Section 6.3.1, the component separator MUST be 382 specified even if the component value is missing. Similarly, the 383 jCard array containing the structured data MUST contain all required 384 elements, even if they are empty. 386 vCard Example: 388 ADR;LABEL="123 Maple Ave\nSuite 901\nVancouver BC\nA1B 2C9\nCan 389 ada":;;;;;; 391 jCard Example: 393 ["adr", 394 {"label":"123 Maple Ave\nSuite 901\nVancouver BC\nA1B 2C9\nCanada"}, 395 "text", 396 ["", "", "", "", "", "", ""] 397 ] 399 3.3. Parameters (RFC6350 Section 5) 401 Property parameters are represented as a JSON object where each key- 402 value pair represents the vCard parameter name and its value. The 403 name of the parameter MUST be in lowercase, the original case of the 404 parameter value MUST be preserved. For example, the "LANG" property 405 parameter is represented in jCard by the "lang" key. Any new vCard 406 parameters added in the future will be converted in the same way. 408 Example: 410 ["vcard", 411 [ 412 ["role", { "lang": "tr" }, "text", "roca"], 413 ... 414 ] 415 ] 417 3.3.1. VALUE parameter 419 vCard defines a "VALUE" property parameter (Section 5.2 of 420 [RFC6350]). This property parameter MUST NOT be added to the 421 parameters object. Instead, the value type is always explicitly 422 mentioned in the third element of the array describing the property. 423 Thus, when converting from vCard to jCard, any "VALUE" property 424 parameters are skipped. When converting from jCard into vCard, the 425 appropriate "VALUE" property parameter MUST be included in the vCard 426 property if the value type is not "unknown" or the default value type 427 for that property. See Section 5 for information on handling unknown 428 value types. 430 3.3.2. Multi-value Parameters 432 In [RFC6350], some parameters allow using a COMMA-separated list of 433 values. To ease processing in jCard, the value to such parameters 434 MUST be represented in an array containing the separated values. The 435 array elements MUST be string values. Single-value parameters SHOULD 436 be represented using a single string value, although a more simple 437 implementation might prefer an array with one string element. An 438 example for a such parameter is the vCard "SORT-AS" parameter, more 439 such parameters may be added in extensions. 441 DQUOTE characters used to encapsulate the separated values MUST NOT 442 be added to the jCard parameter value. 444 Example 1: 446 ["vcard", 447 [ 448 ["n", 449 { "sort-as": ["Harten", "Rene"] }, 450 "text", 451 "van der Harten;Rene,J.;Sir;R.D.O.N." 452 ], 453 ["fn", {}, "text", "Rene van der Harten"] 454 ... 455 ] 456 ] 458 3.4. Values (RFC6350 Section 4) 460 The type of a vCard value is explicitly mentioned in the third 461 element of the array describing a jCard property. The actual values 462 of the property can be found in the fourth and following elements of 463 the array. 465 3.4.1. Text (RFC6350 Section 4.1) 467 Description: vCard "TEXT" property values are represented by a 468 property with the type identifier "text". The value elements are 469 JSON strings. For details on structured text values, see 470 Section 3.2.1.4. 472 Example: 474 ["kind", {}, "text", "group"] 476 3.4.2. URI (RFC6350 Section 4.2) 478 Description: vCard "URI" property values are represented by a 479 property with the type identifier "uri". The value elements are 480 JSON strings. 482 Example: 484 ["source", {}, "uri", "ldap://ldap.example.com/cn=babs%20jensen"] 486 3.4.3. Date (RFC6350 Section 4.3.1) 488 Description: vCard "DATE" property values are represented by a 489 property with the type identifier "date". The value elements are 490 JSON strings with the same date value specified by [RFC6350], but 491 represented using the extended format specified in 492 [ISO.8601.2004], Section 4.1.2. If the complete representation is 493 not used, the same date format restrictions regarding reduced 494 accuracy, truncated representation and expanded representation 495 noted in [RFC6350] Section 4.1.2.3 apply. Whenever the extended 496 format is not applicable, the basic format MUST be used. 498 ABNF Schema: 500 date-complete = year "-" month "-" day ;YYYY-MM-DD 502 date-noreduc = date-complete 503 / "--" month "-" day; --MM-DD 504 / "---" day; ---DDD 506 date = date-noreduc 507 / year; YYYY 508 / year "-" month ; YYYY-MM 509 / "--" month; --MM 511 Examples: 513 ["bday", {}, "date", "1985-04-12"], 514 ["bday", {}, "date", "1985-04"], 515 ["bday", {}, "date", "1985"], 516 ["bday", {}, "date", "--04-12"], 517 ["bday", {}, "date", "---12"] 519 This table contains possible conversions between the vCard DATE 520 format its jCard date. This information is just an example and not a 521 formal specification of the syntax. The specification can be found 522 in [ISO.8601.2000] and [ISO.8601.2004]: 524 +-----------+----------+------------+ 525 | | vCard | jCard | 526 +-----------+----------+------------+ 527 | Complete | 19850412 | 1985-04-12 | 528 | | | | 529 | Reduced | 1985-04 | 1985-04 | 530 | | | | 531 | Reduced | 1985 | 1985 | 532 | | | | 533 | Truncated | --0412 | --04-12 | 534 | | | | 535 | Truncated | --04 | --04 | 536 | | | | 537 | Truncated | ---12 | ---12 | 538 +-----------+----------+------------+ 540 3.4.4. Time (RFC6350 Section 4.3.2) 542 Description: vCard "TIME" property values are represented by a 543 property with the type identifier "time". The value elements are 544 JSON strings with the same time value specified by [RFC6350], but 545 represented using the extended format specified in 546 [ISO.8601.2004], Section 4.2. If the complete representation is 547 not used, the same time format restrictions regarding reduced 548 accuracy, decimal fraction and truncated representation noted in 549 [RFC6350] Section 4.3.2 apply. Whenever the extended format is 550 not applicable, the basic format MUST be used. The seconds value 551 of 60 MUST only be used to account for positive "leap" seconds and 552 the midnight hour is always represented by 00, never 24. 553 Fractions of a second are not supported by this format. Contrary 554 to [I-D.ietf-jcardcal-jcal], UTC offsets are permitted within a 555 time value. 557 ABNF Schema: 559 time-notrunc = hour [":" minute [":" second]] [zone] 561 time = time-notrunc 562 / "-" minute ":" second [zone]; -mm:ss 563 / "-" minute [zone]; -mm 564 / "--" second [zone]; --ss 566 Examples: 568 ["x-time-local", {}, "time", "12:30:00"], 569 ["x-time-utc", {}, "time", "12:30:00Z"], 570 ["x-time-offset", {}, "time", "12:30:00-08:00"], 571 ["x-time-reduced", {}, "time", "23"], 572 ["x-time-truncated", {}, "time", "-30"] 574 This table contains possible conversions between the vCard TIME 575 format its jCard time. This information is just an example and not a 576 formal specification of the syntax. The specification can be found 577 in [ISO.8601.2000] and [ISO.8601.2004]: 579 +-----------+--------+----------+ 580 | | vCard | jCard | 581 +-----------+--------+----------+ 582 | Complete | 232050 | 23:20:50 | 583 | | | | 584 | Reduced | 2320 | 23:20 | 585 | | | | 586 | Reduced | 23 | 23 | 587 | | | | 588 | Truncated | -2050 | -20:50 | 589 | | | | 590 | Truncated | -20 | -20 | 591 | | | | 592 | Truncated | --50 | --50 | 593 +-----------+--------+----------+ 595 Also, all combinations may have any zone designator appended, as in 596 the complete representation. 598 3.4.5. Date-Time (RFC6350 Section 4.3.3) 600 Description: vCard "DATE-TIME" property values are represented by a 601 property with the type identifier "date-time". The value elements 602 are JSON strings with the same date value specified by [RFC6350], 603 but represented using the extended format specified in 604 [ISO.8601.2004], Section 4.3. If the complete representation is 605 not used, the same date and time format restrictions as in 606 Section 3.4.4 and Section 3.4.3 apply. Just as in [RFC6350], 607 truncation of the date part is permitted. 609 Example: 611 ["anniversary", {}, "date-time", "2013-02-14T12:30:00"], 612 ["anniversary", {}, "date-time", "2013-01-10T19:00:00Z"], 613 ["anniversary", {}, "date-time", "2013-08-15T09:45:00+01:00"], 614 ["anniversary", {}, "date-time", "---15T09:45:00+01:00"] 616 This table contains possible conversions between the vCard DATE-TIME 617 format its jCard date-time. This information is just an example and 618 not a formal specification of the syntax. The specification can be 619 found in [ISO.8601.2000] and [ISO.8601.2004]: 621 +----------------+----------------------+---------------------------+ 622 | Representation | vCard | jCard | 623 +----------------+----------------------+---------------------------+ 624 | Complete | 19850412T232050 | 1985-04-12T23:20:50 | 625 | | | | 626 | Complete | 19850412T232050Z | 1985-04-12T23:20:50Z | 627 | | | | 628 | Complete | 19850412T232050+0400 | 1985-04-12T23:20:50+04:00 | 629 | | | | 630 | Complete | 19850412T232050+04 | 1985-04-12T23:20:50+04 | 631 | | | | 632 | Reduced | 19850412T2320 | 1985-04-12T23:20 | 633 | | | | 634 | Reduced | 19850412T23 | 1985-04-12T23 | 635 | | | | 636 | Truncated and | --0412T2320 | --04-12T23:20 | 637 | Reduced | | | 638 | | | | 639 | Truncated and | --04T2320 | --04T23:20 | 640 | Reduced | | | 641 | | | | 642 | Truncated and | ---12T2320 | ---12T23:20 | 643 | Reduced | | | 644 | | | | 645 | Truncated and | --0412T2320 | --04-12T23:20 | 646 | Reduced | | | 647 | | | | 648 | Truncated and | --04T23 | --04T23 | 649 | Reduced | | | 650 +----------------+----------------------+---------------------------+ 652 As specified in [ISO.8601.2000], the date component shall not be 653 represented with reduced accuracy and the time component shall not be 654 truncated. Also, all combinations may have any zone designator 655 appended, as in the complete representation. 657 3.4.6. Date and/or Time (RFC6350 Section 4.3.4) 659 Description: vCard "DATE-AND-OR-TIME" property values are 660 represented by a property with the type identifier "date-and-or- 661 time". The value elements are either a date-time (Section 3.4.5), 662 a date (Section 3.4.3) or a time (Section 3.4.4) value. Just as 663 in [RFC6350] Section 4.3.4, a stand-alone time value MUST always 664 be preceded by a "T". 666 Example: 668 ["bday", {}, "date-and-or-time", "2013-02-14T12:30:00"], 669 ["bday", {}, "date-and-or-time", "---22T14:00"] 670 ["bday", {}, "date-and-or-time", "1985"], 671 ["bday", {}, "date-and-or-time", "T12:30"] 673 3.4.7. Timestamp (RFC6350 Section 4.3.5) 675 Description: vCard "TIMESTAMP" property values are represented by a 676 property with the type identifier "timestamp". The value elements 677 are JSON strings with the same timestamp value specified by 678 [RFC6350], but represented using the extended format and complete 679 representation specified in [ISO.8601.2004], Section 4.3.2. 681 Example: 683 ["rev", {}, "timestamp", "2013-02-14T12:30:00"], 684 ["rev", {}, "timestamp", "2013-02-14T12:30:00Z"], 685 ["rev", {}, "timestamp", "2013-02-14T12:30:00-05"], 686 ["rev", {}, "timestamp", "2013-02-14T12:30:00-05:00"] 688 This table contains possible conversions between the vCard TIMESTAMP 689 format its jCard timestamp. This information is just an example and 690 not a formal specification of the syntax. The specification can be 691 found in [ISO.8601.2000] and [ISO.8601.2004]: 693 +----------------+----------------------+---------------------------+ 694 | Representation | vCard | jCard | 695 +----------------+----------------------+---------------------------+ 696 | Complete | 19850412T232050 | 1985-04-12T23:20:50 | 697 | | | | 698 | Complete | 19850412T232050Z | 1985-04-12T23:20:50Z | 699 | | | | 700 | Complete | 19850412T232050+0400 | 1985-04-12T23:20:50+04:00 | 701 | | | | 702 | Complete | 19850412T232050+04 | 1985-04-12T23:20:50+04 | 703 +----------------+----------------------+---------------------------+ 705 3.4.8. Boolean (RFC6350 Section 4.4) 707 Description: vCard "BOOLEAN" property values are represented by a 708 property with the type identifier "boolean". The value element is 709 a JSON boolean value. 711 Example: 713 ["x-non-smoking", {}, "boolean", true] 715 3.4.9. Integer (RFC6350 Section 4.5) 717 Description: vCard "INTEGER" property values are represented by a 718 property with the type identifier "integer". The value elements 719 are JSON primitive number values. 721 Examples: 723 ["x-karma-points", {}, "integer", 42] 725 3.4.10. Float (RFC6350 Section 4.6) 727 Description: vCard "FLOAT" property values are represented by a 728 property with the type identifier "float". The value elements are 729 JSON primitive number values. 731 Example: 733 ["x-grade", {}, "float", 1.3] 735 3.4.11. UTC Offset (RFC6350 Section 4.7) 736 Description: vCard "UTC-OFFSET" property values are represented by a 737 property with the type identifier "utc-offset". The value 738 elements are JSON strings with the same UTC offset value specified 739 by [RFC6350], with the exception that the hour and minute 740 components are separated by a ":" character, for consistency with 741 the [ISO.8601.2004] timezone offset, extended format. 743 Example: 745 // Note: [RFC6350] mentions use of utc-offset 746 // for the TZ property as NOT RECOMMENDED 747 ["tz", {}, "utc-offset", "-05:00"] 749 3.4.12. Language Tag (RFC6350 Section 4.8) 751 Description: vCard "LANGUAGE-TAG" property values are represented by 752 a property with the type identifier "language-tag". The value 753 elements are JSON strings containing a single language-tag, as 754 defined in [RFC5646]. 756 Example: 758 ["lang", {}, "language-tag", "de"] 760 3.5. Extensions (RFC6350 Section 6.10) 762 vCard extension properties and property parameters (those with an 763 "X-" prefix in their name) are handled in the same way as other 764 properties and property parameters: the property is represented by an 765 array, the property parameter represented by an object. The property 766 or parameter name uses the same name as for the vCard extension, but 767 in lowercase. For example, the "X-FOO" property in vCard turns into 768 the "x-foo" jCard property. See Section 5 for how to deal with 769 default values for unrecognized extension properties or property 770 parameters. 772 4. Converting from jCard into vCard 774 When converting property and property parameter values, the names 775 SHOULD be converted to uppercase. Although vCard names are case 776 insensitive, common practice is to keep them all uppercase following 777 the actual definitions in [RFC6350]. 779 Character escaping and line folding MUST be applied to the resulting 780 vCard data as required by [RFC6350] and [RFC6868]. 782 When converting to vCard, the VALUE parameter MUST be added to 783 properties whose default value type is unknown. The VALUE parameter 784 MAY be omitted for properties using the default value type. 786 5. Handling Unrecognized Properties or Parameters 788 In vCard, properties can have one or more value types as specified by 789 their definition, with one of those values being defined as the 790 default. When a property uses its default value type, the "VALUE" 791 property parameter does not need to be specified on the property. 792 For example, "BDAY"'s default value type is "date-and-or-time", so 793 "VALUE=date-and-or-time" need not be set as a property parameter. 794 However, "BDAY" also allows a "text" value to be specified, and if 795 that is used, "VALUE=text" has to be set as a property parameter. 797 When new properties are defined or "X-" properties used, a vCard to 798 jCard converter might not recognize them, and not know what the 799 appropriate default value types are, yet they need to be able to 800 preserve the values. A similar issue arises for unrecognized 801 property parameters. 803 In jCard, a new "unknown" property value type is introduced. Its 804 purpose is to allow preserving unknown property values when round- 805 tripping between jCard and vCard. To avoid collisions, this 806 specification reserves the UNKNOWN property value type in vCard. It 807 MUST NOT be used in any vCard as specified by [RFC6350], nor any 808 extensions to it. 810 Value name: UNKNOWN 812 Purpose: To allow preserving unknown property values during round- 813 tripping between jCard and vCard 815 Format definition: (Not applicable) 817 Description: The UNKNOWN value data type is reserved for the 818 exclusive use of the jCard format RFCTODO. It MUST NOT be used in 819 plain vCard [RFC6350]. 821 Example: As this registration serves as a reservation of the UNKNOWN 822 type so that it is not used in vCard, there is no applicable vCard 823 example. For examples of its usage in jCard, see RFCTODO 825 5.1. Converting vCard into jCard 827 Any property that does not include a "VALUE" property parameter and 828 whose default value type is not known, MUST be converted to a 829 primitive JSON string. The content of that string is the unprocessed 830 value text. Also, value type MUST be set to "unknown". 832 To correctly implement this format, it is critical that if the 833 default type is not known that the type "unknown" is used. If this 834 requirement is ignored and for example "text" is used, additional 835 escaping may occur which breaks round-tripping values. 837 Any unrecognized property parameter MUST be converted to a string 838 value, with its content set to the property parameter value text, 839 treated as if it were a "TEXT" value. 841 5.2. Converting jCard into vCard 843 Since jCard always explicitly specifies the value type, it can always 844 be converted to vCard using the VALUE parameter. 846 If the value type specified in jCard matches the default value type 847 in vCard, the VALUE parameter MAY be omitted. 849 If the value type specified in jCard is set to "unknown", the value 850 MUST be taken over in vCard without processing. In this case, the 851 VALUE parameter MUST NOT be specified. 853 5.3. Examples 855 The following is an example of an unrecognized vCard property (that 856 uses an "URI" value as its default), and the equivalent jCard 857 representation of that property. 859 vCard: 861 X-COMPLAINT-URI:mailto:abuse@example.org 863 jCard: 865 ["x-complaint-uri", {}, "unknown", "mailto:abuse@example.org"] 867 The following is an example of how to cope with jCard data where the 868 parser was unable to identify the type. Note how the "unknown" value 869 type is not added to the vCard data and escaping, aside from standard 870 JSON string escaping, is not processed. 872 jCard: 874 ["x-coffee-data", {}, "unknown", "Stenophylla;Guinea\\,Africa"] 876 vCard: 878 X-COFFEE-DATA:Stenophylla;Guinea\,Africa 880 The following is an example of a jCard property (where the 881 corresponding vCard property uses a "INTEGER" value as its default), 882 and the equivalent vCard representation of that property. It is 883 assumed that the parser has knowledge of the default data type for 884 the "x-karma-points" property. 886 jCard: 888 ["x-karma-points", {}, "integer", 95] 890 vCard: 892 X-KARMA-POINTS:95 894 The following is an example of an unrecognized vCard property 895 parameter (that uses a "FLOAT" value as its default) specified on a 896 recognized vCard property, and the equivalent jCard representation of 897 that property and property parameter. 899 vCard: 901 GENDER;X-PROBABILITY=0.8:M 903 jCard: 905 ["gender", { "x-probability": "0.8" }, "text", "M"] 907 6. Implementation Status (to be removed prior to publication as an RFC) 909 This section describes libraries known to implement this draft as per 910 [I-D.sheffer-running-code]. 912 1. ICAL.js - Philipp Kewisch, James Lal. A JavaScript parser for 913 iCalendar (rfc5545) 914 Source: https://github.com/mozilla-comm/ical.js/ 916 Maturity: alpha (for jCard) 918 Coverage: Currently geared towards jCal, therefore not all 919 formats are supported. Includes an online validator. (as 920 of rev 847c67c501, 2013-02-14) 922 Licensing: MPL, Mozilla Public License 2.0 924 2. Py Calendar - Cyrus Daboo. iCalendar/vCard Library 926 Source: https://svn.calendarserver.org/repository/calendarserver 927 /PyCalendar/branches/json/ 929 Maturity: production 931 Coverage: All aspects of this draft, up to version 01. 933 Licensing: Apache License, Version 2.0 935 3. ez-vcard - Michael Angstadt. A vCard parser library written in 936 Java 938 Source: https://code.google.com/p/ez-vcard/ 940 Maturity: production 942 Coverage All aspects of this draft. 944 Licensing: New BSD License 946 Additionally, interoperability testing of this draft is an ongoing 947 effort under members of calconnect, the Calendaring and Scheduling 948 Consortium. CalDAV Vendors are looking into supporting this draft. 950 7. Security Considerations 952 For security considerations specific to calendar data, see Section 9 953 of [RFC6350]. Since this specification is a mapping from vCard, no 954 new security concerns are introduced related to calendar data. 956 The use of JSON as a format does have security risks. Section 7 of 957 [RFC4627] discusses these risks. 959 8. IANA Considerations 960 This document defines a MIME media type for use with vCard in JSON 961 data. This media type SHOULD be used for the transfer of calendaring 962 data in JSON. 964 Type name: application 966 Subtype name: vcard+json 968 Required parameters: none 970 Optional parameters: version as defined for the text/vcard media 971 type in [RFC6350]. 973 Encoding considerations: Same as encoding considerations of 974 application/json as specified in [RFC4627]. 976 Security considerations: See Section 7. 978 Interoperability considerations: This media type provides an 979 alternative format for vCard data based on JSON. 981 Published specification: This specification. 983 Applications which use this media type: Applications that currently 984 make use of the text/vcard media type can use this as an 985 alternative. Similarly, Applications that use the application/ 986 json media type to transfer directory data can use this to further 987 specify the content. 989 Person & email address to contact for further information: 990 vcarddav@ietf.org 992 Intended usage: COMMON 994 Restrictions on usage: There are no restrictions on where this media 995 type can be used. 997 Author: See the "Author's Address" section of this document. 999 Change controller: IETF 1001 8.1. GROUP vCard Parameter 1003 IANA has added the following entry to the vCard Parameters registry, 1004 defined in Section 10.3.2 of [RFC6350]. 1006 +-----------+-----------+--------------------------+ 1007 | Namespace | Parameter | Reference | 1008 +-----------+-----------+--------------------------+ 1009 | | GROUP | RFCTODO, Section 3.2.1.3 | 1010 +-----------+-----------+--------------------------+ 1012 8.2. UNKNOWN vCard Value Data Type 1014 IANA has added the following entry to the vCard Data Types registry, 1015 defined in Section 10.3.3 of [RFC6350]. 1017 +-----------------+--------------------+ 1018 | Value Data Type | Reference | 1019 +-----------------+--------------------+ 1020 | UNKNOWN | RFCTODO, Section 5 | 1021 +-----------------+--------------------+ 1023 9. Acknowledgments 1025 The author would like to thank the following for their valuable 1026 contributions: Cyrus Daboo, Mike Douglass, William Gill, Erwin Rehme, 1027 and Dave Thewlis. Simon Perreault, Michael Angstadt, Peter Saint- 1028 Andre, Bert Greevenbosch, Javier Godoy. This specification 1029 originated from the work of the XML-JSON technical committee of the 1030 Calendaring and Scheduling Consortium. 1032 10. References 1034 10.1. Normative References 1036 [I-D.ietf-jcardcal-jcal] 1037 Kewisch, P., Daboo, C., and M. Douglass, "jCal: The JSON 1038 format for iCalendar", draft-ietf-jcardcal-jcal-00 (work 1039 in progress), March 2013. 1041 [ISO.8601.2000] 1042 International Organization for Standardization, ""Data 1043 elements and interchange formats -- Information 1044 interchange -- Representation of dates and times" ", ISO 1045 8601, 12 2000. 1047 [ISO.8601.2004] 1048 International Organization for Standardization, ""Data 1049 elements and interchange formats -- Information 1050 interchange -- Representation of dates and times" ", ISO 1051 8601, 12 2004. 1053 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1054 Requirement Levels", BCP 14, RFC 2119, March 1997. 1056 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 1057 Specifications: ABNF", STD 68, RFC 5234, January 2008. 1059 [RFC5545] Desruisseaux, B., "Internet Calendaring and Scheduling 1060 Core Object Specification (iCalendar)", RFC 5545, 1061 September 2009. 1063 [RFC5646] Phillips, A. and M. Davis, "Tags for Identifying 1064 Languages", BCP 47, RFC 5646, September 2009. 1066 [RFC6321] Daboo, C., Douglass, M., and S. Lees, "xCal: The XML 1067 Format for iCalendar", RFC 6321, August 2011. 1069 [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, 1070 August 2011. 1072 [RFC6351] Perreault, S., "xCard: vCard XML Representation", RFC 1073 6351, August 2011. 1075 [RFC6868] Daboo, C., "Parameter Value Encoding in iCalendar and 1076 vCard", RFC 6868, February 2013. 1078 10.2. Informative References 1080 [I-D.sheffer-running-code] 1081 Sheffer, Y. and A. Farrel, "Improving Awareness of Running 1082 Code: the Implementation Status Section", draft-sheffer- 1083 running-code-02 (work in progress), January 2013. 1085 [RFC4627] Crockford, D., "The application/json Media Type for 1086 JavaScript Object Notation (JSON)", RFC 4627, July 2006. 1088 [calconnect-artifacts] 1089 The Calendaring and Scheduling Consortium, "Code Artifacts 1090 and Schemas", , 1091 . 1093 Appendix A. ABNF Schema 1095 Below is an ABNF schema as per [RFC5234] for vCard in JSON. ABNF 1096 Symbols not described here are taken from [RFC4627]. The schema is 1097 non-normative and given for reference only. 1099 The numeric section numbers given in the comments refer to section in 1100 [RFC6350]. Additional semantic restrictions apply, especially 1101 regarding the allowed properties and sub-components per component. 1102 Details on these restrictions can be found in this document and 1103 [RFC6350]. 1105 Additional schemas may be available on the internet at 1106 [calconnect-artifacts]. 1108 ; A jCard component uses the name "vcard" and a properties array. 1109 ; Restrictions to which properties and may be specified are to 1110 ; be taken from RFC6350. 1111 jcardobject = begin-array 1112 DQUOTE component-name DQUOTE value-separator 1113 properties-array 1114 end-array 1116 ; A jCard property consists of the name string, parameters object, 1117 ; type string and one or more values as specified in this document. 1118 property = begin-array 1119 DQUOTE property-name DQUOTE value-separator 1120 params-object value-separator 1121 DQUOTE type-name DQUOTE 1122 propery-value *(value-separator property-value) 1123 end-array 1124 properties-array = begin-array 1125 [ property *(value-separator property) ] 1126 end-array 1128 ; Property values depend on the type-name. Aside from the value types 1129 ; mentioned here, extensions may make use of other JSON value types. 1130 property-value = simple-prop-value / structured-prop-value 1131 simple-prop-value = string / number / true / false 1132 structured-prop-value = 1133 begin-array 1134 [ structured-element *(value-separator structured-element) ] 1135 end-array 1137 ; Each structured element may have multiple values if 1138 ; semantically allowed 1139 structured-element = simple-prop-value / structured-multi-prop 1140 structured-multi-prop = 1141 begin-array 1142 [ simple-prop-value *(value-separator simple-prop-value) ] 1143 end-array 1145 ; The jCard params-object is a JSON object which follows the semantic 1146 ; guidelines described in this document. 1147 params-object = begin-object 1148 [ params-member *(value-separator params-member) ] 1149 end-object 1150 params-member = DQUOTE param-name DQUOTE name-separator param-value 1151 param-value = string / param-multi 1152 param-multi = begin-array 1153 [ string *(value-separtor string) ] 1154 end-array 1156 ; The type MUST be a valid type as described by this document. New 1157 ; value types can be added by extensions. 1158 type-name = "text" / "uri" / "date" / "time" / "date-time" / 1159 "boolean" / "integer" / "float" / "utc-offset" / 1160 "language-tag" / x-type 1162 ; Property, parameter and type names MUST be lowercase. Additional 1163 ; semantic restrictions apply as described by this document and 1164 ; RFC6350. 1165 component-name = lowercase-name 1166 property-name = lowercase-name 1167 param-name = lowercase-name 1168 x-type = lowercase-name 1169 lowercase-name = 1*(%x61-7A / DIGIT / "-") 1171 Appendix B. Examples 1173 This section contains an example of a vCard object with its jCard 1174 representation. 1176 B.1. Example: vCard of the author of RFC6350 1178 B.1.1. vCard Data 1180 BEGIN:VCARD 1181 VERSION:4.0 1182 FN:Simon Perreault 1183 N:Perreault;Simon;;;ing. jr,M.Sc. 1184 BDAY:--0203 1185 ANNIVERSARY:20090808T1430-0500 1186 GENDER:M 1187 LANG;PREF=1:fr 1188 LANG;PREF=2:en 1189 ORG;TYPE=work:Viagenie 1190 ADR;TYPE=work:;Suite D2-630;2875 Laurier; 1191 Quebec;QC;G1V 2M2;Canada 1192 TEL;VALUE=uri;TYPE="work,voice";PREF=1:tel:+1-418-656-9254;ext=102 1193 TEL;VALUE=uri;TYPE="work,cell,voice,video,text":tel:+1-418-262-6501 1194 EMAIL;TYPE=work:simon.perreault@viagenie.ca 1195 GEO;TYPE=work:geo:46.772673,-71.282945 1196 KEY;TYPE=work;VALUE=uri: 1197 http://www.viagenie.ca/simon.perreault/simon.asc 1198 TZ:-0500 1199 URL;TYPE=home:http://nomis80.org 1200 END:VCARD 1202 B.1.2. jCard Data 1204 ["vcard", 1205 [ 1206 ["version", {}, "text", "4.0"], 1207 ["fn", {}, "text", "Simon Perreault"], 1208 ["n", 1209 {}, 1210 "text", 1211 ["Perreault", "Simon", "", "", ["ing. jr", "M.Sc."]] 1212 ], 1213 ["bday", {}, "date-and-or-time", "--02-03"], 1214 ["anniversary", 1215 {}, 1216 "date-and-or-time", 1217 "2009-08-08T14:30:00-05:00" 1218 ], 1219 ["gender", {}, "text", "M"], 1220 ["lang", { "pref": "1" }, "language-tag", "fr"], 1221 ["lang", { "pref": "2" }, "language-tag", "en"], 1222 ["org", { "type": "work" }, "text", "Viagenie"], 1223 ["adr", 1224 { "type": "work" }, 1225 "text", 1226 [ 1227 "", 1228 "Suite D2-630", 1229 "2875 Laurier", 1230 "Quebec", 1231 "QC", 1232 "G1V 2M2", 1233 "Canada" 1234 ] 1235 ], 1236 ["tel", 1237 { "type": ["work", "voice"], "pref": "1" }, 1238 "uri", 1239 "tel:+1-418-656-9254;ext=102" 1240 ], 1241 ["tel", 1242 { "type": ["work", "cell", "voice", "video", "text"] }, 1243 "uri", 1244 "tel:+1-418-262-6501" 1245 ], 1246 ["email", 1247 { "type": "work" }, 1248 "text", 1249 "simon.perreault@viagenie.ca" 1250 ], 1251 ["geo", { "type": "work" }, "uri", "geo:46.772673,-71.282945"], 1252 ["key", 1253 { "type": "work" }, 1254 "uri", 1255 "http://www.viagenie.ca/simon.perreault/simon.asc" 1256 ], 1257 ["tz", {}, "utc-offset", "-05:00"], 1258 ["url", { "type": "home" }, "uri", "http://nomis80.org"] 1259 ] 1260 ] 1262 Appendix C. Change History (to be removed prior to publication as an 1263 RFC) 1265 draft-kewisch-vcard-in-json-01 1267 * Added ABNF and improved references in date/time related 1268 sections 1270 * Changes to wording in "vCard Stream" section 1272 * Changes to wording about VALUE parameter when converting to 1273 vCard 1275 * Corrected missing "type" parameter and separator in example 1277 * Minor wording corrections 1279 draft-ietf-jcardcal-jcard-00 1281 * Pubication as a WG draft 1283 draft-ietf-jcardcal-jcard-01 1285 * Changed grouping syntax to use new GROUP parameter and added 1286 respective IANA section 1288 * Added timestamp and date-and-or-time types instead of 1289 converting them from date/time/date-time 1291 * Added a further sentence on preprocessing and escaping to 1292 clarify that JSON escaping must be used 1294 * Described how to handle structured text values and structured 1295 text components with multiple values. 1297 * Corrections and additions to the ABNF Section, adaptions to 1298 example 1300 draft-ietf-jcardcal-jcard-02 1302 * Made more clear that complete representation is not mandatory 1304 * Added sheffer-running-code section 1306 * Changed handling of unknown property parameter types 1308 * Minor corrections to sections regarding dates, fixing typos 1310 draft-ietf-jcardcal-jcard-03 1312 * Add LABEL property example and description 1314 * Added acknowledgements 1316 * More typos fixed 1318 draft-ietf-jcardcal-jcard-04 1320 * Added reference to rfc6868 1322 * Various editorial changes per jcardcal issue tracker 1324 * Resolved a few MAY/SHOULD conflicts 1326 * Put the VERSION property into its own section 1328 * Improved GROUP/UNKNOWN registrations by only putting vcard 1329 related information into the registration template 1331 * Removed vcard stream construct. 1333 * Added reference to RFC6868 for both directions 1335 * Corrected some examples and ABNF 1337 Author's Address 1338 Philipp Kewisch 1339 Mozilla Corporation 1340 650 Castro Street, Suite 300 1341 Mountain View, CA 94041 1342 USA 1344 EMail: mozilla@kewis.ch 1345 URI: http://www.mozilla.org/