Deploying to gh-pages from @ xproc/3.0-steps@a490406 🚀

pr/600/etc/step-validation/library.xml

@@ -58,10 +58,7 @@
       <p:option name="report-format" select="'xvrl'" as="xs:string"/>
    </p:declare-step>
    <p:declare-step type="p:validate-with-dtd" xml:id="validate-with-dtd">
-      <p:input port="source" primary="true" content-types="xml html text"/>
-      <p:input port="doctype" content-types="text" sequence="true">
-         <p:empty/>
-      </p:input>
+      <p:input port="source" primary="true" content-types="xml html"/>
       <p:output port="result" primary="true" content-types="xml"/>
       <p:output port="report" sequence="true" content-types="xml json"/>
       <p:option name="report-format" select="'xvrl'" as="xs:string"/>

pr/600/etc/step-validation/source.xml

@@ -493,10 +493,7 @@ properties are preserved on the <port>report</port> port.</para>
   <para>The <tag>p:validate-with-dtd</tag> step validates XML with a DTD.</para>
 
 <p:declare-step type="p:validate-with-dtd">
-  <p:input port="source" primary="true" content-types="xml html text"/>
-  <p:input port="doctype" content-types="text" sequence="true">
-    <p:empty/>
-  </p:input>
+  <p:input port="source" primary="true" content-types="xml html"/>
   <p:output port="result" primary="true" content-types="xml"/>
   <p:output port="report" sequence="true" content-types="xml json"/>
   <p:option name="report-format" select="'xvrl'" as="xs:string"/>
@@ -506,61 +503,51 @@ properties are preserved on the <port>report</port> port.</para>
 
 <para>DTD validation differs from the other XML validation technologies in that
 it is applied during parsing. It isn’t possible to validate an XML data model with
-a DTD. This step necessarily serializes the source document and then parses it
-back into a new data model.
-</para>
-
-<para>There are several possible approaches, with varying degrees of complexity.
-The general model is that the contents of the <port>doctype</port> port and
-the result of serializing the <port>source</port> are concatenated together.
-</para>
+a DTD. This step necessarily serializes and reparses.</para>
 
-<itemizedlist>
-<listitem>
-<para>In the simple case, the <port>doctype</port> is empty and <port>source</port>
-document is simply serialized. In order to have any chance of being DTD-valid,
-the serialization properties must include at least a <code>doctype-system</code>
-property.</para>
-</listitem>
-<listitem>
-<para>If an internal subset is required, it is provided on the <port>doctype</port> port.
-In this case, the <code>source</code> document must be serialized <emphasis>without</emphasis>
-a <code>doctype-system</code> property; both the internal and external declarations must appear
-on the <port>doctype</port> port.</para>
-</listitem>
-<listitem>
-<para>Finally, if a text document is provided on the <port>source</port> port,
-it is simply concatenated with the <port>doctype</port> port.</para>
-</listitem>
-</itemizedlist>
+<para>The <tag>p:validate-with-dtd</tag> step serializes the document on the <port>source</port>
+port and parses the serialization with a
+validating XML parser. Any warning or error messages produced by the parser will
+appear on the <port>report</port> port.</para>
 
-<para>The resulting text is parsed using a validating XML parser. Any warning or
-error messages produced by the parser will appear on the <port>report</port>
-port.
-</para>
+<note>
+<para>The serialization options must include at least the
+<literal>doctype-system</literal> property (without a system identifier, the
+document cannot be successfully parsed with a validating parser).</para>
+</note>
 
 <para><error code="C0210">It is a <glossterm>dynamic error</glossterm>
 if the <option>assert-valid</option> option on <tag>p:validate-with-dtd</tag>
 is <literal>true</literal>
 and the input document is not valid.</error></para>
 
-<para>The output from this step is a copy of the input. If validation was successful,
-the output may have been augmented by the DTD.</para>
+<para>The output from this step is a copy of the input. If validation was
+successful, the output may have been augmented by the DTD. (For example, default
+attributes may have been added.)</para>
+
+<simplesect>
+<title>Using an internal subset</title>
+
+<para>To validate a document with an internal subset, construct a text document
+that is a syntactically valid XML document with the internal
+subset, use <tag>p:cast-content-type</tag> to create an XML document,
+and then validate the resulting document with this step.</para>
+</simplesect>
 
 <simplesect>
-  <title>Document properties</title>
-  <para feature="validate-with-dtd-preserves-all">All document properties
-  on the <port>source</port> port are preserved on the <port>result</port>
-  port. No document properties are
-  preserved on the <port>report</port> port.</para>
+<title>Document properties</title>
+<para feature="validate-with-dtd-preserves-all">All document properties
+on the <port>source</port> port are preserved on the <port>result</port>
+port. No document properties are
+preserved on the <port>report</port> port.</para>
 </simplesect>
 </section>  
 </section>
 
 <section xml:id="errors">
 <title>Step Errors</title>
 
