Difference between revisions of "XprocVnext"

From W3C Wiki
Jump to: navigation, search
m (Updated link to XProc Usability)
m (Readability tweaks (formatting, phrasing, clarity))
Line 3: Line 3:
 
Try to use the following high-level categories, but if necessary add new ones or, after due consideration, reorganize things
 
Try to use the following high-level categories, but if necessary add new ones or, after due consideration, reorganize things
  
# [[Architecture]]: XDM more generally, text, JSON, . . .
+
# [[Architecture]]: XDM. More generally: text, JSON, etc.
 
# [[XProc Usability Issues|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]]: More-or-less persistent, named pipeline-local resource creation and access
# [[Integration]]:  profiling, APIs, tooling, 'choreography' for e.g. XRX applications
+
# [[Integration]]:  Profiling, APIs, tooling, ‘choreography’ (e.g. for XRX applications)
  
  
== Unsorted V.next items ==
+
== Unsorted XProc v.Next Issues ==
  
=== Things from xproc.org ===
+
=== Issues from xproc.org ===
  
[[OldWikiVnext]]: cut n pasted from xproc.org
+
[[OldWikiVnext]]: Copy-pasted from [http://xproc.org|xproc.org]
  
=== Issues from the XProc CR issues document that we decided were potential V.next topics ===
+
=== Issues from the XProc CR Issues document ===
 +
Potential V.next topics, taken from the [http://www.w3.org/XML/XProc/xproc-candidate-issues/ XProc Candidate Issues document] as determined at our October 31 f2f ([http://www.w3.org/2011/10/31-xproc-irc.html minutes]). 
  
Taken from the [http://www.w3.org/XML/XProc/xproc-candidate-issues/ xproc candidate issues document] as determined at our October 31 f2f ([http://www.w3.org/2011/10/31-xproc-irc.html minutes]).  Issue numbers refer to numbers given in the issues document.
+
Issue numbers refer to numbers given in the Issues document.
  
'''Issue 001:''' extend our current p:template in order to have some
+
'''Issue 001:''' extend our current <code>p:template</code> in order to have some
 
higher level construct without going into FULL XSLT  
 
higher level construct without going into FULL XSLT  
  
Line 37: Line 38:
 
=== Left over from V1 requirements document ===
 
=== Left over from V1 requirements document ===
  
We also want to go through the [http://www.w3.org/TR/xproc-requirements/ V1 requirements document]  
+
'''ToDo:''' Go through the [http://www.w3.org/TR/xproc-requirements/ V1 requirements document]  
and add to our V.next considerations anything from there that hasn't been addressed by V1.
+
and add anything from there that hasn’t been addressed by V1.

Revision as of 15:17, 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, etc.
  2. Usability: Syntax, defaults, constraints, etc.
  3. NewSteps: And control primitives
  4. ResourceManager: More-or-less persistent, named pipeline-local resource creation and access
  5. Integration: Profiling, APIs, tooling, ‘choreography’ (e.g. for XRX applications)


Unsorted XProc v.Next Issues

Issues from xproc.org

OldWikiVnext: Copy-pasted from [1]

Issues from the XProc CR Issues document

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

ToDo: Go through the V1 requirements document and add anything from there that hasn’t been addressed by V1.