<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 14 (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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
.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]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoPlainText">Hello, Colin. I've looked through the two RIDs that you forwarded, and here are my responses.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">The first of the two RIDs (CSSM-056) recommends that "schedulePackageID" be changed to "schedulePackageId". I agree with the reviewer that this follows the camelCase convention that we have used elsewhere in the document.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">The second RID (CSSM-058) recommends that a version "specification" be added to the schema, " such that any validating parser can check if the version of the XML instance is compliant with the version of the schema". The WG accepted
the recommendation and I concur. Here are my thoughts and plans for how to do so. I welcome any comments.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">There are two levels at which the version of the schema can be validated. At the top level, namespaces are used to demarcate the version at the level of the Issue of the Recommended Standard, with each Issue getting its own namespace.
An instance document generated from schema registered under one namespace cannot be validated under a different namespace. E.g., if Mission X generates a Simple Schedules using a (future) Issue-2 schema and attempts to submit it to a PCSSS that still only
support the Issue-1 version, it will of course fail validation. Different namespaces are required because multiple versions of the schema must be supported concurrently (at least for some period) owing to legacy support considerations and differing rates of
standards adoption and maintenance.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">The second level of versioning occurs where the schema maintenance produces intermediate corrected versions for the same Issue of the Recommended Standard, e.g., because the original version of the schema inadvertently omitted a required
enumeration value. This does not result in a new namespace but a replacement of the schemas within the existing namespace*. Technically, only one set of schemas is valid for each namespace at any given time, but schema maintenance for the various implementation
of those schemas will almost certainly take place at different rates. At some point it is likely that some creator/consumer pair will be using different iterations of the "Issue X" schema (and therefore using the same Issue-X namespace), with both sides believing
their version to be current and correct. To flag this level of versioning I will add a
<span style="font-family:"Courier New"">schemaVersion</span> attribute to the <span style="font-family:"Courier New"">
SimpleSchedule</span> type. The <span style="font-family:"Courier New"">schemaVersion</span> attribute will be of type xsd:string with the syntax ‘X.Y.Z’, where “X” is the Blue Book Issue number, “Y” represents a Technical Corrigendum number (if any – it is
zero otherwise), and “Z” represents the iteration of the current schema. Technically, the “X” component is unnecessary since that information is captured in the namespace itself, but I think it is nice to have the complete provenance of the version in one
place. The “Y” component is there to record the fact that the schema reflects changes (if any) caused by a Technical Corrigendum, since a TC does not change the Issue number itself. For purposes of versioning uniqueness and validity are concerned, I propose
that only the version of the schema that includes all approved TCs is valid – i.e., there is still only one formally valid schema for each issue.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> [NOTE – The extended (post-Blue-publication) NASA/JAXA interoperability tests unveiled some typos in element names that were subsequently corrected in the Blue-1 schema and therefore resulted in a new version number. We subsequently
agreed that schemas that otherwise accurately represent the data structures of the Recommended Standard should not be changed just to correct typos, because the resulting effort to update otherwise-good schemas in operational systems would generally outweigh
the benefit of correcting a few tags in the instance documents. New intermediate versions should be created only when the existing schema is found to incorrectly or incompletely represent the functionality of the Recommended Standard.]<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Best regards,<o:p></o:p></p>
<p class="MsoPlainText">John <o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">-----Original Message-----<br>
From: Colin.Haddow@esa.int [mailto:Colin.Haddow@esa.int] <br>
Sent: Monday, November 17, 2014 12:53 PM<br>
To: John Pietras<br>
Subject: RIDs for the SchemaMaster</p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Hi John,<o:p></o:p></p>
<p class="MsoPlainText"> hope you had a good trip home. As you may remember there were a couple of RIDs on the Simple Schedule book flagged for the attention of the SchemaMaster. I've attached these below for your comments.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Cheers for now,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Colin<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">(See attached file: RIDs for SchemaMaster.docx)<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">---------------------------------------------------------------------------------------------------------<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Dr. Colin R. Haddow,<o:p></o:p></p>
<p class="MsoPlainText">HSO-GI, European Space Agency,<o:p></o:p></p>
<p class="MsoPlainText">European Space Operations Centre,<o:p></o:p></p>
<p class="MsoPlainText">Robert-Bosch-Str 5,<o:p></o:p></p>
<p class="MsoPlainText">64293 Darmstadt,<o:p></o:p></p>
<p class="MsoPlainText">Germany.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Phone; +49 6151 90 2896<o:p></o:p></p>
<p class="MsoPlainText">Fax; +49 6151 90 3010<o:p></o:p></p>
<p class="MsoPlainText">E-Mail; <a href="mailto:colin.haddow@esa.int"><span style="color:windowtext;text-decoration:none">colin.haddow@esa.int</span></a><o:p></o:p></p>
<p class="MsoPlainText">---------------------------------------------------------------------------------------------------------<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></p>
<p class="MsoPlainText">The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted.<o:p></o:p></p>
<p class="MsoPlainText">If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></p>
<p class="MsoPlainText">Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Please consider the environment before printing this email.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
</div>
</body>
</html>