<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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.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="MsoNormal">Colin,<o:p></o:p></p>
<p class="MsoNormal">Thanks for forwarding the 3 schema-related RIDs. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">RID CSSM-047 asked that the parameters in the schemas follow the same order as those in the UML diagrams and tables, and this I had actually already done in the process of making the other changes to the schemas.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">RIDCSSM-059 asked that real time values be used in the example XML document, and this I have just completed.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Which leaves RID CSSM-058, which states “<b><span style="font-size:10.0pt;font-family:"Courier New";mso-fareast-language:EN-GB">It is proposed to use a version specification of the XML schema, such that any validating parser can check if
the version of the XML instance is compliant with the version of the schema.<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Courier New";mso-fareast-language:EN-GB">It would make it easier if evolving schema versions were to occur to check the validity of an XML instance against a specific schema (version)</span></b><span style="mso-fareast-language:EN-GB">”,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-GB">for which you provided the Disposition</span><span style="font-family:"Courier New";mso-fareast-language:EN-GB"> “</span><b><span style="font-size:10.0pt;font-family:"Courier New";mso-fareast-language:EN-GB">Accepted:
pending further discussion with schemaMaster (JVP</span></b><b><span style="font-family:"Courier New";mso-fareast-language:EN-GB">)</span></b><b><span style="mso-fareast-language:EN-GB">”.<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="mso-fareast-language:EN-GB"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-GB">My reaction is that by using versioned name spaces, we are satisfying the RID. Since the version number of the namespace appears in both the schema itself and any instance document that is to be
validated against that schema, any attempt to validate an instance document against a different version (i.e., a different version of the name space) will result in a validation failure.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-GB">Unless you are any other member of the CSSMWG can think of a form of versioning that would be useful but requires some other mechanism (e.g., a dedicated ‘schemaVersion’ parameter), I propose that
what we now have is sufficient.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New";mso-fareast-language:EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal">John <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>