consultative committee for space data systems documents/navigation... · through the process of...

ConsultativeCommittee for

SpaceData Systems

DRAFT RECOMMENDATION FOR SPACE DATA SYSTEM STANDARDS

XML SPECIFICATION FOR

NAVIGATION DATA MESSAGES

CCSDS 505.0-W-1.78

WHITE BOOK

SEPTEMBER 2005

DRAFT CCSDS RECOMMENDATION FOR NAVIGATION DATA MESSAGE XML SPECIFICATION

CCSDS 505.0-W-1.78 Page i September 2005

AUTHORITY

Issue: White Book, Issue 1.78

Date: September 2005

Location: Pasadena, CA USA

(WHEN THIS DRAFT RECOMMENDATION IS FINALIZED, IT WILL CONTAIN THE FOLLOWING STATEMENT OF AUTHORITY:)

This document has been approved for publication by the Management Council of the Consultative Committee for Space Data Systems (CCSDS) and represents the consensus technical agreement of the participating CCSDS Member Agencies. The procedure for review and authorization of CCSDS Recommendations is detailed in the Procedures Manual for the Consultative Committee for Space Data Systems, and the record of Agency participation in the authorization of this document can be obtained from the CCSDS Secretariat at the address below.

This Recommendation is published and maintained by:

CCSDS Secretariat Program Integration Division (Code MT) National Aeronautics and Space Administration Washington, DC 20546, USA


CCSDS 505.0-W-1.78 Page ii September 2005

FOREWORD

(WHEN THIS RECOMMENDATION IS FINALIZED, IT WILL CONTAIN THE FOLLOWING FOREWORD:)

This document is a technical Recommendation for an XML Specification for Navigation Data Messages (Orbit Data Messages, Attitude Data Messages, Tracking Data Messages). It has been prepared by the Consultative Committee for Space Data Systems (CCSDS). The XML schema described in this Recommendation is the baseline concept for exchanging navigation data in XML format between Agencies of the CCSDS.

This Recommendation establishes a common framework and provides a common basis for the interchange of navigation data in XML format. It allows implementing organizations within each Agency to proceed coherently with the development of compatible derived standards for the flight and ground systems that are within their cognizance. Derived Agency standards may implement only a subset of the optional features allowed by the Recommendation and may incorporate features not addressed by this Recommendation.

Through the process of normal evolution, it is expected that expansion, deletion or modification to this document may occur. This Recommendation is therefore subject to CCSDS document management and change control procedures, as defined in the Procedures Manual for the Consultative Committee for Space Data Systems. Current versions of CCSDS documents are maintained at the CCSDS Web site:

http://www.ccsds.org/

Questions relating to the contents or status of this document should be addressed to the CCSDS Secretariat.


CCSDS 505.0-W-1.78 Page iii September 2005

At time of publication, the active Member and Observer Agencies of the CCSDS were: Member Agencies – Agenzia Spaziale Italiana (ASI)/Italy. – British National Space Centre (BNSC)/United Kingdom. – Canadian Space Agency (CSA)/Canada. – Centre National d’Etudes Spatiales (CNES)/France. – Deutsches Zentrum für Luft- und Raumfahrt e.V. (DLR)/Germany. – European Space Agency (ESA)/Europe. – Instituto Nacional de Pesquisas Espaciais (INPE)/Brazil. – Japan Aerospace Exploration Agency (JAXA)/Japan. – National Aeronautics and Space Administration (NASA)/USA. – Russian Space Agency (RSA)/Russian Federation. Observer Agencies – Austrian Space Agency (ASA)/Austria. – Central Research Institute of Machine Building (TsNIIMash)/Russian Federation. – Centro Tecnico Aeroespacial (CTA)/Brazil. – Chinese Academy of Space Technology (CAST)/China. – Commonwealth Scientific and Industrial Research Organization (CSIRO)/Australia. – Communications Research Laboratory (CRL)/Japan. – Danish Space Research Institute (DSRI)/Denmark. – European Organization for the Exploitation of Meteorological Satellites

(EUMETSAT)/Europe. – European Telecommunications Satellite Organization (EUTELSAT)/Europe. – Federal Science Policy Office (FSPO)/Belgium. – Hellenic National Space Committee (HNSC)/Greece. – Indian Space Research Organization (ISRO)/India. – Institute of Space Research (IKI)/Russian Federation. – KFKI Research Institute for Particle & Nuclear Physics (KFKI)/Hungary. – Korea Aerospace Research Institute (KARI)/Korea. – MIKOMTEK: CSIR (CSIR)/Republic of South Africa. – Ministry of Communications (MOC)/Israel. – National Oceanic & Atmospheric Administration (NOAA)/USA. – National Space Program Office (NSPO)/Taipei. – Space and Upper Atmosphere Research Commission (SUPARCO)/Pakistan. – Swedish Space Corporation (SSC)/Sweden. – United States Geological Survey (USGS)/USA.


CCSDS 505.0-W-1.78 Page iv September 2005

PREFACE

This document is a Proposed CCSDS Draft Recommendation. Its ‘White Book” status indicates that the CCSDS believes the document to be technically immature and has not released it for formal review by technical organizations. As such, its technical content is highly unstable and several iterations of it will occur in response to comments received during the proposal development process. Implementers are cautioned not to develop any final software in accordance with this document’s technical content.

In this draft, there are a number of author’s notes, indicated with the word “NOTE” in all caps, as well as author’s questions, indicated with the word “QUESTION” in all caps. As the issues associated with these notes and questions are resolved through subsequent drafts, these indicators will be removed from the document, depending on the content of the note.


CCSDS 505.0-W-1.78 Page v September 2005

DOCUMENT CONTROL Document Title and Issue Date Status

CCSDS 50x-NDM/XML.0-W-1.0

XML Specification for Navigation Data Messages, Draft 1.0

August 2004 Original Issue



October 2004 Corrects errors in original issue 1.0 document, as well as improving the NDM XML Schema. Replaced schema and example.



November 2004 Incorporates comments from Nav WG reviews, ISSFD subgroup meeting, corrects errors in issue 1.1 document, adds units accommodation for ODM items, incorporates changes from TDM 1.7 and ADM July 2004 version. Replaced updated schema and example.



November 2004 Updates from Fall 2004 Meetings discussions



March 2005 Updates to accommodate some ideas from Fall 2004 meetings, upgrade for ADM 2.1, TDM 1.10



April 2005 Upgrade for TDM 1.11, ADM 2.2, miscellaneous changes



April 2005 From Spring 2005 meetings, plus reflects updates to ADM and TDM that were discussed at the Spring 2005 meetings, plus some of the GMV recommendations.



September 2005 Reflects updates introduced in TDM 1.14, plus discussions of 06/02/2005 Nav WG teleconference. Updates processed for TDM 1.13 through 1.17; ADM 2.4. Official document number added. Changed CCSDS logo to new style.


CCSDS 505.0-W-1.78 Page vi September 2005



September 2005 Fall 2005 Meetings, compatibility with TDM 1.18, ADM 2.5, modularized schema.


CCSDS 505.0-W-1.78 Page vii September 2005

CONTENTS

Section Page

1 INTRODUCTION................................................................................................................... 1 1.1 PURPOSE..................................................................................................................... 1 1.2 SCOPE AND APPLICABILITY .................................................................................. 1 1.3 CONVENTIONS AND DEFINITIONS....................................................................... 1 1.4 STRUCTURE OF THIS DOCUMENT........................................................................ 2 1.5 REFERENCES ............................................................................................................. 2 1.6 INFORMATION SECURITY ...................................................................................... 3

2 OVERVIEW............................................................................................................................ 5 2.1 THE ATTITUDE DATA MESSAGE (ADM) ............................................................. 5 2.2 THE ORBIT DATA MESSAGE (ODM) ..................................................................... 5 2.3 THE TRACKING DATA MESSAGE (TDM)............................................................. 5

3 XML OVERVIEW.................................................................................................................. 6 3.1 XML OVERVIEW ....................................................................................................... 6 3.2 JUSTIFICATION FOR USING XML SCHEMA ........................................................ 7 3.3 JUSTIFICATION FOR INTEGRATED NDM/XML SCHEMA................................. 8

4 BASIC STRUCTURE OF THE NDM/XML SCHEMA ..................................................... 9 4.1 NDM BASIC STRUCTURE ........................................................................................ 9 4.2 SUBSTRUCTURE 1: APM, OPM............................................................................ 10 4.3 SUBSTRUCTURE 2: AEM, OEM, TDM................................................................. 11 4.4 NDM/XML TAGS...................................................................................................... 12 4.5 DISCUSSION OF “CHECKING”.............................................................................. 13

ANNEX A RATIONALE FOR TRACKING DATA MESSAGES...................................... A-1 ANNEX B ABBREVIATIONS AND ACRONYMS.............................................................. B-4 ANNEX C NDM/XML MASTER SCHEMA......................................................................... C-5 ANNEX D AEM SCHEMA...................................................................................................... D-8 ANNEX E APM SCHEMA .................................................................................................... E-13 ANNEX F OEM SCHEMA.....................................................................................................F-17 ANNEX G OPM SCHEMA ...................................................................................................G-19 ANNEX H TDM SCHEMA ...................................................................................................H-23 ANNEX I NDM/XML COMMON SCHEMA....................................................................... I-29 ANNEX J NDM/XML EXAMPLES ...................................................................................... J-34 ANNEX K AUTHOR’s to-do.................................................................................................K-35 1 INTRODUCTION................................................................................................................... 1

1.1 PURPOSE..................................................................................................................... 1 1.2 SCOPE AND APPLICABILITY .................................................................................. 1 1.3 CONVENTIONS AND DEFINITIONS....................................................................... 1 1.4 STRUCTURE OF THIS DOCUMENT........................................................................ 2 1.5 REFERENCES ............................................................................................................. 2 1.6 INFORMATION SECURITY ...................................................................................... 3

2 OVERVIEW............................................................................................................................ 4 2.1 THE ATTITUDE DATA MESSAGE (ADM) ............................................................. 4


CCSDS 505.0-W-1.78 Page viii September 2005

2.2 THE ORBIT DATA MESSAGE (ODM) ..................................................................... 4 2.3 THE TRACKING DATA MESSAGE (TDM)............................................................. 4

3 XML OVERVIEW.................................................................................................................. 5 3.1 XML OVERVIEW ....................................................................................................... 5 3.2 JUSTIFICATION FOR USING XML SCHEMA ....................................................... 6 3.3 JUSTIFICATION FOR INTEGRATED NDM/XML SCHEMA................................. 7

4 BASIC STRUCTURE OF THE NDM/XML SCHEMA ..................................................... 8 4.1 NDM BASIC STRUCTURE ........................................................................................ 8 4.2 SUBSTRUCTURE 1: APM, OPM.............................................................................. 9 4.3 SUBSTRUCTURE 2: AEM, OEM, TDM................................................................. 10 4.4 NDM/XML TAGS...................................................................................................... 11 4.5 DISCUSSION OF “CHECKING”.............................................................................. 11

ANNEX A RATIONALE FOR TRACKING DATA MESSAGES...................................... A-1 ANNEX B ABBREVIATIONS AND ACRONYMS.............................................................. B-4 ANNEX C QUESTIONS .......................................................................................................... C-5 ANNEX D AUTHOR’s to-do ................................................................................................... D-6 ANNEX E NDM/XML Schema ............................................................................................... E-8 ANNEX F NDM/XML EXAMPLE........................................................................................F-38


CCSDS 505.0-W-1.78 Page ix September 2005

CONTENTS (continued)

Figures Page

Figure 4-1 NDM/XML Basic Structure ..................................................................................... 109

Figure 4-2 NDM/XML Substructure for APM and OPM........................................................ 1110

Figure 4-3 NDM/XML Substructure for AEM, OEM, TDM .................................................. 1211

Tables Page

Table A-1: Primary Requirements .............................................................................................. A-2

Table A-2: Heritage Requirements ............................................................................................. A-3

Table A-3: Desirable Characteristics .......................................................................................... A-3


CCSDS 505.0-W-1.78 Page 1 September 2005

1 INTRODUCTION

1.1 PURPOSE This Draft Recommendation specifies a standard for use in exchanging spacecraft navigation data between space agencies. Such exchanges are used for distributing attitude, orbit, and tracking data between participating space agencies. This Draft Recommendation has been developed via consensus of the Navigation Working Group of the CCSDS Mission Operations and Information Management Services (MOIMS) area. It describes an integrated XML schema that applies to all types of CCSDS approved Navigation Data Messages (NDM): Attitude Data Messages (ADM, see reference [3]), Orbit Data Messages (ODM, see reference [4]), and Tracking Data Messages (TDM, see reference [5]).

This document includes sets of requirements and criteria that the XML schema has been designed to meet. The rationale behind the design of the message is described in Annex A and may help the application engineer construct a suitable message. For exchanges where these requirements do not capture the needs of the participating agencies another mechanism may be selected.

This XML schema is suited to inter-agency exchanges of any number of navigation data messages (ADM, ODM, and/or TDM).

1.2 SCOPE AND APPLICABILITY

a) This Draft Recommendation is applicable only to the schema content and layout, and instantiations of the schema, but not to the transmission of any instantiation of the schema (note that the potential for compression/decompression of the message is an aspect of the transmission that is not part of this standard). The means of transmission of an XML-formatted NDM between agencies is beyond the scope of this document and should be specified via other arrangements, for example, an Interface Control Document (ICD). Transmission of an XML-formatted NDM could be based on the CCSDS Real-Time Radiometric Data Transfer Service Specification currently under development (White Book status as of August October 20045), file based transfer protocol such as SFTP, streaming media, or services provided via the World Wide Web and XML-compatible web browsers. In general, it is a requirement that the transmission mechanism not place constraints on the technical data content of a navigation data message.

1.3 CONVENTIONS AND DEFINITIONS

The following conventions apply throughout this Draft Recommendation:

a) the words “shall” and “must” imply a binding and verifiable specification;



b) the word “should” implies an optional, but desirable, specification;

c) the word “may” implies an optional specification;

d) the words “is”, “are”, and “will” imply statements of fact.

1.4 STRUCTURE OF THIS DOCUMENT

Chapter 2 provides a very brief overview of the individual messages that constitute an NDM (i.e., ADM, ODM, TDM).

Chapter 3 provides a very brief overview of XML, and the justification for an integrated NDM/XML schema.

Chapter 4 provides an overview of the basic structure of the NDM/XML schema. This structure is external to the internal structure provided by the constituent messages.

Chapter 5 consists of a listing of the NDM/XML Schema.

Chapter 6 consists of a listing of an example NDM/XML instance.

Annex A lists a set of requirements that were taken into consideration in the design of the NDM/XML Schema. EDITOR’s NOTE: These requirements should be reviewed, augmented, reduced by discussion of the Navigation Working Group.

Annex B is a list of abbreviations and acronyms applicable to the NDM/XML.

Annexes C through I provide listings of the NDM/XML Master Schema, AEM Schema, APM Schema, OEM Schema, OPM Schema, TDM Schema, and NDM/XML Common Schema respectively.

Annex J consists of some example NDM/XML messages, with a description of where more test files can be located.

Annexes C and DK is are lists of Questions and “To-Do” items that will NOT be part of the final document, nor will this statement.

1.5 REFERENCES

The following documents contain provisions which, through reference in this text, constitute provisions of this Draft Recommendation. At the time of publication, the editions indicated were valid. All documents are subject to revision, and users of this Draft Recommendation are encouraged to investigate the possibility of applying the most recent editions of the documents indicated below. The CCSDS Secretariat maintains a register of currently valid CCSDS Recommendations.



