]> Mozilla Corporation

650 Castro Street, Suite 300 Mountain View CA 94041 USA mozilla@kewis.ch http://www.mozilla.org/

Applications This specification defines "jCard", a JSON format for vCard data.

The vCard data format has gone through multiple revisions, most recently vCard 4. The goal followed by this format is the capture and exchange of information normally stored within an address book or directory application. As certain similarities to the iCalendar data format exist it makes sense to define a JSON-based data format for vCards that is similar to the jCal format defined in . The purpose of this specification is to define "jCard", a JSON format for vCard data. One main advantage to using a JSON-based format as defined in over the classic vCard format is easier processing for JavaScript based widgets and libraries, especially in the scope of web-based applications. The key design considerations are essentially the same as those for and , that is: Round-tripping (converting a vCard instance to jCard and back) will give the same semantic result as the starting point. For example, all components, properties and property parameters are guaranteed to be preserved, with the exception of those which have default values. Ordering of elements will not necessarily be preserved. Preserve the semantics of the vCard data. While a simple consumer can easily browse the data in jCard, a full understanding of vCard is still required in order to modify and/or fully comprehend the directory data. Ability to handle many extensions to the underlying vCard specification without requiring an update to this document.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in . The underlying format used for jCard is JSON. Consequently, the terms "object" and "array" as well as the four primitive types are to be interpreted as described in Section 1 of . Some examples in this document contain "partial" JSON documents used for illustrative purposes. In these examples, three periods "..." are used to indicate a portion of the document that has been removed for compactness.

This section describes how vCard data is converted to jCard using a simple mapping between the vCard data model and JSON elements.

vCard uses a line folding mechanism to limit lines of data to a maximum line length (typically 72 characters) to ensure maximum likelihood of preserving data integrity as it is transported via various means (e.g., email) - see Section 3.2 of . Prior to converting vCard data into jCard all folded lines MUST be unfolded. vCard data uses an "escape" character sequence for text values and property parameter values. When such text elements are converted into jCard the escaping MUST be removed. See Section 3.4 of . The only escaping that may be applied is any escaping mandated by JSON. One key difference in the formatting of values used in vCard and jCard is that in jCard the specification uses date/time values aligned with the complete representation, extended format of .

In certain cases it makes sense to group a sequence of vcard objects into a stream of objects. While the vCard 4 standard doesn't define a stream of vcard objects, having one makes it easier to identify multiple jCard objects and also ensures compatibility to jCal. A jCard stream is identified by an array, where the first element is the string "vcardstream". Subsequent elements are vCard objects represented as described in this document. In the typical case where there is only one vCard object, encapsulation inside a "vcardstream" array MAY be omitted. A vCard stream can contain one or more vCard objects. Each vCard object, delimited by "BEGIN:VCARD" and "END:VCARD", is represented in JSON as a fixed length array with two elements: The string "vcard" An array of jCard properties The representation of a vCard object in JSON will be named "vcard component" throughout this document.

Example:

vCard objects are comprised of a set of "properties", "parameters" and "values". The top level of a vCard object contains "properties". A "property" has a "value" and a set of zero or more "parameters". vCard objects are delimited by the general properties "BEGIN" and "END" with the fixed value "VCARD" as defined in Section 6.1.1 and 6.1.2 of . In addition, the vCard format is versioned, therefore the "version" property is mandatory. To comply with Section 6.7.9 of , the value of the version property MUST be "4.0".

Each individual vCard property is represented in jCard by an array with three fixed elements, followed by one or more additional elements, depending on if the property is a multi-value property as described in Section 3.3 of . The array consists of the following fixed elements: The name of the property as a string, but in lowercase. An object containing the parameters as described in . The type identifier string of the value, in lowercase. The remaining elements of the array are used for the value of the property. For single-value properties, the array MUST have exactly four elements, for multi-valued properties as described in there can be any number of additional elements. The array describing the property can then be inserted into the array designated for properties in the "vcard" component.

Example:

The property parameters in the second element of the property array associate a set of parameter names with their respective value. Parameters are further described in . To allow for a cleaner implementation, the parameter object MUST be present even if there are no parameters. In this case, an empty object MUST be used. As described in , it is important to check the data type of the value even if it is assumed to be a string in most cases. The value could turn out to be a structured value, in which case the type is an array.

This section describes some properties that have special handling when converting to jCard.

Various vCard properties defined in , for example the "CATEGORIES" property, are defined as multi-valued properties. In jCal these properties are added as further members of the array describing the property. Note that additional multi-valued properties may be added in extensions to the iCalendar format.

Example:

Section 3.3 defines a grouping construct that is used to group related properties together. In jCard, a new GROUP parameter is introduced. Its purpose is to eliminate the need for group syntax in jCard, thus unifying the general syntax with that of jCal. <empty> GROUP To simplify the jCard format. The GROUP parameter is reserved for the exclusive use of the jCard format [RFCTODO] Replace RFCTODO with the target RFC number for this document. It MUST NOT be used in plain vCard , nor in xCard . In jCard, the parameter's value is a single opaque string. Conversion rules are as follows: From vCard to jCard, the group construct (see , Section 3.3, Page 7) is removed. In its place, the GROUP parameter is added (lowercased, as any other parameter). Its value is a string corresponding to the group name. The name's case MUST be preserved intact. From jCard to vCard, the reverse procedure is performed. The GROUP parameter MUST NOT appear in the resulting vCard. (Not applicable)

