Each input connection (the second p:input signature box, the one after https://www.w3.org/TR/xproc/#err.inline.S0042 in the 1.0 spec, or p:with-input in the 3.0 spec) can have optional attributes. In 1.0, it’s @select, in 3.0, it’s also @href.
In the graph, an input connection corresponds to properties on the small input port bubbles of each atomic or compound step. (It doesn’t correspond to the connecting line because @select provides a selecting XPath expression for all p:pipes or p:documents connecting to this input port.)
Whether an input port is primary or sequence needs to be specified in its declaration. So there need not be any affordance to manipulate @primary or @sequence where a step is instantiated. This is different from @select and @href: A pipeline author needs to be able to edit these properties on step instances.
Each input connection (the second
p:inputsignature box, the one after https://www.w3.org/TR/xproc/#err.inline.S0042 in the 1.0 spec, orp:with-inputin the 3.0 spec) can have optional attributes. In 1.0, it’s@select, in 3.0, it’s also@href.In the graph, an input connection corresponds to properties on the small input port bubbles of each atomic or compound step. (It doesn’t correspond to the connecting line because
@selectprovides a selecting XPath expression for allp:pipes orp:documents connecting to this input port.)Whether an input port is primary or sequence needs to be specified in its declaration. So there need not be any affordance to manipulate
@primaryor@sequencewhere a step is instantiated. This is different from@selectand@href: A pipeline author needs to be able to edit these properties on step instances.