ODM RB2 Review

1
ODM RB-2 Review

• ODM currently has a number of ambiguities that
  will corrupt interchanges
• It is defined on the basis of lines, which vary
  among operating systems
• Contrary to more modern message syntaxes, such as
  ODL, CCSDS/ISO PVL, and XML
• Keywords that have allowed values, such as
  TIME_SYSTEM, do not have unambiguously defined
  values
• UTC versus Universal Time Coordinated

2
Proposal

• Use the CCSDS PVL language for the syntax
• Allow other syntaxes in the future by putting the
  syntax at the end of the document as a separate
  section or annex
• Clearly define the allowed values, and whether
  any of them include spaces or not. If spaces are
  allowed, how many and where?

3
Possible OPM Example

• CCSDS_OPM_VERS 1.0
• CREATION_DATE 2001-11-06T092357
• / Geocentric, cartesian, Earth-Fixed /
• BEGIN_GROUP General_Information
• OBJECT_NAME GODZILLA
• OBJECT_ID 2000-028A
• CENTER_FRAME EARTH
• REF_FRAME ITRF-97
• TIME_SYSTEM UTC
• / OBJECT_ID 1998-057A /
• / ITIM 1998 OCT ./
• / ITIM 1998 OCT /
• EPOCH 1996-12-18T142815.1172
• END_GROUP General_Information
• BEGIN_GROUP STATE_VECTOR
• X 6503.514000 ltKMgt
• Y 1239.647000 ltKMgt