[Smwg] FW: First cut at more complete OID and database design

[Shames, Peter M (312B)]

Guys,

Here is the rest of the DRAFT set of models for these registries, along with some descriptive materials.  Please see if these, plus the mark-ups I just sent, provide you with enoug to work with for your "name" (spacecraft) and "originating Organization" (service provider) registry references.

Thanks, Peter


From: Peter Shames <peter.m.shames at jpl.nasa.gov<mailto:peter.m.shames at jpl.nasa.gov>>
Date: Friday, June 19, 2015 at 6:25 PM
To: Marc Blanchet <marc.blanchet at viagenie.ca<mailto:marc.blanchet at viagenie.ca>>, Brian Oliver <briano at aiaa.org<mailto:briano at aiaa.org>>, Kelvin Nichols <kelvin.nichols at nasa.gov<mailto:kelvin.nichols at nasa.gov>>, Tom Gannett <thomas.gannett at tgannett.net<mailto:thomas.gannett at tgannett.net>>, Erik Barkley <Erik.J.Barkley at jpl.nasa.gov<mailto:Erik.J.Barkley at jpl.nasa.gov>>
Cc: Space Assigned Numbers Authority <info at sanaregistry.org<mailto:info at sanaregistry.org>>
Subject: First cut at more complete OID and database design

Guys,

Attached please find the set of files that I have created to try and capture in a more accessible way the proposed design for the OID tree and the org, person, spacecraft, and site databases that define these information models and also reference these OIDs.   This is going to look complicated, but much of what I am showing here is actually already in these databases.  In some cases it is just a matter of adding an OID field where needed to tie things together.  In other cases we will need to build a new database, such as the Site & GS database.   And there are a couple of databases that just serve to map terms from one form to another.  One of these is the unique org code to org OID map, the other is a country name or ID to ISO country code map.  Since OIDs must all contain only numbers we need these code mappers.

Here is how it all fits together:

OID Tree (new)

  *   Defines the classifiers for all the key object types
  *   Defines, using these classifiers, the unique OIDs for various leaf nodes (people, orgs, sites, object types, roles, etc)
  *   Includes the ability to define sub-node structure, like NASA / JPL / DSN
  *   Used to define a unique OID for every kind of referencable object

Org Types & Relationships (largely existent now)

  *   Defines the structure of the database of organizations
  *   Shows the hierarchy of organzations and approval/sponsorship
  *   Includes data structures for organizations (and their parts, using OIDs), name, address, phone, URL, etc
  *   Provides for differentiating member, observer, affiliate, etc orgs and for tracking who sponsored them
  *   Allows assignment of roles to different orgs and elements (0..*)
  *   Includes fields tracking who requested the change and who made the change (using OIDs)
  *   Using OIDs the organization database ties to the CCSDS website database

Person info and roles (largely existent now)

  *   Defines the structure of the database of persons
  *   Shows the registration paths for people from the organizations they are part of
  *   Includes data structures for name, address, phone, organization (using OID) , etc and for their person OID
  *   Allows assignment of roles to different persons  (0..*)
  *   Includes fields tracking who requested the change and who made the change (using OIDs)
  *   Using OIDs the person database ties to the CCSDS website database

Spacecraft (largely existent now)

  *   Used to assign OIDs, and SCIDs to spacecraft
  *   Adds name & alias capability, and more SCID validity period info
  *   Includes fields tracking who requested the change and who made the change (using OIDs)

Service Site and GS Database (mostly all new)

  *   includes site definitions, service definitions, and ground station (GS) definitions
  *   Permits sites with services, or with GS, or with both
  *   Handles all sorts of weird "corner cases" like the DSN spilt mode where the forward SLE is at the GS site (DSCC, which is a site with GS and Services) and the return SLE is at the DSOC (a site with service, but no GS)
  *   Assigns OIDs to all of these keys objects and can be extended as needed by CSS to add new services, FR, OIDs, etc
  *   The GS part of the database uses OIDs to tie these GS (which have more of a space link and SLE service focus) to the related RF Asset database (which needs to have OIDs added
  *   See the IOAG RF Assets database design too, it's a separate file

Org Code database (all new, but built incrementally)

  *   Provides a flat file mapping of an organization's OID (a string of numbers and periods) to a simple 1-3 digit number that can itself be referenced in the OIDs of objects that belong to that organization

Country Code database (all new)

  *   Provides a flat file mapping of the ISO country codes (3 digits), full names, 2 character ASCII abbreviations (A2) and 3 character ASCII names (A3) to a simple number that can itself be referenced in the OIDs of objects that are in that country

So, one taxonomy / set of classifiers used to define objects used in a variety of inter-related databases and two mapping databases that help it all to hang together.  This all looks a lot like the chart that Erik and I produced a few days ago, but it does differ in some details.  I did not build a new overview yet, but I will.  This approach also provides hooks (I think) for all the extensions that the CSS guys want to make, but that is another whole separate topic for conversation, as are the details of what we need to do with the RF Assets database.  Those need to be worked, but one thing at a time.

The other key item is that this does what we said we were going to do, and that is to minimize impact on the CCSDS website databases.  For that to hook in correctly we just need to finalize the OID tree, assign the necessary unique OIDs (as SANA functions) and then tell Brian which OIDs go with what organizations and people.  We'll have some update and verify work to do, but that will hook things together.

Right?

Have a good weekend, Peter




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20150622/79f8d4c3/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CCSDS Org Types & Relationships 19Jun15 v1.pdf
Type: application/pdf
Size: 103292 bytes
Desc: CCSDS Org Types & Relationships 19Jun15 v1.pdf
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20150622/79f8d4c3/attachment.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CCSDS Person Info & Roles 19Jun15 v1.pdf
Type: application/pdf
Size: 92102 bytes
Desc: CCSDS Person Info & Roles 19Jun15 v1.pdf
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20150622/79f8d4c3/attachment-0001.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Spacecraft ID, name, char database 19Jun15 v1.pdf
Type: application/pdf
Size: 74914 bytes
Desc: Spacecraft ID, name, char database 19Jun15 v1.pdf
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20150622/79f8d4c3/attachment-0002.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Service Site and GS Database 19Jun15 v1.pdf
Type: application/pdf
Size: 228249 bytes
Desc: Service Site and GS Database 19Jun15 v1.pdf
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20150622/79f8d4c3/attachment-0003.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: RF Asset Registry (Existing IOAG) 19Jun15 v1.pdf
Type: application/pdf
Size: 139538 bytes
Desc: RF Asset Registry (Existing IOAG) 19Jun15 v1.pdf
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20150622/79f8d4c3/attachment-0004.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Org Code database 19Jun15 v1.pdf
Type: application/pdf
Size: 56000 bytes
Desc: Org Code database 19Jun15 v1.pdf
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20150622/79f8d4c3/attachment-0005.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Country Code Database (ISO) 19Jun15 v1.pdf
Type: application/pdf
Size: 66733 bytes
Desc: Country Code Database (ISO) 19Jun15 v1.pdf
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20150622/79f8d4c3/attachment-0006.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CCSDS OID Tree 19Jun15 v3.pdf
Type: application/pdf
Size: 97498 bytes
Desc: CCSDS OID Tree 19Jun15 v3.pdf
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20150622/79f8d4c3/attachment-0007.pdf>