-<para>This step can raise
+<para>These steps can raise
 <glossterm baseform="dynamic-error">dynamic errors</glossterm>.
 </para>
 

pr/600/file/index.html

@@ -1,4 +1,4 @@
-<html xmlns="http://www.w3.org/1999/xhtml"><head><title>XProc 3.0: file steps</title><meta charset="utf-8" /><meta content="width=device-width, initial-scale=1, shrink-to-fit=no" name="viewport" /><link class="removeOnSave" crossorigin="anonymous" href="https://www.w3.org" rel="preconnect" /><link as="script" class="removeOnSave" href="js/fixup.js" rel="preload" /><link as="style" class="removeOnSave" href="css/base.css" rel="preload" /><link as="image" class="removeOnSave" href="https://www.w3.org/StyleSheets/TR/2016/logos/W3C" rel="preload" /><link rel="stylesheet" href="css/cg-draft.css" /><link rel="stylesheet" href="css/respec.css" /><link rel="alternate" title="XML" href="specification.xml" /><meta name="generator" content="DocBook XSL 2.0 Stylesheets V2.5.0" /><meta name="description" content="Abstract This specification describes the file related steps&#xA;for&#xA;XProc 3.0: An XML Pipeline Language." /><link href="css/default.css" rel="stylesheet" type="text/css" /><link href="css/db-prism.css" rel="stylesheet" type="text/css" /><link rel="stylesheet" type="text/css" href="css/base.css" /><link rel="stylesheet" type="text/css" href="css/xproc.css" /><link rel="stylesheet" type="text/css" href="css/print.css" media="print" /><script type="text/javascript" src="js/dbmodnizr.js"></script></head><body class="h-entry informative toc-sidebar"><div class="head" id="spec.head"><a class="logo" href="https://www.w3.org/"><img alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2016/logos/W3C" width="72" /></a><h1 id="title" class="title p-name">XProc 3.0: file steps</h1><h2>Draft Community Group Report <time class="dt-published" datetime="2024-08-02">2 August 2024</time></h2><div class="editors-draft">Editor's Draft   at <time class="dt-timestamp" datetime="20240802T07:15:45Z">07:15 UTC</time> (<a href="https://github.com/xproc//commit/a4904063b01f661b87254ee4d86fb060babba54c">build 71</a>)</div><dl><dt>Latest editor’s draft:</dt><dd><a href="https://spec.xproc.org/master/head/file/">https://spec.xproc.org/master/head/file/</a></dd><dt>Editors:</dt><dd><span class="personname">Norman Walsh</span></dd><dd><span class="personname">Achim Berndzen</span></dd><dd><span class="personname">Gerrit Imsieke</span></dd><dd><span class="personname">Erik Siegel</span></dd><dt>Participate:</dt><dd><a href="http://github.com/xproc/3.0-steps">GitHub xproc/3.0-steps</a></dd><dd><a href="http://github.com/xproc/3.0-steps/issues">Report an issue</a></dd><dt>Changes:</dt><dd><a href="diff.html">Diff against current “status quo” draft</a></dd><dd><a href="http://github.com/xproc//commits/">Commits for this specification</a></dd></dl><p>This document is also available in these non-normative formats: <a href="specification.xml">XML</a> and HTML with automatic change markup  courtesy of <a href="http://www.deltaxml.com/">DeltaXML</a>.</p><p class="copyright"><a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © <span class="years">2018, 2019, 2020</span> the Contributors to the <cite>XProc 3.0: file steps</cite> specification, published by the <a href="https://www.w3.org/community/xproc-next/">XProc Next Community Group</a> under the <a href="https://www.w3.org/community/about/agreements/cla/">W3C
+<html xmlns="http://www.w3.org/1999/xhtml"><head><title>XProc 3.0: file steps</title><meta charset="utf-8" /><meta content="width=device-width, initial-scale=1, shrink-to-fit=no" name="viewport" /><link class="removeOnSave" crossorigin="anonymous" href="https://www.w3.org" rel="preconnect" /><link as="script" class="removeOnSave" href="js/fixup.js" rel="preload" /><link as="style" class="removeOnSave" href="css/base.css" rel="preload" /><link as="image" class="removeOnSave" href="https://www.w3.org/StyleSheets/TR/2016/logos/W3C" rel="preload" /><link rel="stylesheet" href="css/cg-draft.css" /><link rel="stylesheet" href="css/respec.css" /><link rel="alternate" title="XML" href="specification.xml" /><meta name="generator" content="DocBook XSL 2.0 Stylesheets V2.5.0" /><meta name="description" content="Abstract This specification describes the file related steps&#xA;for&#xA;XProc 3.0: An XML Pipeline Language." /><link href="css/default.css" rel="stylesheet" type="text/css" /><link href="css/db-prism.css" rel="stylesheet" type="text/css" /><link rel="stylesheet" type="text/css" href="css/base.css" /><link rel="stylesheet" type="text/css" href="css/xproc.css" /><link rel="stylesheet" type="text/css" href="css/print.css" media="print" /><script type="text/javascript" src="js/dbmodnizr.js"></script></head><body class="h-entry informative toc-sidebar"><div class="head" id="spec.head"><a class="logo" href="https://www.w3.org/"><img alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2016/logos/W3C" width="72" /></a><h1 id="title" class="title p-name">XProc 3.0: file steps</h1><h2>Draft Community Group Report <time class="dt-published" datetime="2024-08-02">2 August 2024</time></h2><div class="editors-draft">Editor's Draft   at <time class="dt-timestamp" datetime="20240802T08:54:01Z">08:54 UTC</time> (<a href="https://github.com/xproc//commit/a4904063b01f661b87254ee4d86fb060babba54c">build 72</a>)</div><dl><dt>Latest editor’s draft:</dt><dd><a href="https://spec.xproc.org/master/head/file/">https://spec.xproc.org/master/head/file/</a></dd><dt>Editors:</dt><dd><span class="personname">Norman Walsh</span></dd><dd><span class="personname">Achim Berndzen</span></dd><dd><span class="personname">Gerrit Imsieke</span></dd><dd><span class="personname">Erik Siegel</span></dd><dt>Participate:</dt><dd><a href="http://github.com/xproc/3.0-steps">GitHub xproc/3.0-steps</a></dd><dd><a href="http://github.com/xproc/3.0-steps/issues">Report an issue</a></dd><dt>Changes:</dt><dd><a href="diff.html">Diff against current “status quo” draft</a></dd><dd><a href="http://github.com/xproc//commits/">Commits for this specification</a></dd></dl><p>This document is also available in these non-normative formats: <a href="specification.xml">XML</a> and HTML with automatic change markup  courtesy of <a href="http://www.deltaxml.com/">DeltaXML</a>.</p><p class="copyright"><a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © <span class="years">2018, 2019, 2020</span> the Contributors to the <cite>XProc 3.0: file steps</cite> specification, published by the <a href="https://www.w3.org/community/xproc-next/">XProc Next Community Group</a> under the <a href="https://www.w3.org/community/about/agreements/cla/">W3C
     Community Contributor License Agreement (CLA)</a>. A human-readable <a href="https://www.w3.org/community/about/agreements/cla-deed/">summary</a> is available.</p><hr title="Separator for header" /><section id="abstract" class="introductory"><h2>Abstract</h2>
 <p>This specification describes the file related steps
 for

