4.3. Builtin Atomic Types

A number of builtin Atomic Types are predefined. Most of them have counterparts in XML Schema 1.1, because they are very useful also in JSON (for example : dates, times, ...). In particular, they have the same value space, the same lexical space, the same lexical mapping and (for primitive types) the same associated set of atomic facets.

Some of these builtin types are primitive and marked as such below. Others are derived from another builtin type.

string (primitive),
anyURI (primitive),
base64Binary (primitive),
hexBinary (primitive).
date (primitive),
dateTime (primitive),
time (primitive),
dateTimeStamp (derived from dateTime),
gYear (primitive),
gYearMonth (primitive),
gMonth (primitive),
gMonthDay (primitive),
gDay (primitive),
duration (primitive),
dayTimeDuration (derived from duration),
yearMonthDuration (derived from duration),
decimal (primitive),
integer (derived from decimal),
long (derived from integer),
int (derived from long),
short (derived from int),
byte (derived from short),
double (primitive),
float (primitive).
boolean (primitive)
null (primitive), which has a singleton value space containing the JSON null value with the lexical representation "null".

There is also a special builtin type atomic, which is a supertype of all primitive types and, by transition, of all atomic types.

The lexical namespace of dateTime as defined in XML Schema 1.1 is a superset of the date representation defined in ECMAScript. In addition, JSound extends the lexical representation of respectively date, time, dateTime defined above, to allow the format defined in RFC 2822 (nonterminals date, time, date-time respectively). This is because many JavaScript implementations do so.