7.5 Attributes Validation Support

March 3, 2026 02:25 AM

3 min read

Copy
Link copied
Print

This appendix describes the data types most used in Technical Documentation.

7.5.1 String Data Types

The following table describes the available string data types. All listed types are processed on the client as “string” types. They are only validated against defined restrictions.

Type Name	Description	Schema validation	Attribute dialog validation
ENTITIES		Yes	No
ENTITY		Yes	No
ID	A string that represents the ID attribute in XML (only used with schema attributes)	Yes	No
IDREF	A string that represents the IDREF attribute in XML (only used with schema attributes)	Yes	No
IDREFS		Yes	No
language	A string that contains a valid language id	Yes	No
Name	A string that contains a valid XML name	Yes	No
NCName		Yes	No
NMTOKEN	A string that represents the NMTOKEN attribute in XML (only used with schema attributes)	Yes	No
NMTOKENS		No	No
normalizedString	A string that does not contain line feeds, carriage returns, or tabs	No	No
QName		Yes	No
string	A string	Yes	Yes
token	A string that does not contain line feeds, carriage returns, tabs, leading or trailing spaces, or multiple spaces	No	No
anyURI		Yes	Yes
base64Binary		Yes	No
hexBinary		Yes	No
NOTATION		Yes	No

7.5.2 Date and Time Data Types

Type Name	Description	Schema validation	Attribute dialog validation
date	Defines a date value	Yes	Yes. Works like dateTime.
dateTime	Defines a date and time value	Yes	Yes
duration	Defines a time interval	Yes	No
gDay	Defines a part of a date - the day (DD)	Yes	No
gMonth	Defines a part of a date - the month (MM)	Yes	No
gMonthDay	Defines a part of a date - the month and day (MM-DD)	Yes	No
gYear	Defines a part of a date - the year (YYYY)	Yes	No
gYearMonth	Defines a part of a date - the year and month (YYYY-MM)	Yes	No
time	Defines a time value	Yes	No

7.5.3 Numeric Data Types

Numeric types are processed as a ‘long’ on the client and not validated against type boundaries.
There is a limitation within the .Net processing logic for ‘default/fixed’ values validation. If the min/maxExclusive restriction is specified and it has a value that exceeds the type of boundary by one (‘1’), then system will show a validation error. For example:
byte has a range of values -128 .. 127. If the maxExclusive restriction is given a value of ‘128’ then a validation error will be shown.
The Javascript parseInt/Float() method is used to process strings for client-side validation within the Attributes Dialog. Strings that contain invalid characters for a numeric value will not show as invalid (warning icon).
Restriction ' totalDigits’ is not processed for integer, long, int, short, and byte types.

Type Name	Description	Schema validation	Attribute dialog validation
byte	A signed 8-bit integer	Yes [2]	Yes [1]
unsignedByte	An unsigned 8-bit integer	Yes [2]	No
short	A signed 16-bit integer	Yes [2]	Yes [1,3]
unsignedShort	An unsigned 16-bit integer	Yes [2]	No
decimal	A decimal value	Yes [2]	Yes [3]
int	A signed 32-bit integer	Yes [2]	Yes [1,3]
unsignedInt	An unsigned 32-bit integer	Yes [2]	No
integer	An integer value	Yes [2]	Yes [1,3]
long	A signed 64-bit integer	Yes [2]	Yes [3]
unsignedLong	An unsigned 64-bit integer	Yes [2]	No
negativeInteger	An integer containing only negative values (..,-2,-1)	Yes [2]	No
nonNegativeInteger	An integer containing only non-negative values (0,1,2,..)	Yes [2]	No
nonPositiveInteger	An integer containing only non-positive values (..,-2,-1,0)	Yes [2]	No
positiveInteger	An integer containing only positive values (1,2,..)	Yes [2]	No

Type Name	Description	Schema validation	Attribute dialog validation
double		Yes	Yes [3]
float		Yes	Yes [3]

7.5.4 Miscellaneous Data Types

Value can be represented as ‘0’-‘1’ or ‘true’-‘false’ pairs in the XML Schema. However, since the editor field on the client is represented as a checkbox we support only ‘true’-‘false’ pair.

Type Name	Description	Schema validation	Attribute dialog validation
boolean		Yes	Yes [1]