pr/600/ixml/index.html

@@ -1,4 +1,4 @@
-<html xmlns="http://www.w3.org/1999/xhtml"><head><title>XProc 3.0: Invisible XML</title><meta charset="utf-8" /><meta content="width=device-width, initial-scale=1, shrink-to-fit=no" name="viewport" /><link class="removeOnSave" crossorigin="anonymous" href="https://www.w3.org" rel="preconnect" /><link as="script" class="removeOnSave" href="js/fixup.js" rel="preload" /><link as="style" class="removeOnSave" href="css/base.css" rel="preload" /><link as="image" class="removeOnSave" href="https://www.w3.org/StyleSheets/TR/2016/logos/W3C" rel="preload" /><link rel="stylesheet" href="css/cg-draft.css" /><link rel="stylesheet" href="css/respec.css" /><link rel="alternate" title="XML" href="specification.xml" /><meta name="generator" content="DocBook XSL 2.0 Stylesheets V2.5.0" /><meta name="description" content="Abstract This specification describes the p:ixml&#xA;step for&#xA;XProc 3.0: An XML Pipeline Language." /><link href="css/default.css" rel="stylesheet" type="text/css" /><link href="css/db-prism.css" rel="stylesheet" type="text/css" /><link rel="stylesheet" type="text/css" href="css/base.css" /><link rel="stylesheet" type="text/css" href="css/xproc.css" /><link rel="stylesheet" type="text/css" href="css/print.css" media="print" /><script type="text/javascript" src="js/dbmodnizr.js"></script></head><body class="h-entry informative toc-sidebar"><div class="head" id="spec.head"><a class="logo" href="https://www.w3.org/"><img alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2016/logos/W3C" width="72" /></a><h1 id="title" class="title p-name">XProc 3.0: Invisible XML</h1><h2>Draft Community Group Report <time class="dt-published" datetime="2024-08-02">2 August 2024</time></h2><div class="editors-draft">Editor's Draft   at <time class="dt-timestamp" datetime="20240802T07:15:51Z">07:15 UTC</time> (<a href="https://github.com/xproc//commit/a4904063b01f661b87254ee4d86fb060babba54c">build 71</a>)</div><dl><dt>Latest editor’s draft:</dt><dd><a href="https://spec.xproc.org/master/head/ixml/">https://spec.xproc.org/master/head/ixml/</a></dd><dt>Editor:</dt><dd><span class="personname">Norman Walsh</span></dd><dt>Participate:</dt><dd><a href="http://github.com/xproc/3.0-steps">GitHub xproc/3.0-steps</a></dd><dd><a href="http://github.com/xproc/3.0-steps/issues">Report an issue</a></dd><dt>Changes:</dt><dd><a href="diff.html">Diff against current “status quo” draft</a></dd><dd><a href="http://github.com/xproc//commits/">Commits for this specification</a></dd></dl><p>This document is also available in these non-normative formats: <a href="specification.xml">XML</a> and HTML with automatic change markup  courtesy of <a href="http://www.deltaxml.com/">DeltaXML</a>.</p><p class="copyright"><a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © <span class="years">2021</span> the Contributors to the <cite>XProc 3.0: Invisible XML</cite> specification, published by the <a href="https://www.w3.org/community/xproc-next/">XProc Next Community Group</a> under the <a href="https://www.w3.org/community/about/agreements/cla/">W3C
+<html xmlns="http://www.w3.org/1999/xhtml"><head><title>XProc 3.0: Invisible XML</title><meta charset="utf-8" /><meta content="width=device-width, initial-scale=1, shrink-to-fit=no" name="viewport" /><link class="removeOnSave" crossorigin="anonymous" href="https://www.w3.org" rel="preconnect" /><link as="script" class="removeOnSave" href="js/fixup.js" rel="preload" /><link as="style" class="removeOnSave" href="css/base.css" rel="preload" /><link as="image" class="removeOnSave" href="https://www.w3.org/StyleSheets/TR/2016/logos/W3C" rel="preload" /><link rel="stylesheet" href="css/cg-draft.css" /><link rel="stylesheet" href="css/respec.css" /><link rel="alternate" title="XML" href="specification.xml" /><meta name="generator" content="DocBook XSL 2.0 Stylesheets V2.5.0" /><meta name="description" content="Abstract This specification describes the p:ixml&#xA;step for&#xA;XProc 3.0: An XML Pipeline Language." /><link href="css/default.css" rel="stylesheet" type="text/css" /><link href="css/db-prism.css" rel="stylesheet" type="text/css" /><link rel="stylesheet" type="text/css" href="css/base.css" /><link rel="stylesheet" type="text/css" href="css/xproc.css" /><link rel="stylesheet" type="text/css" href="css/print.css" media="print" /><script type="text/javascript" src="js/dbmodnizr.js"></script></head><body class="h-entry informative toc-sidebar"><div class="head" id="spec.head"><a class="logo" href="https://www.w3.org/"><img alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2016/logos/W3C" width="72" /></a><h1 id="title" class="title p-name">XProc 3.0: Invisible XML</h1><h2>Draft Community Group Report <time class="dt-published" datetime="2024-08-02">2 August 2024</time></h2><div class="editors-draft">Editor's Draft   at <time class="dt-timestamp" datetime="20240802T08:54:07Z">08:54 UTC</time> (<a href="https://github.com/xproc//commit/a4904063b01f661b87254ee4d86fb060babba54c">build 72</a>)</div><dl><dt>Latest editor’s draft:</dt><dd><a href="https://spec.xproc.org/master/head/ixml/">https://spec.xproc.org/master/head/ixml/</a></dd><dt>Editor:</dt><dd><span class="personname">Norman Walsh</span></dd><dt>Participate:</dt><dd><a href="http://github.com/xproc/3.0-steps">GitHub xproc/3.0-steps</a></dd><dd><a href="http://github.com/xproc/3.0-steps/issues">Report an issue</a></dd><dt>Changes:</dt><dd><a href="diff.html">Diff against current “status quo” draft</a></dd><dd><a href="http://github.com/xproc//commits/">Commits for this specification</a></dd></dl><p>This document is also available in these non-normative formats: <a href="specification.xml">XML</a> and HTML with automatic change markup  courtesy of <a href="http://www.deltaxml.com/">DeltaXML</a>.</p><p class="copyright"><a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © <span class="years">2021</span> the Contributors to the <cite>XProc 3.0: Invisible XML</cite> specification, published by the <a href="https://www.w3.org/community/xproc-next/">XProc Next Community Group</a> under the <a href="https://www.w3.org/community/about/agreements/cla/">W3C
     Community Contributor License Agreement (CLA)</a>. A human-readable <a href="https://www.w3.org/community/about/agreements/cla-deed/">summary</a> is available.</p><hr title="Separator for header" /><section id="abstract" class="introductory"><h2>Abstract</h2>
 <p>This specification describes the <code class="code">p:ixml</code>
 step for