<span style=" font-size:10pt;font-family:sans-serif">Dear all,</span>
<br><span style=" font-size:10pt;font-family: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:10pt;font-family: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:10pt;font-family:sans-serif">902x01
Simple Schedule -
SimSchd</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x02
Comunications Planning Information Formats
-
ComsPlnInfo </span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x04
Service Package Data Formats -
SrvPkg</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x05
Service Agreement and Configuration Profile
Data Formats - SrvAgrConfPrfl</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x06
Space Link Event Sequence Data Format -
EvntSeq</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x07
Service Catalog -
SrvCat</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x08
Service Accounting -
SrvAcnt</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x09
Service Management Utilization Request Formats
- Smurf</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x10
Management Services -
MgtSrv</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x11
Best Practises
BstPrac
(although I don't think we'll need it wrt a schema...)</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x12
Cross Support Service Managment - Common Data
Entities - SmCmnEnt</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x13
Abstract Event Definition -
AbsEvnt</span>
<br>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Based on the use
of these abbreviations the existing schema names would become</span>
<br>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Book 902x01</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x01b1p1-SchemaCssmSimpleSchedule.xsd
-> 902x01b1p1-SimSchd.xsd</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Book 902x02</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x02r1-SchemaCssmPlanningInformationFormats.xsd
->
902x02r1-ComsPlnInfo.xsd</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Book 902x04</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x04w0_00-SchemaCssmServicePackageDataFormats.xsd
-> 902x04w0_00-SrvPkg.xsd</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Book 902x05</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x05w0_00-SchemaCssmServiceAgreementAndConfigurationProfileDataFormats.xsd
->
902x05w0_00-SrvAgrConfPrfl.xsd</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Book 902x06</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x06w0_00-SchemaCssmSpaceLinkEventSequenceDataFormat.xsd
->
902x06w0_00-EvntSeqt.xsd</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Book 902x09</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x09w0_09.02-SchemaCssmServiceManagementUtilizationRequestFormats.xsd
->
902x09w0_09.02-Smurf.xsd</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x09w0_09.02-SchemaCssmServiceManagementUtilizationRequestFormats-BasicConstraints.xsd
->
902x09w0_09.02-Smurf-BasicCons.xsd</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x09w0_09.02-SchemaCssmServiceManagementUtilizationRequestFormats-EnhancedConstraints.xsd
->
902x09w0_09.02-Smurf-EnhancedCons.xsd</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x09w0_09.02-SchemaCssmServiceManagementUtilizationRequestFormats-TrajectoryData.xsd
->
902x09w0_09.02-Smurf-TrajData.xsd</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Book 902x12</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x12m1-SchemaCssmSmAbstractEvent.xsd
-> 902x12m1-SmCmnEnt-AbsEvnt.xsd<br>
902x12m1-SchemaCssmSmCommonClasses.xsd
-> 902x12m1-SmCmnEnt-CmnClss.xsd</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x12m1-SchemaCssmSmInfoEntityHeader.xsd
->
902x12m1-SmCmnEnt-InfEntHdr.xsd</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Book 902x13</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x13m1-SchemaAbstractEvent.xsd
->
902x13m1-AbsEvnt.xsd</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x13m1-SchemaAbstractParameter.xsd
-> 902x13m1-AbsEvnt-AbsParm.xsd</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x13m1-SchemaCcsdsTimecodes.xsd
-> 902x13m1-AbsEvnt-TimCde.xsd</span>
<br>
<br><span style=" font-size:10pt;font-family: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:10pt;font-family: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:10pt;font-family:sans-serif">Cheers for now,</span>
<br>
<br><span style=" font-size:10pt;font-family: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>
---------------------------------------------------------------------------------------------------------<br>
</span><PRE>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
</PRE>