- From: Andrew Eisenberg <andrew.eisenberg@us.ibm.com>
- Date: Mon, 22 Sep 2008 14:37:17 -0400
- To: public-xml-processing-model-comments@w3.org
- Cc: Jim Melton <jim.melton@acm.org>, Sharon Adler <sca@us.ibm.com>, Norman Walsh <ndw@nwalsh.com>
- Message-ID: <OF7A3ED369.BE2D389A-ON852574CC.00659545-852574CC.006649D5@us.ibm.com>
The XML Query and XSL WGs approved the following comments on the XProc LCWD [1] at our meeting on Sept. 16: 1) 2.6.2.2 Step XPath Context, minor technical Some of these items should specify that they are augmenting the values provided by an implementation: Statically known namespaces, Default element/type namespace, In-scope schema definitions, In-scope variables, and Function signatures. An XPath implementation might provide some statically known namespaces, for example, that are then augmented by those of p:namespaces, rather than overwritten by them. 2) 5.14 p:data, editorial Examples use p:file, rather than p:data. 3) 7.2.9 p:xquery, bulleted list beginning "The query port ...", editorial The 4th bullet does not recognize the third bullet. It should be changed to "Otherwise, the interpretation of the query is implementation-defined." 4) 7.2.9 p:xquery, "The static context is augmented as follows:", minor technical The static and dynamic context would be better stated independently of section 2.6.2.2 Step XPath Context. That section is written rather narrowly. It does not, for example, allow namespaces known a priori to the XQuery implementation. We suggest the following: The static context of the XQuery processor is augmented in the following way: Statically known default collection type: document()* Statically known namespaces: The namespace declarations in-scope for the containing element or made available through p:namespaces. The dynamic context used in evaluation the query is: Context item: document provided by the source-node port Context position: 1 Context size: 1 Variable values: The p:xquery parameters augment the variable bindings of the XQuery processor. The parameter values are passed to the XQuery processor as values of type xs:untypedAtomic. Function implementations: The function implementations provided by the XQuery processor. Current dateTime: implementation-defined value Implicit timezone: implementation-defined value Available documents: implementation-dependent Available collections: implementation-dependent Default collection: sequence of documents provided by the source port 5) 7.2.9 p:xquery, an example would be useful, editorial Example: <p:pipeline xmlns:p="http://www.w3.org/ns/xproc"> <p:xinclude/> <p:validate-with-xml-schema> <p:input port="schema"> <p:document href="http://example.com/path/to/schema.xsd"/> </p:input> </p:validate-with-xml-schema> <p:query> <p:input port="query"> <p:data href="file:countp.xq" /> </p:input> <p:input port="source"> <p:pipe step="validate-with-xml-schema" port="result"/> </p:input> </p:query> </p:pipeline> Where countp.xq contains the following: <count>{count(.//p)}</count> -- Andrew [1] XProc: An XML Pipeline Language http://www.w3.org/TR/2008/WD-xproc-20080814/ -------------------- Andrew Eisenberg IBM 4 Technology Park Drive Westford, MA 01886 andrew.eisenberg@us.ibm.com
Received on Monday, 22 September 2008 18:38:02 UTC