Low hanging fruit for V.next

Here's a list culled from the wikis. These are not all equally low hanging
and at least one may be controversial, but it's a start.

* 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'
* Syntactic shortcuts for p:input and/or p:pipe
* Allow variables to be visible in nested pipelines

Easy steps:

* Namespace rename step

Question: if we did these things and nothing else, what would users
still find most irksome?

                                        Be seeing you,
                                          norm

-- 
Norman Walsh
Lead Engineer
MarkLogic Corporation
Phone: +1 413 624 6676
www.marklogic.com