Difference between revisions of "XprocVnext"

From W3C Wiki
Jump to: navigation, search
(XML Processing Model Vnext candidate requirements)
m (Updated link to XProc Usability)
Line 4: Line 4:
  
 
# [[Architecture]]: XDM more generally, text, JSON, . . .
 
# [[Architecture]]: XDM more generally, text, JSON, . . .
# [[Usability]]: Syntax, defaults, constraints, etc.
+
# [[XProc Usability Issues|Usability]]: Syntax, defaults, constraints, etc.
 
# [[NewSteps]]: and control primitives
 
# [[NewSteps]]: and control primitives
 
# [[ResourceManager]]: Named, more-or-less persistent pipeline-local resource creation and access
 
# [[ResourceManager]]: Named, more-or-less persistent pipeline-local resource creation and access

Revision as of 15:09, 11 October 2012

XML Processing Model Vnext candidate requirements

Try to use the following high-level categories, but if necessary add new ones or, after due consideration, reorganize things

  1. Architecture: XDM more generally, text, JSON, . . .
  2. Usability: Syntax, defaults, constraints, etc.
  3. NewSteps: and control primitives
  4. ResourceManager: Named, more-or-less persistent pipeline-local resource creation and access
  5. Integration: profiling, APIs, tooling, 'choreography' for e.g. XRX applications


Unsorted V.next items

Things from xproc.org

OldWikiVnext: cut n pasted from xproc.org

Issues from the XProc CR issues document that we decided were potential V.next topics

Taken from the xproc candidate issues document as determined at our October 31 f2f (minutes). Issue numbers refer to numbers given in the issues document.

Issue 001: extend our current p:template in order to have some higher level construct without going into FULL XSLT

Issue 004: allow attribute value templates within xproc elements

Issue 006: harmonize p:data and p:load

Issue 010: something about document base uri

Issue 015: (V.next unless Norm says it is just closable.) JSON hack

Issue 016: (V.next unless Norm says it is just closable.) conditional output port

Issue 017: simplified store step

Left over from V1 requirements document

We also want to go through the V1 requirements document and add to our V.next considerations anything from there that hasn't been addressed by V1.