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

[Shawn Villaron]

Thanks Jirka,

So it sounds like this is the proposed text ( italics indicate Jirka's proposed changes ):

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 custom markup is extracted, the resulting XML document  can be validated separately from the WordprocessingML 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 namespace of root element in the XML document extracted from custom XML 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).
Regarding the XSLT, Jirka, is that something you could help fix?

Thanks,

shawn


-----Original Message-----
From: Jirka Kosek [mailto:jirka at kosek.cz]
Sent: Wednesday, April 22, 2009 1:04 PM
To: Shawn Villaron
Cc: 'e-SC34-WG4 at ecma-international.org'
Subject: Re: DR-09-0029: WML, Custom XML and Smart Tags: Specification for Validation Lacking

Shawn Villaron wrote:

> 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.

I would prefer less ambiguous wording like:

"Once this custom markup is extracted, the resulting XML document  can be validated separately from the WordprocessingML document."

>  *   Locate the schema element (section 23.2.1) in the Document Settings part whose uri attribute matches the root namespace of the custom markup.

.... matches the namespace of root element in the XML document extracted from custom XML markup

                                Jirka

BTW, the current XSLT code for extraction is slightly broken, so don't look at it ;-) This is already covered in another DR.

--
------------------------------------------------------------------
  Jirka Kosek      e-mail: jirka at kosek.cz      http://xmlguru.cz
------------------------------------------------------------------
       Professional XML consulting and training services
  DocBook customization, custom XSLT/XSL-FO document processing
------------------------------------------------------------------
 OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member
------------------------------------------------------------------


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20090422/89da29bb/attachment.htm>