<span style=" font-size:10pt;font-family:sans-serif">Dear all,</span>
<br><span style=" font-size:10pt;font-family:sans-serif">
those of you who were in
Berlin will recall there was discussion about naming conventions for various
items (files, attributes, etc.). I've just uploaded updated schemas and
UML models into SANA which reflect these changes and also include the other
updates that were discussed in Berlin. For the Schema naming I've adopted
the following convention;</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Directory structure</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">902 Schema
All service
management books are in the 902 series (except for TGFT)</span>
<br><span style=" font-size:10pt;font-family:sans-serif">
902x01
Schema files for Simple Schedule</span>
<br><span style=" font-size:10pt;font-family:sans-serif">
902x02
Schema files for Planning Information Formats</span>
<br><span style=" font-size:10pt;font-family:sans-serif">
902x03
Currently unassigned</span>
<br><span style=" font-size:10pt;font-family:sans-serif">
902x04
Schema files for Service Package Data Formats</span>
<br><span style=" font-size:10pt;font-family:sans-serif">
902x05
Schema files for Service Agreement and Configuration
Profile Data Formats</span>
<br><span style=" font-size:10pt;font-family:sans-serif">
902x06
Schema files for Space Link Event Sequence
Data Format</span>
<br><span style=" font-size:10pt;font-family:sans-serif">
902x07
Schema files for Service Catalog</span>
<br><span style=" font-size:10pt;font-family:sans-serif">
902x08
Schema files for Service Accounting</span>
<br><span style=" font-size:10pt;font-family:sans-serif">
902x09
Schema files for Service Management Utilization
Request Formats</span>
<br><span style=" font-size:10pt;font-family:sans-serif">
902x10
Schema files for Management Services</span>
<br><span style=" font-size:10pt;font-family:sans-serif">
902x11
Schema files for Best Practices</span>
<br><span style=" font-size:10pt;font-family:sans-serif">
902x12
Schema files for Service Management Common
Data Entities</span>
<br><span style=" font-size:10pt;font-family:sans-serif">
902x13
Schema files for Abstract Event Definition
</span>
<br><span style=" font-size:10pt;font-family:sans-serif"><br>
</span>
<br><span style=" font-size:10pt;font-family:sans-serif">For the naming
convention of the schema files themselves I've adopted the following</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">902xNNcM[_OO][pP]-SchemaNameInCamelCase.xsd
where</span>
<br>
<ul>
<li><span style=" font-size:10pt;font-family:sans-serif">NN is the book
number in the 902 series. Note that this is 2 digits with a leading "0"
if required.</span>
<li><span style=" font-size:10pt;font-family:sans-serif">c is the colour
of the book, i.e.</span>
<ul>
<li><span style=" font-size:10pt;font-family:sans-serif">w for White</span>
<li><span style=" font-size:10pt;font-family:sans-serif">r for Red</span>
<li><span style=" font-size:10pt;font-family:sans-serif">m for Magenta</span>
<li><span style=" font-size:10pt;font-family:sans-serif">b for Blue</span></ul>
<li><span style=" font-size:10pt;font-family:sans-serif">M is the issue
of the book</span>
<li><span style=" font-size:10pt;font-family:sans-serif">[_OO] is an optional
minor version prefixed with an underscore, only applies to white and red
drafts. Note again this is 2 digits with a leading "0" if required.</span>
<li><span style=" font-size:10pt;font-family:sans-serif">[pP] is used if
the schema has been updated because of a pink sheet, only applies to blue
and magenta.</span>
<ul>
<li><span style=" font-size:10pt;font-family:sans-serif">p indicates it
is an update due to a pink sheet</span>
<li><span style=" font-size:10pt;font-family:sans-serif">P is the number
of the pink sheet</span></ul>
<li><span style=" font-size:10pt;font-family:sans-serif">A minus sign "-"
is used to seprate the identifer part from the alphabetic part of the name.</span>
<li><span style=" font-size:10pt;font-family:sans-serif">"Schema"
is always the first part of the name</span>
<li><span style=" font-size:10pt;font-family:sans-serif">The alphabetic
part of the name is written in camel case.</span>
<li><span style=" font-size:10pt;font-family:sans-serif">There is no white
space in the file name (This is because when including the schema name
in an xml file using the </span><span style=" font-size:10pt;color:#800080;font-family:Consolas">xsi:schemaLocation</span><span style=" font-size:10pt;font-family:sans-serif">
attribute white space in the file name caused problems. (I haven't been
able to find a way around this but if anybody knows one please let me know.)</span>
<li>
<li></ul><span style=" font-size:10pt;font-family:sans-serif">This results
in names as shown below;</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">902x01b1p1-SchemaCssmSimpleSchedule.xsd
This
is Blue Book Version 1 of the Simple Schedule, updated with Pink Sheet
1 (which does not exist - yet...)</span>
<br><span style=" font-size:10pt;font-family:sans-serif">902x02w0_20-SchemaCssmPlanningInformationFormats.xsd
This
is White Book Draft 0.20 of the Planning Information Formats.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">For the UML Model
I've adopted a similiar approach to the directory and naming conventions
(obviously without the use of "Schema" in the file names)</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">The zip files
containg the schemas and UML models can be found at the URLs below. Note
that in these I've included a slightly modified version of the Simple Schedule
schema and UML model that fits in with the directory and file naming conventions
outlined above. This is labeled as 902x01b1p1-...</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Schema zip file:
</span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Schemas/902%20Schema%2020181102.zip"><span style=" font-size:10pt;color:blue;font-family:sans-serif">https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Schemas/902%20Schema%2020181102.zip</span></a>
<br><span style=" font-size:10pt;font-family:sans-serif">UML model zip
file: </span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/UML%20Model/902%20UML%20Model%2020181102.zip"><span style=" font-size:10pt;color:blue;font-family:sans-serif">https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/UML%20Model/902%20UML%20Model%2020181102.zip</span></a>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">We can discuss
any comments/critiscims about this appraoch at the next WebEx.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">The ".project"
files in the schema sub-directories are Eclipse project files. I use Eclipse
for editing and validating the schema files.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">One final thing
to point out is that those of you who look at the SMURF schema will notice
that it has the following include statements</span>
<br>
<br><span style=" font-size:10pt;font-family:Consolas">
</span><span style=" font-size:10pt;color:#008080;font-family:Consolas"><</span><span style=" font-size:10pt;color:#3f8080;font-family:Consolas">xsd:include</span><span style=" font-size:10pt;font-family:Consolas">
</span><span style=" font-size:10pt;color:#800080;font-family:Consolas">schemaLocation</span><span style=" font-size:10pt;font-family:Consolas">=</span><span style=" font-size:10pt;color:#4200ff;font-family:Consolas"><i>"../902x06/902x06w0_00-SchemaCssmSpaceLinkEventSequenceDataFormat.xsd"</i></span><span style=" font-size:10pt;color:#008080;font-family:Consolas">/></span>
<br><span style=" font-size:10pt;font-family:Consolas">
</span><span style=" font-size:10pt;color:#008080;font-family:Consolas"><</span><span style=" font-size:10pt;color:#3f8080;font-family:Consolas">xsd:include</span><span style=" font-size:10pt;font-family:Consolas">
</span><span style=" font-size:10pt;color:#800080;font-family:Consolas">schemaLocation</span><span style=" font-size:10pt;font-family:Consolas">=</span><span style=" font-size:10pt;color:#4200ff;font-family:Consolas"><i>"../902x05/902x05w0_00-SchemaCssmServiceAgreementAndConfigurationProfileDataFormats.xsd"</i></span><span style=" font-size:10pt;color:#008080;font-family:Consolas">/></span>
<br><span style=" font-size:10pt;font-family:Consolas">
</span><span style=" font-size:10pt;color:#008080;font-family:Consolas"><</span><span style=" font-size:10pt;color:#3f8080;font-family:Consolas">xsd:include</span><span style=" font-size:10pt;font-family:Consolas">
</span><span style=" font-size:10pt;color:#800080;font-family:Consolas">schemaLocation</span><span style=" font-size:10pt;font-family:Consolas">=</span><span style=" font-size:10pt;color:#4200ff;font-family:Consolas"><i>"../902x04/902x04w0_00-SchemaCssmServicePackageDataFormats.xsd"</i></span><span style=" font-size:10pt;color:#008080;font-family:Consolas">/></span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">i.e. it has dependencies
on the Schema files for Service Package Data Formats, Service Agreement
and Configuration Profile Data Formats and Space Link Event Sequence Data
Format. This is because the SMURF is required to be able to submit complete
Service Packages, Configuration Profiles and Event Seqeunces. In view of
this I suggest that we leave these dependencies rather than making them
common data structures beacuase if we make them common data structures
the common data structures book will efectivly need to contain be the Service
Package Data Formats, Service Agreement and Configuration Profile Data
Formats and Space Link Event Sequence Data Format Books. Not a good idea...</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">You will note
that I've made some assumptions about what these 3 schemas will be called,
if the Book Captains for these books would prefer the main schema name
to be changed please let me know and I'll update things accordingly...</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</span>
<br><span style=" font-size:10pt;font-family:sans-serif"><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>