[1] Navigation Data—Definitions and Conventions. Report Concerning Space Data System Standards, CCSDS 500.0-G-1. Green Book. Issue 1. Washington, D.C.: CCSDS, June 2001. [ http://www.ccsds.org/ ]

[2] Information Technology—8-Bit Single-Byte Coded Graphic Character Sets—Part 1: Latin Alphabet No. 1. International Standard, ISO/IEC 8859-1:1998. Geneva: ISO, 1998. [http://www.iso.ch]

[3] Attitude Data Messages. Draft Recommendation for Space Data Systems Standards, CCSDS 50x.0-W-2.15. White Book. Issue 2.15. Washington, D.C.: CCSDS, November 2004September 2005.

[4] Orbit Data Messages. Draft Recommendation for Space Data Systems Standards, CCSDS 502.0-B-1. Blue Book. Issue 1. Washington, D.C.: CCSDS, September 2004.

[5] Tracking Data Message. Draft Recommendation for Space Data Systems Standards, CCSDS 50x.0-W-1.718. White Book. Issue 1.1018. Washington, D.C.: CCSDS, February September 2005.

[6] XML Schema Part 1: Structures, W3C Recommendation, 02 May 200128 October 2004, http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/

[7] XML Schema Part 2: Datatypes, W3C Recommendation, 02 May 2001,28 October 2004, http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/

[8] Time Code Formats. Recommendation for Space Data System Standards, CCSDS 301.0-B-3. Blue Book. Issue 3. Washington, D.C.: CCSDS, January 2002. [ http://www.ccsds.org/ ]

[9] “XML in CCSDS”, presentation at CCSDS Spring 2004 Meetings, Montreal, Canada, http:www.ccsds.org/docu/dscgi/ds.py/Get/File-1705/CCSDS_Workshop_Montreal_2004.ppt

1.6 INFORMATION SECURITY Navigation Data Messages (including the ODM, ADM and TDM) may require moderate security measures to protect the data from unauthorized access. Protection from unauthorized access is especially important if the mission utilizes open ground networks such as the Internet to provide ground station connectivity for the exchange of Navigation Data Messages. In order to provide requisite security, it is recommended that Navigation Data Messages be transferred between participants via Secure FTP (SFTP), real-time authentication such as that incorporated in the Real-Time Radio-Metric Data Transfer Service (RRMDT), or other secure mechanisms approved by the IT Security functionaries of exchange participants. As noted elsewhere in this document, this document does not deal specifically with the means of transferring Navigation Data Messages, focusing rather on content. Specific information security provisions that may apply between agencies involved in an exchange should be specified in an ICD.



2 OVERVIEW

This section will provide a brief overview of the set of Navigation Data Messages (NDM). There are three basic types of NDM (Attitude Data Messages, Orbit Data Messages, and the Tracking Data Message). The remainder of this document will convey the structure of the NDM in an integrated XML schema.

2.1 THE ATTITUDE DATA MESSAGE (ADM)

The ADM comprises 2 message types used to convey spacecraft attitude information: the Attitude Parameter Message (APM) and Attitude Ephemeris Message (AEM). The Attitude Parameter Message consists of an instantaneous attitude state and optional attitude maneuvers. The Attitude Ephemeris Message consists of a history/forecast of the attitude of the object that can be interpolated to obtain the attitude of the spacecraft at times other than those specified in the message. For a complete description of the APM and AEM, see reference [3].

2.2 THE ORBIT DATA MESSAGE (ODM)

The ODM comprises 2 message types used to convey trajectory information: the Orbit Parameter Message (OPM) and Orbit Ephemeris Message (OEM). The OPM consists of a single state vector at a given time that represents the trajectory of the spacecraft; specifications of maneuvers are optional. The OEM represents a history/forecast of state vectors that can be interpolated to obtain the trajectory of the spacecraft at times other than those specified in the message. For a complete description of the OPM and OEM, see reference [4].

2.3 THE TRACKING DATA MESSAGE (TDM)

The TDM comprises a single message type for use in exchanging spacecraft tracking data between space Agencies. Such exchanges are used for distributing tracking data output from interagency cross supports in which spacecraft missions managed by one agency are tracked from a ground station managed by a second agency. Additionally, the ability to transfer tracking data between space agencies facilitates the allocation of tracking sessions to alternate antenna resources and increases the ability of space agencies to tolerate availability issues with their primary antennas. The TDM supports at least the following types: ground-based radio metric types: uplink frequencies, range, Doppler, antenna angles, and interferometric types; spacecraft-to-spacecraft Doppler and range; ancillary information needed to calculate the measurement residuals, such as meteorological data, media delays, and clock parameters. For a complete description of the TDM, see reference [5].



3 XML OVERVIEW

This section will briefly describe the Extensible Markup Language (XML), XML Schema and the justification for using it for Navigation Data Messages. For a complete description of XML Schema, see references [6] and [7]. In addition, for general information there are many popular books describing XML and how to use it.

3.1 XML OVERVIEW

a) During the development of the ODM it was realized that the specified keyword value notation (KVN) format was very limited and that it was not well suited to cover all possible needs of the Navigation Data Messages. XML, the “eXtensible Markup Language”, is a much better form of specifying ASCII-based data. This section will present a brief description of the broad features of XML.

b) XML is similar to the HTML used for creating web pages, in that there are tags (begin tags and end tags) that specify how to organize the content. XML is different from HTML in that HTML tags are “fixed”, while XML provides an extensible framework that allows user-defined tag names that are structured according to the logic of the particular application domain in which the document content exists. Additionally, XML documents must be “well-formed”, whereas this restriction does not exist for HTML documents. Discussion of the details of “well-formedness” are beyond the scope of this document, but it is essentially a set of rules that describe what constitutes a proper XML document. If the rules are not followed, the document cannot be rendered correctly.

c) Some of the advantages of using XML instead of standard ASCII text files for this kind of application include:

• XML allows for the definition of the data message in a machine-readable format. The format is basically a template called a , or “schema”. This schema can then be referred to in the data file and it can be used to verify that the data is compliant with the schema. There are widely-available programs to both specify formats, called schemas in XML, to assist with the processing of XML data, and to automatically verify that the data messages comply with the schema. Each participant in a data exchange can independently verify that the message is compliant. This simplifies the development and validation of the software used to write data in the proper format.

• XML defines standards for time formats and numerical values.

• XML allows for the nesting of data, so it is clear which metadata corresponds to which data.

• XML allows for the specification of default and alternative attributes, such as units.

• XML allows for compulsory and optional elements and attributes.



• XML allows for range checking and specification of lists of allowed values.

• XML allows for sharing elements between different specifications.

d) A few disadvantages of using XML for this application are:

• Some values can be specified as either attributes or child elements, so there may be disagreement as to which method should be used. (Note: this flexibility can also be seen as an advantage, depending upon the application and the implementation).

• Tags are always duplicated, with the opening tag and the corresponding ending tag making files bigger (the byte count for tag information may exceed the byte count of the actual data associated with the tags). However, there are specific compressors for XML data that are much more efficient than those used for ASCII data (e.g., XMILL and XGRIND).

• There are not many Flight Dynamics specialists that are skilled in XML.

3.2 JUSTIFICATION FOR USING XML SCHEMA

xxx NOTE: This section is a skeleton section that will be filled out with justification for using XML Schema. As Francisco has pointed out, it’s a missing section between the discussion of XML, and the section on using an integrated XML schema for the NDM/XML. This section will discuss various possibilities for satisfying the requirement for a valid XML format descriptor, of which XML Schema is one possibility. Add notes on CMC.xxx This resolution resulted from the Panel 1 activity report, then led by Mr. Michel Morlon, which proposed: Panel 1J concerns regarding Panel 2 and Panel 3 work: o Will P3 be recommending use of some particular syntax (e.g. PVL, XML, etc.) for formulation of the basic tracking messages? o Potential conflict between use of FTP versus ASN.1 transfer methods. Will P3 be recommending one or another method(s) for near-real time or for batch (non-real time) transfers? o Will there be requirements/recommendations regarding the syntax for Tracking Data Messages (TDMs) as did P2 with respect to using PVL or XML for Orbit Data Messages? Panel 2 Mr. Don Sawyer reported that Producer-Archive Interface Methodology book will be ready for publication as a Red Book by December 2002 (Resolution MC-F02-08). Panel 2 met with Panel 1J to discuss a data format coordination issue concerning content information in the CCSDS 502.0-R-2 Orbit Data Messages. P2 recommended that PVL or XML would provide better interoperability than what was stated in the book. The MC directed P1J to reorganize the syntax and semantics in the ODM book to comply with PVL or XML (Resolution MC-F02-09). Additionally, resolutions were approved that directed all Panels to consult with P2 during the



development of any Recommendation that contains syntactical representations of semantic concepts before it is released as a Red Book (Resolution MC-F02-10). Finally, Panel 2 requested that all Panel chairs provide brief status of each document after each meeting. These summaries would be distributed so all members, observers, chairs, associates would be made aware of development activities (Resolution MC-F02-11). The Panel 2 report is shown in Attachment M.

There are several ways in which XML files can be processed: without validation, with validation via DTD, with validation via RELAX NG, with validatin via Shematron, and with validation via XML schema. In the case of the CCSDS, the CCSDS Management Council (CMC) has indicated that XML schema shall be used for the XML validation (refer to CMC minutes of October 2002, Resolution MC-F02-09; at that time the CMC directed Panel 1J (precursor to Navigation Working Group) utilize PVL, or preferably XML schema, in the CCSDS 502.0-R-2 Orbit Data Messages.

3.3 JUSTIFICATION FOR INTEGRATED NDM/XML SCHEMA

The basic argument for creating an integrated NDM/XML schema proceeds from a position of symmetry and efficiency. There has been a movement towards the adoption of XML for space data systems data interchange between agencies. Since there are 5 separate NDM types, some of which have considerable overlap, it is more efficient to structure the XML format for the set of NDMs into an integrated whole. This will help to ensure as much consistency as possible between the message implementations, and will hopefully facilitate the coding of programs that will produce the messages that will be exchanged.

It is envisioned that the integrated NDM/XML schema will be hosted on a CCSDS web page accessible to all interested parties, and that agencies creating instantiations of the NDM/XML schema should map them to the CCSDS hosted NDM/XML schema. This will ensure that all instantiations of the NDM/XML schema can be validated in a consistent manner. This vision includes links to developer tools and test resources in addition to the official schema.

Currently, the NDM/XML schema is available at:

http://public.ccsds.org/sites/cwe/moims-nav/Public/Schemas/ndmxml-master-1.8.xsd

In addition to the schemas, there are several test files and example NDM/XML instantiations.



4 BASIC STRUCTURE OF THE NDM/XML SCHEMA

4.1 NDM BASIC STRUCTURE

a) The basic element in the NDM/XML shall be a “Navigation Data Message”, or “NDM”. The NDM shall consist of submessages called:

•Attitude Data Message (ADM) (see reference [3])

•Orbit Data Message (ODM) (see reference [4])

•Tracking Data Message (TDM) (see reference [5])

b) The Attitude Data Message also consists of 2 submessages:

• Attitude Parameter Message (APMapm) (see reference [3])

• Attitude Ephemeris Message (AEMaem) (see reference [3])

c) The Orbit Data Message consists of 2 submessages:

• Orbit Parameter Message (OPMopm) (see reference [4])

• Orbit Ephemeris Message (OEMoem) (see reference [4])

• Tracking Data Message (tdm) (see reference [5])

d) The Tracking Data message consists of a single message type.

eb) In general, an NDM should consist of at least one message (ADMAEM, APM, ODM, OEM, OPM, or TDM). However, there are certain instances when it may be desirable to check connectivity via an NDM which is “empty”, i.e., contains only the outermost tag levels.

f) An ADM must consist of at least one message (APM or AEM).

g) An ODM must consist of at least one message (OPM or OEM).

h) Thus, the basic structure of an NDM shall be as shown in the following figure:



Figure 4-1 NDM/XML Basic Structure

<NDMndm> COMMENT (generally, at least one APEM, AEPM, OPEM, OEPM, or TDM, unless “ping”). COMMENT Note: the messages can occur in any quantity or order. <APMapm> </APMapm> <AEMaem> </AEMaem> <OPMopm> </OPMopm> <OEMoem> </OEMoem> <TDMtdm> </TDMtdm> </NDM>

i) Each message (APM, AEM, OPM, OEM, TDM) consists of a <header> and a <body>. Additionally, the body consists of one or more <segment> constructs, depending upon the message type. Each segment consists of a <metadata>/<data> pair. Note that the <body> and <segment> constructs are not explicitly specified in the constituent message documents (see references [3], [4], [5]),; however, they are logically implied, and are necessary in order to enforce the strict ordering of metadata and data sections. There are two basic message substructures as discussed in the following two sections; one is used for the “parameter messages” (APM, OPM), the other is used for the “ephemeris messages” (AEM, OEM) and TDM.

4.2 SUBSTRUCTURE 1: APM, OPM

In Substructure 1, the body consists of a single segment (in essence, the segment tag is not strictly necessary, however, it is present for structural symmetry with Substructure 2 in the “body” of the message).



Figure 4-2 NDM/XML Substructure for APM and OPM (apm, opm)

<header> </header> <body> <segment> <metadata> </metadata> <data> </data> </segment> </body>

4.3 SUBSTRUCTURE 2: AEM, OEM, TDM

In Substructure 2, the body consists of one or more segments. The alternation of associated metadata and data sections are is the structural element that necessitates the notion of the segment.



Figure 4-3 NDM/XML Substructure for AEM, OEM, TDM

<header> </header> <body> <segment> <metadata> </metadata> <data> </data> </segment> <segment> <metadata> </metadata> <data> </data> </segment> . . . <segment> <metadata> </metadata> <data> </data> </segment> </body>

4.4 NDM/XML TAGS

Within the above structure and substructure, the individual tags specific to the various message types are defined. See the reference documents [3], [4], [5] for the details regarding the contents of the specific tags. This document will describe the XML tags, which with rare exception are identical to the keywords in the reference documents.

As a general rule, an NDM/XML tag shall be all uppercase if it corresponds directly to a keyword in one of the reference documents. NDM/XML keywords that do not correspond directly to a keyword in one of the reference documents will be in “LowerCamelCase”. CamelCase is a common name for the practice of writing compound words or phrases where the words are joined without spaces, and each word is capitalized within the compound. In the variant known as LowerCamelCase, the first word starts with a lower case character, and each successive word has its first letter capitalized. If the tag consists of only a single word (e.g., “header”), the tag consists entirely of lower case characters.



4.5 DISCUSSION OF “CHECKING”

Note that there are some elements in the ADM, ODM, TDM that have structure for which checking is not done. The notion of developing 2 schemas has been discussed; one which provides a strict level of checking for all structured items in the navigation data messages, and one which provides a more relaxed level of checking for certain uses, e.g., testing of simulated files for prospective missions, etc.Specifically, time systems, object names, reference frames, and center names could be defined by an enumerated list, and object ID’s could be defined via a pattern that must be matched. However, it has been decided not to enforce these restrictions and allow a generic string to be used for the values associated with these concepts.


CCSDS 505.0-W-1.78 Page A-1 September 2005

ANNEX A

RATIONALE FOR TRACKING DATA MESSAGES

(This annex is not part of the Draft Recommendation)

A1 GENERAL

NOTE: The following lists of requirements have been assembled by starting from the list of ODM/TDM requirements and eliminating requirements that were specific to the technical content of those documents. To the remaining requirements were added some that seemed to apply to the XML implementation (from the unilateral point of this author). These represent a starting point for discussion.

This annex presents the rationale behind the design of the Navigation Data Message XML Specification. It may help the application engineer construct a suitable valid message. Corrections and/or additions to these requirements may occur during future updates.

A specification of requirements agreed to by all parties is essential to focus design and to ensure the product meets the needs of the Member Agencies. There are many ways of organizing requirements, but the categorization of requirements is not as important as the agreement to a sufficiently comprehensive set. In this section the requirements are organized into three categories:

Primary Requirements - These are the most elementary and necessary requirements. They would exist no matter the context in which the CCSDS is operating: i.e., regardless of pre-existing conditions within the CCSDS or its Member Agencies.

Heritage Requirements - These are additional requirements that derive from pre-existing Member Agency requirements, conditions or needs. Ultimately these carry the same weight as the Primary Requirements. This Draft Recommendation reflects heritage requirements pertaining to some of the panels' home institutions collected during the preparation of the Draft Recommendation; it does not speculate on heritage requirements that could arise from other Member Agencies. Corrections and/or additions to these requirements are expected during future updates.

Desirable Characteristics - These are not requirements, but they are felt to be important or useful features of the Draft Recommendation.



A2 PRIMARY REQUIREMENTS ACCEPTED FOR TRACKING DATA MESSAGES

Table A-1: Primary Requirements

ID Requirement Trace A-1-1 The NDM/XML data must be provided in digital form (computer file).

A-1-2 The NDM/XML shall be represented by a valid XML format descriptor.

A-1-3 The NDM/XML format descriptor shall be hosted on the CCSDS web site, and shared by all agencies exchanging instantiations of the format descriptor.

A-1-4 The NDM/XML implementation shall allow for the representation of all the fields available in the Attitude Data Message (ADM). (reference [3]). apply modularization? ADM/XML

A-1-5 The NDM/XML implementation shall allow for the representation of all the fields available in the Orbit Data Message (ODM). (reference [4]). apply modularization? ODM/XML

A-1-6 The NDM/XML implementation shall allow for the representation of all the fields available in the Tracking Data Message (TDM). (reference [5]). apply modularization? TDM/XML

A-1-7 Should there be a requirement which mandates the connectivity test function?

A-1-8 Units must be specified in the NDM/XML instantiations (??). The standard must provide for clear specification of units of measure. (Note: units are specified in the ADM/ODM/TDM, so may not be a requirement for NDM/XML).

A-1-97 Files must be readily portable between and useable within ‘all’ computational environments in use by Member Agencies choosing to exchange NDM’s via XML.

A-1-108

Files must have means of being uniquely identified and clearly annotated. The file name alone is considered insufficient for this purpose.

A-1-119

File name syntax and length must not violate computer constraints for those computing environments in use by Member Agencies.

A-1-1210

The NDM/XML shall use XML elements where there is substructure associated with information, e.g., maneuver parameters.

A-1-1311

The NDM/XML shall use XML elements where there is data type checking associated with information, e.g., maneuver parameters.

A-1-14 The NDM/XML may use XML attributes where there is no substructure associated with information (e.g., units specifications). Reword with “shall”…



Table A-2: Heritage Requirements

ID Requirement Trace

A-2-1 The standard shall be, or must include, an ASCII format.

A-2-2 The standard shall not require software supplied by other agencies to process valid instantiations of the NDM/XML schema.

Table A-3: Desirable Characteristics

Requirement Trace

A-3-1 The standard should be extensible with no disruption to existing users/uses.

A-3-2 Keywords, values, and terminology in the NDM/XML should be the same as those in the ODM, ADM, and TDM, insofar as it is possible.

A-3-3 Structures in the NDM/XML should be re-used across the different message types where practical.

A-3-4 The NDM/XML should minimize the use of tags that do not correspond to keywords in the ADM, ODM, or TDM.

A-3-5 Units may be specified in the NDM/XML instantiations. The standard should provide for clear specification of units of measure.

A-3-6 The NDM/XML may use XML attributes where there is no substructure associated with information (e.g., units specifications).


CCSDS 505.0-W-1.78 Page B-4 September 2005

ANNEX B

ABBREVIATIONS AND ACRONYMS ADM Attitude Data Message AEM Attitude Ephemeris Message aem Attitude Ephemeris Message tag APM Attitude Parameter Message apm Attitude Parameter Message tag ASCII American Standard Code for Information Interchange ANSI American National Standards Institute CCSDS Consultative Committee on Space Data Systems DTD Document Type Definition ICD Interface Control Document IEEE Institute of Electrical and Electronics Engineers ISO International Standards Organization KVN “Keyword = Value” notation MOIMS Mission Operations and Information Management Services N/A Not Applicable / Not Available NDM Navigation Data Message ndm Navigation Data Message tag ODM Orbit Data Message OEM Orbit Ephemeris Message oem Orbit Ephemeris Message tag OPM Orbit Parameter Message opm Orbit Parameter Message tag PVL Parameter Value Language TDM Tracking Data Message tdm Tracking Data Message tag UTC Coordinated Universal Time XML eXtensible Markup Language XSLT eXtensible Stylesheet Language Transformations

CCSDS 505.0-W-1.78 Page C-5 September 2005

ANNEX C NDM/XML MASTER SCHEMA

This annex lists the NDM/XML Master Schema, the top level module in the modular schema. This XML Schema in conjunction with the NDM/XML instances referred to in Annex xxx will validate successfully when validation-checked at:

http://tools.decisionsoft.com/schemaValidate.html

At the time of this publication the suggested URL is active. Users may need to find a current validation tool in the future.

