Difference between revisions of "XprocVnext"

From W3C Wiki
Jump to: navigation, search
m (Moved XProc wiki-template back to bottom (ordering at the top of the page is touchy))
m (Fixed heading levels)
Line 18: Line 18:
  
  
== Unsorted XProc v.Next Issues ==
+
= Unsorted XProc v.Next Issues =
  
=== Issues from xproc.org ===
+
== Issues from xproc.org ==
  
 
[[OldWikiVnext]]: Copy-pasted from [http://xproc.org|xproc.org]
 
[[OldWikiVnext]]: Copy-pasted from [http://xproc.org|xproc.org]
  
=== Issues from the XProc CR Issues document ===
+
== 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]).   
 
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]).   
  
Line 44: Line 44:
 
'''Issue 017:''' simplified store step
 
'''Issue 017:''' simplified store step
  
=== Left over from V1 requirements document ===
+
== Left over from V1 requirements document ==
  
 
'''ToDo:''' 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]  

Revision as of 16:55, 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.


Architecture
XDM. More generally: text, JSON, etc.
Usability
Syntax, defaults, constraints, etc.
New Steps
And control primitives
Resource Manager
More-or-less persistent, named pipeline-local resource creation and access
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.

XProc
XProc v.Next  Architecture | Usabilitiy | New Steps | Resource Manager | Integration