[MOIMS-NAV-EXEC] Navigation WG Requests for SANA "Organization" Registry
SkySentry
finklemand at skysentry.net
Sun Nov 8 13:57:18 UTC 2015
David and Peter,
I suggest that these be sent also to ISO so that they may be included in ISO standard terms and abbreviations. It would be a big job, but it might be done for the entire registry. Since a big job is under way for reengineering, perhaps this could fit in the effort.
Dave
Sent from my iPad
> On Nov 8, 2015, at 1:43 AM, Berry, David S (3920) <david.s.berry at jpl.nasa.gov> wrote:
>
>
> Peter:
>
> With respect to the SANA Registry Re-Engineering ongoing, the Navigation
> WG requires the incorporation of the following into the
> http://sanaregistry.org/r/organizations/organizations.html registry based
> on material that exists in our current set of Blue Book publications.
>
> Additionally, we urge that the conversion from "candidate" to "approved"
> registry be concluded as soon as possible for the Organizations registry.
> Because of its implied size and far-reaching nature, this Organization
> registry is one that could potentially require changes on a weekly basis.
> It will never be perfect, but if the update cycle is sufficiently
> frequent, the gap between the registry and reality should be minimized.
>
> Here are the specific changes requested (since the "Registration Policy"
> for this registry is not yet specified, I'll send them to you):
>
> 1. The role of "CDM Originator" and the values in the registry
> "Conjunction Data Message ORIGINATOR"
> http://sanaregistry.org/r/cdm_originator/cdm_originator.html should be
> added.
>
> Additionally, we would request that the following entries for the
> "Abbreviation" column be added in the Organizations registry based on
> examples shown in our current Blue Books. Until now this has been
> essentially free form text, which explains the variety of values... note
> that there should be no REQUIREMENT for values to be drawn from the SANA
> Registry, as I believe this will restrict some adoption of standards by
> newly interested organizations.
>
> 2. ESA_ESAC (shown on CDM example)
> 3. ESOC (shown in ODM example, TDM example)
> 4. GSFC FDF (shown in ADM example and NDM/XML example)
> 5. GSOC (shown in ODM example, TDM example)
> 6. INMARSAT/UK (shown in ODM example)
>
> 7. INTELSAT/USA (shown in ODM example)
> 8. JSC (shown in ADM example)
> 9. JSPOC (shown on CDM example)
> 10. NASA-JPL (shown on CDM example)
> 11. NASA/JPL (shown in ODM example... agency with specific subordinate
> organization)
>
> 12. NASA/JPL/DSN (specified in NASA JPL 820-013 document)
>
>
> 13. NOAA/USA (shown in ODM example and NDM/XML example... NOAA is in the
> registry, but the ODM recommends including the country when the
> organization is not one of the member agencies)
> 14. SDC (shown on CDM example)
> 15. USAF (shown in ODM example)
>
>
>
> Alternatively, corrigenda could be put into those books that have examples
> that are deemed not suitable for the Organizations registry.
>
> Regards,
> David
>
>
> _______________________________________________
> MOIMS-NAV-EXEC mailing list
> MOIMS-NAV-EXEC at mailman.ccsds.org
> http://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-nav-exec
More information about the MOIMS-NAV-EXEC
mailing list