Should defaulted ports be named?
Comments from the XSLT WG on the XProc Last Call Document
- Re: Comments from the XSLT WG on the XProc Last Call Document
- XPath version (Was: Comments from the XSLT WG on the XProc Last Call Document)
- Steps you can do in XSLT (Was:Comments from the XSLT WG on the XProc Last Call Document)
- Supporting XSLT 2.0 (Was: Comments from the XSLT WG on the XProc Last Call Document)
Does a primary output have to be connected in all branches?
clarification of p:pipeline-library and p:import
proposed changes and clarifications to p:load
propose changing p:directory-list filter option
put optional step in different namespace
Last Call Comment on XProc - http://www.w3.org/TR/2007/WD-xproc-20070920/
Standard (ECMAScript) interface for invoking XProc
Embedding one pipeline into another (or "defaulting pipeline libraries")
[closed] Re: injecting options and parameters into XProc
Scope of options
Form urlencode/decode for p:http-request?
Proposed new step: p:uuid
Proposed new step: p:hash
i meant, there is not document input re 3.4 Associating Documents with Ports
typo in 3.4 Associating Documents with Ports
comments on XProc last-call draft
headers in p:http-request
p:http-request dynamic error if not c:http-request?
- RE: http-request dynamic error if not c:http-request?
- Re: p:http-request dynamic error if not c:http-request?
XSLT 1.0 and XSLT 2.0
[Vasil Rangelov] RE: is p:inline underspecified?
Comment 30, Parameter inputs as strings (was Re: Saxonica Comments on XProc last-call draft, sections 1 and 2)
a note on spec link usability
is p:inline underspecified?
xsl-formatter
re injecting options and another question
clarify 5.11 p:pipe definition and refering to p:pipeline inputs
p:xinclude
http and https in p:http-request
Dynamic errors, choose
error in example 4.3.2 with dangling p:pipeline element
viewport
Primary parameter input port?
Parameter order
injecting options and parameters into XProc
- Re: injecting options and parameters into XProc
- Re: injecting options and parameters into XProc
- Re: injecting options and parameters into XProc
- Re: injecting options and parameters into XProc
- Re: injecting options and parameters into XProc
- RE: injecting options and parameters into XProc
- Re: injecting options and parameters into XProc
- Re: injecting options and parameters into XProc