]> IIT-CNR/Registro.it

Via Moruzzi,1 Pisa IT 56124 mario.loffredo@iit.cnr.it http://www.iit.cnr.it

ICANN

12025 Waterfront Drive, Suite 300 Los Angeles CA 90292 US gavin.brown@icann.org https://www.icann.org/

Applications and Real-Time Registration Protocols Extensions RDAP jCard JSContact This document describes an RDAP extension which represents entity contact information in JSON responses using JSContact.

This document specifies an extension to the Registration Data Access Protocol (RDAP) that allows RDAP servers to use JSContact to represent the contact information associated with entities in RDAP responses, instead of jCard . It also describes the process by which an RDAP server can transition from jCard to JSContact. RDAP query and response extensions are defined to facilitate the transition process.

According to the feedback from RDAP Pilot Working Group , a group of RDAP server implementers representing registries and registrars of generic TLDs, the most commonly raised implementation concern for both servers and client implementers, was related to the use of jCard to represent the contact information associated with entities. Working Group members reported jCard to be unintuitive, complicated to implement for both clients and servers, and incompatible with best practices for RESTful APIs. JSContact provides a simpler and more efficient representation for contact information with regard to time and effort saved in processing it. In addition, similarly to jCard, it provides a means to represent internationalized and unstructured contact information. Support for internationalized contact information has been recognised being necessary to facilitate the future internationalisation of registration data directory services.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

The JSContact specification defines a data model and JSON representation of contact 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 with jCard, it is not a direct mapping from the vCard data model and expands semantics where appropriate. JSContact differs from jCard in that it: follows an object-oriented rather than array-oriented approach; is simple to process; requires no extra work in serialization/deserialization from/to a data model; includes no "jagged" arrays; prefers maps rather than arrays to implement collections. provides guidance on the conversion of jCard into JSContact, and vice versa. shows JSContact counterparts for the most commonly used jCard properties in an RDAP response.

Since JSContact is a generalized representation of contact data, many of its capabilities are not optimized for use in RDAP responses. This document defines a usage profile for JSContact that simplifies the implementation for both clients and servers. The JSContact profile for RDAP is compliant with the rules described in . The profile properties are formally listed in . The information required to register the profile is described in . All types mentioned in this section refer to the JSContact specification (e.g., Card is the JSContact Card type).

Entity objects in RDAP responses MAY include a "jscontact_card" member whose value is a Card object instead of the "vCardArray" member defined in . Servers returning the "jscontact_card" member in their response MUST include the string "jscontact" in the "rdapConformance" array.

This extension supports the following versioning types as defined in : Opaque Versioning: The Opaque Extension Versioning Identifier is "jscontact". Semantic Versioning: The Semantic Extension Versioning Identifier is "jscontact-0.3". Note that this extension identifier's version value may differ from the Card version member value. In fact, the former is related to changes in this RDAP extension, while the latter is related to changes in the JSContact specification. NOTE: Please change the Semantic Versioning value to "jscontact-1.0" prior to publication as an RFC.

The information required to register the Card "version" member value in the "RDAP JSON Values" registry is described in .

The Card "kind" member value MUST be "individual" (default) or "org" to represent an individual or an organization, respectively.

The Card "language" member SHOULD be set when localizations are specified (i.e. the "localizations" member is not null).

The Card "name" member MUST include the "full" member and MAY include the "components" member to specify the name components of an individual. The NameComponent type MUST include only the "kind" and "value" members. The "kind" member value MUST be "given" or "surname".

The Organization type MUST include only the "org" member.

The Address type MUST include at least one between the "full", "components" and "countryCode" members. The AddressComponent type MUST include only the "kind" and "value" members. The "kind" member value MUST be "name", "locality", "region" or "postcode".

The EmailAddress type MUST include only the "address" member.

The Phone type MUST include the "number" member and MAY include the "features" member. The PhoneFeature type value MUST be "voice" or "fax". When the "features" member is missing, the phone number is assumed to be a voice number.

The Link type MUST include the "uri" member and MAY include the "kind" member. The "kind" member value MUST be "contact".