The modular NDM/XML Schema may be found on the CCSDS web page at:

http://public.ccsds.org/sites/cwe/moims-nav/Public/Schemas/

NOTE: The Navigation Working Group is in favor of CCSDS providing a standard XML validator, and perhaps other standardized XML developer tools, at an applicable CCSDS web site. <?xml version="1.0"?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<xsd:include schemaLocation="http://public.ccsds.org/sites/cwe/moims-nav/Public/Schemas/ndmxml-aem-1.8.xsd"/> <xsd:include schemaLocation="http://public.ccsds.org/sites/cwe/moims-nav/Public/Schemas/ndmxml-apm-1.8.xsd"/> <xsd:include schemaLocation="http://public.ccsds.org/sites/cwe/moims-nav/Public/Schemas/ndmxml-oem-1.8.xsd"/> <xsd:include schemaLocation="http://public.ccsds.org/sites/cwe/moims-nav/Public/Schemas/ndmxml-opm-1.8.xsd"/> <xsd:include schemaLocation="http://public.ccsds.org/sites/cwe/moims-nav/Public/Schemas/ndmxml-tdm-1.8.xsd"/> <xsd:include schemaLocation="http://public.ccsds.org/sites/cwe/moims-nav/Public/Schemas/ndmxml-common-1.8.xsd"/>    <xsd:element name="ndm" type="ndmType"/> <xsd:complexType name="ndmType">       <xsd:sequence> <xsd:element name="ndmVersion" type="ndmVersionType"/> <xsd:element name="COMMENT" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <xsd:choice minOccurs="0" maxOccurs="unbounded"> <xsd:element ref="aem" /> <xsd:element ref="apm" /> <xsd:element ref="oem" /> <xsd:element ref="opm" /> <xsd:element ref="tdm" /> </xsd:choice> </xsd:sequence> </xsd:complexType>     <xsd:complexType name="ndmVersionType"> <xsd:attribute name="version" type="ndmVersionString" use="required"

fixed="0.1.8"/> </xsd:complexType> <xsd:simpleType name="ndmVersionString"> <xsd:restriction base="xsd:string">  </xsd:restriction> </xsd:simpleType> </xsd:schema>

CCSDS 505.0-W-1.78 Page D-8 September 2005

ANNEX D AEM SCHEMA <?xml version="1.0"?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">                       <xsd:element name="aem" type="aemType"/>     <xsd:complexType name="aemType"> <xsd:sequence> <xsd:element name="header" type="ndmHeader"/> <xsd:element name="body" type="aemBody"/> </xsd:sequence> </xsd:complexType>    <xsd:complexType name="aemBody"> <xsd:sequence> <xsd:element name="segment" type="aemSegment" minOccurs="1" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType>

<xsd:complexType name="aemSegment"> <xsd:sequence> <xsd:element name="metadata" type="aemMetadata"/> <xsd:element name="data" type="aemData"/> </xsd:sequence> </xsd:complexType>    <xsd:complexType name="aemMetadata"> <xsd:sequence> <xsd:element name="COMMENT" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="OBJECT_NAME" type="xsd:string"/> <xsd:element name="OBJECT_ID" type="xsd:string"/> <xsd:element name="CENTER_NAME" type="xsd:string"/> <xsd:element name="REF_FRAME" type="xsd:string"/> <xsd:element name="TIME_SYSTEM" type="xsd:string"/> <xsd:element name="START_TIME" type="epochType"/> <xsd:element name="USEABLE_START_TIME" type="epochType" minOccurs="0"/> <xsd:element name="USEABLE_STOP_TIME" type="epochType" minOccurs="0"/> <xsd:element name="STOP_TIME" type="epochType"/> <xsd:element name="ATTITUDE_TYPE" type="attitudeTypeType"/> <xsd:element name="QUATERNION_TYPE" type="quaternionTypeType" minOccurs="0"/> <xsd:element name="EULER_ROT_SEQ" type="rotseqType" minOccurs="0"/> <xsd:element name="INTERPOLATION_METHOD" type="xsd:string" minOccurs="0"/> <xsd:element name="INTERPOLATION_DEGREE" type="xsd:positiveInteger" minOccurs="0"/> </xsd:sequence> </xsd:complexType>    <xsd:complexType name="aemData"> <xsd:sequence> <xsd:element name="COMMENT" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="attitudeVector" type="attitudeVectorType" minOccurs="1" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType>

<xsd:complexType name="attitudeVectorType"> <xsd:choice> <xsd:element name="quaternion" type="quaternionType"/> <xsd:element name="quaternionDerivative" type="quaternionDerivativeType"/> <xsd:element name="quaternionEulerRate" type="quaternionEulerRateType"/> <xsd:element name="eulerAngle" type="eulerAngleType"/> <xsd:element name="eulerAngleRate" type="eulerAngleRateType"/> <xsd:element name="spin" type="spinType"/> <xsd:element name="spinNutation" type="spinNutationType"/> </xsd:choice> </xsd:complexType> <xsd:complexType name="quaternionType">  <xsd:sequence> <xsd:element name="EPOCH" type="epochType"/> <xsd:choice> <xsd:sequence> <xsd:element name="QC" type="quaternionComponentType"/> <xsd:element name="Q1" type="quaternionComponentType"/> <xsd:element name="Q2" type="quaternionComponentType"/> <xsd:element name="Q3" type="quaternionComponentType"/> </xsd:sequence> <xsd:sequence> <xsd:element name="Q1" type="quaternionComponentType"/> <xsd:element name="Q2" type="quaternionComponentType"/> <xsd:element name="Q3" type="quaternionComponentType"/> <xsd:element name="QC" type="quaternionComponentType"/> </xsd:sequence> </xsd:choice> </xsd:sequence> </xsd:complexType> <xsd:complexType name="quaternionDerivativeType">  <xsd:sequence> <xsd:element name="EPOCH" type="epochType"/> <xsd:choice> <xsd:sequence> <xsd:element name="QC" type="quaternionComponentType"/> <xsd:element name="Q1" type="quaternionComponentType"/> <xsd:element name="Q2" type="quaternionComponentType"/> <xsd:element name="Q3" type="quaternionComponentType"/> <xsd:element name="QC_DOT" type="quaternionRateType"/> <xsd:element name="Q1_DOT" type="quaternionRateType"/> <xsd:element name="Q2_DOT" type="quaternionRateType"/> <xsd:element name="Q3_DOT" type="quaternionRateType"/> </xsd:sequence> <xsd:sequence> <xsd:element name="Q1" type="quaternionComponentType"/> <xsd:element name="Q2" type="quaternionComponentType"/> <xsd:element name="Q3" type="quaternionComponentType"/> <xsd:element name="QC" type="quaternionComponentType"/> <xsd:element name="Q1_DOT" type="quaternionRateType"/> <xsd:element name="Q2_DOT" type="quaternionRateType"/> <xsd:element name="Q3_DOT" type="quaternionRateType"/> <xsd:element name="QC_DOT" type="quaternionRateType"/>

</xsd:sequence> </xsd:choice> </xsd:sequence> </xsd:complexType> <xsd:complexType name="quaternionEulerRateType">  <xsd:sequence> <xsd:element name="EPOCH" type="epochType"/> <xsd:choice> <xsd:sequence> <xsd:element name="QC" type="quaternionComponentType"/> <xsd:element name="Q1" type="quaternionComponentType"/> <xsd:element name="Q2" type="quaternionComponentType"/> <xsd:element name="Q3" type="quaternionComponentType"/> </xsd:sequence> <xsd:sequence> <xsd:element name="Q1" type="quaternionComponentType"/> <xsd:element name="Q2" type="quaternionComponentType"/> <xsd:element name="Q3" type="quaternionComponentType"/> <xsd:element name="QC" type="quaternionComponentType"/> </xsd:sequence> </xsd:choice> <xsd:element name="ROLL_RATE" type="angleRateType"/> <xsd:element name="PITCH_RATE" type="angleRateType"/> <xsd:element name="YAW_RATE" type="angleRateType"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="eulerAngleType">  <xsd:sequence> <xsd:element name="EPOCH" type="epochType"/> <xsd:element name="ROLL" type="angleType"/> <xsd:element name="PITCH" type="angleType"/> <xsd:element name="YAW" type="angleType"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="eulerAngleRateType">  <xsd:sequence> <xsd:element name="EPOCH" type="epochType"/> <xsd:element name="ROLL" type="angleType"/> <xsd:element name="PITCH" type="angleType"/> <xsd:element name="YAW" type="angleType"/> <xsd:element name="ROLL_RATE" type="angleRateType"/> <xsd:element name="PITCH_RATE" type="angleRateType"/> <xsd:element name="YAW_RATE" type="angleRateType"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="spinType">  <xsd:sequence> <xsd:element name="EPOCH" type="epochType"/> <xsd:element name="SPIN_ALPHA" type="angleType"/> <xsd:element name="SPIN_DELTA" type="angleType"/>

<xsd:element name="SPIN_ANGLE" type="angleType"/> <xsd:element name="SPIN_ANGLE_VEL" type="angleRateType"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="spinNutationType">  <xsd:sequence> <xsd:element name="EPOCH" type="epochType"/> <xsd:element name="SPIN_ALPHA" type="angleType"/> <xsd:element name="SPIN_DELTA" type="angleType"/> <xsd:element name="SPIN_ANGLE" type="angleType"/> <xsd:element name="SPIN_ANGLE_VEL" type="angleRateType"/> <xsd:element name="NUTATION" type="angleType"/> <xsd:element name="NUTATION_PER" type="durationType"/> </xsd:sequence> </xsd:complexType>    <xsd:simpleType name="attitudeTypeType"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="quaternion"/> <xsd:enumeration value="QUATERNION"/> <xsd:enumeration value="quaternion/derivative"/> <xsd:enumeration value="QUATERNION/DERIVATIVE"/> <xsd:enumeration value="quaternion/rate"/> <xsd:enumeration value="QUATERNION/RATE"/> <xsd:enumeration value="euler_angle"/> <xsd:enumeration value="EULER_ANGLE"/> <xsd:enumeration value="euler_angle/rate"/> <xsd:enumeration value="EULER_ANGLE/RATE"/> <xsd:enumeration value="spin"/> <xsd:enumeration value="SPIN"/> <xsd:enumeration value="spin/nutation"/> <xsd:enumeration value="SPIN/NUTATION"/> </xsd:restriction> </xsd:simpleType> <xsd:simpleType name="quaternionTypeType"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="first"/> <xsd:enumeration value="FIRST"/> <xsd:enumeration value="last"/> <xsd:enumeration value="LAST"/> </xsd:restriction> </xsd:simpleType> </xsd:schema>

CCSDS 505.0-W-1.78 Page E-13 September 2005

ANNEX E APM SCHEMA <?xml version="1.0"?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">                       <xsd:element name="apm" type="apmType"/>     <xsd:complexType name="apmType"> <xsd:sequence> <xsd:element name="header" type="ndmHeader"/> <xsd:element name="body" type="apmBody"/> </xsd:sequence> </xsd:complexType>    <xsd:complexType name="apmBody"> <xsd:sequence> <xsd:element name="segment" type="apmSegment" minOccurs="1" maxOccurs="1"/> </xsd:sequence> </xsd:complexType>

<xsd:complexType name="apmSegment"> <xsd:sequence> <xsd:element name="metadata" type="apmMetadata"/> <xsd:element name="data" type="apmData"/> </xsd:sequence> </xsd:complexType>    <xsd:complexType name="apmMetadata"> <xsd:sequence> <xsd:element name="COMMENT" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="OBJECT_NAME" type="xsd:string"/> <xsd:element name="OBJECT_ID" type="xsd:string"/> <xsd:element name="CENTER_NAME" type="xsd:string"/> <xsd:element name="TIME_SYSTEM" type="xsd:string"/> </xsd:sequence> </xsd:complexType>    <xsd:complexType name="apmData"> <xsd:sequence> <xsd:element name="COMMENT" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="stateVector" type="attStateVectorType"/> <xsd:element name="eulerElementsThree" type="eulerElementsThreeType" minOccurs="0"/> <xsd:element name="eulerElementsSpin" type="eulerElementsSpinType" minOccurs="0"/> <xsd:element name="spacecraftParameters" type="attSpacecraftParametersType" minOccurs="0"/> <xsd:element name="maneuverParameters" type="attManeuverParametersType" minOccurs="0" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType>    <xsd:complexType name="attStateVectorType"> <xsd:sequence> <xsd:element name="COMMENT" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="EPOCH" type="epochType"/> <xsd:element name="Q_FRAME" type="xsd:string"/> <xsd:element name="Q1" type="quaternionComponentType"/> <xsd:element name="Q2" type="quaternionComponentType"/> <xsd:element name="Q3" type="quaternionComponentType"/> <xsd:element name="QC" type="quaternionComponentType"/> <xsd:element name="Q1_DOT" type="xsd:double" minOccurs="0"/> <xsd:element name="Q2_DOT" type="xsd:double" minOccurs="0"/> <xsd:element name="Q3_DOT" type="xsd:double" minOccurs="0"/> <xsd:element name="QC_DOT" type="xsd:double" minOccurs="0"/>

</xsd:sequence> </xsd:complexType>       <xsd:complexType name="eulerElementsThreeType"> <xsd:sequence> <xsd:element name="COMMENT" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="EULER_FRAME" type="xsd:string"/> <xsd:element name="EULER_ROT_SEQ" type="rotseqType"/> <xsd:element name="ROLL" type="angleType"/> <xsd:element name="PITCH" type="angleType"/> <xsd:element name="YAW" type="angleType"/> <xsd:element name="ROLL_RATE" type="angleRateType"/> <xsd:element name="PITCH_RATE" type="angleRateType"/> <xsd:element name="YAW_RATE" type="angleRateType"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="eulerElementsSpinType"> <xsd:sequence> <xsd:element name="COMMENT" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="SPIN_FRAME" type="xsd:string"/> <xsd:element name="SPIN_ALPHA" type="angleType"/> <xsd:element name="SPIN_DELTA" type="angleType"/> <xsd:element name="SPIN_ANGLE" type="angleType"/> <xsd:element name="SPIN_ANGLE_VEL" type="angleRateType"/> <xsd:element name="NUTATION" type="angleType"/> <xsd:element name="NUTATION_PER" type="positiveDouble"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="attSpacecraftParametersType"> <xsd:sequence> <xsd:element name="COMMENT" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="IX" type="momentType"/> <xsd:element name="IY" type="momentType"/> <xsd:element name="IZ" type="momentType"/> <xsd:element name="IXY" type="productMomentType"/> <xsd:element name="IXZ" type="productMomentType"/> <xsd:element name="IYZ" type="productMomentType"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="attManeuverParametersType"> <xsd:sequence> <xsd:element name="COMMENT" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="MAN_EPOCH_START" type="epochType"/> <xsd:element name="MAN_DURATION" type="nonNegativeDouble"/> <xsd:element name="MAN_REF_FRAME" type="xsd:string"/>

<xsd:element name="MAN_TOR_1" type="torqueType"/> <xsd:element name="MAN_TOR_2" type="torqueType"/> <xsd:element name="MAN_TOR_3" type="torqueType"/> </xsd:sequence> </xsd:complexType>    <xsd:complexType name="momentType"> <xsd:simpleContent> <xsd:extension base="nonNegativeDouble"> <xsd:attribute name="units" type="momentUnits" use="optional"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <xsd:complexType name="productMomentType"> <xsd:simpleContent> <xsd:extension base="xsd:double"> <xsd:attribute name="units" type="momentUnits" use="optional"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <xsd:simpleType name="momentUnits"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="kg*m**2"/> <xsd:enumeration value="KG*M**2"/> </xsd:restriction> </xsd:simpleType> <xsd:complexType name="torqueType"> <xsd:simpleContent> <xsd:extension base="xsd:double"> <xsd:attribute name="units" type="torqueUnits" use="optional"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <xsd:simpleType name="torqueUnits"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="n*m"/> <xsd:enumeration value="N*m"/> <xsd:enumeration value="N*M"/> </xsd:restriction> </xsd:simpleType> </xsd:schema>

CCSDS 505.0-W-1.78 Page F-17 September 2005

ANNEX F OEM SCHEMA <?xml version="1.0"?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">                   <xsd:element name="oem" type="oemType"/>     <xsd:complexType name="oemType"> <xsd:sequence> <xsd:element name="header" type="ndmHeader"/> <xsd:element name="body" type="oemBody"/> </xsd:sequence> </xsd:complexType>    <xsd:complexType name="oemBody"> <xsd:sequence> <xsd:element name="segment" type="oemSegment" minOccurs="1" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType>

CCSDS 505.0-W-1.78 Page F-18 September 2005

 <xsd:complexType name="oemSegment"> <xsd:sequence> <xsd:element name="metadata" type="oemMetadata"/> <xsd:element name="data" type="oemData"/> </xsd:sequence> </xsd:complexType>    <xsd:complexType name="oemMetadata"> <xsd:sequence> <xsd:element name="COMMENT" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="OBJECT_NAME" type="xsd:string"/> <xsd:element name="OBJECT_ID" type="xsd:string"/> <xsd:element name="CENTER_NAME" type="xsd:string"/> <xsd:element name="REF_FRAME" type="xsd:string"/> <xsd:element name="TIME_SYSTEM" type="xsd:string"/> <xsd:element name="START_TIME" type="epochType"/> <xsd:element name="USEABLE_START_TIME" type="epochType" minOccurs="0"/> <xsd:element name="USEABLE_STOP_TIME" type="epochType" minOccurs="0"/> <xsd:element name="STOP_TIME" type="epochType"/> <xsd:element name="INTERPOLATION" type="xsd:string" minOccurs="0"/> <xsd:element name="INTERPOLATION_DEGREE" type="xsd:positiveInteger" minOccurs="0"/> </xsd:sequence> </xsd:complexType>    <xsd:complexType name="oemData"> <xsd:sequence> <xsd:element name="COMMENT" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="stateVector" type="stateVectorType" minOccurs="1" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> </xsd:schema>

CCSDS 505.0-W-1.78 Page G-19 September 2005

