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

Is the select attribute on p:input really worth the trouble? #570

Closed
ndw opened this Issue Oct 22, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@ndw
Contributor

ndw commented Oct 22, 2018

In XProc 1.0, we used the p:input element for both declaration and use of inputs. We obviously needed a select attribute on the uses, so the least surprising thing to do seemed to be to give it a meaning on the declarations as well.

But now when I read:

The select expression applies only if the default connection is used. If an explicit connection is provided by the caller, then the default select expression is ignored.

I think that sounds like potentially confusing behavior for a very narrow use case.

We have p:with-input today. Is it worth considering a simplification and removing select from p:input?

@xml-project

This comment has been minimized.

Contributor

xml-project commented Oct 22, 2018

My first thought would be to keep it like it is, because I often use

<p:input port="source" select="/doc/element">
   <p:document href="uri" />
</p:input>

to provide a default document from a larger document used on other steps. Does this make sense?

My second argument would be that it becomes difficult for authors to port their XProc 1.0 pipelines to version 3.0 in the selecting from a document case.

@ndw

This comment has been minimized.

Contributor

ndw commented Oct 22, 2018

Ok, I guess it is then :-)

@ndw ndw closed this Oct 22, 2018

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