idnits 2.17.1 draft-ietf-jmap-jscontact-06.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 lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (28 May 2021) is 1036 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: 'String' is mentioned on line 262, but not defined == Missing Reference: 'Anniversary' is mentioned on line 719, but not defined Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 JMAP R. Stepanek 3 Internet-Draft FastMail 4 Intended status: Standards Track M. Loffredo 5 Expires: 29 November 2021 IIT-CNR 6 28 May 2021 8 JSContact: A JSON representation of contact data 9 draft-ietf-jmap-jscontact-06 11 Abstract 13 This specification defines a data model and JSON representation of 14 contact card information that can be used for data storage and 15 exchange in address book or directory applications. It aims to be an 16 alternative to the vCard data format and to be unambiguous, 17 extendable and simple to process. In contrast to the JSON-based 18 jCard format, it is not a direct mapping from the vCard data model 19 and expands semantics where appropriate. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at https://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on 29 November 2021. 38 Copyright Notice 40 Copyright (c) 2021 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 45 license-info) in effect on the date of publication of this document. 46 Please review these documents carefully, as they describe your rights 47 and restrictions with respect to this document. Code Components 48 extracted from this document must include Simplified BSD License text 49 as described in Section 4.e of the Trust Legal Provisions and are 50 provided without warranty as described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 55 1.1. Relation to the xCard and jCard formats . . . . . . . . . 4 56 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 57 1.3. Vendor-specific Property Extensions and Values . . . . . 4 58 1.4. Type Signatures . . . . . . . . . . . . . . . . . . . . . 4 59 1.5. Data types . . . . . . . . . . . . . . . . . . . . . . . 5 60 1.5.1. Context . . . . . . . . . . . . . . . . . . . . . . . 5 61 1.5.2. Id . . . . . . . . . . . . . . . . . . . . . . . . . 5 62 1.5.3. LocalizedString . . . . . . . . . . . . . . . . . . . 6 63 1.5.4. Preference . . . . . . . . . . . . . . . . . . . . . 6 64 1.5.5. UTCDateTime . . . . . . . . . . . . . . . . . . . . . 7 65 2. Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 66 2.1. Metadata properties . . . . . . . . . . . . . . . . . . . 7 67 2.1.1. uid . . . . . . . . . . . . . . . . . . . . . . . . . 7 68 2.1.2. prodId . . . . . . . . . . . . . . . . . . . . . . . 7 69 2.1.3. created . . . . . . . . . . . . . . . . . . . . . . . 7 70 2.1.4. updated . . . . . . . . . . . . . . . . . . . . . . . 8 71 2.1.5. kind . . . . . . . . . . . . . . . . . . . . . . . . 8 72 2.1.6. relatedTo . . . . . . . . . . . . . . . . . . . . . . 8 73 2.2. Name and Organization properties . . . . . . . . . . . . 9 74 2.2.1. name . . . . . . . . . . . . . . . . . . . . . . . . 9 75 2.2.2. fullName . . . . . . . . . . . . . . . . . . . . . . 9 76 2.2.3. nickNames . . . . . . . . . . . . . . . . . . . . . . 10 77 2.2.4. organizations . . . . . . . . . . . . . . . . . . . . 10 78 2.2.5. titles . . . . . . . . . . . . . . . . . . . . . . . 10 79 2.3. Contact and Resource properties . . . . . . . . . . . . . 10 80 2.3.1. emails . . . . . . . . . . . . . . . . . . . . . . . 10 81 2.3.2. phones . . . . . . . . . . . . . . . . . . . . . . . 11 82 2.3.3. online . . . . . . . . . . . . . . . . . . . . . . . 12 83 2.3.4. photos . . . . . . . . . . . . . . . . . . . . . . . 13 84 2.3.5. preferredContactMethod . . . . . . . . . . . . . . . 13 85 2.3.6. preferredContactLanguages . . . . . . . . . . . . . . 14 86 2.4. Address and Location properties . . . . . . . . . . . . . 14 87 2.4.1. addresses . . . . . . . . . . . . . . . . . . . . . . 14 88 2.5. Additional properties . . . . . . . . . . . . . . . . . . 16 89 2.5.1. anniversaries . . . . . . . . . . . . . . . . . . . . 16 90 2.5.2. personalInfo . . . . . . . . . . . . . . . . . . . . 17 91 2.5.3. notes . . . . . . . . . . . . . . . . . . . . . . . . 17 92 2.5.4. categories . . . . . . . . . . . . . . . . . . . . . 17 93 2.5.5. timeZones . . . . . . . . . . . . . . . . . . . . . . 17 94 3. CardGroup . . . . . . . . . . . . . . . . . . . . . . . . . . 18 95 3.1. Group properties . . . . . . . . . . . . . . . . . . . . 18 96 3.1.1. uid . . . . . . . . . . . . . . . . . . . . . . . . . 18 97 3.1.2. members . . . . . . . . . . . . . . . . . . . . . . . 18 98 3.1.3. name . . . . . . . . . . . . . . . . . . . . . . . . 18 99 3.1.4. card . . . . . . . . . . . . . . . . . . . . . . . . 18 100 4. Implementation Status . . . . . . . . . . . . . . . . . . . . 18 101 4.1. IIT-CNR/Registro.it . . . . . . . . . . . . . . . . . . . 19 102 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 103 6. Security Considerations . . . . . . . . . . . . . . . . . . . 19 104 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 105 7.1. Normative References . . . . . . . . . . . . . . . . . . 19 106 7.2. Informative References . . . . . . . . . . . . . . . . . 21 107 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 109 1. Introduction 111 This document defines a data model for contact card data normally 112 used in address book or directory applications and services. It aims 113 to be an alternative to the vCard data format [RFC6350] and to 114 provide a JSON-based standard representation of contact card data. 116 The key design considerations for this data model are as follows: 118 * Most of the initial set of attributes should be taken from the 119 vCard data format [RFC6350] and extensions ([RFC6473], [RFC6474], 120 [RFC6715], [RFC6869], [RFC8605]). The specification should add 121 new attributes or value types, or not support existing ones, where 122 appropriate. Conversion between the data formats need not fully 123 preserve semantic meaning. 125 * The attributes of the cards data represented must be described as 126 a simple key-value pair, reducing complexity of its 127 representation. 129 * The data model should avoid all ambiguities and make it difficult 130 to make mistakes during implementation. 132 * Extensions, such as new properties and components, MUST NOT lead 133 to requiring an update to this document. 135 The representation of this data model is defined in the I-JSON format 136 [RFC7493], which is a strict subset of the JavaScript Object Notation 137 (JSON) Data Interchange Format [RFC8259]. Using JSON is mostly a 138 pragmatic choice: its widespread use makes Card easier to adopt, and 139 the availability of production-ready JSON implementations eliminates 140 a whole category of parser-related interoperability issues. 142 1.1. Relation to the xCard and jCard formats 144 The xCard [RFC6351] and jCard [RFC7095] specifications define 145 alternative representations for vCard data, in XML and JSON format 146 respectively. Both explicitly aim to not change the underlying data 147 model. Accordingly, they are regarded as equal to vCard in the 148 context of this document. 150 1.2. Terminology 152 The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, 153 SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL in this 154 document are to be interpreted as described in BCP 14 [RFC2119] 155 [RFC8174] when, and only when, they appear in all capitals, as shown 156 here. 158 1.3. Vendor-specific Property Extensions and Values 160 Vendors MAY add additional properties to JSContact objects to support 161 their custom features. The names of these properties MUST be 162 prefixed with a domain name controlled by the vendor to avoid 163 conflict, e.g. "example.com/customprop". 165 Some JSContact properties allow vendor-specific value extensions. If 166 so, vendor-specific values MUST be prefixed with a domain name 167 controlled by the vendor, e.g. "example.com/customrel". 169 Vendors are strongly encouraged to register any new property values 170 or extensions that are useful to other systems as well, rather than 171 using a vendor-specific prefix. 173 1.4. Type Signatures 175 Type signatures are given for all JSON values in this document. The 176 following conventions are used: 178 * "*" - The type is undefined (the value could be any type, although 179 permitted values may be constrained by the context of this value). 181 * "String" - The JSON string type. 183 * "Number" - The JSON number type. 185 * "Boolean" - The JSON boolean type. 187 * "A[B]" - A JSON object where the keys are all of type "A", and the 188 values are all of type "B". 190 * "A[]" - An array of values of type "A". 192 * "A|B" - The value is either of type "A" or of type "B". 194 1.5. Data types 196 In addition to the standard JSON data types, a couple of additional 197 data types are common to the definitions of JSContact objects and 198 properties. 200 1.5.1. Context 202 Contact information typically is associated with a context in which 203 it should be used. For example, someone might have distinct phone 204 numbers for work and private contexts. The Context data type 205 enumerates common contexts. 207 Common context values are: 209 * "private": The contact information may be used to contact the card 210 holder in a private context. 212 * "work": The contact information may be used to contact the card 213 holder in a professional context. 215 * "other": The contact information may be used to contact the card 216 holder in some other context. A label property MAY be defined to 217 identify its purpose. 219 Additional allowed values may be defined in the properties or data 220 types that make use of the Context data type, registered in a future 221 RFC, or a vendor-specific value. 223 1.5.2. Id 225 Where "Id" is given as a data type, it means a "String" of at least 1 226 and a maximum of 255 octets in size, and it MUST only contain 227 characters from the "URL and Filename Safe" base64url alphabet, as 228 defined in Section 5 of [RFC4648], excluding the pad character ("="). 229 This means the allowed characters are the ASCII alphanumeric 230 characters ("A-Za-z0-9"), hyphen ("-"), and underscore ("_"). 232 In many places in JSContact a JSON map is used where the map keys are 233 of type Id and the map values are all the same type of object. This 234 construction represents an unordered set of objects, with the added 235 advantage that each entry has a name (the corresponding map key). 236 This allows for more concise patching of objects, and, when 237 applicable, for the objects in question to be referenced from other 238 objects within the JSContact object. 240 Unless otherwise specified for a particular property, there are no 241 uniqueness constraints on an Id value (other than, of course, the 242 requirement that you cannot have two values with the same key within 243 a single JSON map). For example, two Card objects might use the same 244 Ids in their respective "photos" properties. Or within the same Card 245 object the same Id could appear in the "emails" and "phones" 246 properties. These situations do not imply any semantic connections 247 among the objects. 249 1.5.3. LocalizedString 251 The purpose of LocalizedString is to allow for internationalisation 252 of string values. In its simplest form it is just a string value. 253 Optionally, the human language of this value may be specified, as 254 well as localized variants in additional languages. A 255 LocalizedString has the following properties: 257 * value: "String" (mandatory). The property value. 259 * language: "String" (optional). The [RFC5646] language tag of this 260 value, if any. 262 * localizations: "String[String]" (optional). A map from [RFC5646] 263 language tags to the value localized in that language. 265 1.5.4. Preference 267 This data type allows to define a preference order on same-typed 268 contact information. For example, a card holder may have two email 269 addresses and prefer to be contacted with one of them. 271 A preference value MUST be an integer number in the range 1 and 100. 272 Lower values correspond to a higher level of preference, with 1 being 273 most preferred. If no preference is set, then the contact 274 information MUST be interpreted as being least preferred. 276 Note that the preference only is defined in relation to contact 277 information of the same type. For example, the preference orders 278 within emails and phone numbers are indendepent of each other. Also 279 note that the _preferredContactMethod_ property allows to define a 280 preferred contact method across method types. 282 1.5.5. UTCDateTime 284 This is a string in [RFC3339] "date-time" format, with the further 285 restrictions that any letters MUST be in uppercase, and the time 286 offset MUST be the character "Z". Fractional second values MUST NOT 287 be included unless non-zero and MUST NOT have trailing zeros, to 288 ensure there is only a single representation for each date-time. 290 For example, "2010-10-10T10:10:10.003Z" is conformant, but 291 "2010-10-10T10:10:10.000Z" is invalid and is correctly encoded as 292 "2010-10-10T10:10:10Z". 294 2. Card 296 MIME type: "application/jscontact+json;type=card" 298 A Card object stores information about a person, organization or 299 company. 301 2.1. Metadata properties 303 2.1.1. uid 305 Type: "String" (mandatory). 307 An identifier, used to associate the object as the same across 308 different systems, addressbooks and views. [RFC4122] describes a 309 range of established algorithms to generate universally unique 310 identifiers (UUID), and the random or pseudo-random version is 311 recommended. For compatibility with [RFC6350] UIDs, implementations 312 MUST accept both URI and free-form text. 314 2.1.2. prodId 316 Type: "String" (optional). 318 The identifier for the product that created the Card object. 320 2.1.3. created 322 Type: "UTCDateTime" (optional). 324 The date and time when this Card object was created. 326 2.1.4. updated 328 Type: "UTCDateTime" (optional). 330 The date and time when the data in this Card object was last 331 modified. 333 2.1.5. kind 335 Type: "String" (optional). The kind of the entity the Card 336 represents. 338 The value MUST be either one of the following values, registered in a 339 future RFC, or a vendor-specific value: 341 * "individual": a single person 343 * "org": an organization 345 * "location": a named location 347 * "device": a device, such as appliances, computers, or network 348 elements 350 * "application": a software application 352 2.1.6. relatedTo 354 Type: "String[Relation]" (optional). 356 Relates the object to other Card objects. This is represented as a 357 map of the URI (or single text value) of the related objects to a 358 possibly empty set of relation types. The Relation object has the 359 following properties: 361 * relation: "String[Boolean]" (optional, default: empty Object) 362 Describes how the linked object is related to the linking object. 363 The relation is defined as a set of relation types. If empty, the 364 relationship between the two objects is unspecified. Keys in the 365 set MUST be one of the RELATED property [RFC6350] type parameter 366 values, or an IANA-registered value, or a vendor-specific value. 367 The value for each key in the set MUST be true. 369 Note, the Relation object only has one property; it is specified as 370 an object with a single property to allow for extension in the 371 future. 373 2.2. Name and Organization properties 375 2.2.1. name 377 Type: "NameComponent[]" (optional). 379 The name components of the name of the entity represented by this 380 Card. Name components SHOULD be ordered such that their values 381 joined by whitespace produce a valid full name of this entity. Doing 382 so, implementations MAY ignore any "separator" components. 384 A NameComponent has the following properties: 386 * value: "String" (mandatory). The value of this name component. 388 * type: "String" (mandatory). The type of this name component. The 389 value MUST be either one of the following values, registered in a 390 future RFC, or a vendor-specific value: 392 - "prefix". The value is a honorific title(s), e.g. "Mr", "Ms", 393 "Dr". 395 - "personal". The value is a personal name(s), also known as 396 "first name", "given name". 398 - "surname". The value is a surname, also known as "last name", 399 "family name". 401 - "additional". The value is an additional name, also known as 402 "middle name". 404 - "suffix". The value is a honorific suffix, e.g. "B.A.", 405 "Esq.". 407 - "separator". A separator for two name components. The "value" 408 property of the component includes the verbatim separator, for 409 example a newline character. 411 2.2.2. fullName 413 Type: "LocalizedString" (optional). 415 The full name (e.g. the personal name and surname of an individual, 416 the name of an organization) of the entity represented by this card. 417 The purpose of this property is to define a name, even if the 418 individual name components are not known. In addition, it is meant 419 to provide alternative versions of the name for internationalisation. 420 Implementations SHOULD prefer using the _name_ property over this one 421 and SHOULD NOT store the concatenated name component values in this 422 property. 424 2.2.3. nickNames 426 Type: "LocalizedString[]" (optional). 428 The nick names of the entity represented by this card. 430 2.2.4. organizations 432 Type: "Id[Organization]" (optional). 434 The companies or organization names and units associated with this 435 card. An Organization object has the following properties: 437 * name: "LocalizedString" (mandatory). The name of this 438 organization. 440 * units: "LocalizedString[]" (optional). Additional levels of 441 organizational unit names. 443 2.2.5. titles 445 Type : "Id[Title]" (optional). 447 The job titles or functional positions of the entity represented by 448 this card. A Title has object the following properties: 450 * title: "LocalizedString" (mandatory). The title of the entity 451 represented by this card. 453 * organization: "Id" (optional). The id of the organization in 454 which this title is held. 456 2.3. Contact and Resource properties 458 2.3.1. emails 460 Type: "Id[EmailAddress]" (optional). 462 The email addresses to contact the entity represented by this card. 463 An EmailAddress object has the following properties: 465 * email: "String" (mandatory). The email address. This MUST be an 466 _addr-spec_ value as defined in Section 3.4.1 of [RFC5322]. 468 * contexts: "Context[Boolean]" (optional) The contexts in which to 469 use this email address. The value for each key in the object MUST 470 be "true". 472 * pref: "Preference" (optional) The preference of this email address 473 in relation to other email addresses. 475 2.3.2. phones 477 Type: "Id[Phone]" (optional). 479 The phone numbers to contact the entity represented by this card. A 480 phone object has the following properties: 482 * phone: "String" (mandatory). The phone value, as either a URI or 483 a free-text phone number. Typical URI schemes are the [RFC3966] 484 "tel" or [RFC3261] "sip" schemes, but any URI scheme is allowed. 486 * features: "String[Boolean]" (optional). The set of contact 487 features that this phone number may be used for. The set is 488 represented as an object, with each key being a method type. The 489 value for each key in the object MUST be "true". The method type 490 MUST be either one of the following values, registered in a future 491 RFC, or a vendor-specific value: 493 - "voice" The number is for calling by voice. 495 - "fax" The number is for sending faxes. 497 - "pager" The number is for a pager or beeper. 499 - "text" The number supports text messages (SMS). 501 - "cell" The number is for a cell phone. 503 - "textphone" The number is for a device for people with hearing 504 or speech difficulties. 506 - "video" The number supports video conferencing. 508 - "other" The number is for some other purpose. The label 509 property MAY be included to display next to the number to help 510 the user identify its purpose. 512 * contexts: "Context[Boolean]" (optional) The contexts in which to 513 use this number. The value for each key in the object MUST be 514 "true". 516 * label: "String" (optional). A label describing the value in more 517 detail, especially if the type property has value "other" (but MAY 518 be included with any type). 520 * pref: "Preference" (optional) The preference of this number in 521 relation to other numbers. 523 2.3.3. online 525 Type: "Id[Resource]" (optional). 527 The online resources and services that are associated with the entity 528 represented by this card. A Resource object has the following 529 properties: 531 * resource: "String" (mandatory). The resource value, where the 532 allowed value form is defined by the the _type_ property. In any 533 case the value MUST NOT be empty. 535 * type: "String" (optional, default: "other"). The type of the 536 resource value. Allowed values are: 538 - "uri" The resource value is a URI, e.g. a website link. This 539 MUST be a valid _URI_ as defined in Section 3 of [RFC3986] and 540 updates. 542 - "username" The resource value is a username associated with the 543 entity represented by this card (e.g. for social media, or an 544 IM client). The _label_ property SHOULD be included to 545 identify what service this is for. For compatibility between 546 clients, this label SHOULD be the canonical service name, 547 including capitalisation. e.g. "Twitter", "Facebook", "Skype", 548 "GitHub", "XMPP". The resource value may be any non-empty free 549 text. 551 - "other" The resource value is something else not covered by the 552 above categories. A label property MAY be included to display 553 next to the number to help the user identify its purpose. The 554 resource value may be any non-empty free text. 556 * mediaType: "String" (optional). Used for URI resource values. 557 Provides the media type [RFC2046] of the resource identified by 558 the URI. 560 * contexts: "Context[Boolean]" (optional) The contexts in which to 561 use this resource. The value for each key in the object MUST be 562 "true". 564 * label: "String" (optional). A label describing the value in more 565 detail, especially if the type property has value "other" (but MAY 566 be included with any type). 568 * pref: "Preference" (optional) The preference of this resource in 569 relation to other resources. 571 2.3.4. photos 573 Type: "Id[File]" (optional). 575 A map of photo ids to File objects that contain photographs or images 576 associated with this card. A typical use case is to include an 577 avatar for display along the contact name. 579 A File object has the following properties: 581 * href: "String" (mandatory). A URI where to fetch the data of this 582 file. 584 * mediaType: "String" (optional). The content-type of the file, if 585 known. 587 * size: "UnsignedInt" (optional). The size, in octets, of the file 588 when fully decoded (i.e., the number of octets in the file the 589 user would download), if known. 591 * pref: "Preference" (optional) The preference of this photo in 592 relation to other photos. 594 2.3.5. preferredContactMethod 596 Type : "String" (optional) 598 Defines the preferred method to contact the holder of this card. The 599 value MUST be the property names: "emails", "phones", "online". 601 2.3.6. preferredContactLanguages 603 Type : "String[ContactLanguage[]]" (optional) 605 Defines the preferred languages for contacting the entity associated 606 with this card. The keys in the object MUST be [RFC5646] language 607 tags. The values are a (possibly empty) list of contact language 608 preferences for this language. A valid ContactLanguage object MUST 609 have at least one of its properties set. 611 A ContactLanguage object has the following properties: 613 * context: "Context" (optional). Defines the context in which to 614 use this language. 616 * pref: "Preference" (optional). Defines the preference of this 617 language in relation to other languages of the same context. 619 Also see the definition of the VCARD LANG property (Section 6.4.4., 620 [RFC6350]). 622 2.4. Address and Location properties 624 2.4.1. addresses 626 Type: "Id[Address]" (optional). 628 A map of address ids to Address objects, containing physical 629 locations. An Address object has the following properties: 631 * fullAddress: "LocalizedString" (optional). The complete address, 632 excluding type and label. This property is mainly useful to 633 represent addresses of which the individual address components are 634 unknown, or to provide localized representations. 636 * street: "StreetComponent[]" (optional). The street address. The 637 concatenation of the component values, separated by whitespace, 638 SHOULD result in a valid street address for the address locale. 639 Doing so, implementations MAY ignore any "separator" components. 640 The StreetComponent object type is defined in the paragraph below. 642 * locality: "String" (optional). The city, town, village, post 643 town, or other locality within which the street address may be 644 found. 646 * region: "String" (optional). The province, such as a state, 647 county, or canton within which the locality may be found. 649 * country: "String" (optional). The country name. 651 * postcode: "String" (optional). The postal code, post code, ZIP 652 code or other short code associated with the address by the 653 relevant country's postal system. 655 * countryCode: "String" (optional). The ISO-3166-1 country code. 657 * coordinates: "String" (optional) A [RFC5870] "geo:" URI for the 658 address. 660 * timeZone: "String" (optional) Identifies the time zone this 661 address is located in. This either MUST be a time zone name 662 registered in the IANA Time Zone Database (https://www.iana.org/ 663 time-zones), or it MUST be a valid TimeZoneId as defined in FIXME 664 . For the latter, a corresponding time zone MUST be defined in the 665 "timeZones" property. 667 * contexts: "Context[Boolean]" (optional). The contexts of the 668 address information. In addition to the common contexts, allowed 669 values are: 671 - "billing" An address to be used for billing. 673 - "postal" An address to be used for delivering physical items. 674 The value for each key in the object MUST be "true". 676 * label: "String" (optional). A label describing the value in more 677 detail. 679 * pref: "Preference" (optional) The preference of this address in 680 relation to other addresses. 682 A StreetComponent object has the following properties: 684 * type: "String" (mandatory). The type of this street component. 685 The value MUST be either one of the following values, registered 686 in a future RFC, or a vendor-specific value: 688 - "name". The street name. 690 - "number". The street number. 692 - "apartment". The apartment number or identifier. 694 - "room". The room number or identifier. 696 - "extension". The extension designation or box number. 698 - "direction". The cardinal direction, e.g. "North". 700 - "building". The building or building part this address is 701 located in. 703 - "floor". The floor this address is located on. 705 - "postOfficeBox". The post office box number or identifier. 707 - "separator". A separator for two street components. The 708 "value" property of the component includes the verbatim 709 separator, for example a newline character. 711 - "unknown". A name component value for which no type is known. 713 * value: "String" (mandatory). The value of this street component. 715 2.5. Additional properties 717 2.5.1. anniversaries 719 Type : Id[Anniversary] (optional). 721 These are memorable dates and events for the entity represented by 722 this card. An Anniversary object has the following properties: 724 * type: "String" (mandatory). Specifies the type of the 725 anniversary. This RFC predefines the following types, but 726 implementations MAY use additional values: 728 - "birth": a birth day anniversary 730 - "death": a death day anniversary 732 - "other": an anniversary not covered by any of the known types. 734 * label: "String" (optional). A label describing the value in more 735 detail, especially if the type property has value "other" (but MAY 736 be included with any type). 738 * date: "String" (mandatory). The date of this anniversary, in the 739 form "YYYY-MM-DD" (any part may be all 0s for unknown) or a 740 [RFC3339] timestamp. 742 * place: Address (optional). An address associated with this 743 anniversary, e.g. the place of birth or death. 745 2.5.2. personalInfo 747 Type: "Id[PersonalInformation]" (optional). 749 Defines personal information about the entity represented by this 750 card. A PersonalInformation object has the following properties: 752 * type: "String" (mandatory). Specifies the type for this personal 753 information. Allowed values are: 755 - "expertise": a field of expertise or credential 757 - "hobby": a hobby 759 - "interest": an interest 761 - "other": an information not covered by the above categories 763 * value: "String" (mandatory). The actual information. This 764 generally is free-text, but future specifications MAY restrict 765 allowed values depending on the type of this PersonalInformation. 767 * level: "String" (optional) Indicates the level of expertise, or 768 engagement in hobby or interest. Allowed values are: "high", 769 "medium" and "low". 771 2.5.3. notes 773 Type: "LocalizedString" (optional). 775 Arbitrary notes about the entity represented by this card. 777 2.5.4. categories 779 Type: "String[Boolean]" (optional). The set of free-text or URI 780 categories that relate to the card. The set is represented as an 781 object, with each key being a category. The value for each key in 782 the object MUST be "true". 784 2.5.5. timeZones 786 Type: "String[TimeZone]" (optional). Maps identifiers of custom time 787 zones to their time zone definitions. For a description of this 788 property see the "timeZones" property definition in FIXME . 790 3. CardGroup 792 MIME type: "application/jscontact+json;type=cardgroup" 794 A CardGroup object represents a group of cards. Its members may be 795 Cards or CardGroups. 797 3.1. Group properties 799 3.1.1. uid 801 Type: "String" (mandatory). The uid of this group. Both CardGroup 802 and Card share the same namespace for the "uid" property. 804 3.1.2. members 806 Type: "String[Boolean]" (mandatory). The members of this group. 808 The set is represented as an object, with each key being the uid of 809 another Card or CardGroup. The value for each key in the object MUST 810 be "true". 812 3.1.3. name 814 Type: "String" (optional). The user-visible name for the group, e.g. 815 "Friends". This may be any UTF-8 string of at least 1 character in 816 length and maximum 255 octets in size. The same name may be used by 817 two different groups. 819 3.1.4. card 821 Type: "Card" (optional). The card that represents this group. 823 4. Implementation Status 825 NOTE: Please remove this section and the reference to [RFC7942] prior 826 to publication as an RFC. This section records the status of known 827 implementations of the protocol defined by this specification at the 828 time of posting of this Internet-Draft, and is based on a proposal 829 described in [RFC7942]. The description of implementations in this 830 section is intended to assist the IETF in its decision processes in 831 progressing drafts to RFCs. Please note that the listing of any 832 individual implementation here does not imply endorsement by the 833 IETF. Furthermore, no effort has been spent to verify the 834 information presented here that was supplied by IETF contributors. 835 This is not intended as, and must not be construed to be, a catalog 836 of available implementations or their features. Readers are advised 837 to note that other implementations may exist. According to 839 [RFC7942], "this will allow reviewers and working groups to assign 840 due consideration to documents that have the benefit of running code, 841 which may serve as evidence of valuable experimentation and feedback 842 that have made the implemented protocols more mature. It is up to 843 the individual working groups to use this information as they see 844 fit". 846 4.1. IIT-CNR/Registro.it 848 * Responsible Organization: Institute of Informatics and Telematics 849 of National Research Council (IIT-CNR)/Registro.it 851 * Location: https://rdap.pubtest.nic.it/ 852 (https://rdap.pubtest.nic.it/) 854 * Description: This implementation includes support for RDAP queries 855 using data from the public test environment of .it ccTLD. The 856 RDAP server does not implement any security policy because data 857 returned by this server are only for experimental testing 858 purposes. The RDAP server returns responses including Card in 859 place of jCard when queries contain the parameter jscard=1. 861 * Level of Maturity: This is a "proof of concept" research 862 implementation. 864 * Coverage: This implementation includes all of the features 865 described in this specification. 867 * Contact Information: Mario Loffredo, mario.loffredo@iit.cnr.it 869 5. IANA Considerations 871 TBD 873 6. Security Considerations 875 TBD 877 7. References 879 7.1. Normative References 881 [RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail 882 Extensions (MIME) Part Two: Media Types", RFC 2046, 883 DOI 10.17487/RFC2046, November 1996, 884 . 886 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 887 Requirement Levels", BCP 14, RFC 2119, 888 DOI 10.17487/RFC2119, March 1997, 889 . 891 [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally 892 Unique IDentifier (UUID) URN Namespace", RFC 4122, 893 DOI 10.17487/RFC4122, July 2005, 894 . 896 [RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying 897 Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646, 898 September 2009, . 900 [RFC5870] Mayrhofer, A. and C. Spanring, "A Uniform Resource 901 Identifier for Geographic Locations ('geo' URI)", 902 RFC 5870, DOI 10.17487/RFC5870, June 2010, 903 . 905 [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, 906 DOI 10.17487/RFC6350, August 2011, 907 . 909 [RFC6351] Perreault, S., "xCard: vCard XML Representation", 910 RFC 6351, DOI 10.17487/RFC6351, August 2011, 911 . 913 [RFC7095] Kewisch, P., "jCard: The JSON Format for vCard", RFC 7095, 914 DOI 10.17487/RFC7095, January 2014, 915 . 917 [RFC7493] Bray, T., Ed., "The I-JSON Message Format", RFC 7493, 918 DOI 10.17487/RFC7493, March 2015, 919 . 921 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 922 Code: The Implementation Status Section", BCP 205, 923 RFC 7942, DOI 10.17487/RFC7942, July 2016, 924 . 926 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 927 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 928 May 2017, . 930 [RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data 931 Interchange Format", STD 90, RFC 8259, 932 DOI 10.17487/RFC8259, December 2017, 933 . 935 7.2. Informative References 937 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 938 A., Peterson, J., Sparks, R., Handley, M., and E. 939 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 940 DOI 10.17487/RFC3261, June 2002, 941 . 943 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 944 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 945 . 947 [RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", 948 RFC 3966, DOI 10.17487/RFC3966, December 2004, 949 . 951 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 952 Resource Identifier (URI): Generic Syntax", STD 66, 953 RFC 3986, DOI 10.17487/RFC3986, January 2005, 954 . 956 [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data 957 Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006, 958 . 960 [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, 961 DOI 10.17487/RFC5322, October 2008, 962 . 964 [RFC6473] Saint-Andre, P., "vCard KIND:application", RFC 6473, 965 DOI 10.17487/RFC6473, December 2011, 966 . 968 [RFC6474] Li, K. and B. Leiba, "vCard Format Extensions: Place of 969 Birth, Place and Date of Death", RFC 6474, 970 DOI 10.17487/RFC6474, December 2011, 971 . 973 [RFC6715] Cauchie, D., Leiba, B., and K. Li, "vCard Format 974 Extensions: Representing vCard Extensions Defined by the 975 Open Mobile Alliance (OMA) Converged Address Book (CAB) 976 Group", RFC 6715, DOI 10.17487/RFC6715, August 2012, 977 . 979 [RFC6869] Salgueiro, G., Clarke, J., and P. Saint-Andre, "vCard 980 KIND:device", RFC 6869, DOI 10.17487/RFC6869, February 981 2013, . 983 [RFC8605] Hollenbeck, S. and R. Carney, "vCard Format Extensions: 984 ICANN Extensions for the Registration Data Access Protocol 985 (RDAP)", RFC 8605, DOI 10.17487/RFC8605, May 2019, 986 . 988 Authors' Addresses 990 Robert Stepanek 991 FastMail 992 PO Box 234, Collins St West 993 Melbourne VIC 8007 994 Australia 996 Email: rsto@fastmailteam.com 998 Mario Loffredo 999 IIT-CNR 1000 Via Moruzzi,1 1001 56124 Pisa 1002 Italy 1004 Email: mario.loffredo@iit.cnr.it