DR-09-0029: WML, Custom XML and Smart Tags: Specification for Validation Lacking

[Shawn Villaron]

Greetings,

I'd like to propose the following response regarding this defect report which is described as "[v]alidation of custom XML markups is not clearly specified.  Demonstrating examples are strongly needed."

Editor's Response:
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:
Once this information is extracted, the resulting custom markup + text can be validated separately from the document.
For example, the custom XML for the example on pp. 530, once extracted, would be:

<invoice xmlns="http://www.example.com/2006/invoice">

      <customerName>Tristan Davis</customerName>
</invoice>
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:

 *   Locate the schema element (section 23.2.1) in the Document Settings part whose uri attribute matches the root namespace of the custom markup.
 *   If that element also specifies a schemaLocation attribute, the resulting path is used to locate the schema used for validation.
 *   Once this schema is located, validation should be triggered based on the value of doNotValidateAgainstSchema (section 17.15.1.43).

Please advise if you see this as a satisfactory response or if you have specific improvements you'd like to see.

Thanks,

Shawn Villaron
Group Program Manager, Microsoft Office PowerPoint
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20090422/d801cb2a/attachment.htm>