<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</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>Hi Erik, et al,</div>
<div><br>
</div>
<div>Attached please find your text with some mark-ups. See also the attached diagrams showing the proposed structures for organization, person, OID, spacecraft, and Site & Ground Station registries.</div>
<div><br>
</div>
<div>The biggest question for me in looking over your stuff is whether you want to persist in using names (even formal & registered ones) for sites, assets, and spacecraft, or whether you are willing to shift to using OIDs as unambiguous references? If we
do as proposed (and following your lead) adopt OIDs for every major org, person, site, service element, and antenna, then I wonder if you really want to continue using names? I get that names are human readable, but they are nowhere near as convenient, and
unambigous, as an OID. Is it NASA / JPL or just JPL, or maybe JPL – CIT? </div>
<div><br>
</div>
<div>Or maybe you want both, names for convenience and OIDs to remove any possible ambiguity?</div>
<div><br>
</div>
<div>I am attaching the Site / GS and OID models here. I'll send the whole wad of DRAFT models, with explanation, in a separate note. These are evolving and are not yet fixed. If you guys have changes or comments (like "THAT won't work") please let me know.
I'm also atached a "SCID registry relationships" model that tries to say how these various registries are connected. It's not really correct (yet), but it should give you and idea of what I had in mind. There would be, of course, a similar "Site and GS
relationships" model, maybe I'll sketch that next.</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>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, June 22, 2015 at 11:44 AM<br>
<span style="font-weight:bold">To: </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">Cc: </span>SMWG <<a href="mailto:smwg@mailman.ccsds.org">smwg@mailman.ccsds.org</a>>, Marc Blanchet <<a href="mailto:marc.blanchet@viagenie.ca">marc.blanchet@viagenie.ca</a>><br>
<span style="font-weight:bold">Subject: </span>Input from SE Area requested: Proposed updates to SoS SANA Registry section<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">Peter,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Attached please find the SANA registries considerations section extracted from the current scheduling of services blue book candidate with the proposed modifications that I believe are consistent with the newly emerging SANA registry policy.
Colin and I had a teleconference this morning and I believe the changes indicated in the attached represent our consensus as to how to proceed with the registry updates. Track changes has been turned on so you can see what the differences are. Please note
that there are eight editorial notes listed in bracketed italic font which indicate various implications as a result of having updated the verbiage to match the emerging policy. Your comments with regard to those notes that have an effect on registry definitions
or merit consideration from overall registry management will be much appreciated at your earliest convenience.
<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">-Erik<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>