diff --git a/.gitignore b/.gitignore
index 75ffd59..ea333b4 100644
--- a/.gitignore
+++ b/.gitignore
@@ -15,3 +15,4 @@
/steps/build/
/step-json/build/
/step-ixml/build/
+/step-message/build/
diff --git a/build.gradle b/build.gradle
index 95a73bc..eab40fa 100644
--- a/build.gradle
+++ b/build.gradle
@@ -731,7 +731,7 @@ task step_message(type: DocBookTask,
param("ci-tag", getenv("CI_TAG"))
option("style", file("tools/xsl/xproc-specs.xsl"))
- option("diff", '')
+ option("diff", deltaxml())
option("specid", "message")
option("diffloc", buildAbsDir + "/message/diff.html")
diff --git a/step-message/build/glossary.xml b/step-message/build/glossary.xml
deleted file mode 100644
index a4efcee..0000000
--- a/step-message/build/glossary.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-Glossaryimplementation-definedAn
-implementation-defined feature is one where the
-implementation has discretion in how it is performed.
-Conformant implementations must document
-how implementation-defined features are performed.implementation-dependentAn
-implementation-dependent feature is one where the
-implementation has discretion in how it is performed.
-Implementations are not required to document or explain
-how implementation-dependent features are performed.
\ No newline at end of file
diff --git a/step-message/build/library.xml b/step-message/build/library.xml
deleted file mode 100644
index b9b0303..0000000
--- a/step-message/build/library.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-
-
-
-
-
-
-
-
diff --git a/step-message/build/source.xml b/step-message/build/source.xml
deleted file mode 100644
index fe19b34..0000000
--- a/step-message/build/source.xml
+++ /dev/null
@@ -1,242 +0,0 @@
-
-
- XProc 3.1: message step
-
-2025
-the Contributors to the XProc 3.1 Standard Step Library
-specifications
-
-
-xproc/3.0-steps
-XProc Next
-
- XML
-
-
- Norman Walsh
-
-
- Achim Berndzen
-
-
- Gerrit Imsieke
-
-
- Erik Siegel
-
-
-
-
- This specification describes an optional message step for
-XProc 3.1: An XML Pipeline Language.
-
-
-
- This specification was published by the
- XProc
- Next Community Group. It is not a W3C Standard nor is it on
- the W3C Standards Track. Please note that under the
- W3C
- Community Contributor License Agreement (CLA) there is a limited
- opt-out and other conditions apply. Learn more about W3C Community and Business
- Groups.
-
-
- If you wish to make comments regarding this document, please
- send them to
- xproc-dev@w3.org.
- (subscribe,
- archives).
-
-
-
-This draft is the “editor’s working draft” and may continue to evolve.
-
-
-
-
-
-
- Introduction
-
- This specification describes an optional message step for XProc 3.1.
-A machine-readable description of this step may be found in
-steps.xpl.
-
-Familarity with the general nature of
- steps is assumed.
-
-
-
-Step library
-
-
-p:message
-
-The p:message step conditionally produces a message.
-
-
-
-
-
-
-
-
-Steps that produce messages offer one way for an author to keep track of
-the progress of a pipeline. The [p:]message
-attribute can be added to any step to display a message when it runs.
-
-Status and debugging messages that are appropriate during pipeline
-development may be distracting when the pipeline is running “in production”.
-Existing mechanisms for conditional compilation can be used to mediate between
-“development” and “production” runs, but they are a bit heavyweight. Adding many
-steps with [p:]use-when attributes and managing the
-connections between steps that may be conditionally removed can make pipelines
-harder to read and understand.
-
-The p:message step can be used to achieve much the same effect
-and is considerably less verbose.
-
-If the test attribute is
-“true”, the select expression is
-evaluated and made available. (As with the message
-attribute, this is intentionally vague. Precisely what “made
-available” means is implementation-defined.
-Often it means “printed on the console”.)
-
-Irrespective of the value of the test
-attribute, the p:message passes all of the documents that appear on
-its source port through to the result port,
-unchanged and in the same order.
-
-If exactly one document appears on the source port, it is the
-context item when the test and select expressions are evaluated. In all other cases,
-the context item is undefined.
-
-
-If the test expression is “false”,
-it is implementation-dependent if the
-select expression is evaluated.
-
-
-
-If it can be determined statically that test expression is
-always “false”, the processor may remove the
-step from the pipeline entirely, although it must guarantee that all of the connections
-are preserved.
-
-
-
- Document properties
- All document properties are preserved.
-
-
-
-
-
-
-
-Conformance
-
-Conformant processors must implement all of the features
-described in this specification except those that are explicitly identified
-as optional.
-
-Some aspects of processor behavior are not completely specified; those
-features are either implementation-dependent or
-implementation-defined.
-
-An
-implementation-dependent feature is one where the
-implementation has discretion in how it is performed.
-Implementations are not required to document or explain
-how implementation-dependent features are performed.
-
-
-An
-implementation-defined feature is one where the
-implementation has discretion in how it is performed.
-Conformant implementations must document
-how implementation-defined features are performed.
-
-
-
-Implementation-defined features
-
-The following features are implementation-defined:
-
-
-
-
-
-Implementation-dependent features
-
-The following features are implementation-dependent:
-
-
-
-
-
-
-
- References
-
- XProc 3.1
-XProc 3.1:
-An XML Pipeline Language.
-Norman Walsh, Achim Berndzen, Gerrit Imsieke and Erik Siegel, editors.
-
-
-
-
-
- Glossaryimplementation-definedAn
-implementation-defined feature is one where the
-implementation has discretion in how it is performed.
-Conformant implementations must document
-how implementation-defined features are performed.implementation-dependentAn
-implementation-dependent feature is one where the
-implementation has discretion in how it is performed.
-Implementations are not required to document or explain
-how implementation-dependent features are performed.
-
-
-Ancillary files
-
-This specification includes by reference a number of
-ancillary files.
-
-
-
-
-
-An XProc step library for the declared steps.
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/step-message/build/steps.rnc b/step-message/build/steps.rnc
deleted file mode 100644
index 4ea2562..0000000
--- a/step-message/build/steps.rnc
+++ /dev/null
@@ -1,18 +0,0 @@
-default namespace p = "http://www.w3.org/ns/xproc"
-namespace local = ""
-
-# This schema could be made more constrained.
-
-Step = Step-message
-
-Step-message =
- element message {
- name.ncname.attr?,
- common.attributes,
- use-when.attr?,
- step.attributes,
- attribute test { avt.datatype }?,
- attribute select { avt.datatype }?,
- (WithInput* & WithOption* & (Documentation|PipeInfo)*)
- }
-
diff --git a/step-message/build/steps.rng b/step-message/build/steps.rng
deleted file mode 100644
index 7e337be..0000000
--- a/step-message/build/steps.rng
+++ /dev/null
@@ -1,43 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/step-message/build/xinclude.xml b/step-message/build/xinclude.xml
deleted file mode 100644
index fe19b34..0000000
--- a/step-message/build/xinclude.xml
+++ /dev/null
@@ -1,242 +0,0 @@
-
-
- XProc 3.1: message step
-
-2025
-the Contributors to the XProc 3.1 Standard Step Library
-specifications
-
-
-xproc/3.0-steps
-XProc Next
-
- XML
-
-
- Norman Walsh
-
-
- Achim Berndzen
-
-
- Gerrit Imsieke
-
-
- Erik Siegel
-
-
-
-
- This specification describes an optional message step for
-XProc 3.1: An XML Pipeline Language.
-
-
-
- This specification was published by the
- XProc
- Next Community Group. It is not a W3C Standard nor is it on
- the W3C Standards Track. Please note that under the
- W3C
- Community Contributor License Agreement (CLA) there is a limited
- opt-out and other conditions apply. Learn more about W3C Community and Business
- Groups.
-
-
- If you wish to make comments regarding this document, please
- send them to
- xproc-dev@w3.org.
- (subscribe,
- archives).
-
-
-
-This draft is the “editor’s working draft” and may continue to evolve.
-
-
-
-
-
-
- Introduction
-
- This specification describes an optional message step for XProc 3.1.
-A machine-readable description of this step may be found in
-steps.xpl.
-
-Familarity with the general nature of
- steps is assumed.
-
-
-
-Step library
-
-
-p:message
-
-The p:message step conditionally produces a message.
-
-
-
-
-
-
-
-
-Steps that produce messages offer one way for an author to keep track of
-the progress of a pipeline. The [p:]message
-attribute can be added to any step to display a message when it runs.
-
-Status and debugging messages that are appropriate during pipeline
-development may be distracting when the pipeline is running “in production”.
-Existing mechanisms for conditional compilation can be used to mediate between
-“development” and “production” runs, but they are a bit heavyweight. Adding many
-steps with [p:]use-when attributes and managing the
-connections between steps that may be conditionally removed can make pipelines
-harder to read and understand.
-
-The p:message step can be used to achieve much the same effect
-and is considerably less verbose.
-
-If the test attribute is
-“true”, the select expression is
-evaluated and made available. (As with the message
-attribute, this is intentionally vague. Precisely what “made
-available” means is implementation-defined.
-Often it means “printed on the console”.)
-
-Irrespective of the value of the test
-attribute, the p:message passes all of the documents that appear on
-its source port through to the result port,
-unchanged and in the same order.
-
-If exactly one document appears on the source port, it is the
-context item when the test and select expressions are evaluated. In all other cases,
-the context item is undefined.
-
-
-If the test expression is “false”,
-it is implementation-dependent if the
-select expression is evaluated.
-
-
-
-If it can be determined statically that test expression is
-always “false”, the processor may remove the
-step from the pipeline entirely, although it must guarantee that all of the connections
-are preserved.
-
-
-
- Document properties
- All document properties are preserved.
-
-
-
-
-
-
-
-Conformance
-
-Conformant processors must implement all of the features
-described in this specification except those that are explicitly identified
-as optional.
-
-Some aspects of processor behavior are not completely specified; those
-features are either implementation-dependent or
-implementation-defined.
-
-An
-implementation-dependent feature is one where the
-implementation has discretion in how it is performed.
-Implementations are not required to document or explain
-how implementation-dependent features are performed.
-
-
-An
-implementation-defined feature is one where the
-implementation has discretion in how it is performed.
-Conformant implementations must document
-how implementation-defined features are performed.
-
-
-
-Implementation-defined features
-
-The following features are implementation-defined:
-
-
-
-
-
-Implementation-dependent features
-
-The following features are implementation-dependent:
-
-
-
-
-
-
-
- References
-
- XProc 3.1
-XProc 3.1:
-An XML Pipeline Language.
-Norman Walsh, Achim Berndzen, Gerrit Imsieke and Erik Siegel, editors.
-
-
-
-
-
- Glossaryimplementation-definedAn
-implementation-defined feature is one where the
-implementation has discretion in how it is performed.
-Conformant implementations must document
-how implementation-defined features are performed.implementation-dependentAn
-implementation-dependent feature is one where the
-implementation has discretion in how it is performed.
-Implementations are not required to document or explain
-how implementation-dependent features are performed.
-
-
-Ancillary files
-
-This specification includes by reference a number of
-ancillary files.
-
-
-
-
-
-An XProc step library for the declared steps.
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/step-message/src/main/xml/specification.xml b/step-message/src/main/xml/specification.xml
index 1519f8a..898557e 100644
--- a/step-message/src/main/xml/specification.xml
+++ b/step-message/src/main/xml/specification.xml
@@ -125,12 +125,6 @@ context item when the test and select expressions are evaluated. In all other cases,
the context item is undefined.
-
-If the test expression is “false”,
-it is implementation-dependent if the
-select expression is evaluated.
-
-
If it can be determined statically that test expression is
always “false”, the processor may remove the
@@ -201,14 +195,6 @@ how implementation-defined features are
-
-Implementation-dependent features
-
-The following features are implementation-dependent:
-
-
-
-