ANNEX G OPM SCHEMA <?xml version="1.0"?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">                    <xsd:element name="opm" type="opmType"/>     <xsd:complexType name="opmType"> <xsd:sequence> <xsd:element name="header" type="ndmHeader"/> <xsd:element name="body" type="opmBody"/> </xsd:sequence> </xsd:complexType>    <xsd:complexType name="opmBody"> <xsd:sequence> <xsd:element name="segment" type="opmSegment" minOccurs="1" maxOccurs="1"/> </xsd:sequence> </xsd:complexType>      <xsd:complexType name="opmSegment"> <xsd:sequence>

<xsd:element name="metadata" type="opmMetadata"/> <xsd:element name="data" type="opmData"/> </xsd:sequence> </xsd:complexType>    <xsd:complexType name="opmMetadata"> <xsd:sequence> <xsd:element name="COMMENT" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="OBJECT_NAME" type="xsd:string"/> <xsd:element name="OBJECT_ID" type="xsd:string"/> <xsd:element name="CENTER_NAME" type="xsd:string"/> <xsd:element name="REF_FRAME" type="xsd:string"/> <xsd:element name="TIME_SYSTEM" type="xsd:string"/> </xsd:sequence> </xsd:complexType>    <xsd:complexType name="opmData"> <xsd:sequence> <xsd:element name="COMMENT" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="stateVector" type="stateVectorType"/> <xsd:element name="keplerianElements" type="keplerianElementsType" minOccurs="0"/> <xsd:element name="spacecraftParameters" type="spacecraftParametersType"/> <xsd:element name="maneuverParameters" type="maneuverParametersType" minOccurs="0" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType>     <xsd:complexType name="keplerianElementsType"> <xsd:sequence> <xsd:element name="COMMENT" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="SEMI_MAJOR_AXIS" type="distanceType"/> <xsd:element name="ECCENTRICITY" type="nonNegativeDouble"/> <xsd:element name="INCLINATION" type="inclinationType"/> <xsd:element name="RA_OF_ASC_NODE" type="angleType"/> <xsd:element name="ARG_OF_PERICENTER" type="angleType"/> <xsd:choice> <xsd:element name="TRUE_ANOMALY" type="angleType"/> <xsd:element name="MEAN_ANOMALY" type="angleType"/>

</xsd:choice> <xsd:element name="GM" type="gmType"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="spacecraftParametersType"> <xsd:sequence> <xsd:element name="COMMENT" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="MASS" type="massType"/> <xsd:element name="SOLAR_RAD_AREA" type="areaType"/> <xsd:element name="SOLAR_RAD_COEFF" type="nonNegativeDouble"/> <xsd:element name="DRAG_AREA" type="areaType"/> <xsd:element name="DRAG_COEFF" type="nonNegativeDouble"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="maneuverParametersType"> <xsd:sequence> <xsd:element name="COMMENT" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="MAN_EPOCH_IGNITION" type="epochType"/> <xsd:element name="MAN_DURATION" type="durationType"/> <xsd:element name="MAN_DELTA_MASS" type="deltamassType"/> <xsd:element name="MAN_REF_FRAME" type="xsd:string"/> <xsd:element name="MAN_DV_1" type="speedType"/> <xsd:element name="MAN_DV_2" type="speedType"/> <xsd:element name="MAN_DV_3" type="speedType"/> </xsd:sequence> </xsd:complexType>    <xsd:complexType name="inclinationType"> <xsd:simpleContent> <xsd:extension base="inclination"> <xsd:attribute name="units" type="angleUnits" use="optional"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <xsd:simpleType name="inclination"> <xsd:restriction base="angleRange"> <xsd:minInclusive value="0.0"/> <xsd:maxInclusive value="180.0"/> </xsd:restriction> </xsd:simpleType> <xsd:complexType name="gmType"> <xsd:simpleContent> <xsd:extension base="positiveDouble"> <xsd:attribute name="units" type="gmUnits" use="optional"/> </xsd:extension> </xsd:simpleContent>



</xsd:complexType> <xsd:simpleType name="gmUnits"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="km**3/s**2"/> <xsd:enumeration value="KM**3/S**2"/> </xsd:restriction> </xsd:simpleType> </xsd:schema>

CCSDS 505.0-W-1.78 Page H-23 September 2005

ANNEX H TDM SCHEMA <?xml version="1.0"?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">                             <xsd:element name="tdm" type="tdmType"/>     <xsd:complexType name="tdmType"> <xsd:sequence> <xsd:element name="header" type="ndmHeader"/> <xsd:element name="body" type="tdmBody"/> </xsd:sequence> </xsd:complexType>    <xsd:complexType name="tdmBody"> <xsd:sequence> <xsd:element name="segment" type="tdmSegment" minOccurs="1" maxOccurs="unbounded"/> </xsd:sequence>

</xsd:complexType>         <xsd:complexType name="tdmSegment"> <xsd:sequence> <xsd:element name="metadata" type="tdmMetadata"/> <xsd:element name="data" type="tdmData"/> </xsd:sequence> </xsd:complexType>    <xsd:complexType name="tdmMetadata"> <xsd:sequence> <xsd:element name="COMMENT" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="TIME_SYSTEM" type="xsd:string"/> <xsd:element name="PARTICIPANT_1" type="xsd:string"/> <xsd:element name="PARTICIPANT_2" type="xsd:string" minOccurs="0"/> <xsd:element name="PARTICIPANT_3" type="xsd:string" minOccurs="0"/> <xsd:element name="PARTICIPANT_4" type="xsd:string" minOccurs="0"/> <xsd:element name="PARTICIPANT_5" type="xsd:string" minOccurs="0"/> <xsd:element name="MODE" type="modeType" /> <xsd:element name="PATH" type="pathType" default="N/A" minOccurs="0" /> <xsd:element name="DIFF_MODE" type="diffmodeType" default="N/A" minOccurs="0" /> <xsd:element name="TIMETAG_REF" type="timetagType" default="RECEIVE" minOccurs="0" /> <xsd:element name="INTEGRATION_INTERVAL" type="nonNegativeDouble" default="1.0" minOccurs="0"/> <xsd:element name="INTEGRATION_REF" type="integrationrefType" default="MIDDLE" minOccurs="0" /> <xsd:element name="FREQ_OFFSET" type="xsd:double" default="0.0" minOccurs="0" /> <xsd:element name="RANGE_MODE" type="rangemodeType" default="COHERENT" minOccurs="0" /> <xsd:element name="RANGE_MODULUS" type="nonNegativeDouble" default="0.0" minOccurs="0"/> <xsd:element name="RANGE_UNITS" type="rangeunitsType" default="S" minOccurs="0"/> <xsd:element name="ANGLE_TYPE" type="angleTypeType" default="N/A" minOccurs="0"/> <xsd:element name="REFERENCE_FRAME" type="xsd:string" default="N/A" minOccurs="0" />

<xsd:element name="TRANSMIT_DELAY_1" type="nonNegativeDouble" default="0.0" minOccurs="0" /> <xsd:element name="TRANSMIT_DELAY_2" type="nonNegativeDouble" default="0.0" minOccurs="0" /> <xsd:element name="TRANSMIT_DELAY_3" type="nonNegativeDouble" default="0.0" minOccurs="0" /> <xsd:element name="TRANSMIT_DELAY_4" type="nonNegativeDouble" default="0.0" minOccurs="0" /> <xsd:element name="TRANSMIT_DELAY_5" type="nonNegativeDouble" default="0.0" minOccurs="0" /> <xsd:element name="RECEIVE_DELAY_1" type="nonNegativeDouble" default="0.0" minOccurs="0" /> <xsd:element name="RECEIVE_DELAY_2" type="nonNegativeDouble" default="0.0" minOccurs="0" /> <xsd:element name="RECEIVE_DELAY_3" type="nonNegativeDouble" default="0.0" minOccurs="0" /> <xsd:element name="RECEIVE_DELAY_4" type="nonNegativeDouble" default="0.0" minOccurs="0" /> <xsd:element name="RECEIVE_DELAY_5" type="nonNegativeDouble" default="0.0" minOccurs="0" /> <xsd:element name="START_TIME" type="epochType" /> <xsd:element name="STOP_TIME" type="epochType" /> <xsd:element name="DATA_QUALITY" type="dataQualityType" default="VALIDATED" minOccurs="0" /> <xsd:element name="CORRECTION_RNGCAL" type="xsd:double" minOccurs="0" /> <xsd:element name="CORRECTION_ANGLE_1" type="xsd:double" minOccurs="0" /> <xsd:element name="CORRECTION_ANGLE_2" type="xsd:double" minOccurs="0" /> <xsd:element name="CORRECTION_DOPPLER" type="xsd:double" minOccurs="0" /> <xsd:element name="CORRECTION_TROPO" type="xsd:double" minOccurs="0" /> <xsd:element name="CORRECTION_CP" type="xsd:double" minOccurs="0" /> </xsd:sequence> </xsd:complexType>    <xsd:complexType name="tdmData"> <xsd:sequence> <xsd:element name="COMMENT" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="observation" type="trackingDataObservationType" minOccurs="1" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType>

<xsd:complexType name="trackingDataObservationType"> <xsd:sequence> <xsd:element name="EPOCH" type="epochType"/> <xsd:choice> <xsd:element name="AGC" type="xsd:double" /> <xsd:element name="ANGLE_1" type="angleType"/> <xsd:element name="ANGLE_2" type="angleType"/> <xsd:element name="AZIMUTH_RATE" type="xsd:double"/> <xsd:element name="CARRIER_SNR" type="xsd:double"/> <xsd:element name="CLOCK_BIAS" type="xsd:double" default="0.0"/> <xsd:element name="CLOCK_DRIFT" type="xsd:double" default="0.0"/> <xsd:element name="CPDELAY" type="xsd:double" /> <xsd:element name="PRESSURE" type="xsd:double"/> <xsd:element name="RANGE_OBS" type="xsd:double"/> <xsd:element name="RANGE_RATE" type="xsd:double"/> <xsd:element name="RANGE_SNR" type="xsd:double"/> <xsd:element name="RECEIVE_FREQ" type="xsd:double"/> <xsd:element name="RECEIVE_FREQ_1" type="xsd:double"/> <xsd:element name="RECEIVE_FREQ_2" type="xsd:double"/> <xsd:element name="RECEIVE_FREQ_3" type="xsd:double"/> <xsd:element name="RECEIVE_FREQ_4" type="xsd:double"/> <xsd:element name="RECEIVE_FREQ_5" type="xsd:double"/> <xsd:element name="RHUMIDITY" type="percentType"/> <xsd:element name="TEMPERATURE" type="nonNegativeDouble"/> <xsd:element name="TRANSMIT_FREQ_1" type="positiveDouble"/> <xsd:element name="TRANSMIT_FREQ_2" type="positiveDouble"/> <xsd:element name="TRANSMIT_FREQ_3" type="positiveDouble"/> <xsd:element name="TRANSMIT_FREQ_4" type="positiveDouble"/> <xsd:element name="TRANSMIT_FREQ_5" type="positiveDouble"/> <xsd:element name="TRANSMIT_FREQ_RATE_1" type="xsd:double"/> <xsd:element name="TRANSMIT_FREQ_RATE_2" type="xsd:double"/> <xsd:element name="TRANSMIT_FREQ_RATE_3" type="xsd:double"/> <xsd:element name="TRANSMIT_FREQ_RATE_4" type="xsd:double"/> <xsd:element name="TRANSMIT_FREQ_RATE_5" type="xsd:double"/> <xsd:element name="TROPO_DRY" type="nonNegativeDouble"/> <xsd:element name="TROPO_WET" type="nonNegativeDouble"/> </xsd:choice> </xsd:sequence> </xsd:complexType> <xsd:simpleType name="timeRef"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="start"/> <xsd:enumeration value="Start"/> <xsd:enumeration value="START"/> <xsd:enumeration value="end" /> <xsd:enumeration value="End" /> <xsd:enumeration value="END" /> </xsd:restriction> </xsd:simpleType> <xsd:simpleType name="dataQualityType"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="raw"/> <xsd:enumeration value="RAW"/> <xsd:enumeration value="validated" />

<xsd:enumeration value="VALIDATED" /> <xsd:enumeration value="degraded" /> <xsd:enumeration value="DEGRADED" /> </xsd:restriction> </xsd:simpleType> <xsd:simpleType name="modeType"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="SEQUENTIAL"/> <xsd:enumeration value="sequential"/> <xsd:enumeration value="SINGLE-DIFF" /> <xsd:enumeration value="single-diff" /> <xsd:enumeration value="DOUBLE-DIFF" /> <xsd:enumeration value="double-diff" /> <xsd:enumeration value="N/A"/> <xsd:enumeration value="n/a"/> </xsd:restriction> </xsd:simpleType> <xsd:simpleType name="pathType">   <xsd:restriction base="xsd:string">  <xsd:pattern value="\d{1},\d{1}(,\d{1})*|N\/A"/> </xsd:restriction> </xsd:simpleType> <xsd:simpleType name="timetagType"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="TRANSMIT"/> <xsd:enumeration value="transmit"/> <xsd:enumeration value="RECEIVE"/> <xsd:enumeration value="receive"/> </xsd:restriction> </xsd:simpleType> <xsd:simpleType name="diffmodeType"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="delay"/> <xsd:enumeration value="DELAY"/> <xsd:enumeration value="range"/> <xsd:enumeration value="RANGE"/> <xsd:enumeration value="N/A" /> <xsd:enumeration value="n/a" /> </xsd:restriction> </xsd:simpleType> <xsd:simpleType name="integrationrefType"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="START"/> <xsd:enumeration value="start"/> <xsd:enumeration value="MIDDLE"/> <xsd:enumeration value="middle"/> <xsd:enumeration value="END"/> <xsd:enumeration value="end"/>



</xsd:restriction> </xsd:simpleType> <xsd:simpleType name="rangeunitsType"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="ru"/> <xsd:enumeration value="RU"/> <xsd:enumeration value="s"/> <xsd:enumeration value="S"/> <xsd:enumeration value="km"/> <xsd:enumeration value="KM"/> </xsd:restriction> </xsd:simpleType> <xsd:simpleType name="rangemodeType"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="coherent"/> <xsd:enumeration value="COHERENT"/> <xsd:enumeration value="constant"/> <xsd:enumeration value="CONSTANT"/> </xsd:restriction> </xsd:simpleType> <xsd:simpleType name="angleTypeType"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="AZEL"/> <xsd:enumeration value="azel"/> <xsd:enumeration value="RADEC"/> <xsd:enumeration value="radec"/> <xsd:enumeration value="XEYN"/> <xsd:enumeration value="xeyn"/> <xsd:enumeration value="XSYE"/> <xsd:enumeration value="xsye"/> <xsd:enumeration value="N/A"/> <xsd:enumeration value="n/a"/> </xsd:restriction> </xsd:simpleType> </xsd:schema>

CCSDS 505.0-W-1.78 Page I-29 September 2005

ANNEX I NDM/XML COMMON SCHEMA <?xml version="1.0"?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">                        <xsd:complexType name="ndmHeader"> <xsd:sequence> <xsd:choice> <xsd:element name="CCSDS_AEM_VERS" type="versionType" fixed="0.2.5"/> <xsd:element name="CCSDS_APM_VERS" type="versionType" fixed="0.2.5"/> <xsd:element name="CCSDS_OEM_VERS" type="versionType" fixed="1.0"/> <xsd:element name="CCSDS_OPM_VERS" type="versionType" fixed="1.0"/> <xsd:element name="CCSDS_TDM_VERS" type="versionType" fixed="0.1.18"/> </xsd:choice> <xsd:element name="COMMENT" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="CREATION_DATE" type="epochType"/> <xsd:element name="ORIGINATOR" type="xsd:string"/> </xsd:sequence> </xsd:complexType>

<xsd:simpleType name="epochType"> <xsd:restriction base="xsd:string"> <xsd:pattern value="-?\d{4}\d*-((\d{2}-\d{2})|\d{3})T\d{2}:\d{2}:\d{2}(\.\d*)?(Z|[+|-]\d{2}:\d{2})?|[+|-]?\d*(\.\d*)?"/> </xsd:restriction> </xsd:simpleType> <xsd:complexType name="stateVectorType"> <xsd:sequence> <xsd:element name="COMMENT" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="EPOCH" type="epochType"/> <xsd:element name="X" type="distanceType"/> <xsd:element name="Y" type="distanceType"/> <xsd:element name="Z" type="distanceType"/> <xsd:element name="X_DOT" type="speedType"/> <xsd:element name="Y_DOT" type="speedType"/> <xsd:element name="Z_DOT" type="speedType"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="distanceType"> <xsd:simpleContent> <xsd:extension base="xsd:double"> <xsd:attribute name="units" type="distance" use="optional"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <xsd:simpleType name="distance"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="km"/> <xsd:enumeration value="KM"/> </xsd:restriction> </xsd:simpleType> <xsd:complexType name="speedType"> <xsd:simpleContent> <xsd:extension base="xsd:double"> <xsd:attribute name="units" type="speed" use="optional"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <xsd:simpleType name="speed"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="km/s"/> <xsd:enumeration value="KM/S"/> </xsd:restriction> </xsd:simpleType> <xsd:complexType name="massType"> <xsd:simpleContent>



<xsd:extension base="nonNegativeDouble"> <xsd:attribute name="units" type="massUnits" use="optional"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <xsd:complexType name="deltamassType"> <xsd:simpleContent> <xsd:extension base="negativeDouble"> <xsd:attribute name="units" type="massUnits" use="optional"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <xsd:simpleType name="massUnits"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="kg"/> <xsd:enumeration value="KG"/> </xsd:restriction> </xsd:simpleType> <xsd:complexType name="areaType"> <xsd:simpleContent> <xsd:extension base="nonNegativeDouble"> <xsd:attribute name="units" type="areaUnits" use="optional"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <xsd:simpleType name="areaUnits"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="m**2"/> <xsd:enumeration value="M**2"/> </xsd:restriction> </xsd:simpleType> <xsd:complexType name="durationType"> <xsd:simpleContent> <xsd:extension base="nonNegativeDouble"> <xsd:attribute name="units" type="timeUnits" use="optional"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <xsd:simpleType name="timeUnits"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="s"/> <xsd:enumeration value="S"/> </xsd:restriction> </xsd:simpleType> <xsd:complexType name="angleType"> <xsd:simpleContent> <xsd:extension base="angleRange">



