| Internet-Draft | vCard JSContact Extensions | July 2022 |
| Stepanek & Loffredo | Expires 12 January 2023 | [Page] |
This document defines a set of new properties for vCard and extends the use of existing ones. Their primary purpose is to align the same set of features between the JSContact and vCard formats, but the new definitions also aim to be useful within just the vCard format.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
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 12 January 2023.¶
Copyright (c) 2022 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 and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
This document is a work in progress. The list of new or updated properties and parameters is likely to be incomplete. This section is removed from the document before publication.¶
The JSContact [ref-jscontact] format aims to be an alternative to the vCard [RFC6350] format for representation of contact and addressbook data. As such, it introduces new semantics that are not covered in the current definition of vCard and its various extensions. Converting contact data between the two formats is defined in [ref-jscontact-vcard] with the goal of not loosing any semantics during conversion. In order to do so, this document defines a new set of properties for vCard and extends existing definitions.¶
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 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
This property is defined by the following notation:¶
created = "CREATED" createdparam
":" timestamp CRLF
createdparam = *(
;
; The following is OPTIONAL,
; but MUST NOT occur more than once.
;
(";" "VALUE" "=" "TIMESTAMP") /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" any-param)
;
)
¶
CREATED:20220705093412Z CREATED;VALUE=TIMESTAMP:20211022T140000-05¶
This property defines the grammatical gender that the contact prefers to be addressed by or referred at. Many human languages use grammatical genders in salutations and other language constructs. For example, the German language typically distinguishes between the gender of the recipient in both formal and informal salutations. The allowed values for this property aim to cover grammatical genders for the the majority of human languages. Future RFCs MAY define additional values if the current selection is found to be inadequate.¶
This property is defined by the following notation:¶
gram-gender = "GRAMMATICAL-GENDER" gram-gender-param
":" gram-gender-value CRLF
gram-gender-param =
*(
;
; The following is OPTIONAL,
; but MUST NOT occur more than once.
;
(";" language-param) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" any-param)
;
)
gram-gender-value = "ANIMATE" /
"FEMALE" /
"INANIMATE" /
"MALE" /
"NEUTER" /
x-value
¶
GRAMMATICAL-GENDER:NEUTER¶
LANG parameter to the property. In absence
of this parameter, implementations need to attempt detecting the
language by text analysis. The LOCALE property allows
to define a default locale in which such property values can be
assumed to be written in.¶
This property is defined by the following notation:¶
locale = "LOCALE" any-param
":" lang-tag CRLF
lang-tag = TEXT ; MUST be a valid Language-Tag value as
; specified in section 2.1 RFC5646
¶
CREATED:20220705093412Z CREATED;VALUE=TIMESTAMP:20211022T140000-05¶
This property is defined by the following notation:¶
pronouns = "PRONOUNS" pronouns-param
":" text CRLF
pronouns-param =
*(
;
; The following is OPTIONAL,
; but MUST NOT occur more than once.
;
(";" language-param) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" any-param)
;
)
¶
PRONOUNS=they/them PRONOUNS;LANG=de:sie PRONOUNS:xe/xir¶
This parameter uniquely identifies a property among all of its siblings with the same name within a calendar component. A valid PROP-ID value must be of 1 and a maximum of 255 octets in size, and it MUST only contain the ASCII alphanumeric characters (A-Za-z0-9), hyphen (-), and underscore (_). The identifier only has the purpose to uniquely identify siblings, its value has no other meaning. If an application makes use of PROP-ID it SHOULD assign a unique identifier to each sibling property of the same name within their embedding component. The same identifier MAY be used for properties of a different name, and it MAY also be assigned to a same-named property that is not a sibling.¶
Resolving duplicate identifier conflicts is specific to the application. Similarly, handling properties where some but not all siblings have a PROP-ID is assigned, is application-specific.¶
prop-id-param = "PROP-ID" "=" 1*255(ALPHA / DIGIT / "-"/ "_")¶
PHOTO;PROP-ID=p827:data:image/jpeg;base64,MIICajCCAdOgAwIBAg
<...remainder of base64-encoded data...>
¶
This section will be filled at a later stage.¶
This section will be filled at a later stage.¶