Since most of the JSContact collections are represented as maps, map keys must be defined. A JSContact map key MUST comply with the definition of the Id type (see Section 1.4.1 of ). To aid interoperability, RDAP providers MUST use the following keys related to string values and labels defined in : "org" in the "organizations" map when there is a single <contact:org> element; "addr" in the "addresses" map when there is a single <contact:addr> element; "email" in the "emails" map for the <contact:email> element; "voice" in the "phones" map for the <contact:voice> element; "fax" in the "phones" map for the <contact:fax> element. In cases where both internationalized and localized versions of organization, postal address, and email exist, the related map MUST include the internationalized version, while the localized version MUST be included in the localizations map, as described in . Additional keys of the "links" map that MUST be used to represent contact links which result from converting jCard "uri" and "contact-uri" properties are: "url" used for the unique or preferred contact url (e.g. a web site). The "kind" member of the Link object MUST NOT be set; "contact-uri" used for the contact uri as defined in . The "kind" member of the Link object MUST be set to "contact". The information required to register the JSContact Id values in the "RDAP JSON Values" registry is described in . Any additional key used for the above maps SHOULD conform with the following scheme: "<registered key>-<sequential number>". For example, a phones map containing three voice numbers would contain the following keys: "voice", "voice-1", "voice-2". The keys SHOULD remain stable until the associated contact information is changed. Any gaps in the numbering MAY only occur when redaction is applied.

If present, the localized versions of name, organization, postal address and email MUST be added to the "localizations" map. With reference to the definition of localization in , an RDAP response with JSContact content MUST expand all localizations (i.e. a nested PatchObject key like "{key1}/{key2}/.../{keyN}" is not allowed). The following is an elided example of an RDAP entity lookup response including a Card that includes localized version for name, organization and postal address (See PDF for non-ASCII character string).

... "jscontact_card": { "@type": "Card", "version": "2.0", "language": "en", "name": { "full": "Vasya Pupkin" }, "organizations": { "org": { "name": "My Company" } }, "addresses": { "addr": { "components": [ { "kind": "name", "value": "1 Street" }, { "kind": "locality", "value": "Kyiv" } ], "countryCode": "UA" } }, "localizations": { "ua": { "addresses": { "addr": { "components": [ { "kind": "name", "value": "1, Улица" }, { "kind": "locality", "value": "Киев" } ], "countryCode": "UA" } }, "name": { "full": "Вася Пупкин" }, "organizations": { "org": { "name": "Моя Компания" } } } } } ...

The properties of the JSContact profile registered in the JSContact Profile registry as described in are the following:

Property Name	Property Context	Restricted Attributes	Restricted Enum Values	Restricted PatchObject Keys
language	Card
kind	Card		individual, org
name	Card
full	Name	mandatory
components	Name
kind	NameComponent		given, surname
value	NameComponent
organizations	Card
name	Organization
addresses	Card
full	Address
countryCode	Address
components	Address
kind	AddressComponent		name, locality, region, postcode, country
value	AddressComponent
emails	Card
address	EmailAddress
phones	Card
features	Phone		voice, fax
number	Phone
links	Card
kind	Link		contact
uri	Link
localizations	Card			yes

For each property, the "Restricted Property Type" field is empty. To be consistent with what is stated in Section 2.1 of , clients SHOULD ignore JSContact properties other than these.

The following is an example of an RDAP entity including a Card.