<xsd:attribute name="units" type="angleUnits" use="optional"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <xsd:simpleType name="angleRange"> <xsd:restriction base="xsd:double"> <xsd:minInclusive value="-180.0"/> <xsd:maxExclusive value="360.0"/> </xsd:restriction> </xsd:simpleType> <xsd:simpleType name="angleUnits"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="deg"/> <xsd:enumeration value="DEG"/> </xsd:restriction> </xsd:simpleType> <xsd:complexType name="angleRateType"> <xsd:simpleContent> <xsd:extension base="xsd:double"> <xsd:attribute name="units" type="angleRateUnits" use="optional"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <xsd:simpleType name="angleRateUnits"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="deg/s"/> <xsd:enumeration value="DEG/S"/> </xsd:restriction> </xsd:simpleType> <xsd:simpleType name="versionType"> <xsd:restriction base="xsd:string"> <xsd:pattern value="\p{Nd}(\p{Nd})?\.\p{Nd}(\p{Nd})?(\.\p{Nd}(\p{Nd})?)?" /> </xsd:restriction> </xsd:simpleType> <xsd:simpleType name="negativeDouble"> <xsd:restriction base="xsd:double"> <xsd:maxExclusive value="0.0"/> </xsd:restriction> </xsd:simpleType> <xsd:simpleType name="nonNegativeDouble"> <xsd:restriction base="xsd:double"> <xsd:minInclusive value="0.0"/> </xsd:restriction> </xsd:simpleType>



<xsd:simpleType name="positiveDouble"> <xsd:restriction base="xsd:double"> <xsd:minExclusive value="0.0"/> </xsd:restriction> </xsd:simpleType> <xsd:simpleType name="percentType"> <xsd:restriction base="xsd:double"> <xsd:minInclusive value="0.0"/> <xsd:maxInclusive value="100.0"/> </xsd:restriction> </xsd:simpleType> <xsd:simpleType name="quaternionComponentType"> <xsd:restriction base="xsd:double"> <xsd:minInclusive value="-1.0"/> <xsd:maxInclusive value="1.0"/> </xsd:restriction> </xsd:simpleType> <xsd:complexType name="quaternionRateType"> <xsd:simpleContent> <xsd:extension base="xsd:double"> <xsd:attribute name="units" type="quaternionRateUnits" use="optional"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <xsd:simpleType name="quaternionRateUnits"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="s*-1"/> <xsd:enumeration value="S*-1"/> <xsd:enumeration value="1/s"/> <xsd:enumeration value="1/S"/> </xsd:restriction> </xsd:simpleType> <xsd:simpleType name="rotseqType"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="121"/> <xsd:enumeration value="123"/> <xsd:enumeration value="131"/> <xsd:enumeration value="132"/> <xsd:enumeration value="212"/> <xsd:enumeration value="213"/> <xsd:enumeration value="231"/> <xsd:enumeration value="232"/> <xsd:enumeration value="312"/> <xsd:enumeration value="313"/> <xsd:enumeration value="321"/> <xsd:enumeration value="323"/> </xsd:restriction> </xsd:simpleType> </xsd:schema>


CCSDS 505.0-W-1.78 Page J-34 September 2005

ANNEX J NDM/XML EXAMPLES

An assortment of instantiations of the NDM/XML Schema may be found on the CCSDS web page at:

http://public.ccsds.org/sites/cwe/moims-nav/Public/Schemas/TestFiles/ndmxml-1.8.xml

These test XML instantiations in conjunction with the NDM/XML schema in Annex E will validate successfully when validation-checked using the XML validator available at http://tools.decisionsoft.com/schemaValidate.html . At the time of this publication the suggested URL is active. Users may need to find a current validation tool in the future.


CCSDS 505.0-W-1.78 Page K-35 September 2005

ANNEX K AUTHOR’S TO-DO

1. Update schema to specify units (note: complete for ODM, partially complete for ADM, TDM)

2. Put more realistic data into the examples

3. Missing requirements… should have some lower level requirements on the specification.

4. Need to add graphical representation of the schema

6. Check to see if W3C has a recommended validator.

Following are responses to Fran’s specific suggestions/comments regarding NDM/XML 1.4. Some have been implemented in NDM/XML 1.5, and some must wait for 1.6 or 1.7. Numbers are relative to his document 2005/04/04, “GMV Support to XML Implementation of CCSDS/NDM”.

1. Review the GMV presentation from Spring 2004 for your ideas about strengthening the advantages of using XML and XML schema. In progress… target for version 1.8,

6. Evaluate how "strong" the data structure needs to be. Consider whether strengthening the data structure adds unnecessary complication. Talk with Fran about what he has in mind. Open discussion item before the Working Group. Keyword triggering?

12. Complete addition of units for all elements. Ongoing (some new in 1.6). See first item in this annex. 19. Determine whether or not schema is listed in the document. For now, it will be, but it will be moved to an annex (note: for comparison, the XTCE Red Book (XML Telemetric And Command Exchange) has the full schema in an Annex, with a graphical representation in the body of the text).

END of FRAN’s COMMENTS

BEGIN OF ADDITIONAL COMMENTS

19a. Consider visual representation of the schema in the document.



9. Suggestion to extract range information from the XML schema (use XML spy) Graphical view, Schema design, generate schema documentation.

13. Tips for constructing an NDM/XML that are not documented in the ADM/ODM/TDM (e.g., use of non-keywords). 14. Add Annex containing all NDM/XML tags that are *not* keywords in the ADM, ODM, TDM (?)



ANNEX C QUESTIONS

1.Do we want to have a pattern specified for the “OBJECT_ID”? A “valid format” is specified in the metadata section of the standards documents. This will limit flexibility to some extent, if included.

2.Do we want to maintain 2 different schemas? One for “strong type checking” and the other for “weak type checking” (e.g., such as might be used for testing).



ANNEX D AUTHOR’S TO-DO

1.Update schema to specify units (note: complete for ODM, partially complete for ADM, TDM)

2.modularize the schema for easier perusal

3.Put more realistic data into the examples

4.Missing requirements… should have some lower level requirements on the specification.

Following are responses to Fran’s specific suggestions/comments regarding NDM/XML 1.4. Some have been implemented in NDM/XML 1.5, and some must wait for 1.6 or 1.7. Numbers are relative to his document 2005/04/04, “GMV Support to XML Implementation of CCSDS/NDM”.

1. Review the GMV presentation from Spring 2004 for your ideas about strengthening the advantages of using XML and XML schema. In progress… target for version 1.8,

2. Add a justification for using XML schema as opposed to some other approach. Populate based on the material in GMV Spring 2004 presentation. Will be in Version 1.8

6. Evaluate how "strong" the data structure needs to be. Consider whether strengthening the data structure adds unnecessary complication. Talk with Fran about what he has in mind. Open discussion item before the Working Group. Keyword triggering?

10. Reconsider structuring the OBJECT_ID string. Depends on group decision regarding “strength” of data structure.

11. Reconsider an enumerated list for time systems and reference frames. Depends on group decision regarding “strength” of data structure, though the group has been leaning towards *not* checking time systems and reference frames.

12. Complete addition of units for all elements. Ongoing (some new in 1.6). See first item in this annex. 19. Determine whether or not schema is listed in the document. For now, it will be, but it will be moved to an annex (note: for comparison, the XTCE Red Book (XML Telemetric And Command Exchange) has the full schema in an Annex, with a graphical representation in the body of the text).



END of FRAN’s COMMENTS

BEGIN OF ADDITIONAL COMMENTS

19a. Consider visual representation of the schema in the document.

3.Could have “strict” and “loose” schemas (things like OBJECT_ID, TIME_SYSTEM, REFERENCE_FRAME, etc. could have strict checking with enumeration and/or structure in the strict schema, and just “xsd:string” in the loose structure).

4.<INTERPOLATION> add this structure

<INTERPOLATION_METHOD/>

<INTERPOLATION_DEGREE/>

8. Date checking: don’t check just the pattern… also check that month 1<=x<=12, days 1<=31

9. Suggestion to extract range information from the XML schema (use XML spy) Graphical view, Schema design, generate schema documentation.

11. modularize it! (target for 1.8)

12. Note for ADM: APM data structure currently has EPOCH, Q_FRAME, and then the quaternion. In the XML schema, the EPOCH has been defined as part of the “statevector” structure: (the statevector structure has EPOCH, quaternion, and quaternion_rates elements). It may be a good idea to move Q_FRAME before EPOCH in the ASCII version, or after the quaternion. In the OPM, the reference frame information is in the metadata, but it was moved out of the APM metadata and into the data section.



ANNEX E NDM/XML SCHEMA

This annex lists the NDM/XML Schema. This XML Schema in conjunction with the NDM/XML instance in Annex F will validate successfully when validation-checked at http://tools.decisionsoft.com/schemaValidate.html . At the time of this publication the suggested URL is active. Users may need to find a current validation tool in the future.

<?xml version="1.0"?>

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"

xmlns:odm="ndmxml-1.7-odm.xsd">

















































<xsd:element name="ndm" type="ndmType"/>

<xsd:complexType name="ndmType">













<xsd:sequence>

<xsd:element name="ndmVersion" type="ndmVersionType"/>

<xsd:element name="COMMENT" type="xsd:string"

minOccurs="0" maxOccurs="unbounded"/>

<xsd:choice minOccurs="0" maxOccurs="unbounded">

<xsd:element name="aem" type="aemType"/>

<xsd:element name="apm" type="apmType"/>

<xsd:element name="oem" type="oemType"/>

<xsd:element name="opm" type="opmType"/>

<xsd:element name="tdm" type="tdmType"/>

</xsd:choice>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="ndmVersionType">

<xsd:attribute name="version" type="ndmVersionString" use="required"

fixed="0.1.7"/>

</xsd:complexType>

<xsd:simpleType name="ndmVersionString">

<xsd:restriction base="xsd:string">



</xsd:restriction>

</xsd:simpleType>































<xsd:complexType name="aemType">

<xsd:sequence>

<xsd:element name="header" type="ndmHeader"/>



<xsd:element name="body" type="aemBody"/>



</xsd:sequence>

</xsd:complexType>



<xsd:complexType name="apmType">

<xsd:sequence>




<xsd:element name="body" type="apmBody"/>



</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="oemType">

<xsd:sequence>




<xsd:element name="body" type="oemBody"/>



</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="opmType">

<xsd:sequence>




<xsd:element name="body" type="opmBody"/>



</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="tdmType">

<xsd:sequence>




<xsd:element name="body" type="tdmBody"/>



</xsd:sequence>

</xsd:complexType>













<xsd:complexType name="ndmHeader">

<xsd:sequence>

<xsd:choice>

<xsd:element name="CCSDS_AEM_VERS" type="versionType"

fixed="0.2.4"/>

<xsd:element name="CCSDS_APM_VERS" type="versionType"

fixed="0.2.4"/>

<xsd:element name="CCSDS_OEM_VERS" type="versionType"

fixed="1.0"/>

<xsd:element name="CCSDS_OPM_VERS" type="versionType"

fixed="1.0"/>

<xsd:element name="CCSDS_TDM_VERS" type="versionType"

fixed="0.1.17"/>

</xsd:choice>



<xsd:element name="CREATION_DATE" type="epochType"/>



<xsd:element name="ORIGINATOR" type="xsd:string"/>



</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="apmBody">

<xsd:sequence>

<xsd:element name="segment" type="apmSegment"

minOccurs="1" maxOccurs="1"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="aemBody">

<xsd:sequence>

<xsd:element name="segment" type="aemSegment"


</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="opmBody">

<xsd:sequence>

<xsd:element name="segment" type="opmSegment"

minOccurs="1" maxOccurs="1"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="oemBody">

<xsd:sequence>

<xsd:element name="segment" type="oemSegment"


</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="tdmBody">

<xsd:sequence>

<xsd:element name="segment" type="tdmSegment"


</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="apmSegment">

<xsd:sequence>

<xsd:element name="metadata" type="apmMetadata"/>

<xsd:element name="data" type="apmData"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="aemSegment">

<xsd:sequence>

<xsd:element name="metadata" type="aemMetadata"/>

<xsd:element name="data" type="aemData"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="opmSegment">

<xsd:sequence>

<xsd:element name="metadata" type="opmMetadata"/>

<xsd:element name="data" type="opmData"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="oemSegment">

<xsd:sequence>

<xsd:element name="metadata" type="oemMetadata"/>

<xsd:element name="data" type="oemData"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="tdmSegment">

<xsd:sequence>

<xsd:element name="metadata" type="tdmMetadata"/>

<xsd:element name="data" type="tdmData"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="apmMetadata">

<xsd:sequence>



<xsd:element name="OBJECT_NAME" type="xsd:string"/>

<xsd:element name="OBJECT_ID" type="xsd:string"/>

<xsd:element name="CENTER_NAME" type="xsd:string"/>

<xsd:element name="TIME_SYSTEM" type="xsd:string"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="aemMetadata">

<xsd:sequence>






<xsd:element name="REF_FRAME" type="xsd:string"/>


<xsd:element name="START_TIME" type="epochType"/>

<xsd:element name="USEABLE_START_TIME" type="epochType" minOccurs="0"/>

<xsd:element name="USEABLE_STOP_TIME" type="epochType" minOccurs="0"/>

<xsd:element name="STOP_TIME" type="epochType"/>

<xsd:element name="INTERPOLATION_METHOD" type="xsd:string"

minOccurs="0"/>

<xsd:element name="INTERPOLATION_DEGREE" type="xsd:positiveInteger"

minOccurs="0"/>

<xsd:element name="ATTITUDE_TYPE" type="attitudeTypeType"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="opmMetadata">

<xsd:sequence>






</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="oemMetadata">

<xsd:sequence>








<xsd:element name="START_TIME" type="epochType"/>

<xsd:element name="USEABLE_START_TIME" type="epochType" minOccurs="0"/>

<xsd:element name="USEABLE_STOP_TIME" type="epochType" minOccurs="0"/>

<xsd:element name="STOP_TIME" type="epochType"/>

<xsd:element name="INTERPOLATION" type="xsd:string"

minOccurs="0"/>

<xsd:element name="INTERPOLATION_DEGREE" type="xsd:positiveInteger"

minOccurs="0"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="tdmMetadata">

<xsd:sequence>




<xsd:element name="PARTICIPANT_1" type="xsd:string"/>

<xsd:element name="PARTICIPANT_2" type="xsd:string"

minOccurs="0"/>


minOccurs="0"/>


minOccurs="0"/>


minOccurs="0"/>

<xsd:element name="MODE" type="modeType" />

<xsd:element name="PATH" type="pathType" default="N/A"

minOccurs="0" />

<xsd:element name="DIFF_MODE" type="diffmodeType" default="N/A"



minOccurs="0" />

<xsd:element name="TIMETAG_REF" type="timetagType" default="RECEIVE"

minOccurs="0" />

<xsd:element name="COMPRESSION_TIME" type="nonNegativeDouble"

default="0.0" minOccurs="0"/>

<xsd:element name="INTEGRATION_REF" type="integrationrefType"

default="MIDDLE" minOccurs="0" />

<xsd:element name="FREQ_OFFSET" type="xsd:double" default="0.0"

minOccurs="0" />

<xsd:element name="RANGE_MODE" type="rangemodeType" default="COHERENT"

minOccurs="0" />

<xsd:element name="RANGE_MODULUS" type="nonNegativeDouble"

default="0.0" minOccurs="0"/>

<xsd:element name="RANGE_UNITS" type="rangeunitsType" default="S"

minOccurs="0"/>

<xsd:element name="ANGLE_TYPE" type="angleTypeType" default="N/A"

minOccurs="0"/>

<xsd:element name="REFERENCE_FRAME" type="xsd:string" default="N/A"

minOccurs="0" />

<xsd:element name="TRANSMIT_DELAY_1" type="nonNegativeDouble"

default="0.0" minOccurs="0" />









<xsd:element name="RECEIVE_DELAY_1" type="nonNegativeDouble"










<xsd:element name="START_TIME" type="epochType" minOccurs="0" />

<xsd:element name="STOP_TIME" type="epochType" minOccurs="0" />

<xsd:element name="DATA_QUALITY" type="dataQualityType"

default="VALIDATED" minOccurs="0" />

<xsd:element name="CORRECTION_RNGCAL" type="xsd:double" minOccurs="0" />

<xsd:element name="CORRECTION_ANGLE_1" type="xsd:double" minOccurs="0"

/>

<xsd:element name="CORRECTION_ANGLE_2" type="xsd:double" minOccurs="0"

/>

<xsd:element name="CORRECTION_DOPPLER" type="xsd:double" minOccurs="0"

/>

<xsd:element name="CORRECTION_TROPO" type="xsd:double" minOccurs="0" />

<xsd:element name="CORRECTION_CP" type="xsd:double" minOccurs="0" />

</xsd:sequence>

</xsd:complexType>









<xsd:complexType name="apmData">

<xsd:sequence>



<xsd:element name="Q_FRAME" type="xsd:string"/>

<xsd:element name="stateVector" type="attStateVectorType"/>

<xsd:element name="eulerElementsThree" type="eulerElementsThreeType"

minOccurs="0"/>

<xsd:element name="eulerElementsSpin" type="eulerElementsSpinType"

minOccurs="0"/>

<xsd:element name="spacecraftParameters"

type="attSpacecraftParametersType" minOccurs="0"/>

<xsd:element name="maneuverParameters"

type="attManeuverParametersType" minOccurs="0"

maxOccurs="unbounded"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="aemData">

<xsd:sequence>



<xsd:element name="attitudeVector" type="attitudeVectorType"


</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="opmData">

<xsd:sequence>

<xsd:element name="stateVector" type="stateVectorType"/>

<xsd:element name="keplerianElements" type="keplerianElementsType"

minOccurs="0"/>

<xsd:element name="spacecraftParameters"

type="spacecraftParametersType"/>

<xsd:element name="maneuverParameters" type="maneuverParametersType"


</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="oemData">

<xsd:sequence>



<xsd:element name="stateVector" type="stateVectorType"


</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="tdmData">

<xsd:sequence>



<xsd:element name="observation"

type="trackingDataObservationType"


</xsd:sequence>

</xsd:complexType>







<xsd:complexType name="attStateVectorType">

