Skip to content
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

Edit section "Extension Steps" #468

Closed
xml-project opened this issue Jul 24, 2018 · 4 comments · Fixed by #915
Assignees
Labels

Comments

@xml-project
Copy link
Contributor

@xml-project xml-project commented Jul 24, 2018

The first sentence of section "Extension step" currently is:

Pipeline authors may also have access to additional steps not defined or described by this specification. Atomic extension steps are invoked just like standard steps ...

I wonder if it makes sense to be a bit more elaborate here because this section not only applies to the minor case of build-in processor extensions but also to the IMHO much larger use case of calling steps declared by pipeline authors with p:declare-step.

@ndw

This comment has been minimized.

Copy link
Contributor

@ndw ndw commented Jul 24, 2018

Sure. Go ahead and propose something more complete.

@xml-project

This comment has been minimized.

Copy link
Contributor Author

@xml-project xml-project commented Jul 24, 2018

Will do!

@xml-project xml-project self-assigned this Jul 24, 2018
@gimsieke

This comment has been minimized.

Copy link
Contributor

@gimsieke gimsieke commented Nov 11, 2018

Also consider the comments in #635 about regrouping the current “atomic steps” and “extension steps” sections and adapting the prose in Sect. 17.5. In 17.5, there is currently a distinction between “atomic steps” (in the sense of processor-implemented standard steps) and “pipelines” (user-defined steps written in XProc). The distinction should follow the proposed new distinction in 16.8.

Proposal for regrouping 16.8 and 16.9. (thereby eliminating 16.9):

16.8 Atomic Steps
16.8.1 Processor-Implemented Standard Atomic Steps
All atomic steps whose type is in the XProc namespace and whose declarations don’t have a subpipeline

16.8.2 Standard Atomic Steps Written in XProc
There aren’t any yet. This section will only be included if we decide to pursue this way.

16.8.3 User-Defined Atomic Extension Steps
Declaration with subpipeline, namespace not XProc, need to be imported.

16.8.4 Atomic Processor Extension Steps
Declaration without subpipeline, namespace not XProc. Whether they need to be imported (or which need not be imported, like the EXProc steps in 1.0 for certain processor versions, I believe) is implementation-defined.

16.8.5 Atomic Step Errors
XS0010, XS0044, XS0048, XD0010

@xml-project xml-project removed their assignment Nov 11, 2018
@ndw ndw self-assigned this Nov 30, 2018
@ndw ndw assigned gimsieke and unassigned ndw Nov 9, 2019
@ndw

This comment has been minimized.

Copy link
Contributor

@ndw ndw commented Nov 9, 2019

Clarify: steps in the XProc namespace do not have to be imported, everything else does.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.