- From: Norman Walsh <ndw@nwalsh.com>
- Date: Thu, 26 Jan 2012 11:09:10 -0500
- To: public-xml-processing-model-wg@w3.org
- Message-ID: <m27h0esaxl.fsf@nwalsh.com>
Here's a revised list of possible low-hanging-fruit items based on our call today: * Define XProc in terms of XPath 2.0 data models (drop XPath 1.0 support) * Attribute value templates * Arbitrary data model fragments for parameters/options/variables * Data types for options and parameters * Support for 'depends-on' (or some mechanism for asserting dependencies that are not manifest in the data flow) * Syntactic shortcuts for p:input and/or p:pipe * Allow variables to be visible in nested pipelines * Some additional support for non-XML documents. Perhaps: * The ability to load HTML5/JSON/etc. as XML * An option on p:store to save decoded/binary data * Some mechanism for loading sets of documents at the p:document/p:data level (e.g., <p:document href="/path/to/directory" include="*.xml"/>). * Simplify the task of passing "optional options" through a pipeline? * Explore using maps to simplify the parameters story Did I miss any that we discussed today? Can you think of any others? Be seeing you, norm -- Norman Walsh Lead Engineer MarkLogic Corporation Phone: +1 413 624 6676 www.marklogic.com
Received on Thursday, 26 January 2012 16:09:39 UTC