<xsd:sequence>



<xsd:element name="EPOCH" type="epochType"/>

<xsd:element name="Q1" type="quaternionComponentType"/>



<xsd:element name="QC" type="quaternionComponentType"/>

<xsd:element name="Q1_DOT" type="xsd:double" minOccurs="0"/>

<xsd:element name="QC_DOT" type="xsd:double" minOccurs="0"/>

</xsd:sequence>

</xsd:complexType>













<xsd:complexType name="eulerElementsThreeType">

<xsd:sequence>



<xsd:element name="EULER_FRAME" type="xsd:string"/>

<xsd:element name="EULER_ROT_SEQ" type="rotseqType"/>

<xsd:element name="ROLL" type="angleType"/>

<xsd:element name="PITCH" type="angleType"/>

<xsd:element name="YAW" type="angleType"/>

<xsd:element name="ROLL_RATE" type="angleRateType"/>

<xsd:element name="PITCH_RATE" type="angleRateType"/>

<xsd:element name="YAW_RATE" type="angleRateType"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="eulerElementsSpinType">

<xsd:sequence>



<xsd:element name="SPIN_FRAME" type="xsd:string"/>

<xsd:element name="SPIN_ALPHA" type="angleType"/>

<xsd:element name="SPIN_DELTA" type="angleType"/>

<xsd:element name="SPIN_ANGLE" type="angleType"/>

<xsd:element name="SPIN_ANGLE_VEL" type="angleRateType"/>

<xsd:element name="NUTATION" type="angleType"/>

<xsd:element name="NUTATION_PER" type="positiveDouble"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="attSpacecraftParametersType">

<xsd:sequence>

<xsd:element name="IX" type="momentType"/>

<xsd:element name="IY" type="momentType"/>

<xsd:element name="IZ" type="momentType"/>

<xsd:element name="IXY" type="productMomentType"/>

<xsd:element name="IXZ" type="productMomentType"/>

<xsd:element name="IYZ" type="productMomentType"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="attManeuverParametersType">

<xsd:sequence>



<xsd:element name="MAN_EPOCH_START" type="epochType"/>

<xsd:element name="MAN_DURATION" type="nonNegativeDouble"/>

<xsd:element name="MAN_REF_FRAME" type="xsd:string"/>

<xsd:element name="MAN_TOR_1" type="torqueType"/>



</xsd:sequence>

</xsd:complexType>







<xsd:complexType name="attitudeVectorType">

<xsd:choice>

<xsd:element name="quaternion" type="quaternionType"/>

<xsd:element name="quaternionderivative"

type="quaternionDerivativeType"/>

<xsd:element name="quaternioneulerrate" type="quaternionEulerRateType"/>

<xsd:element name="eulerangle" type="eulerAngleType"/>

<xsd:element name="euleranglerate" type="eulerAngleRateType"/>

<xsd:element name="spin" type="spinType"/>

<xsd:element name="spinnutation" type="spinNutationType"/>

</xsd:choice>

</xsd:complexType>

<xsd:complexType name="quaternionType">



<xsd:sequence>







</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="quaternionDerivativeType">


<xsd:sequence>






<xsd:element name="Q1_DOT" type="quaternionRateType"/>



<xsd:element name="QC_DOT" type="quaternionRateType"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="quaternionEulerRateType">


<xsd:sequence>









</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="eulerAngleType">


<xsd:sequence>





</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="eulerAngleRateType">


<xsd:sequence>








</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="spinType">


<xsd:sequence>





<xsd:element name="SPIN_ANGLE_VEL" type="xsd:double"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="spinNutationType">


<xsd:sequence>





<xsd:element name="SPIN_ANGLE_VEL" type="xsd:double"/>

<xsd:element name="NUTATION" type="angleType"/>

<xsd:element name="NUTATION_PER" type="positiveDouble"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="stateVectorType">

<xsd:sequence>




<xsd:element name="X" type="distanceType"/>

<xsd:element name="Y" type="distanceType"/>

<xsd:element name="Z" type="distanceType"/>

<xsd:element name="X_DOT" type="speedType"/>

<xsd:element name="Y_DOT" type="speedType"/>

<xsd:element name="Z_DOT" type="speedType"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="keplerianElementsType">

<xsd:sequence>



<xsd:element name="SEMI_MAJOR_AXIS" type="distanceType"/>

<xsd:element name="ECCENTRICITY" type="nonNegativeDouble"/>

<xsd:element name="INCLINATION" type="inclinationType"/>

<xsd:element name="RA_OF_ASC_NODE" type="angleType"/>

<xsd:element name="ARG_OF_PERICENTER" type="angleType"/>

<xsd:choice>

<xsd:element name="TRUE_ANOMALY" type="angleType"/>

<xsd:element name="MEAN_ANOMALY" type="angleType"/>

</xsd:choice>

<xsd:element name="GM" type="gmType"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="spacecraftParametersType">

<xsd:sequence>



<xsd:element name="MASS" type="massType"/>

<xsd:element name="SOLAR_RAD_AREA" type="areaType"/>

<xsd:element name="SOLAR_RAD_COEFF" type="nonNegativeDouble"/>

<xsd:element name="DRAG_AREA" type="areaType"/>

<xsd:element name="DRAG_COEFF" type="nonNegativeDouble"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="maneuverParametersType">

<xsd:sequence>



<xsd:element name="MAN_EPOCH_IGNITION" type="epochType"/>

<xsd:element name="MAN_DURATION" type="durationType"/>

<xsd:element name="MAN_DELTA_MASS" type="deltamassType"/>

<xsd:element name="MAN_REF_FRAME" type="xsd:string"/>

<xsd:element name="MAN_DV_1" type="speedType"/>



</xsd:sequence>

</xsd:complexType>

























<xsd:complexType name="trackingDataObservationType">

<xsd:sequence>


<xsd:choice>

<xsd:element name="AGC" type="xsd:double" />

<xsd:element name="ANGLE_1" type="angleType"/>

<xsd:element name="ANGLE_2" type="angleType"/>

<xsd:element name="AZIMUTH_RATE" type="xsd:double"/>

<xsd:element name="CARRIER_SNR" type="xsd:double"/>

<xsd:element name="CLOCK_BIAS" type="xsd:double" default="0.0"/>

<xsd:element name="CLOCK_DRIFT" type="xsd:double" default="0.0"/>

<xsd:element name="CPDELAY" type="xsd:double" />

<xsd:element name="PRESSURE" type="xsd:double"/>

<xsd:element name="RANGE_OBS" type="xsd:double"/>

<xsd:element name="RANGE_RATE" type="xsd:double"/>

<xsd:element name="RANGE_SNR" type="xsd:double"/>

<xsd:element name="RECEIVE_FREQ" type="xsd:double"/>

<xsd:element name="RECEIVE_FREQ_1" type="xsd:double"/>





<xsd:element name="RHUMIDITY" type="percentType"/>

<xsd:element name="TEMPERATURE" type="nonNegativeDouble"/>

<xsd:element name="TRANSMIT_FREQ_1" type="positiveDouble"/>





<xsd:element name="TRANSMIT_FREQ_RATE_1" type="xsd:double"/>





<xsd:element name="TROPO_DRY" type="nonNegativeDouble"/>

<xsd:element name="TROPO_WET" type="nonNegativeDouble"/>

</xsd:choice>

</xsd:sequence>

</xsd:complexType>







<xsd:complexType name="distanceType">

<xsd:simpleContent>

<xsd:extension base="xsd:double">

<xsd:attribute name="units" type="distance" use="optional"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<xsd:simpleType name="distance">


<xsd:enumeration value="km"/>

<xsd:enumeration value="KM"/>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="speedType">



<xsd:simpleContent>


<xsd:attribute name="units" type="speed" use="optional"/>

</xsd:extension>


</xsd:complexType>

<xsd:simpleType name="speed">


<xsd:enumeration value="km/s"/>

<xsd:enumeration value="KM/S"/>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="inclinationType">

<xsd:simpleContent>

<xsd:extension base="inclination">

<xsd:attribute name="units" type="angleUnits" use="optional"/>

</xsd:extension>


</xsd:complexType>

<xsd:simpleType name="inclination">

<xsd:restriction base="angleRange">

<xsd:minInclusive value="0.0"/>

<xsd:maxInclusive value="180.0"/>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="gmType">

<xsd:simpleContent>

<xsd:extension base="positiveDouble">

<xsd:attribute name="units" type="gmUnits" use="optional"/>

</xsd:extension>


</xsd:complexType>

<xsd:simpleType name="gmUnits">


<xsd:enumeration value="km**3/s**2"/>

<xsd:enumeration value="KM**3/S**2"/>



</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="massType">

<xsd:simpleContent>

<xsd:extension base="nonNegativeDouble">

<xsd:attribute name="units" type="massUnits" use="optional"/>

</xsd:extension>


</xsd:complexType>

<xsd:complexType name="deltamassType">

<xsd:simpleContent>

<xsd:extension base="negativeDouble">

<xsd:attribute name="units" type="massUnits" use="optional"/>

</xsd:extension>


</xsd:complexType>

<xsd:simpleType name="massUnits">


<xsd:enumeration value="kg"/>

<xsd:enumeration value="KG"/>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="areaType">

<xsd:simpleContent>


<xsd:attribute name="units" type="areaUnits" use="optional"/>

</xsd:extension>


</xsd:complexType>

<xsd:simpleType name="areaUnits">


<xsd:enumeration value="m**2"/>

<xsd:enumeration value="M**2"/>

</xsd:restriction>

</xsd:simpleType>



<xsd:complexType name="durationType">

<xsd:simpleContent>


<xsd:attribute name="units" type="timeUnits" use="optional"/>

</xsd:extension>


</xsd:complexType>

<xsd:simpleType name="timeUnits">


<xsd:enumeration value="s"/>

<xsd:enumeration value="S"/>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="angleType">

<xsd:simpleContent>

<xsd:extension base="angleRange">

<xsd:attribute name="units" type="angleUnits" use="optional"/>

</xsd:extension>


</xsd:complexType>

<xsd:simpleType name="angleRange">

<xsd:restriction base="xsd:double">

<xsd:minInclusive value="-180.0"/>

<xsd:maxExclusive value="360.0"/>

</xsd:restriction>

</xsd:simpleType>

<xsd:simpleType name="angleUnits">


<xsd:enumeration value="deg"/>

<xsd:enumeration value="DEG"/>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="angleRateType">

<xsd:simpleContent>




<xsd:attribute name="units" type="angleRateUnits" use="optional"/>

</xsd:extension>


</xsd:complexType>

<xsd:simpleType name="angleRateUnits">


<xsd:enumeration value="deg/s"/>

<xsd:enumeration value="DEG/S"/>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="quaternionRateType">

<xsd:simpleContent>


<xsd:attribute name="units" type="quaternionRateUnits"

use="optional"/>

</xsd:extension>


</xsd:complexType>

<xsd:simpleType name="quaternionRateUnits">


<xsd:enumeration value="s*-1"/>

<xsd:enumeration value="S*-1"/>

<xsd:enumeration value="1/s"/>

<xsd:enumeration value="1/S"/>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="momentType">

<xsd:simpleContent>


<xsd:attribute name="units" type="momentUnits" use="optional"/>

</xsd:extension>


</xsd:complexType>

<xsd:complexType name="productMomentType">

<xsd:simpleContent>


<xsd:attribute name="units" type="momentUnits" use="optional"/>

</xsd:extension>


</xsd:complexType>

<xsd:simpleType name="momentUnits">


<xsd:enumeration value="kg*m**2"/>

<xsd:enumeration value="KG*M**2"/>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="torqueType">

<xsd:simpleContent>


<xsd:attribute name="units" type="torqueUnits" use="optional"/>

</xsd:extension>


</xsd:complexType>

<xsd:simpleType name="torqueUnits">


<xsd:enumeration value="n*m"/>

<xsd:enumeration value="N*m"/>

<xsd:enumeration value="N*M"/>

</xsd:restriction>

</xsd:simpleType>



















<xsd:simpleType name="epochType">



<xsd:pattern value="-?\d{4}\d*-((\d{2}-

\d{2})|\d{3})T\d{2}:\d{2}:\d{2}(\.\d*)?(Z|[+|-]\d{2}:\d{2})?|[+|-

]?\d*(\.\d*)?"/>

</xsd:restriction>

</xsd:simpleType>

<xsd:simpleType name="versionType">


<xsd:pattern

value="\p{Nd}(\p{Nd})?\.\p{Nd}(\p{Nd})?(\.\p{Nd}(\p{Nd})?)?" />

</xsd:restriction>

</xsd:simpleType>

<xsd:simpleType name="negativeDouble">


<xsd:maxExclusive value="0.0"/>

</xsd:restriction>

</xsd:simpleType>

<xsd:simpleType name="nonNegativeDouble">



</xsd:restriction>

</xsd:simpleType>

<xsd:simpleType name="positiveDouble">


<xsd:minExclusive value="0.0"/>

</xsd:restriction>

</xsd:simpleType>

<xsd:simpleType name="percentType">




</xsd:restriction>

</xsd:simpleType>

<xsd:simpleType name="timeRef">


<xsd:enumeration value="start"/>

<xsd:enumeration value="Start"/>

<xsd:enumeration value="START"/>

<xsd:enumeration value="end" />

<xsd:enumeration value="End" />

<xsd:enumeration value="END" />

</xsd:restriction>

</xsd:simpleType>

<xsd:simpleType name="dataQualityType">


<xsd:enumeration value="raw"/>

<xsd:enumeration value="RAW"/>

<xsd:enumeration value="validated" />

<xsd:enumeration value="VALIDATED" />

<xsd:enumeration value="degraded" />

<xsd:enumeration value="DEGRADED" />

</xsd:restriction>

</xsd:simpleType>

<xsd:simpleType name="modeType">


<xsd:enumeration value="SEQUENCE"/>

<xsd:enumeration value="sequence"/>

<xsd:enumeration value="SINGLE-DIFF" />

<xsd:enumeration value="single-diff" />

<xsd:enumeration value="DOUBLE-DIFF" />

<xsd:enumeration value="double-diff" />

<xsd:enumeration value="N/A"/>

<xsd:enumeration value="n/a"/>

</xsd:restriction>

</xsd:simpleType>

<xsd:simpleType name="pathType">








</xsd:restriction>

</xsd:simpleType>

<xsd:simpleType name="timetagType">




<xsd:enumeration value="TRANSMIT"/>

<xsd:enumeration value="transmit"/>

<xsd:enumeration value="RECEIVE"/>

<xsd:enumeration value="receive"/>

</xsd:restriction>

</xsd:simpleType>

<xsd:simpleType name="quaternionComponentType">


<xsd:minInclusive value="-1.0"/>


</xsd:restriction>

</xsd:simpleType>

<xsd:simpleType name="rotseqType">


<xsd:enumeration value="121"/>












</xsd:restriction>

</xsd:simpleType>

<xsd:simpleType name="attitudeTypeType">


<xsd:enumeration value="quaternion"/>

<xsd:enumeration value="QUATERNION"/>

<xsd:enumeration value="quaternion/derivative"/>

<xsd:enumeration value="QUATERNION/DERIVATIVE"/>

<xsd:enumeration value="quaternion/rate"/>

<xsd:enumeration value="QUATERNION/RATE"/>

<xsd:enumeration value="euler_angle"/>

<xsd:enumeration value="EULER_ANGLE"/>

<xsd:enumeration value="euler_angle/rate"/>



<xsd:enumeration value="EULER_ANGLE/RATE"/>

<xsd:enumeration value="spin"/>

<xsd:enumeration value="SPIN"/>

<xsd:enumeration value="spin/nutation"/>

<xsd:enumeration value="SPIN/NUTATION"/>

</xsd:restriction>

</xsd:simpleType>

<xsd:simpleType name="diffmodeType">


<xsd:enumeration value="delay"/>

<xsd:enumeration value="DELAY"/>

<xsd:enumeration value="range"/>

<xsd:enumeration value="RANGE"/>

<xsd:enumeration value="N/A" />

<xsd:enumeration value="n/a" />

</xsd:restriction>

</xsd:simpleType>

<xsd:simpleType name="integrationrefType">


<xsd:enumeration value="START"/>

<xsd:enumeration value="start"/>

<xsd:enumeration value="MIDDLE"/>

<xsd:enumeration value="middle"/>

<xsd:enumeration value="END"/>

<xsd:enumeration value="end"/>

</xsd:restriction>

</xsd:simpleType>

<xsd:simpleType name="rangeunitsType">


<xsd:enumeration value="ru"/>

<xsd:enumeration value="RU"/>

<xsd:enumeration value="s"/>

<xsd:enumeration value="S"/>

<xsd:enumeration value="km"/>

<xsd:enumeration value="KM"/>

</xsd:restriction>

</xsd:simpleType>

<xsd:simpleType name="rangemodeType">




<xsd:enumeration value="coherent"/>

<xsd:enumeration value="COHERENT"/>

<xsd:enumeration value="constant"/>

<xsd:enumeration value="CONSTANT"/>

</xsd:restriction>

</xsd:simpleType>

<xsd:simpleType name="angleTypeType">


<xsd:enumeration value="AZEL"/>

<xsd:enumeration value="azel"/>

<xsd:enumeration value="RADEC"/>

<xsd:enumeration value="radec"/>

<xsd:enumeration value="XEYN"/>

<xsd:enumeration value="xeyn"/>

<xsd:enumeration value="XSYE"/>

<xsd:enumeration value="xsye"/>

<xsd:enumeration value="N/A"/>

<xsd:enumeration value="n/a"/>

</xsd:restriction>

</xsd:simpleType>

</xsd:schema>



ANNEX F NDM/XML EXAMPLE

This annex lists an instantiation of the NDM/XML Schema. This XML instantiation in conjunction with the NDM/XML schema in Annex E will validate successfully when validation-checked at http://tools.decisionsoft.com/schemaValidate.html . At the time of this publication the suggested URL is active. Users may need to find a current validation tool in the future.

