[CESG] [EXTERNAL] CCSDS SM W/G SANA wish list with respect to spacecraft and aperture aliases;

[Shames, Peter M (US 312B)]

Thanks Colin,

This seems to accurately reflect the discussion that we had during the SSG meeting.  I believe that most of this is essentially operational policy and that it does not require any new SANA registry structures, but it does change how we use and update certain fields.  It does add new assignment process and a new request on the ARs for each Agency to update the Spacecraft and SS&A registries with these somewhat more formalized Alias entries.  As I understand it, the operational process is essentially going to be something like this:


  1.  Agency A wants to add a new S/C or Aperture Alias to an entry owned by Agency B.
  2.  Agency A must ask the AR for the Agency B to add a new Alias to their registry entries.
  3.  If Agency B agrees, they would add a new text string alias entry in the form “Agency A::A-alias” to their existing Agency B entries.
  4.  These “Agency A” identifier prefix would use whatever the Agency A AR had established in the official “Abbreviation” field for the Agency A entry in the Organization Registry.
  5.  That is all that is needed.

The only other question would appear to be this:

  1.  Is it essential for the SANA to update all of the existing Aliases to add these “Agency X::” prefixes for ALL existing aliases of each Agency X entity that is registered?

I think that CSS must document these changes to the process for these two registries, the effect on the Agency AR responsibilities, and the changes to the SANA process in a Blue or Magenta Book SANA annex.  In fact, you need to update the SANA RMP to reflect these changes as well.

We could prototype it in a Beta registry for your evaluation, but the Production changes will need to be documented, formalized, and approved.

Cheers, Peter


From: Colin Haddow <Scotty.Consulting at outlook.de> on behalf of Colin Haddow <Scotty.Consulting at Scotty-Enterprizes.com>
Date: Tuesday, November 14, 2023 at 4:53 AM
To: SANA <info at sanaregistry.org>, Peter Shames <peter.m.shames at jpl.nasa.gov>
Cc: Marcin Gnat <marcin.gnat at dlr.de>, Erik Barkley <erik.j.barkley at jpl.nasa.gov>
Subject: [EXTERNAL] CCSDS SM W/G SANA wish list with respect to spacecraft and aperture aliases;

Hi Julien, Peter,
                          following on from the discussion at the SANA Steering Group last Friday about aliases for spacecraft and apertures I've put together a "wish list";


Spacecraft Registry

  1.  The spacecraft registry is still a "candidate" registry and this would need to be made an "approved" registry.

  1.  "World Read Access" (shouldn't be a problem as I think the whole spacecraft registry is currently world read access) to at least the following fields in the registry;

     *   Name

     *   Abbreviation

     *   Aliases
Service Sites and Apertures

  1.  "World read access" to the following fields;

     *   Site Name

     *   Site Name Abbreviation

     *   Site Name Aliases

     *   Aperture Name

     *   Aperture Name Abbreviation

     *   Aperture Name Aliases
Organizations Registry

  1.  "World Read Access" (shouldn't be a problem as I think the whole organizations registry is currently world read access) to at least the following fields in the registry;

     *   Name

     *   Abbreviation
The name space qualifier for the abbreviations would, as discussed, be the Abbreviation from the Organization with 2 colons appended, e.g. ESA::
Programmatic access to these fields would also, potentially, be useful.

Cheers for now,

Colin



Dr. Colin R. Haddow

Scotty Consulting UG
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20231115/0d28cf65/attachment-0001.htm>