]> Comodo Group Inc.

philliph@comodo.com

General Internet Engineering Task Force JSON SCIJER (pronounced skyjer) specifies a mapping of data types to JavaScript Object Notation (JSON) encoding. The JSON specification defines encodings for integers, strings, arrays and objects. This document specifies a mapping between JSON encoding and an extended set of types.

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 following terms are used in this document:

JSON is a format for encoding data structures in UTF8 text format with similar capabilities to XML and ASN.1 but with lower coding overhead. Unlike XML and ASN.1, JSON does not have a schema language. This draft defines a mapping between JSON data types and programming language types that MAY be used as the basis for a schema language definition.

Specify conversions between JSON encoding and C, C# and Java types.

true | false int bool boolean

number without decimal point int or long

number with decimal point float or double

The String type maps to the JSON string encoding. The following subtypes are defined to represent commonly used syntactic restrictions. String encoding char * [NB must use appropriate wrappers to encode/decode UTF8] String URI Label Name

A URI is a string that contains a URI as specified in .

A label is a string that MUST NOT contain any ASCII character other than digits (0-9), alphabetic (a-z, A-Z), underscore or dash. All other UNICODE characters are permitted. The Label type provide a means of avoiding content injection attacks by ensuring that a field does not contain characters commonly used as control characters in scripting languages.

A Name is a sequence of Labels separated by period characters '.'. Note that the syntactic restriction of a Name is not exactly the same as the restriction on a DNS address.

An enumeration is encoded as a Label.

SSCIJER supports two encodings A string encoded in format. This provides a human readable representation. A number that represents the number of seconds that have elapsed since January 1, 0001 at 00:00:00.000 in the Gregorian calendar. Decimals MAY be used to represent time intervals of less than a second. Conversion between the two encodings MUST be informed by the times at which leap seconds were introduced into the UTC coding. This creates a challenge in the case that a device only has access to time in one form but not the other. In order to address this problem, implementations MUST accept time values encoded in either format and SHOULD emit the encoding specified in the schema.

String [Encoded in format.] System dependent DateTime Date Represents a date and time in the Gregorian callendar using the format described in .

Number System dependent DateTime Date A number that represents the number of seconds that have elapsed since January 1, 0001 at 00:00:00.000 in the Gregorian calendar. Decimals MAY be used to represent time intervals of less than a second.

String [Base64 encoding of binary data] {unsigned char *, length} byte []

The name of this draft was inspired by Mark Nottingham.

&RFC1035; &RFC2119; &RFC3339; &RFC3986;