<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Georgia",serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Colin,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">I think it is a step in the right direction but I’m still not quite convinced – I realize this comes down to personal preference. So, to close out my action from
yesterday, here is what a proposed list of abbreviations with some selected examples might look like. For contrast I have put both the “Erik Approach” and “Colin Approach” names in the table. To me the abbreviation with the full sub-schema name is a bit easier
to read. I do think this is converging. In any case, I’d like to see if anyone in the WG ventures an opinion on this.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">I tend to agree with Hugh that SimSchd might be confused for simulated schedule. The table is immediately below. In case it does not render well an excel file with
the table is also attached. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">CSSM Colleagues,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Can you take a look and register a preference if you have one?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">-Erik
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><img width="1755" height="719" style="width:18.2812in;height:7.4895in" id="Picture_x0020_1" src="cid:image001.png@01D5B04C.FB977D70"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> SMWG <smwg-bounces@mailman.ccsds.org>
<b>On Behalf Of </b>Hugh Kelliher<br>
<b>Sent:</b> Wednesday, December 11, 2019 12:20<br>
<b>To:</b> Colin.Haddow@esa.int; smwg@mailman.ccsds.org<br>
<b>Subject:</b> [EXTERNAL] Re: [cssm] Proposal for updates Schema naming convention<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Hi Colin,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">It looks fine to me overall. I only have one small question, do you think something like SmplSched might avoid future possible misinterpretation
of SimSchdl as simulated schedule? Probably not an issue but just a thought.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Cheers,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Hugh<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> SMWG [<a href="mailto:smwg-bounces@mailman.ccsds.org">mailto:smwg-bounces@mailman.ccsds.org</a>]
<b>On Behalf Of </b><a href="mailto:Colin.Haddow@esa.int">Colin.Haddow@esa.int</a><br>
<b>Sent:</b> 11 December 2019 10:53<br>
<b>To:</b> <a href="mailto:smwg@mailman.ccsds.org">smwg@mailman.ccsds.org</a><br>
<b>Subject:</b> [cssm] Proposal for updates Schema naming convention<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">Dear all,</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif"> as a result of the telecon yesterday (10th Dec), I've had a think about the schema naming convention and have come up with the following proposal.
</span><span lang="EN-GB"><br>
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">Below is the suggested abbreviation for the Book Titles to be used in the schema names;</span><span lang="EN-GB">
<br>
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x01 Simple Schedule - SimSchd</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x02 Comunications Planning Information Formats - ComsPlnInfo
</span><span lang="EN-GB"><br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x04 Service Package Data Formats - SrvPkg</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x05 Service Agreement and Configuration Profile Data Formats - SrvAgrConfPrfl</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x06 Space Link Event Sequence Data Format - EvntSeq</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x07 Service Catalog - SrvCat</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x08 Service Accounting - SrvAcnt</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x09 Service Management Utilization Request Formats - Smurf</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x10 Management Services - MgtSrv</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x11 Best Practises BstPrac (although I don't think we'll need it wrt a schema...)</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x12 Cross Support Service Managment - Common Data Entities - SmCmnEnt</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x13 Abstract Event Definition - AbsEvnt</span><span lang="EN-GB">
<br>
<br>
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">Based on the use of these abbreviations the existing schema names would become</span><span lang="EN-GB">
<br>
<br>
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">Book 902x01</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x01b1p1-SchemaCssmSimpleSchedule.xsd -> 902x01b1p1-SimSchd.xsd</span><span lang="EN-GB">
<br>
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">Book 902x02</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x02r1-SchemaCssmPlanningInformationFormats.xsd -> 902x02r1-ComsPlnInfo.xsd</span><span lang="EN-GB">
<br>
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">Book 902x04</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x04w0_00-SchemaCssmServicePackageDataFormats.xsd -> 902x04w0_00-SrvPkg.xsd</span><span lang="EN-GB">
<br>
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">Book 902x05</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x05w0_00-SchemaCssmServiceAgreementAndConfigurationProfileDataFormats.xsd -> 902x05w0_00-SrvAgrConfPrfl.xsd</span><span lang="EN-GB">
<br>
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">Book 902x06</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x06w0_00-SchemaCssmSpaceLinkEventSequenceDataFormat.xsd -> 902x06w0_00-EvntSeqt.xsd</span><span lang="EN-GB">
<br>
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">Book 902x09</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x09w0_09.02-SchemaCssmServiceManagementUtilizationRequestFormats.xsd -> 902x09w0_09.02-Smurf.xsd</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x09w0_09.02-SchemaCssmServiceManagementUtilizationRequestFormats-BasicConstraints.xsd -> 902x09w0_09.02-Smurf-BasicCons.xsd</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x09w0_09.02-SchemaCssmServiceManagementUtilizationRequestFormats-EnhancedConstraints.xsd -> 902x09w0_09.02-Smurf-EnhancedCons.xsd</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x09w0_09.02-SchemaCssmServiceManagementUtilizationRequestFormats-TrajectoryData.xsd -> 902x09w0_09.02-Smurf-TrajData.xsd</span><span lang="EN-GB">
<br>
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">Book 902x12</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x12m1-SchemaCssmSmAbstractEvent.xsd -> 902x12m1-SmCmnEnt-AbsEvnt.xsd<br>
902x12m1-SchemaCssmSmCommonClasses.xsd -> 902x12m1-SmCmnEnt-CmnClss.xsd</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x12m1-SchemaCssmSmInfoEntityHeader.xsd -> 902x12m1-SmCmnEnt-InfEntHdr.xsd</span><span lang="EN-GB">
<br>
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">Book 902x13</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x13m1-SchemaAbstractEvent.xsd -> 902x13m1-AbsEvnt.xsd</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x13m1-SchemaAbstractParameter.xsd -> 902x13m1-AbsEvnt-AbsParm.xsd</span><span lang="EN-GB">
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">902x13m1-SchemaCcsdsTimecodes.xsd -> 902x13m1-AbsEvnt-TimCde.xsd</span><span lang="EN-GB">
<br>
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">To me this appesr to satisfy the desire to shorten the names without resorting to the use of TLAs or XTLAs.</span><span lang="EN-GB">
<br>
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">If this is acceptable I would also apply it to the names of the UML model files.</span><span lang="EN-GB">
<br>
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">Cheers for now,</span><span lang="EN-GB">
<br>
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">Colin<br>
<br>
---------------------------------------------------------------------------------------------------------<br>
Dr. Colin R. Haddow,<br>
HSO-GI, European Space Agency,<br>
European Space Operations Centre,<br>
Robert-Bosch-Str 5,<br>
64293 Darmstadt,<br>
Germany.<br>
<br>
Phone; +49 6151 90 2896<br>
Fax; +49 6151 90 3010<br>
E-Mail; <a href="mailto:colin.haddow@esa.int">colin.haddow@esa.int</a><br>
---------------------------------------------------------------------------------------------------------</span><span lang="EN-GB"><o:p></o:p></span></p>
<pre><span lang="EN-GB">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></span></pre>
<pre><span lang="EN-GB">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></span></pre>
<pre><span lang="EN-GB">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></span></pre>
<pre><span lang="EN-GB">personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (<a href="mailto:dpo@esa.int">dpo@esa.int</a>).<o:p></o:p></span></pre>
</div>
</body>
</html>