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

Rethink non-step wrappers #636

xml-project opened this Issue Nov 11, 2018 · 1 comment


None yet
2 participants
Copy link

xml-project commented Nov 11, 2018

Currently the specs say:

Each subpipeline is identified by a non-step wrapper element: p:when and p:otherwise in the case of p:choose, p:group and p:catch in the case of p:try.

Here we have at least to remove the p:group from the p:try-list and add a p:finally. But as @ndw remarked:

I'm not sure what to do about the whole "non-step wrapper" terminology. But if we're going to keep it, I think you have to say something about the fact that the body of the p:try element preceding the first p:catch is somehow in an implicit non-step wrapper.


This comment has been minimized.

Copy link

xml-project commented Dec 9, 2018

See #39

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