Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Default connection of input ports #544
This paragraph is taken from the 1.0 specification. I think we can completely remove it and state the new rule
With regard to 1.0 compatibility I think this change of concept shouldn't be a problem: A pipeline, that had a static error in 1.0 (unconnected input port) will now run in XProc 3.0 if there is a default binding for the port. A 1.0 pipeline that executed correctly will also do so in 3.0 because it has an actual binding, so the default binding is newer used.
will always be an error because
Will be an error if
I can imagine an author editing a pipeline, replacing
But I'm not going to fight hard against it if that's where consensus falls.
referenced this issue
Jan 4, 2019
I don't recall that we said input ports could be unconnected. I assume that an unconnected input would act as if it was connected to p:empty; I think that "empty" inputs are uncommon enough that it would be a usability mistake to silently create them. I think it's more likely that an unconnected input is an error than should be empty.
With respect to @xml-project 's proposal above, I assume that it's an error if the unconnected port has no default.