New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2.6 Allow attribute value templates #33

Closed
ndw opened this Issue Aug 22, 2014 · 4 comments

Comments

Projects
None yet
3 participants
@ndw
Collaborator

ndw commented Aug 22, 2014

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.

@innovimax

This comment has been minimized.

innovimax commented Oct 5, 2014

Do we want to allow curly braces or add "_att" to allow such behaviour (as it's done in XSLT 3.0 ) ?

@ndw

This comment has been minimized.

Collaborator

ndw commented Oct 6, 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

  <p:store href="{$expression}"/>

which would set the value of the href attribute based on a runtime evaluation of $expression (and would have, for example, the default readable port (I assume) as its context).

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.

@ndw

This comment has been minimized.

Collaborator

ndw commented Oct 6, 2014

c.f. issue #78

@ndw

This comment has been minimized.

Collaborator

ndw commented Oct 29, 2014

This issue was addressed by build 97 on 29 October 2014.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment