CCSDS 508.0-R-1, Conjunction Data Message (Red Book, Issue 1 ...

DRAFT CCSDS RECOMMENDED STANDARD FOR CONJUNCTION DATA MESSAGES4.2.4 KVN keywords shall be uppercase with ‘_’ (the underscore character) as separators.XML tags shall be uppercase and correspond with the keywords in 3.2 through 3.6. TheXML logical tags related to message structure shall be in lowerCamelCase.4.3 CONSTRUCTING A CDM/XML INSTANCE4.3.1 OVERVIEWThis subsection provides more detailed instructions for the user on how to create an XMLmessage based on the ASCII-text KVN-formatted message described in 3.1 through 3.6 (seereference [6]).4.3.2 XML VERSIONThe first line in the instantiation shall specify the XML version:This line must appear on the first line of each instantiation, exactly as shown.4.3.3 BEGINNING THE INSTANTIATION: ROOT DATA ELEMENT4.3.3.1 A CDM instantiation shall be delimited with the root element tagsusing the standard attributes documented in reference [3].4.3.3.2 The XML Schema Instance namespace attribute must appear in the root element tagof all CDM/XML instantiations, exactly as shown:xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance"4.3.3.3 If it is desired to validate an instantiation against the CCSDS Web-based schema,the xsi:noNamespaceSchemaLocation attribute must be coded as a single string of non-blankcharacters, with no line breaks, exactly as shown:xsi:noNamespaceSchemaLocation="http://sanaregistry.org/r/ndmxml/ndmxml-1.0-master.xsd"NOTE – The length of the value associated with the xsi:noNamespaceSchemaLocationattribute can cause the string to wrap to a new line; however, the string itselfcontains no breaks.4.3.3.4 For use in a local operations environment, the schema set may be downloaded fromthe CCSDS Web site to a local server that meets local requirements for operationsrobustness.CCSDS 508.0-R-1 Page 4-2 March 2012