--- 1/draft-ietf-jmap-jscontact-02.txt 2020-12-14 04:13:19.450487853 -0800 +++ 2/draft-ietf-jmap-jscontact-03.txt 2020-12-14 04:13:19.470488123 -0800 @@ -1,19 +1,19 @@ JMAP R. Stepanek Internet-Draft FastMail Intended status: Standards Track M. Loffredo -Expires: December 17, 2020 IIT-CNR - June 15, 2020 +Expires: June 17, 2021 IIT-CNR + December 14, 2020 JSContact: A JSON representation of contact data - draft-ietf-jmap-jscontact-02 + draft-ietf-jmap-jscontact-03 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 December 17, 2020. + This Internet-Draft will expire on June 17, 2021. Copyright Notice Copyright (c) 2020 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 @@ -252,22 +252,23 @@ Type: "NameComponent[]" (optional). The name components of the name of the entity represented by this JSCard. Name components SHOULD be ordered such that their values joined by whitespace produce a valid full name of this entity. A NameComponent has the following properties: o value: "String" (mandatory). The value of this name component. - o type: "String" (mandatory). The type of this name component. - Valid name component types are: + o type: "String" (mandatory). The type of this name component. The + value MUST be either one of the following values, registered in a + future RFC, or a vendor-specific value: * "prefix". The value is a honorific title(s), e.g. "Mr", "Ms", "Dr". * "personal". The value is a personal name(s), also known as "first name", "given name". * "surname". The value is a surname, also known as "last name", "family name".