Petr Cimprich said:
> 2. Japan
>
> Their argument is clear and I do accept it. I also appreciate the four
> suggested options. My preferable way would be to focus on the
> combination of Schematron and STXPath. We know that Schematron already
> allows STXPath as query language but an expressiveness of this
> combination is rather low. This limitation could be passed over using a
> little microformat-like extension to Schematron (to control buffering).
> The Part 6 then could consist of the specs of this extension module,
> perhaps plus the specs of STXPath - provided nobody in ISO/ETC nor W3C
> minds.
ISO Schematron has a mechanism called a "Query Language Binding" which
lists the things required in order to use a different query language.
Part 6 should be a query language binding for Schematron. A Query Language
Binding can add any foreign elements or attributes it likes: for XSLT it
adds xsl:key for example. So you can already add any attributes you like
for buffering etc.
There is an example Query Language Binding document in an Annex of ISO
Schematron: it is for the default XSLT, but it can be used as boilerplate
text that you can change the details of.
Cheers
Rick Jelliffe
-- DSDL members discussion list To unsubscribe, please send a message with the command "unsubscribe" to dsdl-discuss-request@dsdl.org (mailto:dsdl-discuss-request@dsdl.org?Subject=unsubscribe)Received on Tue Aug 14 20:10:07 2007
This archive was generated by hypermail 2.1.8 : Wed Aug 15 2007 - 13:13:03 UTC