--- 1/draft-ietf-jmap-jscontact-06.txt 2021-07-12 07:13:10.562386930 -0700 +++ 2/draft-ietf-jmap-jscontact-07.txt 2021-07-12 07:13:10.590387290 -0700 @@ -1,19 +1,19 @@ JMAP R. Stepanek Internet-Draft FastMail Intended status: Standards Track M. Loffredo -Expires: 29 November 2021 IIT-CNR - 28 May 2021 +Expires: 13 January 2022 IIT-CNR + 12 July 2021 JSContact: A JSON representation of contact data - draft-ietf-jmap-jscontact-06 + draft-ietf-jmap-jscontact-07 Abstract This specification defines a data model and JSON representation of contact card information that can be used for data storage and exchange in address book or directory applications. It aims to be an alternative to the vCard data format and to be unambiguous, extendable and simple to process. In contrast to the JSON-based jCard format, it is not a direct mapping from the vCard data model and expands semantics where appropriate. @@ -26,21 +26,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on 29 November 2021. + This Internet-Draft will expire on 13 January 2022. Copyright Notice Copyright (c) 2021 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights @@ -653,23 +653,23 @@ relevant country's postal system. * countryCode: "String" (optional). The ISO-3166-1 country code. * coordinates: "String" (optional) A [RFC5870] "geo:" URI for the address. * timeZone: "String" (optional) Identifies the time zone this address is located in. This either MUST be a time zone name registered in the IANA Time Zone Database (https://www.iana.org/ - time-zones), or it MUST be a valid TimeZoneId as defined in FIXME - . For the latter, a corresponding time zone MUST be defined in the - "timeZones" property. + time-zones), or it MUST be a valid TimeZoneId as defined in + [jscalendar]. For the latter, a corresponding time zone MUST be + defined in the "timeZones" property. * contexts: "Context[Boolean]" (optional). The contexts of the address information. In addition to the common contexts, allowed values are: - "billing" An address to be used for billing. - "postal" An address to be used for delivering physical items. The value for each key in the object MUST be "true". @@ -778,21 +778,21 @@ Type: "String[Boolean]" (optional). The set of free-text or URI categories that relate to the card. The set is represented as an object, with each key being a category. The value for each key in the object MUST be "true". 2.5.5. timeZones Type: "String[TimeZone]" (optional). Maps identifiers of custom time zones to their time zone definitions. For a description of this - property see the "timeZones" property definition in FIXME . + property see the "timeZones" property definition in [jscalendar]. 3. CardGroup MIME type: "application/jscontact+json;type=cardgroup" A CardGroup object represents a group of cards. Its members may be Cards or CardGroups. 3.1. Group properties @@ -871,20 +871,24 @@ TBD 6. Security Considerations TBD 7. References 7.1. Normative References + [jscalendar] + "JSCalendar: A JSON Representation of Calendar Data", + . + [RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046, DOI 10.17487/RFC2046, November 1996, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, .