<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;">
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
Thanks Erik. I agree with your assessment and with your statement of the intended purpose.</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;">
As an example, what this would mean for the MOIMS Nav WG CDM is this:</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;">
Now:</div>
<ul>
<li style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
In the CDM they defined a data structure that includes an "ORIGINATOR" data field</li><li style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
The ORIGINATOR is defined like this "<span style="font-family: ArialMT; font-size: 9pt;">Creating agency or owner/operator (value should be registered in SANA). (See 5.2.9 for formatting rules.)"</span></li><li style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<span style="font-family: ArialMT; font-size: 9pt;">Examples are provided: </span><span style="font-family: ArialMT; font-size: 9pt;">JSPOC, ESA, CNES, NASA, SDC </span></li><li style="color: rgb(0, 0, 0);"><span style="font-family: ArialMT; font-size: 12px; color: rgb(0, 0, 0); font-style: normal; font-weight: normal; text-decoration: none;">They reference a CATALOG_NAME of SATCAT and an OBJECT_NAME with examples like "</span><span style="color: rgb(0, 0, 0); font-style: normal; font-weight: normal; text-decoration: none;"><font face="Calibri,sans-serif"><span style="font-family: ArialMT; font-size: 9pt;">SPOT,
ENVISAT, IRIDIUM, INTELSAT</span>"</font></span><span style="font-family: ArialMT; font-size: 9pt;"> </span></li><li style="color: rgb(0, 0, 0);"><span style="color: rgb(0, 0, 0); font-family: ArialMT; font-size: 12px; font-style: normal; font-weight: normal; text-decoration: none;">There is an ORIGINATOR registry (http://sanaregistry.org/r/cdm_originator/cdm_originator.html)
that just has Keyword (name) and Meaning (like JSPOC) fields,</span></li><li style="color: rgb(0, 0, 0);"><span style="color: rgb(0, 0, 0); font-family: ArialMT; font-size: 12px; font-style: normal; font-weight: normal; text-decoration: none;">There is a CATALOG_NAME registry (http://sanaregistry.org/r/cdm_catalog/cdm_catalog.html),
it also has just Keyword, like SATCAT and Meaning, like "United States Strategic Command (USSTRATCOM) satellite catalog"</span></li><li style="color: rgb(0, 0, 0);"><span style="color: rgb(0, 0, 0); font-family: ArialMT; font-size: 12px; font-style: normal; font-weight: normal; text-decoration: none;">Presumably the OBJECT_NAME are all registered in these catalogs, but this is not clearly
stated and the names may only be relevant separately in each catalog</span></li><li style="color: rgb(0, 0, 0);"><span style="color: rgb(0, 0, 0); font-family: ArialMT; font-size: 12px; font-style: normal; font-weight: normal; text-decoration: none;">Section 5.2.9, which is referenced for several of these fields, says this </span></li><li style="color: rgb(0, 0, 0);"><span style="color: rgb(0, 0, 0); font-family: ArialMT; font-size: 12px; font-style: normal; font-weight: normal; text-decoration: none;">
<div class="page" title="Page 47">
<div class="layoutArea">
<div class="column">
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<p><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">5.2.9 In the value fields for the keywords ORIGINATOR, MESSAGE_ID, OBJECT_DESIGNATOR, CATALOG_NAME and INTERNATIONAL_DESIGNATOR, values shall be given as alphanumeric text. The underscore
"_" and dash "-" may also be used. </span></p>
</blockquote>
</div>
</div>
</div>
</span></li><li><span style="font-size: 16px;">The SANA Consideratins Section says this:</span></li><li><span style="color: rgb(0, 0, 0); font-family: TimesNewRomanPSMT; font-size: 16px; font-style: normal; font-weight: normal; text-decoration: none;">
<div class="page" title="Page 73">
<div class="layoutArea">
<div class="column">
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<p><span style="font-size: 12pt;">The CDM XML schema;<br>
A transform from the CDM XML to the CDM KVN version;<br>
Values for the keywords ORIGINATOR and CATALOG_NAME; and<br>
A list of options for the COLLISION_PROBABILITY_METHOD keyword. </span></p>
</blockquote>
</div>
</div>
</div>
</span></li><li><span style="color: rgb(0, 0, 0); font-size: 16px; font-style: normal; font-weight: normal; text-decoration: none;">There is no clear definition for these registries nor for the fields that they should contain, as stated in the current SANA YB.</span></li></ul>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
Assuming the revised SANA Enterprise registries and "registry re-use / adapt policy":</div>
<div>
<ul>
<li style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0);">
In the CDM they defined a data structure that includes an "ORIGINATOR" data field</li><li style="font-family: Calibri, sans-serif; font-size: 14px;">The ORIGINATOR is defined like this "<span style="font-family: ArialMT; font-size: 9pt;">Creating agency or owner/operator (<b><font color="#ff0000">Organziation shall be registered in SANA Organization
registry)</font></b>. (See 5.2.9 for formatting rules.)"</span></li><li style="font-family: Calibri, sans-serif; font-size: 14px;"><span style="color: rgb(0, 0, 0); font-family: ArialMT; font-size: 9pt;">Examples are provided: </span><span style="font-family: ArialMT; font-size: 9pt;">JSPOC, ESA, CNES, NASA, SDC
<b><font color="#ff0000">(These will all have to be registered if they are not already)</font></b></span></li><li style="font-family: Calibri; font-size: medium;"><span style="color: rgb(0, 0, 0); font-family: ArialMT; font-size: 12px;">They reference a CATALOG_NAME of SATCAT and an OBJECT_NAME with examples like "</span><font face="Calibri,sans-serif" style="color: rgb(0, 0, 0);"><span style="font-family: ArialMT; font-size: 9pt;">SPOT,
ENVISAT, IRIDIUM, INTELSAT</span>"</font><span style="font-family: ArialMT; font-size: 9pt;">
<b><font color="#ff0000">(There is a list of Catalogs, but they are just catalog names, there should be URLs for them too and references to the Orgs that own them)</font></b></span></li><li style="font-family: Calibri; font-size: medium;"><span style="font-family: ArialMT; font-size: 12px;">There is an ORIGINATOR registry that just has the Keyword (name) and Meaning (like JSPOC)
<b><font color="#ff0000">(Each ORIGINATOR org should be registered in the Organization Registry. Ideally each of these specific orgs would also have the CDM Provider Role set.)</font></b></span></li><li style="font-family: Calibri; font-size: medium;"><span style="color: rgb(255, 0, 0); font-family: ArialMT; font-size: 12px; font-style: normal; font-weight: bold; text-decoration: none;">The CDM would ask that the "CDM Provider Role" be created as an Org
Role so that it could be assigned to an Org, or sub-org, as needed.</span></li><li style="font-family: Calibri; font-size: medium;"><span style="font-family: ArialMT; font-size: 12px;">There is a CATALOG_NAME registry, it also has just Keyword, like SATCAT and Meaning, like "United States Strategic Command (USSTRATCOM) satellite catalog"<b><font color="#ff0000">
(The Catalog registry really should contain at least a URL and the Org that wons the catalog in the registry.</font></b></span></li><li style="font-family: Calibri; font-size: medium;"><span style="font-family: ArialMT; font-size: 12px;">Presumably the OBJECT_NAME are all registered in these catalogs, but this is not clearly stated and the names may only be relevant separately in each catalog
<b><font color="#ff0000">(There should be some clear statement to the effect that each OBJECT_NAME<span style="font-style: italic;">
</span>and also OBJECT<span style="font-style: italic;">_</span>DESIGNATOR is only defined in the context of the referenced CATALOG)</font></b></span></li><li style="font-family: Calibri; font-size: medium; color: rgb(0, 0, 0);"><span style="font-family: ArialMT; font-size: 12px;">Section 5.2.9, which is referenced for several of these fields, says this </span></li><li style="font-family: Calibri; font-size: medium; color: rgb(0, 0, 0);"><span style="font-family: ArialMT; font-size: 12px;">
<div class="page" title="Page 47">
<div class="layoutArea">
<div class="column">
<blockquote style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<p><span style="font-size: 12pt; font-family: TimesNewRomanPSMT;">5.2.9 In the value fields for the keywords ORIGINATOR, MESSAGE_ID, OBJECT_DESIGNATOR, CATALOG_NAME and INTERNATIONAL_DESIGNATOR, values shall be given as alphanumeric text. The underscore "_"
and dash "-" may also be used. </span></p>
</blockquote>
</div>
</div>
</div>
</span></li><li><font face="TimesNewRomanPSMT" color="#ff0000"><span style="font-size: 16px;"><b>5.2.10 The value fields for ORIGINATOR are found in the CCSDS Organization registry (SANA reference), the CATALOG_NAME is in the CDN Catalog registry (SANA reference), the
OBJECT_Designator will be found in the related Catalog</b></span></font></li><li style="font-family: Calibri; font-size: medium; color: rgb(0, 0, 0);"><span style="font-size: 16px;">The SANA Consideratins Section says this:</span></li><li style="font-family: Calibri; font-size: medium; color: rgb(0, 0, 0);"><span style="font-family: TimesNewRomanPSMT; font-size: 16px;">The CDM XML schema;<br>
A transform from the CDM XML to the CDM KVN version;</span></li></ul>
<blockquote style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div><font face="TimesNewRomanPSMT" color="#ff0000"><span style="font-size: 16px;"><b>Values for the keyword ORIGINATOR must be a valid CCSDS Organization name</b></span></font></div>
<div style="font-family: Calibri, sans-serif; font-size: 14px;"><span style="font-family: TimesNewRomanPSMT; font-size: 16px;"><b><font color="#ff0000">Every CDM ORIGINATOR shall be registered in the CCSDS Organization Registry with the Org Role of CDM Provider</font></b></span></div>
<div style="font-family: Calibri, sans-serif; font-size: 14px;"><span style="font-family: TimesNewRomanPSMT; font-size: 16px;"><b><font color="#ff0000">The CATALOG_NAME shall be registered in a CDM Catalog Name registry, which contains Catalog Identifier (current
Keyword), Catalog Name (current Meaning), Organization Reference (to registered Org), and URL. Field sizes and types should be defined (they are not now).</font></b><br>
A list of options for the COLLISION_PROBABILITY_METHOD keyword. </span></div>
</blockquote>
</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;">
So yes, there are a few lines of changes to the doc and to the registries. This was discussed, in broad strokes, with the Nav WG chair, David Berry, and he agreed, at least conceptually, that being able to reference an esixting org structure would have been
useful to them. The full impact of each of these proposed changes would need to be discussed with the Nav WG. </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;">
What they do is to not change any of the data structures, but to add some specificity and to remove ambiguity. Surely that cannot be a problem when what one is trying to do is to avoid two spacecraft colliding.</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;">
Best regards, 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>
<span id="OLK_SRC_BODY_SECTION" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<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><<a href="mailto:cesg-bounces@mailman.ccsds.org">cesg-bounces@mailman.ccsds.org</a>> on behalf of Erik Barkley <<a href="mailto:Erik.J.Barkley@jpl.nasa.gov">Erik.J.Barkley@jpl.nasa.gov</a>><br>
<span style="font-weight:bold">Date: </span>Monday, July 13, 2015 at 10:13 AM<br>
<span style="font-weight:bold">To: </span>CCSDS Engineering Steering Group - CESG Exec <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>><br>
<span style="font-weight:bold">Subject: </span>[CESG] Very quick follow up re registry updates policy implications<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 xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">CESG Colleagues,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As we ran out of time, an example of new registry policy relative to CDM (Conjunction data message):<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Currently: recommendation creates a registry of conjunction data message providers.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Future: recommendation will leverage agency registry to provide an enumeration value for a service provider attribute to identify conjunction data message providers. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The main implication is that future recommendation book bosses will need to be more aware of the information model in SANA. The main goal is to ensure we are not creating overlapping (and potentially conflicting and/or incoherent) sets
of registries.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">-Erik<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>