Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
2.6 Allow attribute value templates #33
The syntactic sugar that allows step options to be expressed concisely as attribute values on a step is foiled whenever the value of the option must be computed by the pipeline. Allowing those options to contain XSLT-style attribute value templates (AVTs) would simplify many pipelines. Additionally, allowing AVTs in other places, such as the href attribute on p:document, will be considered.
[XSLT 3.0] introduces a feature which allows expressions in curly braces to be evaluated in element content. This feature is similar to the facility provided by the p:template step. Extending XProc to support curly braces in a manner consistent with [XSLT 3.0] will be considered.
referenced this issue
Oct 3, 2014
I think we might want to do both. Allowing, for example, href on p:store to be an AVT would make it possible to write
which would set the value of the href attribute based on a runtime evaluation of
We could also allow _href with the proviso that it must be evaluated statically.
The much more interesting question is, should we allow _step or _port on p:pipe? This would allow a static parameter to have influence over the connections in the pipeline. Not impossible.
I'll start a new issue for this.