{ "rdapConformance": [ "rdap_level_0", "jscontact" ], "objectClassName": "entity", "handle":"XXXX", "jscontact_card":{ "@type": "Card", "version": "2.0", "name": { "full": "Joe User", "components": [ { "kind": "given", "value": "Joe" }, { "kind": "surname", "value": "User" } ] }, "organizations": { "org": { "name": "Org Example" } }, "addresses": { "addr": { "components": [ { "kind": "name", "value": "Main Street 1" }, { "kind": "locality", "value": "Ludwigshafen am Rhein" }, { "kind": "region", "value": "Rhineland-Palatinate" }, { "kind": "postcode", "value": "67067" }, { "kind": "country", "value": "Germany" } ], "countryCode": "DE" }, "addr-1": { "full": "Somewhere Street 1 Mutterstadt 67112 Germany" } }, "phones": { "voice": { "number": "tel:+49-1522-3433333" }, "fax": { "features": { "fax": true }, "number": "tel:+49-30-901820" } }, "emails": { "email": { "address": "joe.user@example.com" } }, "links": { "url": { "uri": "https://www.example.com" }, "contact-uri": { "kind": "contact", "uri": "mailto:contact@example.com" } } }, "roles":[ "registrar" ], "publicIds":[ { "type":"IANA Registrar ID", "identifier":"1" } ], "links":[ { "value":"https://example.com/entity/XXXX", "rel":"self", "href":"https://example.com/entity/XXXX", "type" : "application/rdap+json" } ], "events":[ { "eventAction":"registration", "eventDate":"1990-12-31T23:59:59Z" } ], "asEventActor":[ { "eventAction":"last changed", "eventDate":"1991-12-31T23:59:59Z" } ] }

The client MAY request the server to include the "jscontact_card" member in the RDAP response by using only one of the following HTTP elements: the "versioning" query parameter as defined in ; the RDAP media type's "extensions" parameter as defined in . Their usage in the transtion from jCard to JSContact is further explained in .

The use of JSContact updates the mappings of two reverse search properties, namely "fn" and "email", defined in . Such new mappings are registered in the Reverse Search Mapping registry as described in .

RDAP allows servers to communicate service information to clients through notices. According to Section 4.3 of , an RDAP response may contain one or more notice objects. Each notice may include a set of link objects, which can be used to provide clients with references. These link objects may have a "rel" member which defines the relationship between resources, as described in Section 4 of . The transition process outlined in this document uses the "alternate" link relation type. The information about the specifications used in the construction of the response is also described by the strings that appear in the "rdapConformance" array of the RDAP response.

The transition procedure consists of three contiguous stages. During the procedure, the presence of the string "jscontact" in the "rdapConformance" array indicates that JSContact is returned instead of jCard. The date and time format used to notify clients about the stages of this procedure is defined in .

The procedure described in this document aims to achieve the following goals: only one contact representation would be included in the response; the response would always conform to because: since the "jscontact_card" member is a response extension, its presence would be signaled by the string "jscontact" in the "rdapConformance" array; since "vcardArray" member is optional in a response, its absence would be allowed; clients would be informed about the transition timeline; the backward compatibility would be ensured throughout the transition; servers and clients could perform their transitions independently.

This stage corresponds to providing jCard as the default contact card . The RDAP server is not able to provide an alternate format for contacts. The "rdapConformance" array MUST NOT contain the string "jscontact".

During this stage, the server returns jCard by default, but the RDAP server will return JSContact if the client requests it through one of the methods described in . The "rdapConformance" array MUST contain the string "jscontact" if JSContact is returned. From this stage onward, the RDAP server MUST include the string "jscontact" in the "rdapConformance" array of the help response to signal clients that JSContact can be returned instead of jCard. If JSContact is not requested, the RDAP server SHOULD include a notice whose type member is set to "jCard sunset end". This notice contains a description that reports the jCard sunset end date and time, and an OPTIONAL link to the corresponding JSContact-based response requested via the method used by the client to negotiate extensions (). If neither method was used, the RDAP server includes links for both methods ().

"notices": [ { "type": "jCard sunset end", "description": ["2025-12-31T23:59:59Z"], "links": [ { "value": "https://example.net/entity/XXXX", "rel": "alternate", "type": "application/rdap+json", "href": ".../entity/XXXX?versioning=versioning-0.2,jscontact-0.3" }, { "value": "https://example.net/entity/XXXX", "rel": "alternate", "type": "application/rdap+json;exts_list=\"rdap_level_0 jscontact\"", "href": "https://example.net/entity/XXXX" } ] } ]

This stage corresponds to providing JSContact as the default format for contact data. The "rdapConformance" array always contains the string "jscontact". The request for JSContact through any method described in MUST be ignored. The RDAP server MUST include the string "noJcard" in the "rdapConformance" array of the help response to signal clients that jCard is no longer returned. The RDAP server SHOULD also include a notice whose type member is set to "jCard deprecation" whose description reports the verbatim string "jCard has been deprecated" ().

"notices": [ { "type": "jCard deprecation", "description": ["jCard has been deprecated"], } ]

The length of the jCard sunset period is not fixed by this specification. Anyway, RDAP providers are RECOMMENDED to monitor the server log to figure out whether the declared time needs to be changed to meet client requirements.

NOTE: Please remove this section and the reference to RFC 7942 prior to publication as an RFC. This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in RFC 7942 . The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist. According to RFC 7942, "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit".

Responsible Organization: Institute of Informatics and Telematics of National Research Council (IIT-CNR)/Registro.it Location:https://rdap.pubtest.nic.it/ Description: This implementation includes support for RDAP queries using data from the public test environment of .it ccTLD. Level of Maturity: This is an "alpha" test implementation. Coverage: This implementation includes all of the features described in this specification. Contact Information: Mario Loffredo, mario.loffredo@iit.cnr.it

Responsible Organization: Institute of Informatics and Telematics of National Research Council (IIT-CNR)/Registro.it Location: https://web-rdap.pubtest.nic.it/ Description: This is a Javascript web-based RDAP client. RDAP responses are retrieved from RDAP servers by the browser, parsed into an HTML representation, and displayed in a format improving the user experience. RDAP responses containing JSContact objects are handled identically to those containing jCard objects. Raw versions of RDAP responses including either jCard or JSContact objects are provided. Level of Maturity: This is an "alpha" test implementation. Coverage: This implementation includes all of the features described in this specification. Contact Information: Francesco Donini, francesco.donini@iit.cnr.it

Location: https://client.rdap.org/ Description: This is a web-based "single page" RDAP client. RDAP responses are retrieved from RDAP servers by the browser, and parsed into an HTML representation. RDAP responses containing JSContact objects are handled identically to those containing jCard objects. Level of Maturity: This is an "alpha" test implementation. Coverage: This implementation implements client support for parsing JSContact objects in RDAP responses. Contact Information: Gavin Brown, feedback@rdap.org

Responsible Organization: CentralNic Group PLC Location: https://rdap.centralnic.com/{tld} Description: This server is the product RDAP service for all top-level domains on the CentralNic registry platform. Level of Maturity: Production quality. Coverage: This implementation includes all of the features described in this specification. Contact Information: support@centralnic.com

Responsible Organization: ICANN Location: https://github.com/icann/icann-rdap Description: ICANN RDAP contains an RDAP client, server, and common libraries. Level of Maturity: Mature. Coverage: This implementation includes all the features described in this specification, except support for semantic versioning and the provision of reverse search mapping. Contact Information: globalsupport@icann.org

IANA is requested to register the following values in the RDAP Extensions Registry: Extension identifier: jscontact Registry operator: Any Published specification: This document. Contact: IETF <iesg@ietf.org> Intended usage: This extension identifier is used as prefix for the "jscontact_card" member returned in the JSON response . Extension identifier: noJcard Registry operator: Any Published specification: This document. Contact: IETF <iesg@ietf.org> Intended usage: This extension identifier is used by the server to signal clients that jCard is no longer returned.

With regard to the fields of the RDAP JSON Values Registry, the "JSContact version value" type SHALL be used to register the RDAP values for the Card version member while the "JSContact Id value" type SHALL be used to register the RDAP values for the JSContact Id type as defined in . IANA is requested to register the following values in this registry: jCard sunset end notice and remark type This notice signals clients that JSContact can be returned upon request. IETF iesg@ietf.org This document jCard deprecation notice and remark type This notice signals clients that jCard is no longer returned. IETF iesg@ietf.org This document 2.0 JSContact version value The JSContact version to use in implementing this specification. IETF iesg@ietf.org This document org JSContact Id value The key in the JSContact "organizations" map identifiying the contact organization. IETF iesg@ietf.org This document addr JSContact Id value The key in the JSContact "addresses" map identifiying the unique or preferred contact postal address. IETF iesg@ietf.org This document email JSContact Id value The key in the JSContact "emails" map identifiying the unique or preferred contact email address. IETF iesg@ietf.org This document voice JSContact Id value The key in the JSContact "phones" map identifiying the unique or preferred contact voice number. IETF iesg@ietf.org This document fax JSContact Id value The key in the JSContact "phones" map identifiying the unique or preferred contact fax number. IETF iesg@ietf.org This document url JSContact Id value The key in the JSContact "links" map identifiying the unique or preferred url. IETF iesg@ietf.org This document contact-uri JSContact Id value The key in the JSContact "links" map identifiying the contact uri as defined in . IETF iesg@ietf.org This document

IANA is requested to register the following entries in the RDAP Reverse Search Mapping Registry: domains, nameservers, entities, ips, autnums entity fn $.entities[*].jscontact_card.[name.full, localizations.*.name.full] IETF iesg@ietf.org This document domains, nameservers, entities entity email $.entities[*].jscontact_card.[emails.email.address, localizations.*.emails.email.address] IETF iesg@ietf.org This document

IANA is requested to register the following entry in the "JSContact Profile" registry : rdap 1

Unlike jCard, the formatted name as well as any other personally identifiable information is not required in JSContact 1.0 . JSContact version 2.0 makes also uid property optional. Therefore, with reference to what is described in , properties can be redacted by Removal Method.

The extension described in this document does not provide any security services beyond those described by .

The authors would like to acknowledge the following individuals for their contributions to this document: Jasdip Singh, Andrew Newton, Marc Blanchet, Rick Wilhelm, Pawel Kowalik and Francesco Donini.

&RFC2119; &RFC3339; &RFC5733; &RFC6350; &RFC7095; &RFC9083; &RFC7942; &RFC8174; &RFC8288; &RFC9536; &RFC9553; &RFC9555; &I-D.ietf-regext-rdap-versioning; &I-D.ietf-regext-rdap-x-media-type; &I-D.ietf-calext-jscontact-profiles; &I-D.ietf-calext-jscontact-uid; IANA IANA IANA &RFC8605; &RFC9535; &RFC9537; ICANN RDAP Pilot WG

