[MOIMS-NAV-EXEC] Request to Add/Modify Entries in the "Organizations" Registry

[Berry, David S (3920)]

Dear SANA Operator:

The Navigation WG is continuing its effort to phase out the "Conjunction Data Message Originator" registry in the SANA (https://sanaregistry.org/r/cdm_originator ). This is being done as part of Peter Shames' re-engineering effort to eliminate the many role-based registries that contain "organization" related information.

Thank you for creating the "Conjunction Data Message Originator" role in the "Organization Roles" SANA registry https://sanaregistry.org/r/organization-roles (currently a "Candidate Registry"); this was the first step in our plan detailed below.

The attached document corresponds to Steps 2 and 3 in the plan detailed in the below message from August 2017 (however, I note that the "Organizations" registry, while listed as an "Approved" registry, still has every entry marked as having a Status of "Provisional", and for some organizations there are multiple entries).

At any rate, there are several requested changes detailed in the attachment, for your consideration. The plan outlined below provides context for these requests.

Regards,
David Berry
Chair, CCSDS Navigation WG



On 8/20/17, 5:56 AM, "Berry, David S (3920)" <david.s.berry at jpl.nasa.gov> wrote:

    Dear SANA Operator:
    
    At Peter Shames' suggestion/request, the CCSDS Navigation WG is in the process of phasing out the current "Conjunction Data Message Originator" registry ( https://sanaregistry.org/r/cdm_originator ).
    
    Phasing out the existing registry will be a multi-step process, and we are not yet ready eliminate it, but one of the necessary preliminary steps is to add a role to the new "Organization Roles" registry ( https://sanaregistry.org/r/organization-roles ). The new role should be something like "Conjunction Data Message Originator". This role is similar in concept to some of the roles currently in that registry, e.g., "D-DOR Service Provider" and "Relay Service Provider". Organizations that are authorized to create CDMs will ultimately have the new attribute added to their entry in the "Organizations" registry (https://sanaregistry.org/r/organizations/ ). 
    
    For planning purposes, our process involves:
    
    1. Creating the "Conjunction Data Message Originator" role in Organization Roles.
    2. Ensuring that all organizations currently listed in the existing Conjunction Data Message Originator registry have an entry in the Organizations registry.
    3. Adding the new "Conjunction Data Message Originator" role to the Organization entries for those entities identified in the preceding step.
    4. Filing a Corrigendum to the CDM Blue Book 508.0-B-1 to reference the new registry structure.
    5. Eliminate the existing Conjunction Data Message Originator registry. 
    
    The request in this email applies to Step 1 in this plan. The Navigation WG is currently collecting the information required for Step 2.
    
    Regards,
    David Berry
    Chair, CCSDS Navigation WG 
    
    





-------------- next part --------------
A non-text attachment was scrubbed...
Name: CDM-originator-table.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 133686 bytes
Desc: CDM-originator-table.docx
URL: <http://mailman.ccsds.org/pipermail/moims-nav-exec/attachments/20171212/a7c7ea13/attachment.docx>