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

xproc · Jan 28, 2025 · 0d97f63 · 0d97f63
1 parent 5d9c1b1
commit 0d97f63
Show file tree

Hide file tree

Showing 21 changed files with 37 additions and 37 deletions.
diff --git a/master/head/etc/step-file/source.xml b/master/head/etc/step-file/source.xml
@@ -129,15 +129,15 @@ access them, or they may be ignored by some or all steps.</para>
 
     <para>The <option>max-depth</option> option may contain either the string “<literal>unbounded</literal>” or a string
       that may be cast to a non-negative integer. An integer value of <literal>0</literal> means that only information
-      about the directory that is given in the <option>path</option> option is returned. A <option>max-depth</option> of
-      <literal>1</literal>, which is the default, will effect that also information about the top-level directory’s
-      immediate children will be included. For larger values of <option>max-depth</option>, also the content of
+      about the directory that is given in the <option>path</option> option is returned. If <option>max-depth</option> is
+      <literal>1</literal>, which is the default, information about the top-level directory’s
+      immediate children will also be included. For larger values of <option>max-depth</option>, also the content of
       directories will be considered recursively up to the maximum depth, and it will be included as children of the
       corresponding <tag>c:directory</tag> elements.</para>
 
     <para>If present, the value of the <option>include-filter</option> or
       <option>exclude-filter</option> option <rfc2119>must</rfc2119> be a sequence of strings, each
-      one representing a regular expressions as specified in <biblioref linkend="xpath31-functions"/>,
+      one representing a regular expression as specified in <biblioref linkend="xpath31-functions"/>,
       section 7.61 “<literal>Regular Expression Syntax</literal>”. <error code="C0147">It is a <glossterm>dynamic
         error</glossterm> if a specified value is not a valid XPath regular
         expression.</error></para>
@@ -167,7 +167,7 @@ access them, or they may be ignored by some or all steps.</para>
     entries, matching an entry <emphasis>does</emphasis> automatically include
     all of its ancestors (back to the initial directory). This assures that the hierarchy
     of the XML elements matches the hierarchy of the filesystem. When ancestors are
-    included this way, none of their other entires are included unless they match
+    included this way, none of their other entries are included unless they match
     an include filter.</para>
 
     <para>For a file <literal>a/a/b/file.txt</literal> below the initial
@@ -250,7 +250,7 @@ access them, or they may be ignored by some or all steps.</para>
       value is a relative IRI reference, giving the (local) file or
       directory name.</para>
 
-    <para>Each of these element also contains the corresponding resource’s URI in an <tag role="attribute">xml:base</tag>
+    <para>Each of these elements also contains the corresponding resource’s URI in an <tag role="attribute">xml:base</tag>
       attribute, which may be a relative URI for any but the top-level <tag>c:directory</tag> element. In the case of
       <tag>c:directory</tag>, it must end in a trailing slash. This way, users will always be able to compute the
       absolute URI for any of these elements by applying <code>fn:base-uri()</code> to it.</para>