is equivalent to:

The vCard specification defines properties with structured values, for example GENDER or ADR, where each text component of the structured value is delimited by the SEMICOLON character. In jCard, the property value is an array containing one element for each text component.

vCard Example:

jCard Example:

Some vCard properties, for example ADR, also allow a structured value element that itself has multiple values. In this case, the element of the array describing the structured value is itself an array with one element for each of the component's multiple values.

vCard Example:

jCard Example:

In both cases, the array element values MUST have the primative type that matches the jCard type identifier. In , there are only structured text values and thus only JSON strings are used. Extensions may for example define structured number or boolean values, where JSON number or boolean types MUST be used. If a multi-valued text component is changed to hold only one value, the text component SHOULD be represented as a single primative value, but MAY be represented as an array with a single primative value. Similarly, structured values that consist of two text components with one being optional (for example, GENDER) MAY be represented as a single text value. Therefore, implementors SHOULD check even known property values for structured information. This is especially important for languages where accessing array members is done by the same construct as accessing characters of a string.

Examples:

Property parameters are represented as a JSON object where each key-value pair represents the vCard parameter name and its value. The name of the parameter MUST be in lowercase, the original case of the parameter value MUST be preserved. For example, the "LANG" property parameter is represented in jCard by the "lang" key. Any new vCard parameters added in the future will be converted in the same way.

Example:

vCard defines a "VALUE" property parameter (Section 5.2 of ). This property parameter MUST NOT be added to the parameters object. Instead, the value type is always explicitly mentioned in the third element of the array describing the property. Thus, when converting from vCard to jCard, any "VALUE" property parameters are skipped. When converting from jCard into vCard, the appropriate "VALUE" property parameter MUST be included in the vCard property if the value type is not the default value type for that property.

In , some parameters allow using a COMMA-separated list of values. To ease processing in jCard, the value to such parameters MUST be represented in an array containing the separated values. The array elements MUST be string values. Single-value parameters SHOULD be represented using a single string value, but an array with one element MAY also be used. An example for a such parameter is the vCard "SORT-AS" parameter, more such parameters may be added in extensions. DQUOTE characters used to encapsulate the separated values MUST NOT be added to the jCard parameter value.

Example 1:

The type of a vCard value is explicitly mentioned in the third element of the array describing a jCard property. The actual values of the property can be found in the fourth and following elements of the array.

vCard "TEXT" property values are represented by a property with the type identifier "text". The value elements are JSON strings. For details on structured text values, see .

vCard "URI" property values are represented by a property with the type identifier "uri". The value elements are JSON strings.

vCard "DATE" property values are represented by a property with the type identifier "date". The value elements are JSON strings with the same date value specified by , but formatted using the complete representation, extended format. The same date format restrictions regarding reduced accuracy, truncated representation and expanded representation noted in Section 4.1.2.3 apply. Whenever the extended format is not applicable, the basic format is to be used.

vCard "TIME" property values are represented by a property with the type identifier "time". The value elements are JSON strings with the same time value specified by , but formatted using the complete representation, extended format. The same date format restrictions regarding reduced accuracy, decimal fraction and truncated representation noted in Section 4.3.2 apply. Whenever the extended format is not applicable, the basic format is to be used. The seconds value of 60 MUST only be used to account for positive "leap" seconds and the midnight hour is always represented by 00, never 24. Fractions of a second are not supported by this format. Contrary to , UTC offsets are permitted within a time value.

vCard "DATE-TIME" property values are represented by a property with the type identifier "date-time". The value elements are JSON strings with the same date value specified by , but formatted using the complete representation, extended format. The same restrictions with respect to leap seconds, fractions of a second and UTC offsets as in apply. Just as in , truncation of the date part is permitted.

vCard "DATE-AND-OR-TIME" property values are represented by a property with the type identifier "date-and-or-time". The value elements are either a date-time (), a date () or a time () value. Just as in Section 4.3.4, a stand-alone time value is always preceded by a "T".

vCard "TIMESTAMP" property values are represented by a property with the type identifier "timestamp". The value elements are JSON strings with the same timestamp value specified by , but formatted using the complete representation, extended format.

vCard "BOOLEAN" property values are represented by a property with the type identifier "boolean". The value element is a JSON boolean value.

vCard "INTEGER" property values are represented by a property with the type identifier "integer". The value elements are JSON primitive number values.

vCard "FLOAT" property values are represented by a property with the type identifier "float". The value elements are JSON primitive number values.

vCard "UTC-OFFSET" property values are represented by a property with the type identifier "utc-offset". The value elements are JSON strings with the same UTC offset value specified by , with the exception that the hour and minute components are separated by a ":" character, for consistency with the timezone offset, extended format.

vCard "LANGUAGE-TAG" property values are represented by a property with the type identifier "language-tag". The value elements are JSON strings containing a single language-tag, as defined in .