<?xml version="1.0"?> <ndm xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:odm="ndmxml-1.7-odm.xsd" xsi:noNamespaceSchemaLocation="ndmxml-1.7.xsd"> <ndmVersion version="0.1.7"/> <COMMENT>This instantiation is compatible with NDM/XML 1.7</COMMENT> <COMMENT>It would be good to correlate the examples here with the </COMMENT> <COMMENT>examples in the ADM, ODM, TDM </COMMENT> <apm> <header> <CCSDS_APM_VERS>0.2.4</CCSDS_APM_VERS> <COMMENT>This is a test message</COMMENT> <CREATION_DATE>2004-281T17:26:06</CREATION_DATE> <COMMENT>Today is a good day for APM's</COMMENT> <ORIGINATOR>me</ORIGINATOR> <COMMENT>this is it!</COMMENT> </header> <body> <segment> <metadata> <COMMENT>Cassini spacecraft APM</COMMENT> <OBJECT_NAME>Cassini</OBJECT_NAME> <OBJECT_ID>1997-061A</OBJECT_ID> <CENTER_NAME>Saturn</CENTER_NAME> <TIME_SYSTEM>UTC</TIME_SYSTEM> </metadata> <data> <Q_FRAME>ICRF</Q_FRAME> <stateVector> <EPOCH>2004-100T00:00:00Z</EPOCH> <Q1>1</Q1> <Q2>1</Q2> <Q3>1</Q3> <QC>1</QC> <Q1_DOT>1</Q1_DOT>



<Q2_DOT>1</Q2_DOT> <Q3_DOT>1</Q3_DOT> <QC_DOT>1</QC_DOT> </stateVector> <eulerElementsThree> <EULER_FRAME>J2000</EULER_FRAME> <EULER_ROT_SEQ>123</EULER_ROT_SEQ> <ROLL units="deg">45</ROLL> <PITCH units="DEG">0</PITCH> <YAW units="deg">15</YAW> <ROLL_RATE units="deg/s">45</ROLL_RATE> <PITCH_RATE units="DEG/S">0</PITCH_RATE> <YAW_RATE units="deg/s">15</YAW_RATE> </eulerElementsThree> <eulerElementsSpin> <SPIN_FRAME>J2000</SPIN_FRAME> <SPIN_ALPHA units="DEG">100</SPIN_ALPHA> <SPIN_DELTA>45</SPIN_DELTA> <SPIN_ANGLE>45</SPIN_ANGLE> <SPIN_ANGLE_VEL units="deg/s">45</SPIN_ANGLE_VEL> <NUTATION>0</NUTATION> <NUTATION_PER>23</NUTATION_PER> </eulerElementsSpin> <spacecraftParameters> <IX units="kg*m**2">34</IX> <IY units="KG*M**2">34</IY> <IZ units="kg*m**2">34</IZ> <IXY units="KG*M**2">34</IXY> <IXZ units="kg*m**2">34</IXZ> <IYZ units="kg*m**2">34</IYZ> </spacecraftParameters> <maneuverParameters> <MAN_EPOCH_START>2004-125T00:00:00</MAN_EPOCH_START> <MAN_DURATION>0</MAN_DURATION> <MAN_REF_FRAME>GRC</MAN_REF_FRAME> <MAN_TOR_1 units="n*m">1</MAN_TOR_1> <MAN_TOR_2 units="N*M">1</MAN_TOR_2> <MAN_TOR_3>1</MAN_TOR_3> </maneuverParameters> </data> </segment> </body> </apm> <opm>



<header> <CCSDS_OPM_VERS>1.0</CCSDS_OPM_VERS> <CREATION_DATE>2004-281T17:26:06</CREATION_DATE> <ORIGINATOR>me</ORIGINATOR> <COMMENT>this is it!</COMMENT> </header> <body> <segment> <metadata> <OBJECT_NAME>Cassini</OBJECT_NAME> <OBJECT_ID>1997-061A</OBJECT_ID> <CENTER_NAME>Saturn</CENTER_NAME> <REF_FRAME>IAU-Saturn</REF_FRAME> <TIME_SYSTEM>UTC</TIME_SYSTEM> </metadata> <data> <COMMENT>final COMMENT, I think</COMMENT> <stateVector> <EPOCH>2004-100T00:00:00Z</EPOCH> <X>1</X> <Y>1</Y> <Z>1</Z> <X_DOT>1</X_DOT> <Y_DOT>1</Y_DOT> <Z_DOT>1</Z_DOT> </stateVector> <keplerianElements> <SEMI_MAJOR_AXIS units="km">1</SEMI_MAJOR_AXIS> <ECCENTRICITY>0</ECCENTRICITY> <INCLINATION units="deg">45</INCLINATION> <RA_OF_ASC_NODE units="deg">0</RA_OF_ASC_NODE> <ARG_OF_PERICENTER units="deg">15</ARG_OF_PERICENTER> <TRUE_ANOMALY units="deg">15</TRUE_ANOMALY> <GM units="km**3/s**2">398644</GM> </keplerianElements> <spacecraftParameters> <MASS units="kg">100</MASS> <SOLAR_RAD_AREA units="m**2">2</SOLAR_RAD_AREA> <SOLAR_RAD_COEFF>1</SOLAR_RAD_COEFF> <DRAG_AREA units="m**2">2</DRAG_AREA> <DRAG_COEFF>2.0</DRAG_COEFF> </spacecraftParameters> <maneuverParameters> <MAN_EPOCH_IGNITION>2004-125T00:00:00Z</MAN_EPOCH_IGNITION> <MAN_DURATION>0</MAN_DURATION>



<MAN_DELTA_MASS>-1</MAN_DELTA_MASS> <MAN_REF_FRAME>GRC</MAN_REF_FRAME> <MAN_DV_1 units="km/s">1</MAN_DV_1> <MAN_DV_2 units="km/s">1</MAN_DV_2> <MAN_DV_3 units="KM/S">1</MAN_DV_3> </maneuverParameters> </data> </segment> </body> </opm> <opm> <header> <CCSDS_OPM_VERS>1.0</CCSDS_OPM_VERS> <CREATION_DATE>2004-281T17:26:06</CREATION_DATE> <ORIGINATOR>me</ORIGINATOR> <COMMENT>this is it!</COMMENT> </header> <body> <segment> <metadata> <OBJECT_NAME>Cassini</OBJECT_NAME> <OBJECT_ID>1997-061A</OBJECT_ID> <CENTER_NAME>Saturn</CENTER_NAME> <REF_FRAME>IAU-Saturn</REF_FRAME> <TIME_SYSTEM>UTC</TIME_SYSTEM> </metadata> <data> <stateVector> <COMMENT>this is a comment</COMMENT> <EPOCH>2004-100T00:00:00</EPOCH> <X>1</X> <Y>1</Y> <Z>1</Z> <X_DOT>1</X_DOT> <Y_DOT>1</Y_DOT> <Z_DOT>1</Z_DOT> </stateVector> <spacecraftParameters> <COMMENT>This is a COMMENT</COMMENT> <MASS>100</MASS> <SOLAR_RAD_AREA>2</SOLAR_RAD_AREA> <SOLAR_RAD_COEFF>1</SOLAR_RAD_COEFF> <DRAG_AREA units="M**2">2</DRAG_AREA> <DRAG_COEFF>2.0</DRAG_COEFF>



</spacecraftParameters> <maneuverParameters> <COMMENT>This is a COMMENT</COMMENT> <MAN_EPOCH_IGNITION>2004-125T00:00:00</MAN_EPOCH_IGNITION> <MAN_DURATION units="S">0</MAN_DURATION> <MAN_DELTA_MASS units="KG">-1</MAN_DELTA_MASS> <MAN_REF_FRAME>GRC</MAN_REF_FRAME> <MAN_DV_1>1</MAN_DV_1> <MAN_DV_2>1</MAN_DV_2> <MAN_DV_3>1</MAN_DV_3> </maneuverParameters> </data> </segment> </body> </opm> <oem> <header> <CCSDS_OEM_VERS>1.0</CCSDS_OEM_VERS> <CREATION_DATE>2004-281T17:26:06</CREATION_DATE> <ORIGINATOR>me</ORIGINATOR> <COMMENT>this is it!</COMMENT> </header> <body> <segment> <metadata> <OBJECT_NAME>Cassini</OBJECT_NAME> <OBJECT_ID>1997-061A</OBJECT_ID> <CENTER_NAME>Saturn</CENTER_NAME> <REF_FRAME>IAU-Saturn</REF_FRAME> <TIME_SYSTEM>UTC</TIME_SYSTEM> <START_TIME>2004-100T00:00:00.000000</START_TIME> <STOP_TIME>2004-100T01:00:00.000000</STOP_TIME> <INTERPOLATION>Hermite</INTERPOLATION> <INTERPOLATION_DEGREE>1</INTERPOLATION_DEGREE> </metadata> <data> <stateVector> <EPOCH>2004-100T00:00:00</EPOCH> <X units="km">1</X> <Y>1</Y> <Z>1</Z> <X_DOT units="km/s">1</X_DOT> <Y_DOT>1</Y_DOT>



<Z_DOT>1</Z_DOT> </stateVector> <stateVector> <EPOCH>2004-100T00:00:00</EPOCH> <X>1</X> <Y units="km">1</Y> <Z>1</Z> <X_DOT>1</X_DOT> <Y_DOT units="km/s">1</Y_DOT> <Z_DOT>1</Z_DOT> </stateVector> <stateVector> <EPOCH>2004-100T00:00:00</EPOCH> <X>1</X> <Y>1</Y> <Z units="km">1</Z> <X_DOT>1</X_DOT> <Y_DOT>1</Y_DOT> <Z_DOT units="km/s">1</Z_DOT> </stateVector> </data> </segment> </body> </oem> <tdm> <header> <CCSDS_TDM_VERS>0.1.17</CCSDS_TDM_VERS> <CREATION_DATE>2004-281T17:26:06</CREATION_DATE> <ORIGINATOR>me</ORIGINATOR> <COMMENT>this is it!</COMMENT> </header> <body> <segment> <metadata> <TIME_SYSTEM>UTC</TIME_SYSTEM> <PARTICIPANT_1>DSS-25</PARTICIPANT_1> <PARTICIPANT_2>Cassini</PARTICIPANT_2> <PARTICIPANT_3>DSS-45</PARTICIPANT_3> <MODE>SEQUENCE</MODE> <PATH>123</PATH> <DIFF_MODE>N/A</DIFF_MODE> <COMPRESSION_TIME>60</COMPRESSION_TIME> <INTEGRATION_REF>start</INTEGRATION_REF>



<FREQ_OFFSET>1.273e+5</FREQ_OFFSET> <RANGE_MODE>coherent</RANGE_MODE> <RANGE_MODULUS>2e+23</RANGE_MODULUS> <RANGE_UNITS>ru</RANGE_UNITS> <ANGLE_TYPE>AZEL</ANGLE_TYPE> <TRANSMIT_DELAY_1>1.076234</TRANSMIT_DELAY_1> <START_TIME>2004-100T00:00:00.000000</START_TIME> <STOP_TIME>2004-100T01:00:00.000000</STOP_TIME> <DATA_QUALITY>validated</DATA_QUALITY> <CORRECTION_RNGCAL>170000</CORRECTION_RNGCAL> <CORRECTION_ANGLE_2>-1.987</CORRECTION_ANGLE_2> <CORRECTION_DOPPLER>-1</CORRECTION_DOPPLER> <CORRECTION_TROPO>-.005</CORRECTION_TROPO> <CORRECTION_CP>5.4327</CORRECTION_CP> </metadata> <data> <observation> <EPOCH>2004-100T01:01:01.111111</EPOCH> <AGC> 0.78 </AGC> </observation> <observation> <EPOCH>2004-100T01:01:01.111111</EPOCH> <ANGLE_1>57.29</ANGLE_1> </observation> <observation> <EPOCH>2004-100T01:01:01.111111</EPOCH> <ANGLE_2>57.29</ANGLE_2> </observation> <observation> <EPOCH>2004-100T01:01:01.111111</EPOCH> <CLOCK_BIAS>1.32375</CLOCK_BIAS> </observation> <observation> <EPOCH>2004-100T01:01:01.111111</EPOCH> <CLOCK_DRIFT>1.32375</CLOCK_DRIFT> </observation> <observation> <EPOCH>2004-100T01:01:01.111111</EPOCH> <CPDELAY> 43.1 </CPDELAY> </observation>



</segment> </body> </tdm> <tdm> <header> <CCSDS_TDM_VERS>0.1.17</CCSDS_TDM_VERS> <CREATION_DATE>2004-281T17:26:06</CREATION_DATE> <ORIGINATOR>me</ORIGINATOR> <COMMENT>this is it!</COMMENT> </header> <body> <segment> <metadata> <TIME_SYSTEM>UTC</TIME_SYSTEM> <PARTICIPANT_1>DSS-25</PARTICIPANT_1> <PARTICIPANT_2>Cassini</PARTICIPANT_2> <PARTICIPANT_3>DSS-45</PARTICIPANT_3> <MODE>SEQUENCE</MODE> <PATH>123</PATH> <DIFF_MODE>RANGE</DIFF_MODE> <TIMETAG_REF>TRANSMIT</TIMETAG_REF> <COMPRESSION_TIME>10</COMPRESSION_TIME> <INTEGRATION_REF>end</INTEGRATION_REF> <FREQ_OFFSET>0</FREQ_OFFSET> <RANGE_MODE>constant</RANGE_MODE> <RANGE_MODULUS>16777216.1</RANGE_MODULUS> <RANGE_UNITS>km</RANGE_UNITS> <ANGLE_TYPE>RADEC</ANGLE_TYPE> <START_TIME>2004-100T00:00:00.000000</START_TIME> <STOP_TIME>2004-100T01:00:00.000000</STOP_TIME> <DATA_QUALITY>degraded</DATA_QUALITY> </metadata> <data> <observation> <EPOCH>2004-100T01:01:01.111111</EPOCH> <AGC>12345.624</AGC> </observation> <observation> <EPOCH>2004-100T01:01:01.111111</EPOCH> <ANGLE_1>57.29</ANGLE_1> </observation> <observation> <EPOCH>2004-100T01:01:01.111111</EPOCH> <ANGLE_2>57.29</ANGLE_2> </observation>



<EPOCH>2004-100T01:01:01.111111</EPOCH> <TROPO_WET>1.171</TROPO_WET> </observation> <observation> <EPOCH>2004-100T01:01:01.111111</EPOCH> <TRANSMIT_FREQ_1>8415000000.1234567</TRANSMIT_FREQ_1> </observation> <observation> <EPOCH>2004-100T01:01:01.111111</EPOCH> <TRANSMIT_FREQ_RATE_1>36.2</TRANSMIT_FREQ_RATE_1> </observation> </data> </segment> </body> </tdm> <tdm> <header> <CCSDS_TDM_VERS>0.1.17</CCSDS_TDM_VERS> <CREATION_DATE>2004-281T17:26:06</CREATION_DATE> <ORIGINATOR>me</ORIGINATOR> <COMMENT>this is it!</COMMENT> </header> <body> <segment> <metadata> <TIME_SYSTEM>UTC</TIME_SYSTEM> <PARTICIPANT_1>DSS-25</PARTICIPANT_1> <PARTICIPANT_2>Cassini</PARTICIPANT_2> <PARTICIPANT_3>DSS-45</PARTICIPANT_3> <PARTICIPANT_4>DSS-45</PARTICIPANT_4> <PARTICIPANT_5>DSS-45</PARTICIPANT_5> <MODE>SEQUENCE</MODE> <PATH>123</PATH> <TIMETAG_REF>receive</TIMETAG_REF> <RANGE_MODE>coherent</RANGE_MODE> <RANGE_MODULUS>16777216</RANGE_MODULUS> <RANGE_UNITS>RU</RANGE_UNITS> <ANGLE_TYPE>XEYN</ANGLE_TYPE> <START_TIME>2004-100T00:00:00.000000</START_TIME> <STOP_TIME>2004-100T01:00:00.000000</STOP_TIME> <DATA_QUALITY>RAW</DATA_QUALITY> </metadata> <data> <observation> <EPOCH>2004-01-01T00:00:00.1</EPOCH>



</observation> <observation> <EPOCH>2004-100T01:01:01.111111</EPOCH> <RANGE_RATE>3.7</RANGE_RATE> </observation> <observation> <EPOCH>2004-100T01:01:01.111111</EPOCH> <RANGE_SNR>30</RANGE_SNR> </observation> <observation> <EPOCH>2004-100T01:01:01.111111</EPOCH> <RECEIVE_FREQ_3>8415000000.1234567</RECEIVE_FREQ_3> </observation> <observation> <EPOCH>2004-100T01:01:01.001111</EPOCH> <RECEIVE_FREQ_3>0</RECEIVE_FREQ_3> </observation> <observation> <EPOCH>2004-100T01:01:01.011111</EPOCH> <RECEIVE_FREQ_3>-1</RECEIVE_FREQ_3> </observation> <observation> <EPOCH>2004-100T01:01:01.111111</EPOCH> <TROPO_DRY>0.723</TROPO_DRY> </observation> <observation> <EPOCH>2004-100T01:01:01.111111</EPOCH> <TROPO_WET>1.171</TROPO_WET> </observation> <observation> <EPOCH>2004-100T01:01:01.111111</EPOCH> <TRANSMIT_FREQ_1>8415000000.1234567</TRANSMIT_FREQ_1> </observation> <observation> <EPOCH>2004-100T01:01:01.111111</EPOCH> <TRANSMIT_FREQ_RATE_1>36.2</TRANSMIT_FREQ_RATE_1> </observation> </data> </segment> </body> </tdm> <aem> <header> <CCSDS_AEM_VERS>0.2.4</CCSDS_AEM_VERS> <CREATION_DATE>2004-281T17:26:06</CREATION_DATE>



