XML File Syntax

The contents of the XML configuration file must follow an important hierarchy: the file contains one or more libraries; each library contains one or more profiles; each profile contains QoS settings.

In addition, the file must follow these syntax rules:

• The syntax is XML and the character encoding is UTF-8.
• Opening tags are enclosed in <>; closing tags are enclosed in </>.
• A tag value is a UTF-8 encoded string. Legal values are alphanumeric characters. The middleware’s parser will remove all leading and trailing spaces1Leading and trailing spaces in enumeration fields will not be considered valid if you use the distributed XSD document to do validation at run-time with a code editor (see URL Groups").from the string before it is processed.
• For example, <tag> value </tag> is the same as <tag>value</tag>.
• All values are case-sensitive unless otherwise stated.
• Comments are enclosed as follows: <!-- comment -->.
• The root tag of the configuration file must be <dds> and end with </dds>.
• The primitive types for tag values are specified in .

Supported Tag Values

Type	Format	Notes
DDS_Boolean	yes2These values will not be considered valid if you use the distributed XSD document to do validation at run-time with a code editor (see URL Groups)., 1, true, BOOLEAN_TRUE or DDS_BOOLEAN_TRUE: these all mean TRUE	Not case-sensitive
	no, 0, false, BOOLEAN_FALSE or DDS_BOOLEAN_FALSE: these all mean FALSE
DDS_Enum	A string. Legal values are those listed in the API Reference HTML documentation for the C or Java API.	Must be specified as a string. (Do not use numeric values.)
DDS_Long	-2147483648 to 2147483647 or 0x80000000 to 0x7fffffff or LENGTH_UNLIMITED or DDS_LENGTH_UNLIMITED	A 32-bit signed integer
DDS_UnsignedLong	0 to 4294967296 or 0 to 0xffffffff	A 32-bit unsigned integer
String	UTF-8 character string	All leading and trailing spaces are ignored between two tags

© 2016 RTI