vCard extension properties and property parameters (those with an "X-" prefix in their name) are handled in the same way as other properties and property parameters: the property is represented by an array, the property parameter represented by an object. The property or parameter name uses the same name as for the vCard extension, but in lowercase. For example, the "X-FOO" property in vCard turns into the "x-foo" jCard property. See for how to deal with default values for unrecognized extension properties or property parameters.

When converting property and property parameter values, the names SHOULD be converted to uppercase. Although vCard names are case insensitive, common practice is to keep them all uppercase following the actual definitions in . Backslash escaping and line folding MUST be applied to the resulting vCard data as required by . When converting to vCard, the VALUE parameter MUST be added to properties whose default value type is unknown. The VALUE parameter SHOULD NOT be added to properties using the default value type.

In vCard, properties have a default value type specified by their definition, e.g. "BDAY"'s value type is "date-and-or-time", but it can also be reset to a single "text" value. When a property uses its default value type, the "VALUE" property parameter does not need to be specified on the property. When new properties are defined or "X-" properties used, a vCard to jCard converter might not recognize them, and not know what the appropriate default value types are, yet they need to be able to preserve the values. A similar issue arises for unrecognized property parameters. As a result, the following rules are applied when dealing with unrecognized properties and property parameters: When converting vCard into jCard: Any property that does not include a "VALUE" property parameter and whose default value type is not known, MUST be converted to a string object. The content of that string is the unprocessed value text. Any unrecognized property parameter MUST be converted to a string value, with its content set to the property parameter value text, treated as if it were a "TEXT" value. When converting jCard into vCard: Since jCard always explicitly specifies the value type, it can always be converted to vCard using the VALUE parameter. If the value type specified in jCard matches the default value type in vCard, the VALUE parameter SHOULD be omitted. Example: The following is an example of an unrecognized vCard property (that uses an "URI" value as its default), and the equivalent jCard representation of that property.

vCard:

jCard:

Example: The following is an example of a jCard property (where the corresponding vCard property uses a "INTEGER" value as its default), and the equivalent vCard representation of that property. It is assumed that the parser has knowledge of the default data type for the "x-karma-points" property.

jCard:

vCard:

Example: The following is an example of an unrecognized vCard property parameter (that uses a "FLOAT" value as its default) specified on a recognized vCard property, and the equivalent jCard representation of that property and property parameter.

vCard:

jCard:

For security considerations specific to calendar data, see Section 9 of . Since this specification is a mapping from vCard, no new security concerns are introduced related to calendar data. The use of JSON as a format does have security risks. Section 7 of discusses these risks.

This document defines a MIME media type for use with vCard in JSON data. This media type SHOULD be used for the transfer of calendaring data in JSON. application vcard+json none version as defined for the text/vcard media type in . Same as encoding considerations of application/json as specified in . See . This media type provides an alternative format for vCard data based on JSON. This specification. Applications that currently make use of the text/vcard media type can use this as an alternative. Similarly, Applications that use the application/json media type to transfer directory data can use this to further specify the content. vcarddav@ietf.org COMMON There are no restrictions on where this media type can be used. See the "Author's Address" section of this document. IETF

IANA has added the following entry to the vCard Parameters registry, defined in Section 10.3.2 of . Namespace Parameter Reference GROUP RFCTODO, Replace RFCTODO with the target RFC number for this document.

The author would like to thank the following for their valuable contributions: Cyrus Daboo, Mike Douglass, William Gill, Erwin Rehme, and Dave Thewlis. This specification originated from the work of the XML-JSON technical committee of the Calendaring and Scheduling Consortium.

&rfc2119; &rfc5234; &rfc5545; &rfc5646; &rfc6321; &rfc6350; &rfc6351; &I-D.ietf-jcardcal-jcal; International Organization for Standardization &rfc4627; The Calendaring and Scheduling Consortium

Below is an ABNF schema as per for vCard in JSON. ABNF Symbols not described here are taken from . The schema is non-normative and given for reference only. The numeric section numbers given in the comments refer to section in . Additional semantic restrictions apply, especially regarding the allowed properties and sub-components per component. Details on these restrictions can be found in this document and . Additional schemas may be available on the internet at .

This section contains an example of a vCard object with its jCard representation.

Remove this section prior to publishing doesn't define any kind of stream for multiple vcard elements. For similarity with the jCal draft, I have added a "vcardstream". Is this wanted and does the name fit? (Maybe rather "jcardstream" ?) vCard defines the VERSION property MUST come first. Do we need to do the same here?

Remove this section prior to publishing Added ABNF and improved references in date/time related sections Changes to wording in "vCard Stream" section Changes to wording about VALUE parameter when converting to vCard Corrected missing "type" parameter and separator in example Minor wording corrections Pubication as a WG draft Changed grouping syntax to use new GROUP parameter and added respective IANA section Added timestamp and date-and-or-time types instead of converting them from date/time/date-time Added a further sentence on preprocessing and escaping to clarify that JSON escaping must be used. Described how to handle structured text values and structured text components with multiple values. Corrections and additions to the ABNF Section, adaptions to example