The following data types are used in the :

Data Types Used in Release Files

Data Type	Description
	A between 6 and 18 digits long, as described in 6.2 SCTID Representation. This data type is used to identify , to refer to a from another or from a , and also to represent the values for (see Concept Enumerations.).
	A Universally Unique Identifier is a 128-bit unsigned generated using a standard algorithm. UUIDs are represented as strings of hexadecimal characters split by - characters as points specified by the UUID standard.
	A 32-bit signed integer.
	text of a specified length.
	A Boolean value, represented as one of two possible integer values (1 = true, 0 = false).
	A date and time format expressed as a text string in line the basic representation specified in the ISO 8601 standard. Where only date is required the format is YYYYMMDD (e.g. 20180125 refers to 25th January 2018) Where a time is also required the YYYYMMDDThhmmssZ (e.g. 20180125T123000Z refers to 12:30 UTC on 25th January 2018) The time should be expressed as UTC, as indicated by the trailing "Z".

Concept Enumerations

Concept enumeration values (subtypes of 900000000000442005|Core metadata concept|)

Concept	Comment
	Each of this represents a development module. These provide values to the field that is present in all file. The value indicates the module within which a was created and is being maintained.
	Each of this represents a value that can be applied to the . field. This is used to indicate whether the current set of defining applied to a are sufficient to fully-define it relative to its supertypes.
	Each of this represents a value that can be applied to the . field. This is used to indicate whether the represents a , a synonymous term, a definition or some other symbolic or textual representation of the associated .
	Each of this represents a value that can be applied to the . field. This is used to indicate whether the text of the term can be modified to by switching characters from upper to lower case (or vice-versa).
	Each of this represents a value that can be applied to the . field. This is used to indicate whether a forms part of the definition of the source .
	Each of this represents a value that can be applied to the . field. This is used to indicate the type of (DL) restriction (some, all, etc.) that applies to the .
	Each of this represents a value that can be applied to the . field. This is used to indicate the scheme to which the value belongs.