Provided that the keys defined in are used for the JSContact maps, the mapping between the most commonly used jCard properties in an RDAP response and their JSContact counterparts is shown in the following. The mapping is done through the use of JSONPath expressions . fn Section 6.2.1 of $..vcardArray[1][?(@[0]=='fn')][3] Name.full Section 2.2.1 of $..jscontact_card.[name.full, localizations.*.name.full] "family name" component of n Section 6.2.2 of $..vcardArray[1][?(@[0]=='n')][3][0] "postOfficeBox" NameComponent of Name.components Section 2.5.1 of $..jscontact_card.[name.components[?(@.kind=='surname')].value, localizations.*.name.components[?(@.kind=='surname')].value] "given name" component of n Section 6.2.2 of $..vcardArray[1][?(@[0]=='n')][3][1] "given" NameComponent of Name.components Section 2.5.1 of $..jscontact_card.[name.components[?(@.kind=='given')].value, localizations.*.name.components[?(@.kind=='given')].value] n Section 6.3.1 of $..vcardArray[1][?(@[0]=='n')] Name Section 2.5.1 of $..jscontact_card.[name, localizations.*.name] org Section 6.6.4 of $..vcardArray[1][?(@[0]=='org')][3] Organization.name Section 2.2.3 of $..jscontact_card.[organizations.org.name, localizations.*.organizations.org.name] tel with type="voice" Section 6.4.1 of $..vcardArray[1][?(@[1].type=='voice')][3] Phone.number Section 2.3.3 of $..jscontact_card.phones.voice.number tel with type="fax" Section 6.4.1 of $..vcardArray[1][?(@[1].type=='fax')][3] Phone.number Section 2.3.3 of $..jscontact_card.phones.fax.number email Section 6.4.2 of $..vcardArray[1][?(@[0]=='email')][3] Email.address Section 2.3.1 of $..jscontact_card.[emails.email.address, localizations.*.emails.email.address] "label" parameter of adr Section 6.3.1 of $..vcardArray[1][?(@[0]=='adr')][1].label Address.full Section 2.5.1 of $..jscontact_card.[addresses.adr.full, localizations.*.addresses.adr.full] "post office box" component of adr Section 6.3.1 of $..vcardArray[1][?(@[0]=='adr')][3][1] "postOfficeBox" AddressComponent of Address.components Section 2.5.1 of $..jscontact_card.[addresses.addr.components[?(@.kind=='postOfficeBox')].value, localizations.*.addresses.addr.components[?(@.kind=='postOfficeBox')].value] "street address" component of adr Section 6.3.1 of $..vcardArray[1][?(@[0]=='adr')][3][2] "name" AddressComponent of Address.components Section 2.5.1 of $..jscontact_card.[addresses.addr.components[?(@.kind=='name')].value, localizations.*.addresses.addr.components[?(@.kind=='name')].value] "locality" component of adr Section 6.3.1 of $..vcardArray[1][?(@[0]=='adr')][3][3] "locality" AddressComponent of Address.components Section 2.5.1 of $..jscontact_card.[addresses.addr.components[?(@.kind=='locality')].value, localizations.*.addresses.addr.components[?(@.kind=='locality')].value] "region" component of adr Section 6.3.1 of $..vcardArray[1][?(@[0]=='adr')][3][4] "region" AddressComponent of Address.components Section 2.5.1 of $..jscontact_card.[addresses.addr.components[?(@.kind=='region')].value, localizations.*.addresses.addr.components[?(@.kind=='region')].value] "postal code" component of adr Section 6.3.1 of $..vcardArray[1][?(@[0]=='adr')][3][5] "postcode" AddressComponent of Address.components Section 2.5.1 of $..jscontact_card.[addresses.addr.components[?(@.kind=='postcode')].value, localizations.*.addresses.addr.components[?(@.kind=='postcode')].value] "country name" component of adr Section 6.3.1 of $..vcardArray[1][?(@[0]=='adr')][3][6] "country" AddressComponent of Address.components Section 2.5.1 of $..jscontact_card.[addresses.addr.components[?(@.kind=='country')].value, localizations.*.addresses.addr.components[?(@.kind=='country')].value] "cc" parameter of adr Section 3.1 of $..vcardArray[1][?(@[0]=='adr')][1].cc Address.countryCode Section 2.5.1 of $..jscontact_card.[addresses.addr.countryCode, localizations.*.addresses.addr.countryCode] adr Section 6.3.1 of $..vcardArray[1][?(@[0]=='adr')] Address Section 2.5.1 of $..jscontact_card.[addresses.addr, localizations.*.addresses.addr] contact-uri Section 2.1 of $..vcardArray[1][?(@[0]=='contact-uri')] Link.uri Section 2.6.3 of $..jscontact_card.links.contact-uri.uri url Section 6.7.8 of $..vcardArray[1][?(@[0]=='url')] Link.uri Section 2.6.3 of $..jscontact_card.links.url.uri

Changed category from "Best Current Practice" to "Standards Track" Replaced the example of Changed the title of the "Migration from JCard to JSCard" section to "Transition Considerations" Added "Query Parameters" section. Updated Updated Rearranged the description of stage 1 in Changed the names of the transition stages 1 and 2 Corrected examples Changed the rdapConformance tag "jscard_level_0" to "jscard" Removed the "Best Practices for deprecating a REST API features" section,but added a useful reference.

Removed the sentence "which cannot be represented using jCard" in .

Updated section "Conventions Used in This Document". Updated the contact in "IANA Considerations" section. Changed the reference draft-loffredo-calext-jscontact-vcard to draft-ietf-calext-jscontact-vcard. Added reference to RFC8174. Other minor edits.

Updated the reference draft-dalal-deprecation-header to draft-ietf-httpapi-deprecation-header.

Ported from draft-loffredo-regext-rdap-jcard-deprecation-04 renamed to draft-ietf-regext-rdap-jscontact-00.

Updated and .

Updated and .

Replaced references to obsolete RFC7482 and RFC7483 with RFC9082 and RFC9083. Updated and .

