<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: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 12 (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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
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:0cm;
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;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Colin,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span 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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Cheers,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hugh<o:p></o:p></span></p><p class=MsoNormal><span 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 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> SMWG [mailto:smwg-bounces@mailman.ccsds.org] <b>On Behalf Of </b>Colin.Haddow@esa.int<br><b>Sent:</b> 11 December 2019 10:53<br><b>To:</b> smwg@mailman.ccsds.org<br><b>Subject:</b> [cssm] Proposal for updates Schema naming convention<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Dear all,</span> <br><span 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><br><br><span 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> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>902x01 Simple Schedule - SimSchd</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>902x02 Comunications Planning Information Formats - ComsPlnInfo </span><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>902x04 Service Package Data Formats - SrvPkg</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>902x05 Service Agreement and Configuration Profile Data Formats - SrvAgrConfPrfl</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>902x06 Space Link Event Sequence Data Format - EvntSeq</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>902x07 Service Catalog - SrvCat</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>902x08 Service Accounting - SrvAcnt</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>902x09 Service Management Utilization Request Formats - Smurf</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>902x10 Management Services - MgtSrv</span> <br><span 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> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>902x12 Cross Support Service Managment - Common Data Entities - SmCmnEnt</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>902x13 Abstract Event Definition - AbsEvnt</span> <br><br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Based on the use of these abbreviations the existing schema names would become</span> <br><br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Book 902x01</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>902x01b1p1-SchemaCssmSimpleSchedule.xsd -> 902x01b1p1-SimSchd.xsd</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Book 902x02</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>902x02r1-SchemaCssmPlanningInformationFormats.xsd -> 902x02r1-ComsPlnInfo.xsd</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Book 902x04</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>902x04w0_00-SchemaCssmServicePackageDataFormats.xsd -> 902x04w0_00-SrvPkg.xsd</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Book 902x05</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>902x05w0_00-SchemaCssmServiceAgreementAndConfigurationProfileDataFormats.xsd -> 902x05w0_00-SrvAgrConfPrfl.xsd</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Book 902x06</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>902x06w0_00-SchemaCssmSpaceLinkEventSequenceDataFormat.xsd -> 902x06w0_00-EvntSeqt.xsd</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Book 902x09</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>902x09w0_09.02-SchemaCssmServiceManagementUtilizationRequestFormats.xsd -> 902x09w0_09.02-Smurf.xsd</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>902x09w0_09.02-SchemaCssmServiceManagementUtilizationRequestFormats-BasicConstraints.xsd -> 902x09w0_09.02-Smurf-BasicCons.xsd</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>902x09w0_09.02-SchemaCssmServiceManagementUtilizationRequestFormats-EnhancedConstraints.xsd -> 902x09w0_09.02-Smurf-EnhancedCons.xsd</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>902x09w0_09.02-SchemaCssmServiceManagementUtilizationRequestFormats-TrajectoryData.xsd -> 902x09w0_09.02-Smurf-TrajData.xsd</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Book 902x12</span> <br><span 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> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>902x12m1-SchemaCssmSmInfoEntityHeader.xsd -> 902x12m1-SmCmnEnt-InfEntHdr.xsd</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Book 902x13</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>902x13m1-SchemaAbstractEvent.xsd -> 902x13m1-AbsEvnt.xsd</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>902x13m1-SchemaAbstractParameter.xsd -> 902x13m1-AbsEvnt-AbsParm.xsd</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>902x13m1-SchemaCcsdsTimecodes.xsd -> 902x13m1-AbsEvnt-TimCde.xsd</span> <br><br><span 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> <br><br><span 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> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Cheers for now,</span> <br><br><span 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; colin.haddow@esa.int<br>---------------------------------------------------------------------------------------------------------</span><o:p></o:p></p><pre>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre><pre>protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre><pre>this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre><pre>personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).<o:p></o:p></pre></div></body></html>