XML Specification for Navigation Data Messages - CCSDS

More documents

Recommendations

Info

DRAFT XML SPECIFICATION FOR NAVIGATION DATA MESSAGES 4.13 USER DEFINED PARAMETERS The ODM Version 2.0 introduced the notion of ‘user-defined parameters’. These parameters are situation specific and not standardized, thus they must be specified in ICDs between the exchange participants. The use of user-defined parameters is not encouraged. User-defined parameters in the NDM/XML are only supported for the OMM and OPM Version 2; userdefined parameters are not supported in the OEM Version 2 or any other Navigation Data Message. Because these parameters are not known to the schema, there is only one very broad keyword offered in the NDM/XML: . The user-defined parameters appear in a logical block that is offset with the tag . Following this tag, any number and order of tags may appear. The KVN keywords for user-defined parameters are formed by using the prefix ‘USER_DEFINED’ followed by a variable-length character string that names the parameter. In the NDM/XML, the prefix shall be the XML tag and the variable-length name of the parameter shall be the value for the ‘parameter’ attribute. All information about the user-defined parameters shall be conveyed via the attributes ‘parameter’ and ‘value’. The type for ‘value’ shall be ‘xsd:string’, even if the value is numeric. For example, the following KVN parameters might appear in an OMM or OPM: USER_DEFINED_ATMOSPHERE_MODEL = MSISE90 USER_DEFINED_C3 = 29.376 USER_DEFINED_EARTH_RADIUS = 6378.1 USER_DEFINED_3RD_BODY_PERTURBATION = JUPITER These parameters would appear in an NDM/XML representation as: MSISE90 29.376 6378.1 JUPITER CCSDS 505.0-R-2 Page 4-25 June 2009
DRAFT XML SPECIFICATION FOR NAVIGATION DATA MESSAGES 5 INFORMATION SECURITY 5.1 GENERAL This section presents the results of an analysis of security considerations applied to the technologies specified in this Recommended Standard. 5.2 SECURITY CONCERNS RELATED TO THIS RECOMMENDED STANDARD 5.2.1 DATA PRIVACY Privacy of data formatted in compliance with the specifications of this Recommended Standard should be assured by the systems and networks on which this Recommended Standard is implemented. 5.2.2 DATA INTEGRITY Integrity of data formatted in compliance with the specifications of this Recommended Standard should be assured by the systems and networks on which this Recommended Standard is implemented. 5.2.3 AUTHENTICATION OF COMMUNICATING ENTITIES Authentication of communicating entities involved in the transport of data that complies with the specifications of this Recommended Standard should be provided by the systems and networks on which this Recommended Standard is implemented. 5.2.4 DATA TRANSFER BETWEEN COMMUNICATING ENTITIES The transfer of data formatted in compliance with this Recommended Standard between communicating entities should be accomplished via secure mechanisms approved by the IT Security functionaries of exchange participants. 5.2.5 CONTROL OF ACCESS TO RESOURCES This Recommended Standard assumes that control of access to resources will be managed by the systems upon which provider formatting and recipient processing are performed. 5.2.6 AUDITING OF RESOURCE USAGE This Recommended Standard assumes that auditing of resource usage will be handled by the management of systems and networks on which this Recommended Standard is implemented. CCSDS 505.0-R-2 Page 5-1 June 2009
Page 1 and 2: Draft Recommendation for Space Data
Page 3 and 4: DRAFT XML SPECIFICATION FOR NAVIGAT
Page 47: DRAFT XML SPECIFICATION FOR NAVIGAT

XML Specification for Navigation Data Messages - CCSDS

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?