Data Types

Data TypeDescription
stringString according to XSD string data type. If used in URLs, IDs have to be encoded according to RFC3986 Section 2.5: the string should first be encoded as octets according to the UTF-8 character encoding; then only those octets that do not correspond to characters in the unreserved set (ASCII letters, digits, hyphen, dot, underscore, tilde) should be percent-encoded. In JSON objects the ID strings are encoded according to http://www.json.org
indexnameString of maximum length 20 characters, composed of lowercase
ASCII letters and of digits 0-9, dots, hyphens. NOTE that in contrast to
CDAPI and Ncanto underscores are not supported!
intInteger number according to XSD integer data type
decimalDecimal number according to XSD decimal data type, for example, "1.347"
boolean''true'' or ''false''
timestampTime according to XSD dateTime data type, format
"CCYY-MM-DDThh:mm:ss[Z|(+|-)hh:mm]", for example,
"2001-10-26T21:32:52", "2001-10-26T21:32:52+02:00",
"2001-10-26T19:32:52Z", "2001-10-26T19:32:52+00:00", or
"2001-10-26T21:32:52.12679". Note that for internal implementation reasons timestamps older than 1970-01-01T00:00:00Z may not work in filter requests.
durationTime interval according to XSD duration data type, format
"PnYnMnDTnHnMnS", for example, "PT1Y6M15DT12H" (one year, 6 months, 15 days, 12 hours) or "-PT1H" (minus one hour).
timeTime of day, format "hh:mm:ss", for example, "21:32:52", or "21:32:52.12679"
jsonJSON object (http://www.json.org)
langCodeString composed of ASCII letters, digits, and hyphen '-'. This data type
is used for language specifications and is wide enough to support all
commonly used language codes, for example, ISO 639 and BCP 47.
timezoneTimezone info in tz database format (for example, ''"Europe/Vienna"'') or as fixed offset ''[+-]hh:mm'' (for example, ''"+03:00"''). See http://en.wikipedia.org/
wiki/List_of_tz_database_time_zones for a complete list of tz database IDs.
enumOne of the specified values