From 76ea1d25b1efb87c2a212aec9bf8b2c123906d1d Mon Sep 17 00:00:00 2001
From: Kristen James Eberlein <kris@eberleinconsulting.com>
Date: Mon, 13 Jun 2022 17:36:16 -0400
Subject: [PATCH] Update source files in preparation for review 0:
 accessibility

---
 .../archSpec/base/accessibletablemarkup.dita  | 24 +++++++------------
 .../example-alternate-text-for-an-image.dita  |  3 ---
 ...ta-2.0-key-definitions-cover-pages.ditamap |  6 ++---
 3 files changed, 11 insertions(+), 22 deletions(-)

diff --git a/specification/archSpec/base/accessibletablemarkup.dita b/specification/archSpec/base/accessibletablemarkup.dita
index f6798942..e95ccf05 100644
--- a/specification/archSpec/base/accessibletablemarkup.dita
+++ b/specification/archSpec/base/accessibletablemarkup.dita
@@ -14,14 +14,6 @@
 		</metadata>
 	</prolog>
 	<conbody>
-    <!--<draft-comment author="Kristen J Eberlein" time="28 March 2022"><p>This topic needs a more extensive edit than I did, including:</p><ul><li>Ensuring that the vocabulary aligns with how we describe complex and simple tables in the element-reference topics</li><li>Introducing the content outlined in the definition list</li><li>Alphabeticizing the entries in the definition list</li><li>Recasting the wording for the column headers and irregular headers to focus on what can be done with markup, instead of specifying what an author should do</li></ul></draft-comment>-->
-    <draft-comment author="Kristen J Eberlein" time="09 June 2022">
-      <p>I removed the following sentence from the short description, since
-        this topic does not really describe accessibility guidelines: "This
-        topic describes common accessibility guidelines that are related to
-        tables, along with the DITA markup that is designed to support
-        them."</p>
-    </draft-comment>
     <!--<p>DITA provides two table models, a more complex one using the <xmlelement>table</xmlelement> element and a simple one that used the <xmlelement>simpletable</xmlelement> element. The <xmlelement>table</xmlelement> element is based on the OASIS Exchange Table Model, while the <xmlelement>simpletable</xmlelement> element reflects a simpler model that is closer to an HTML table. Each table model is addressed here. </p>-->
     <p><ph
         conref="../../langRef/containers/table-elements.dita#table2/table-types"
@@ -62,14 +54,14 @@
                   <xmlatt>scope</xmlatt> attribute in the first entry in
                 the first row to can be set to <keyword>col</keyword> to
                 indicate that it is a header for the entire column.</dd>
-              <dd>(Other columns) The <xmlelement>colspec</xmlelement> element can define which
-                columns function as headers. For that case, set the <xmlatt>rowheader</xmlatt>
-                attribute to <keyword>headers</keyword> on the column or columns that function as
-                headers. Alternatively, set the <xmlatt>scope</xmlatt> attribute on each relevant
-                entry in the first row to <keyword>col</keyword>, indicating that the entry is a
-                header for the entire column.<draft-comment author="Kristen J Eberlein"
-                  time="09 June 2022">The last sentence in "Other columns" seems off; Robert, please
-                  verify that this is what you wanted to say.</draft-comment></dd>
+              <dd>(Other columns) The <xmlelement>colspec</xmlelement>
+                element can define which columns function as headers. For
+                that case, set the <xmlatt>rowheader</xmlatt> attribute to
+                  <keyword>headers</keyword> on the column or columns that
+                function as headers. Alternatively, set the
+                  <xmlatt>scope</xmlatt> attribute on each relevant entry
+                in the first row to <keyword>col</keyword>, indicating that
+                the entry is a header for the entire column.</dd>
             </dlentry>
             <dlentry>
               <dt>Simple table</dt>
diff --git a/specification/archSpec/base/example-alternate-text-for-an-image.dita b/specification/archSpec/base/example-alternate-text-for-an-image.dita
index 52b736a5..d9512c2f 100644
--- a/specification/archSpec/base/example-alternate-text-for-an-image.dita
+++ b/specification/archSpec/base/example-alternate-text-for-an-image.dita
@@ -7,9 +7,6 @@
     <conbody>
         <p>The following code sample references an image <filepath>workflow.png</filepath>.
             Alternate text describes the workflow that is shown in the image.</p>
-    <draft-comment author="Kristen J Eberlein" time="09 June 2022">
-      <p>I think we should include the image.</p>
-    </draft-comment>
     <codeblock>&lt;image href="workflow.png">
   &lt;alt>The image is a workflow diagram that shows a ticketing workflow.
        The initial status is "Open". From there, the ticket can move to
diff --git a/specification/dita-2.0-key-definitions-cover-pages.ditamap b/specification/dita-2.0-key-definitions-cover-pages.ditamap
index ea9a8c03..ca8a8cc7 100644
--- a/specification/dita-2.0-key-definitions-cover-pages.ditamap
+++ b/specification/dita-2.0-key-definitions-cover-pages.ditamap
@@ -9,18 +9,18 @@
     <!-- Make common variable content available -->
     <topicref href="common/conref-cover-pages.dita" processing-role="resource-only"/>
     <keydef keys="stage">
-      <!--Used in the master maps as a title-->
+      <!--Used in the mains maps as a title-->
       <!-- Also used in the "Citation format" section.-->
       <topicmeta>
         <keywords>
-          <keyword>Working Draft 25</keyword>
+          <keyword>Working Draft 26</keyword>
         </keywords>
       </topicmeta>
     </keydef>
     <keydef keys="stage-date">
       <topicmeta>
         <keywords>
-          <keyword>05 April 2022</keyword>
+          <keyword>13 June 2022</keyword>
         </keywords>
       </topicmeta>
     </keydef>