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

Unclear rule #625

Closed
xml-project opened this Issue Nov 4, 2018 · 5 comments

Comments

Projects
None yet
2 participants
@xml-project
Contributor

xml-project commented Nov 4, 2018

The specs say:

Within the context of a compound step, the declared outputs of the compound step must describe their connections.

I current fail to understand what this rule means. Can anybody please enlighten me.

@ndw

This comment has been minimized.

Contributor

ndw commented Nov 5, 2018

When you declare (and even, for that matter, use) an atomic step, you never put a connection in a p:output. In declarations, they only describe the properties of the output (primary or secondary, sequence or not, etc.). When you use atomic steps, you never mention them at all.

Things are quite different in compound steps. In compound steps, you must provide a connection (even if it's the default connection to the last step in document order) for the p:output ports.

@xml-project

This comment has been minimized.

Contributor

xml-project commented Nov 5, 2018

Oh, it is this difference. Thanks @ndw Will look at the context again and think about a more explicit formulation.

@xml-project

This comment has been minimized.

Contributor

xml-project commented Nov 5, 2018

Ok, if you know what it is supposed to say, the paragraph is good and I can't easily find a better way to express this. Let's leave it like it is for a while.

@ndw

This comment has been minimized.

Contributor

ndw commented Nov 5, 2018

Ok. Should we close this issue in that case?

@xml-project

This comment has been minimized.

Contributor

xml-project commented Nov 5, 2018

Yes, thanks. Forgot this!

@xml-project xml-project closed this Nov 5, 2018

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