diff --git a/master/head/file/diff.html b/master/head/file/diff.html
diff --git a/master/head/file/index.html b/master/head/file/index.html
@@ -1,4 +1,4 @@
-<html xmlns="http://www.w3.org/1999/xhtml"><head><title>XProc 3.1: 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.1: 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.1: file steps</h1><h2>Draft Community Group Report <time class="dt-published" datetime="2025-01-09">9 January 2025</time></h2><div class="editors-draft">Editor's Draft   at <time class="dt-timestamp" datetime="20250109T08:39:46Z">08:39 UTC</time> (<a href="https://github.com/xproc//commit/1c7468e3b4dc590e34968c6a48c978846e3ca9de">build 79</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.1: 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.1: 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.1: 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.1: file steps</h1><h2>Draft Community Group Report <time class="dt-published" datetime="2025-01-28">28 January 2025</time></h2><div class="editors-draft">Editor's Draft   at <time class="dt-timestamp" datetime="20250128T07:09:04Z">07:09 UTC</time> (<a href="https://github.com/xproc//commit/73b96584273b4e421a11119efa50edd03000eba7">build 80</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.1: 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
@@ -112,15 +112,15 @@
 
     <p>The <a id="opt.inline.max-depth-1"></a><code class="option">max-depth</code> option may contain either the string “<code class="literal">unbounded</code>” or a string
       that may be cast to a non-negative integer. An integer value of <code class="literal">0</code> means that only information
-      about the directory that is given in the <a id="opt.inline.path-2"></a><code class="option">path</code> option is returned. A <a id="opt.inline.max-depth-2"></a><code class="option">max-depth</code> of
-      <code class="literal">1</code>, which is the default, will effect that also information about the top-level directory’s
-      immediate children will be included. For larger values of <a id="opt.inline.max-depth-3"></a><code class="option">max-depth</code>, also the content of
+      about the directory that is given in the <a id="opt.inline.path-2"></a><code class="option">path</code> option is returned. If <a id="opt.inline.max-depth-2"></a><code class="option">max-depth</code> is
+      <code class="literal">1</code>, which is the default, information about the top-level directory’s
+      immediate children will also be included. For larger values of <a id="opt.inline.max-depth-3"></a><code class="option">max-depth</code>, also the content of
       directories will be considered recursively up to the maximum depth, and it will be included as children of the
       corresponding <a href="#cv.directory"><code class="tag-element">c:directory</code></a> elements.</p>
 
     <p>If present, the value of the <a id="opt.inline.include-filter-1"></a><code class="option">include-filter</code> or
       <a id="opt.inline.exclude-filter-1"></a><code class="option">exclude-filter</code> option <span class="rfc2119" id="c.directory-list.8.3">must</span> be a sequence of strings, each
-      one representing a regular expressions as specified in [<a href="#xpath31-functions"><span class="abbrev">XPath and XQuery Functions and Operators 3.1</span></a>],
+      one representing a regular expression as specified in [<a href="#xpath31-functions"><span class="abbrev">XPath and XQuery Functions and Operators 3.1</span></a>],
       section 7.61 “<code class="literal">Regular Expression Syntax</code>”. <a id="err.inline.C0147&#34;"></a>It is a <em class="glossterm"><a href="#dt-dynamic-error">dynamic
         error</a></em> (<a href="#err.C0147"><code class="errqname">err:XC0147</code></a>) if a specified value is not a valid XPath regular
         expression.</p>
@@ -150,7 +150,7 @@
     entries, matching an entry <em>does</em> automatically include
     all of its ancestors (back to the initial directory). This assures that the hierarchy
     of the XML elements matches the hierarchy of the filesystem. When ancestors are
-    included this way, none of their other entires are included unless they match
+    included this way, none of their other entries are included unless they match
     an include filter.</p>
 
     <p>For a file <code class="literal">a/a/b/file.txt</code> below the initial
@@ -233,7 +233,7 @@
       value is a relative IRI reference, giving the (local) file or
       directory name.</p>
 
-    <p>Each of these element also contains the corresponding resource’s URI in an <code class="tag-element attribute">xml:base</code>
+    <p>Each of these elements also contains the corresponding resource’s URI in an <code class="tag-element attribute">xml:base</code>
       attribute, which may be a relative URI for any but the top-level <a href="#cv.directory"><code class="tag-element">c:directory</code></a> element. In the case of
       <a href="#cv.directory"><code class="tag-element">c:directory</code></a>, it must end in a trailing slash. This way, users will always be able to compute the
       absolute URI for any of these elements by applying <code class="code">fn:base-uri()</code> to it.</p>

diff --git a/master/head/file/specification.xml b/master/head/file/specification.xml
@@ -129,15 +129,15 @@ access them, or they may be ignored by some or all steps.</para>
 
     <para>The <option>max-depth</option> option may contain either the string “<literal>unbounded</literal>” or a string
       that may be cast to a non-negative integer. An integer value of <literal>0</literal> means that only information
-      about the directory that is given in the <option>path</option> option is returned. A <option>max-depth</option> of
-      <literal>1</literal>, which is the default, will effect that also information about the top-level directory’s
-      immediate children will be included. For larger values of <option>max-depth</option>, also the content of
+      about the directory that is given in the <option>path</option> option is returned. If <option>max-depth</option> is
+      <literal>1</literal>, which is the default, information about the top-level directory’s
+      immediate children will also be included. For larger values of <option>max-depth</option>, also the content of
       directories will be considered recursively up to the maximum depth, and it will be included as children of the
       corresponding <tag>c:directory</tag> elements.</para>
 
     <para>If present, the value of the <option>include-filter</option> or
       <option>exclude-filter</option> option <rfc2119>must</rfc2119> be a sequence of strings, each
-      one representing a regular expressions as specified in <biblioref linkend="xpath31-functions"/>,
+      one representing a regular expression as specified in <biblioref linkend="xpath31-functions"/>,
       section 7.61 “<literal>Regular Expression Syntax</literal>”. <error code="C0147">It is a <glossterm>dynamic
         error</glossterm> if a specified value is not a valid XPath regular
         expression.</error></para>
@@ -167,7 +167,7 @@ access them, or they may be ignored by some or all steps.</para>
     entries, matching an entry <emphasis>does</emphasis> automatically include
     all of its ancestors (back to the initial directory). This assures that the hierarchy
     of the XML elements matches the hierarchy of the filesystem. When ancestors are
-    included this way, none of their other entires are included unless they match
+    included this way, none of their other entries are included unless they match
     an include filter.</para>
 
     <para>For a file <literal>a/a/b/file.txt</literal> below the initial
@@ -250,7 +250,7 @@ access them, or they may be ignored by some or all steps.</para>
       value is a relative IRI reference, giving the (local) file or
       directory name.</para>
 
-    <para>Each of these element also contains the corresponding resource’s URI in an <tag role="attribute">xml:base</tag>
+    <para>Each of these elements also contains the corresponding resource’s URI in an <tag role="attribute">xml:base</tag>
       attribute, which may be a relative URI for any but the top-level <tag>c:directory</tag> element. In the case of
       <tag>c:directory</tag>, it must end in a trailing slash. This way, users will always be able to compute the
       absolute URI for any of these elements by applying <code>fn:base-uri()</code> to it.</para>

diff --git a/master/head/ixml/diff.html b/master/head/ixml/diff.html