XML Specification for Navigation Data Messages - CCSDS
XML Specification for Navigation Data Messages - CCSDS
XML Specification for Navigation Data Messages - CCSDS
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
DRAFT <strong>XML</strong> SPECIFICATION FOR NAVIGATION DATA MESSAGES<br />
4.4 THE STANDARD NDM/<strong>XML</strong> HEADER SECTION<br />
The NDMs share a standard header <strong>for</strong>mat, with tags and . After the<br />
tag the message may have any number of tag pairs.<br />
The standard NDM header shall contain the and the <br />
tags. The rules <strong>for</strong> these keywords are specified in references [1], [2], and [3].<br />
<br />
This is the common NDM/<strong>XML</strong> header<br />
I can put as many comments here as I want, including none.<br />
2004-281T17:26:06<br />
AGENCY-X<br />
<br />
4.5 THE NDM BODY SECTION<br />
4.5.1 GENERAL<br />
After coding the , the instantiation must include a tag pair.<br />
Inside the tag pair must appear at least one <br />
tag pair. Each segment must be made up of one or more and<br />
tag pairs.<br />
4.5.2 THE NDM METADATA SECTION<br />
All NDMs must have a metadata section. The metadata section shall be set off the by the<br />
tag combination. Between the and<br />
tags, the keywords shall be the same as those in the metadata sections in the<br />
reference documents (reference [1], [2], and [3]), with exceptions as noted in the subsections<br />
below on creating instantiations of the specific messages.<br />
4.5.3 THE NDM DATA SECTION<br />
All NDMs must have a data section. The data section shall follow the metadata section and<br />
shall be set off the by the tag combination. Between the and<br />
tags, the keywords shall be the same as those in the data sections in the reference<br />
documents (references [1], [2], and [3]), with exceptions as noted in the subsections below on<br />
creating instantiations of the specific messages.<br />
<strong>CCSDS</strong> 505.0-R-2 Page 4-3 June 2009