Changed the references to Internet Drafts. Added an example showing how localizations are treated in JSContact. Changed the position of section "Goals" in . Added three more implementations to . Changed the rdapConformance tag "jscard" to "jscard_0" Added clarifications addressing the feedback provided by Jasdip Singh about version -03. Added . Other minor edits.

Updated to make it compliant with draft-ietf-jmap-jscontact-09.

Reviewed the notices presented in stages.

Corrected the JSON Pointer expressions in . Other minor edits.

Corrected a nit in . Removed the reference to draft-ietf-httpapi-deprecation-header. Replaced the "deprecation" link relation type with "related". Moved the references to JSContact drafts to the "Normative References" section.

Updated the references to JSContact drafts due to the transfer from JMAP to CalExt.

Updated to make it compliant with draft-ietf-calext-jscontact-02.

Added Appendix "jCard-JSContact Mapping".

Renamed the "jscard" property to "jscard_0". Corrected JSONPath expressions in .

Reverted the names of response extension, the rdapConformance tag and extension identifier from "jscard_0" to "jscard". Corrected by removing initial '/' character from JSONPath notations related to localizations.

Corrected by replacing "online" property with "cryptoKeys" and "links" properties.

Corrected , and to make them compliant with draft-ietf-calext-jscontact-06. Removed mention of JSContact CardGroup object. Renamed and changed . Added .

Corrected , and to make them compliant with draft-ietf-calext-jscontact-06. Removed mention of JSContact CardGroup object. Renamed and changed . Added .

Replaced JSContact "type" with "kind" in figures. Removed "jCard deprecation" stage and "jcard" query parameter. Renamed "jCard deprecated" stage into "jCard deprecation". Rephrased . Corrected JSContact examples based on draft-ietf-calext-jscontact-11. Fixed nits.

Fixed , , and to make them compliant with draft-ietf-calext-jscontact-16 and purge them of the JSContact properties which are hardly used in RDAP. Rearranged . Added other mapping correspondences to .

Updated references. Updated Gavin Brown's contact info. Removed from the notices field the optional link documenting the transition procedure. Added text to . Added a reference to RFC9553 section defining the Id type. Tagged all BCP14 keywords. Changed the example in Figure 2. Added . Changed by removing the sentence about the duration of the transition process.

Turned the draft status into "Experimental". Changed "@version" to "version" in the examples. Rearranged the content of the "Query Parameters" section and renamed it into "Request for JSContact". Added . Added . Rearranged . Rearranged . Removed from the "FOR DISCUSSION" item. Added to a notice signaling the jCard deprecation. Changed the fixed literal to redact the URI in . Removed an informative reference and the first paragraph of including it.

Renamed the "jscard" extension identifier into "jscontact". Renamed the "jscard" property into "jscontact_card". Replaced any instance of the verbatim string "JSCard" with "JSContact". Rephrased by removing "1.0" as a mandatory value for the JSContact version property in RDAP and adding the value to the "RDAP JSON Values" registry. Corrected link in . Minor editorial changes.

Added the "Experimental Status" section. Changed the controller of IANA registies from IESG to IETF. Replaced "rdap-x" with "rdap" in the rdap-x media type. Minor editorial changes.

Changed JSContact version "1.0" to "2.0". Removed any reference to the JSContact uid property. Rephrased text of . Removed JSContact properties from examples that are not included in the RDAP profile for JSContact. Added a section about the registration of the JSContact profile for RDAP. Added ips and autnums to the searchable resource types of . Minor editorial changes.

Revised the "Experimental Status" section. Revised the registration of the JSContact profile for RDAP. Added a section that formally lists the profile properties. Added the handling and registration of noJcard extension identifier. Changed the notice used in the transaction process by changing the "title" property into "type" and registered the values in the "RDAP JSON Values" registry. Changed the naming scheme for map keys other than those predefined and clarified that those keys should be stable. Revised the "Security Considerations" section and renamed it into "Privacy Considerations". Added a "Security Considerations" section presenting no substantial implication on scurity. Updated the "Acknowledgements" section. Minor editorial changes.

Changed the status to "Standards Track". Removed the "Experimental Status" section and arranged references accordingly. Corrected example in . Added . Added references to IANA registries.