<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Guys,</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Thanks, Peter</div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>><br>
<span style="font-weight:bold">Date: </span>Friday, June 19, 2015 at 6:25 PM<br>
<span style="font-weight:bold">To: </span>Marc Blanchet <<a href="mailto:marc.blanchet@viagenie.ca">marc.blanchet@viagenie.ca</a>>, Brian Oliver <<a href="mailto:briano@aiaa.org">briano@aiaa.org</a>>, Kelvin Nichols <<a href="mailto:kelvin.nichols@nasa.gov">kelvin.nichols@nasa.gov</a>>,
Tom Gannett <<a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a>>, Erik Barkley <<a href="mailto:Erik.J.Barkley@jpl.nasa.gov">Erik.J.Barkley@jpl.nasa.gov</a>><br>
<span style="font-weight:bold">Cc: </span>Space Assigned Numbers Authority <<a href="mailto:info@sanaregistry.org">info@sanaregistry.org</a>><br>
<span style="font-weight:bold">Subject: </span>First cut at more complete OID and database design<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
Guys,</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
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.</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
Here is how it all fits together:</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<b>OID Tree (new)</b></div>
<ul style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<li>Defines the classifiers for all the key object types</li><li>Defines, using these classifiers, the unique OIDs for various leaf nodes (people, orgs, sites, object types, roles, etc)</li><li>Includes the ability to define sub-node structure, like NASA / JPL / DSN</li><li>Used to define a unique OID for every kind of referencable object</li></ul>
<div><b style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">Org Types & Relationships (largely </b><font face="Calibri,sans-serif"><b>existent now)</b></font></div>
<ul style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<li>Defines the structure of the database of organizations</li><li>Shows the hierarchy of organzations and approval/sponsorship</li><li>Includes data structures for organizations (and their parts, using OIDs), name, address, phone, URL, etc</li><li>Provides for differentiating member, observer, affiliate, etc orgs and for tracking who sponsored them</li><li>Allows assignment of roles to different orgs and elements (0..*)</li><li>Includes fields tracking who requested the change and who made the change (using OIDs)</li><li>Using OIDs the organization database ties to the CCSDS website database</li></ul>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<b>Person info and roles </b><b>(largely </b><font face="Calibri,sans-serif"><b>existent now)</b></font></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<ul>
<li>Defines the structure of the database of persons</li><li>Shows the registration paths for people from the organizations they are part of</li><li>Includes data structures for name, address, phone, organization (using OID) , etc and for their person OID</li><li>Allows assignment of roles to different persons (0..*)</li><li>Includes fields tracking who requested the change and who made the change (using OIDs)</li><li>Using OIDs the person database ties to the CCSDS website database</li></ul>
<div><b>Spacecraft</b> <b>(largely </b><font face="Calibri,sans-serif" style="font-size: medium;"><b>existent now)</b></font></div>
<div></div>
</div>
<ul>
<li>Used to assign OIDs, and SCIDs to spacecraft</li><li>Adds name & alias capability, and more SCID validity period info</li><li>Includes fields tracking who requested the change and who made the change (using OIDs)</li></ul>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<b>Service Site and GS Database (mostly all new)</b></div>
<ul>
<li>includes site definitions, service definitions, and ground station (GS) definitions</li><li>Permits sites with services, or with GS, or with both</li><li>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)</li><li>Assigns OIDs to all of these keys objects and can be extended as needed by CSS to add new services, FR, OIDs, etc</li><li>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</li><li>See the IOAG RF Assets database design too, it's a separate file</li></ul>
<div><b>Org Code database </b><b style="font-family: Calibri, sans-serif; font-size: 14px;">(all new, but built incrementally)</b></div>
<ul>
<li>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</li></ul>
<div>
<div><b>Country Code database </b><b style="font-family: Calibri, sans-serif; font-size: 14px;">(all new)</b></div>
<ul>
<li>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</li></ul>
<div></div>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
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.</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
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.</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
Right?</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
Have a good weekend, Peter</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<br>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>