<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Consolas, monospace" size="2">
<div>Thanks Jirka,</div>
<div> </div>
<div>So it sounds like this is the proposed text ( italics indicate Jirka's proposed changes ):</div>
<div> </div>
<div style="margin-bottom: 10pt; "><font face="Calibri, sans-serif" size="3"><b>Editor’s Response:</b></font></div>
<div style="margin-bottom: 10pt; "><font face="Calibri, sans-serif" size="2">The informative Annex F for Part 1 currently demonstrates how to extract the custom XML from a document. To address this concern, the following text will be appended to that Annex:</font></div>
<div style="margin-bottom: 10pt; "><font face="Calibri, sans-serif" size="2" color="#4F81BD"><u><i>Once this custom markup is extracted, the resulting XML document can be validated separately from the WordprocessingML document.</i></u></font></div>
<div style="margin-bottom: 10pt; "><font face="Calibri, sans-serif" size="2" color="#4F81BD"><u>For example, the custom XML for the example on pp. 530, once extracted, would be:</u></font></div>
<div style="margin-bottom: 10pt; padding-left: 36pt; "><font size="2" color="#4F81BD"><u><invoice xmlns="</u><a href="http://www.example.com/2006/invoice"><u>http://www.example.com/2006/invoice</u></a><u>"></u></font></div>
<div style="margin-bottom: 10pt; padding-left: 36pt; "><font size="2" color="#4F81BD"><u> <customerName>Tristan Davis</customerName></u></font></div>
<div style="margin-bottom: 10pt; padding-left: 36pt; "><font size="2" color="#4F81BD"><u></invoice></u></font></div>
<div style="margin-bottom: 10pt; "><font face="Calibri, sans-serif" size="2" color="#4F81BD"><u>An application can employ any desired method to find the appropriate schema(s) for validation. As an example, one such approach using information defined by this
Standard might be:</u></font></div>
<ul style="margin-top: 0pt; margin-bottom: 0pt; margin-left: 36pt; ">
<font face="Calibri, sans-serif" size="2" color="#4F81BD">
<li style="margin-bottom: 10pt; "><u>Locate the </u><font face="Cambria, serif"><u>schema</u></font><u> element (section 23.2.1) in the Document Settings part whose </u><font face="Cambria, serif"><u>uri</u></font><u> attribute </u><u><i>matches the namespace
of root element in the XML document extracted from custom XML markup</i></u></li><li style="margin-bottom: 10pt; "><u>If that element also specifies a </u><font face="Cambria, serif"><u>schemaLocation</u></font><u> attribute, the resulting path is used to locate the schema used for validation.</u></li><li style="margin-bottom: 10pt; "><u>Once this schema is located, validation should be triggered based on the value of doNotValidateAgainstSchema (section 17.15.1.43).</u></li></font>
</ul>
<div>Regarding the XSLT, Jirka, is that something you could help fix?</div>
<div> </div>
<div>Thanks,</div>
<div> </div>
<div>shawn</div>
<div> </div>
<div> </div>
<div>-----Original Message-----<br>
From: Jirka Kosek [<a href="mailto:jirka@kosek.cz">mailto:jirka@kosek.cz</a>] <br>
Sent: Wednesday, April 22, 2009 1:04 PM<br>
To: Shawn Villaron<br>
Cc: 'e-SC34-WG4@ecma-international.org'<br>
Subject: Re: DR-09-0029: WML, Custom XML and Smart Tags: Specification for Validation Lacking</div>
<div> </div>
<div>Shawn Villaron wrote:</div>
<div> </div>
<div>> The informative Annex F for Part 1 currently demonstrates how to extract the custom XML from a document. To address this concern, the following text will be appended to that Annex:</div>
<div>> Once this information is extracted, the resulting custom markup + text can be validated separately from the document.</div>
<div> </div>
<div>I would prefer less ambiguous wording like:</div>
<div> </div>
<div>"Once this custom markup is extracted, the resulting XML document can be validated separately from the WordprocessingML document."</div>
<div> </div>
<div>> * Locate the schema element (section 23.2.1) in the Document Settings part whose uri attribute matches the root namespace of the custom markup.</div>
<div> </div>
<div>... matches the namespace of root element in the XML document extracted from custom XML markup</div>
<div> </div>
<div> Jirka</div>
<div> </div>
<div>BTW, the current XSLT code for extraction is slightly broken, so don't look at it ;-) This is already covered in another DR.</div>
<div> </div>
<div>--</div>
<div>------------------------------------------------------------------</div>
<div> Jirka Kosek e-mail: jirka@kosek.cz <a href="http://xmlguru.cz">http://xmlguru.cz</a></div>
<div>------------------------------------------------------------------</div>
<div> Professional XML consulting and training services</div>
<div> DocBook customization, custom XSLT/XSL-FO document processing</div>
<div>------------------------------------------------------------------</div>
<div> OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member</div>
<div>------------------------------------------------------------------</div>
<div> </div>
<div> </div>
</font>
</body>
</html>