<ORIGINATOR>me</ORIGINATOR> <COMMENT>this is it!</COMMENT> </header> <body> <segment> <metadata> <OBJECT_NAME>Cassini</OBJECT_NAME> <OBJECT_ID>1997-061A</OBJECT_ID> <CENTER_NAME>Saturn</CENTER_NAME> <REF_FRAME>IAU-Saturn</REF_FRAME> <TIME_SYSTEM>UTC</TIME_SYSTEM> <START_TIME>2004-100T00:00:00.000000</START_TIME> <STOP_TIME>2004-100T01:00:00.000000</STOP_TIME> <INTERPOLATION_METHOD>Hermite</INTERPOLATION_METHOD> <INTERPOLATION_DEGREE>11</INTERPOLATION_DEGREE> <ATTITUDE_TYPE>QUATERNION</ATTITUDE_TYPE> </metadata> <data> <COMMENT>This AEM reflects one of each </COMMENT> <COMMENT>type of AEM attitude vector </COMMENT> <attitudeVector> <quaternion> <EPOCH>2004-100T00:00:00</EPOCH> <Q1>1</Q1> <Q2>1</Q2> <Q3>1</Q3> <QC>1</QC> </quaternion> </attitudeVector> <attitudeVector> <quaternion> <EPOCH>2004-100T00:00:00</EPOCH> <Q1>1</Q1> <Q2>1</Q2> <Q3>1</Q3> <QC>1</QC> </quaternion> </attitudeVector> </data> </segment> </body> </aem> <aem> <header>



<CCSDS_AEM_VERS>0.2.4</CCSDS_AEM_VERS> <CREATION_DATE>2004-281T17:26:06</CREATION_DATE> <ORIGINATOR>me</ORIGINATOR> <COMMENT>this is it!</COMMENT> </header> <body> <segment> <metadata> <OBJECT_NAME>Cassini</OBJECT_NAME> <OBJECT_ID>1997-061A</OBJECT_ID> <CENTER_NAME>Saturn</CENTER_NAME> <REF_FRAME>IAU-Saturn</REF_FRAME> <TIME_SYSTEM>UTC</TIME_SYSTEM> <START_TIME>2004-100T00:00:00.000000</START_TIME> <STOP_TIME>2004-100T01:00:00.000000</STOP_TIME> <ATTITUDE_TYPE>QUATERNION/DERIVATIVE</ATTITUDE_TYPE> </metadata> <data> <COMMENT>This AEM reflects a quaternion </COMMENT> <COMMENT>and its derivative </COMMENT> <attitudeVector> <quaternionderivative> <EPOCH>2004-100T00:00:00</EPOCH> <Q1>1</Q1> <Q2>1</Q2> <Q3>1</Q3> <QC>1</QC> <Q1_DOT>1</Q1_DOT> <Q2_DOT>1</Q2_DOT> <Q3_DOT>1</Q3_DOT> <QC_DOT>1</QC_DOT> </quaternionderivative> </attitudeVector> <attitudeVector> <quaternionderivative> <EPOCH>2004-100T00:00:00</EPOCH> <Q1>1</Q1> <Q2>1</Q2> <Q3>1</Q3> <QC>1</QC> <Q1_DOT units="s*-1">1</Q1_DOT> <Q2_DOT units="S*-1">1</Q2_DOT> <Q3_DOT units="1/s">1</Q3_DOT> <QC_DOT units="1/S">1</QC_DOT>



</quaternionderivative> </attitudeVector> </data> </segment> </body> </aem> <aem> <header> <CCSDS_AEM_VERS>0.2.4</CCSDS_AEM_VERS> <CREATION_DATE>2004-281T17:26:06</CREATION_DATE> <ORIGINATOR>me</ORIGINATOR> <COMMENT>this is it!</COMMENT> </header> <body> <segment> <metadata> <OBJECT_NAME>Cassini</OBJECT_NAME> <OBJECT_ID>1997-061A</OBJECT_ID> <CENTER_NAME>Saturn</CENTER_NAME> <REF_FRAME>IAU-Saturn</REF_FRAME> <TIME_SYSTEM>UTC</TIME_SYSTEM> <START_TIME>2004-100T00:00:00.000000</START_TIME> <STOP_TIME>2004-100T01:00:00.000000</STOP_TIME> <ATTITUDE_TYPE>QUATERNION/DERIVATIVE</ATTITUDE_TYPE> </metadata> <data> <COMMENT>This AEM reflects a quaternion </COMMENT> <COMMENT>and its derivative </COMMENT> <attitudeVector> <eulerangle> <EPOCH>2004-100T00:00:00</EPOCH> <ROLL units="DEG">45</ROLL> <PITCH units="DEG">0</PITCH> <YAW units="DEG">15</YAW> </eulerangle> </attitudeVector> <attitudeVector> <eulerangle> <EPOCH>2004-100T00:00:00</EPOCH> <ROLL units="DEG">45</ROLL> <PITCH units="deg">0</PITCH> <YAW units="DEG">15</YAW> </eulerangle> </attitudeVector>



</data> </segment> </body> </aem> <aem> <header> <CCSDS_AEM_VERS>0.2.4</CCSDS_AEM_VERS> <CREATION_DATE>2004-281T17:26:06</CREATION_DATE> <ORIGINATOR>me</ORIGINATOR> <COMMENT>this is it!</COMMENT> </header> <body> <segment> <metadata> <OBJECT_NAME>Cassini</OBJECT_NAME> <OBJECT_ID>1997-061A</OBJECT_ID> <CENTER_NAME>Saturn</CENTER_NAME> <REF_FRAME>IAU-Saturn</REF_FRAME> <TIME_SYSTEM>UTC</TIME_SYSTEM> <START_TIME>2004-100T00:00:00.000000</START_TIME> <STOP_TIME>2004-100T01:00:00.000000</STOP_TIME> <ATTITUDE_TYPE>QUATERNION/DERIVATIVE</ATTITUDE_TYPE> </metadata> <data> <COMMENT>This AEM reflects a quaternion </COMMENT> <COMMENT>and its derivative </COMMENT> <attitudeVector> <spin> <EPOCH>2004-100T00:00:00</EPOCH> <SPIN_ALPHA units="DEG">100</SPIN_ALPHA> <SPIN_DELTA>45</SPIN_DELTA> <SPIN_ANGLE>45</SPIN_ANGLE> <SPIN_ANGLE_VEL>45</SPIN_ANGLE_VEL> </spin> </attitudeVector> <attitudeVector> <spin> <EPOCH>2004-100T00:00:00</EPOCH> <SPIN_ALPHA units="DEG">100</SPIN_ALPHA> <SPIN_DELTA>45</SPIN_DELTA> <SPIN_ANGLE>45</SPIN_ANGLE> <SPIN_ANGLE_VEL>45</SPIN_ANGLE_VEL> </spin> </attitudeVector>



</data> </segment> </body> </aem> <aem> <header> <CCSDS_AEM_VERS>0.2.4</CCSDS_AEM_VERS> <CREATION_DATE>2004-281T17:26:06</CREATION_DATE> <ORIGINATOR>me</ORIGINATOR> <COMMENT>this is it!</COMMENT> </header> <body> <segment> <metadata> <OBJECT_NAME>Cassini</OBJECT_NAME> <OBJECT_ID>1997-061A</OBJECT_ID> <CENTER_NAME>Saturn</CENTER_NAME> <REF_FRAME>IAU-Saturn</REF_FRAME> <TIME_SYSTEM>UTC</TIME_SYSTEM> <START_TIME>2004-100T00:00:00.000000</START_TIME> <STOP_TIME>2004-100T01:00:00.000000</STOP_TIME> <ATTITUDE_TYPE>QUATERNION/DERIVATIVE</ATTITUDE_TYPE> </metadata> <data> <COMMENT>This AEM reflects a quaternion </COMMENT> <COMMENT>and its derivative </COMMENT> <attitudeVector> <quaternioneulerrate> <EPOCH>2004-100T00:00:00</EPOCH> <Q1>1</Q1> <Q2>1</Q2> <Q3>1</Q3> <QC>1</QC> <ROLL_RATE>45</ROLL_RATE> <PITCH_RATE>0</PITCH_RATE> <YAW_RATE>15</YAW_RATE> </quaternioneulerrate> </attitudeVector> <attitudeVector> <quaternioneulerrate> <EPOCH>2004-100T00:00:00</EPOCH> <Q1>1</Q1> <Q2>1</Q2> <Q3>1</Q3>



<QC>1</QC> <ROLL_RATE>45</ROLL_RATE> <PITCH_RATE>0</PITCH_RATE> <YAW_RATE>15</YAW_RATE> </quaternioneulerrate> </attitudeVector> </data> </segment> </body> </aem> <aem> <header> <CCSDS_AEM_VERS>0.2.4</CCSDS_AEM_VERS> <CREATION_DATE>2004-281T17:26:06</CREATION_DATE> <ORIGINATOR>me</ORIGINATOR> <COMMENT>this is it!</COMMENT> </header> <body> <segment> <metadata> <OBJECT_NAME>Cassini</OBJECT_NAME> <OBJECT_ID>1997-061A</OBJECT_ID> <CENTER_NAME>Saturn</CENTER_NAME> <REF_FRAME>IAU-Saturn</REF_FRAME> <TIME_SYSTEM>UTC</TIME_SYSTEM> <START_TIME>2004-100T00:00:00.000000</START_TIME> <STOP_TIME>2004-100T01:00:00.000000</STOP_TIME> <ATTITUDE_TYPE>QUATERNION/DERIVATIVE</ATTITUDE_TYPE> </metadata> <data> <COMMENT>This AEM reflects a quaternion </COMMENT> <COMMENT>and it's derivative </COMMENT> <attitudeVector> <spinnutation> <EPOCH>2004-100T00:00:00</EPOCH> <SPIN_ALPHA units="DEG">100</SPIN_ALPHA> <SPIN_DELTA>45</SPIN_DELTA> <SPIN_ANGLE>45</SPIN_ANGLE> <SPIN_ANGLE_VEL>45</SPIN_ANGLE_VEL> <NUTATION>0</NUTATION> <NUTATION_PER>23</NUTATION_PER> </spinnutation> </attitudeVector> <attitudeVector>



<spinnutation> <EPOCH>2004-100T00:00:00</EPOCH> <SPIN_ALPHA units="DEG">100</SPIN_ALPHA> <SPIN_DELTA>45</SPIN_DELTA> <SPIN_ANGLE>45</SPIN_ANGLE> <SPIN_ANGLE_VEL>45</SPIN_ANGLE_VEL> <NUTATION>0</NUTATION> <NUTATION_PER>23</NUTATION_PER> </spinnutation> </attitudeVector> </data> </segment> </body> </aem> <aem> <header> <CCSDS_AEM_VERS>0.2.4</CCSDS_AEM_VERS> <CREATION_DATE>2004-281T17:26:06</CREATION_DATE> <ORIGINATOR>me</ORIGINATOR> <COMMENT>this is it!</COMMENT> </header> <body> <segment> <metadata> <OBJECT_NAME>Cassini</OBJECT_NAME> <OBJECT_ID>1997-061A</OBJECT_ID> <CENTER_NAME>Saturn</CENTER_NAME> <REF_FRAME>IAU-Saturn</REF_FRAME> <TIME_SYSTEM>UTC</TIME_SYSTEM> <START_TIME>2004-100T00:00:00.000000</START_TIME> <STOP_TIME>2004-100T01:00:00.000000</STOP_TIME> <ATTITUDE_TYPE>QUATERNION/DERIVATIVE</ATTITUDE_TYPE> </metadata> <data> <COMMENT>This AEM reflects a quaternion </COMMENT> <COMMENT>and its derivative </COMMENT> <attitudeVector> <euleranglerate> <EPOCH>2004-100T00:00:00</EPOCH> <ROLL units="deg">45</ROLL> <PITCH units="DEG">0</PITCH> <YAW units="DEG">15</YAW> <ROLL_RATE>45</ROLL_RATE> <PITCH_RATE>0</PITCH_RATE>



<YAW_RATE>15</YAW_RATE> </euleranglerate> </attitudeVector> <attitudeVector> <euleranglerate> <EPOCH>2004-100T00:00:00</EPOCH> <ROLL units="DEG">45</ROLL> <PITCH units="DEG">0</PITCH> <YAW units="deg">15</YAW> <ROLL_RATE>45</ROLL_RATE> <PITCH_RATE>0</PITCH_RATE> <YAW_RATE>15</YAW_RATE> </euleranglerate> </attitudeVector> </data> </segment> </body> </aem> <tdm> <header> <CCSDS_TDM_VERS>0.1.17</CCSDS_TDM_VERS> <CREATION_DATE>2004-281T17:26:06</CREATION_DATE> <ORIGINATOR>me</ORIGINATOR> <COMMENT>Weather/media data only</COMMENT> </header> <body> <segment> <metadata> <TIME_SYSTEM>UTC</TIME_SYSTEM> <PARTICIPANT_1>DSS-25</PARTICIPANT_1> <PARTICIPANT_2>Cassini</PARTICIPANT_2> <MODE>N/A</MODE> <PATH>12</PATH> <TIMETAG_REF>RECEIVE</TIMETAG_REF> <ANGLE_TYPE>n/a</ANGLE_TYPE> <REFERENCE_FRAME>N/A</REFERENCE_FRAME> <START_TIME>2004-100T00:00:00.000000</START_TIME> <STOP_TIME>2004-100T01:00:00.000000</STOP_TIME> </metadata> <data> <observation> <EPOCH>2004-100T01:01:01.111111</EPOCH> <CPDELAY>11.34765</CPDELAY>



</observation> <observation> <EPOCH>2004-100T01:01:01.111111</EPOCH> <TEMPERATURE>1.0</TEMPERATURE> </observation> <observation> <EPOCH>2004-100T01:01:01.111111</EPOCH> <PRESSURE>1000.0</PRESSURE> </observation> <observation> <EPOCH>2004-100T01:01:01.111111</EPOCH> <RHUMIDITY>.50</RHUMIDITY> </observation> <observation> <EPOCH>2004-100T01:01:01.111111</EPOCH> <TROPO_DRY>0.723</TROPO_DRY> </observation> <observation> <EPOCH>2004-100T01:01:01.111111</EPOCH> <TROPO_WET>1.171</TROPO_WET> </observation> </data> </segment> </body> </tdm> <tdm> <header> <CCSDS_TDM_VERS>0.1.17</CCSDS_TDM_VERS> <CREATION_DATE>2005-178T21:45:00</CREATION_DATE> <ORIGINATOR>NASA/JPL</ORIGINATOR> <COMMENT>This example corresponds to the TDM Example</COMMENT> <COMMENT>"delta-DOR Observable"</COMMENT> </header> <body> <segment> <metadata> <TIME_SYSTEM>UTC</TIME_SYSTEM> <PARTICIPANT_1>1997-061A</PARTICIPANT_1> <PARTICIPANT_2>CTD-20</PARTICIPANT_2> <PARTICIPANT_3>DSS-25</PARTICIPANT_3> <PARTICIPANT_4>DSS-55</PARTICIPANT_4> <MODE>DOUBLE-DIFF</MODE> <PATH>N/A</PATH> <DIFF_MODE>RANGE</DIFF_MODE>



<TIMETAG_REF>receive</TIMETAG_REF> <FREQ_OFFSET>0</FREQ_OFFSET> <RANGE_MODE>coherent</RANGE_MODE> <RANGE_MODULUS>1.67485271e+02</RANGE_MODULUS> <RANGE_UNITS>s</RANGE_UNITS> <TRANSMIT_DELAY_3>.000077</TRANSMIT_DELAY_3> <RECEIVE_DELAY_3>.000077</RECEIVE_DELAY_3> <START_TIME>2004-136T15:42:00.000000</START_TIME> <STOP_TIME>2004-136T15:42:00.000000</STOP_TIME> <DATA_QUALITY>validated</DATA_QUALITY> </metadata> <data> <observation> <EPOCH>2004-136T15:42:00.000000</EPOCH> <RANGE_OBS>-4.911896106591159e+06</RANGE_OBS> </observation> </data> </segment> </body> </tdm> <tdm> <header> <CCSDS_TDM_VERS>0.1.17</CCSDS_TDM_VERS> <CREATION_DATE>2005-245T17:00:00</CREATION_DATE> <ORIGINATOR>NASA/JPL</ORIGINATOR> <COMMENT>This example corresponds to the TDM Example</COMMENT> <COMMENT>"differenced Doppler Observable"</COMMENT> </header> <body> <segment> <metadata> <TIME_SYSTEM>UTC</TIME_SYSTEM> <PARTICIPANT_1>yyyy-nnnA</PARTICIPANT_1> <PARTICIPANT_2>DSS-25</PARTICIPANT_2> <PARTICIPANT_3>DSS-55</PARTICIPANT_3> <MODE>SINGLE-DIFF</MODE> <DIFF_MODE>DELAY</DIFF_MODE> <TIMETAG_REF>receive</TIMETAG_REF> <COMPRESSION_TIME>580</COMPRESSION_TIME> <INTEGRATION_REF>MIDDLE</INTEGRATION_REF> <TRANSMIT_DELAY_2>.000077</TRANSMIT_DELAY_2> <RECEIVE_DELAY_2>.000077</RECEIVE_DELAY_2> <START_TIME>2004-136T15:30:00.000000</START_TIME>



<STOP_TIME>2004-136T15:30:00.000000</STOP_TIME> <DATA_QUALITY>validated</DATA_QUALITY> </metadata> <data> <observation> <EPOCH>2004-136T15:30:00.000000</EPOCH> <RECEIVE_FREQ>15100.837278</RECEIVE_FREQ> </observation> </data> </segment> <segment> <metadata> <TIME_SYSTEM>UTC</TIME_SYSTEM> <PARTICIPANT_1>DSS-25</PARTICIPANT_1> <MODE>N/A</MODE> <START_TIME>2004-136T15:30:00.000000</START_TIME> <STOP_TIME>2004-136T15:30:00.000000</STOP_TIME> <DATA_QUALITY>validated</DATA_QUALITY> </metadata> <data> <observation> <EPOCH>2004-136T15:30:00.000000</EPOCH> <CLOCK_BIAS>-4.59e-7</CLOCK_BIAS> </observation> </data> </segment> <segment> <metadata> <TIME_SYSTEM>UTC</TIME_SYSTEM> <PARTICIPANT_1>DSS-55</PARTICIPANT_1> <MODE>N/A</MODE> <START_TIME>2004-136T15:30:00.000000</START_TIME> <STOP_TIME>2004-136T15:30:00.000000</STOP_TIME> <DATA_QUALITY>validated</DATA_QUALITY> </metadata> <data> <observation> <EPOCH>2004-136T15:30:00.000000</EPOCH> <CLOCK_BIAS>-2.953e-6</CLOCK_BIAS> </observation> </data> </segment> </body> </tdm> </ndm>

consultative committee for space data systems documents/navigation... · through the process of...

Documents