Clarify the role of the tool and of human collaborators in summarizin…

…g changes to content. SHA: bf2805a Reason: push, by jasonjgw Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
w3c · Apr 1, 2024 · 088c4f1 · 088c4f1
1 parent 17ae6fe
commit 088c4f1
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/index.html b/index.html
@@ -149,15 +149,15 @@
   "group": "apa",
   "github": "w3c/ctaur",
   "maxTocLevel": 4,
-  "publishISODate": "2024-03-29T00:00:00.000Z",
-  "generatedSubtitle": "W3C Editor's Draft 29 March 2024"
+  "publishISODate": "2024-04-01T00:00:00.000Z",
+  "generatedSubtitle": "W3C Editor's Draft 01 April 2024"
 }</script>
 <link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/2021/W3C-ED"></head>
   <body class="h-entry informative"><div class="head">
     <p class="logos"><a class="logo" href="https://www.w3.org/"><img crossorigin="" alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C" width="72">
   </a></p>
     <h1 id="title" class="title">Collaboration Tools Accessibility User Requirements</h1> 
-    <p id="w3c-state"><a href="https://www.w3.org/standards/types#ED">W3C Editor's Draft</a> <time class="dt-published" datetime="2024-03-29">29 March 2024</time></p>
+    <p id="w3c-state"><a href="https://www.w3.org/standards/types#ED">W3C Editor's Draft</a> <time class="dt-published" datetime="2024-04-01">01 April 2024</time></p>
     <details open="">
       <summary>More details about this document</summary>
       <dl>
@@ -426,7 +426,7 @@ <h1 id="title" class="title">Collaboration Tools Accessibility User Requirements
           <li><strong>User Need 14:</strong> Users with learning or cognitive disabilities, and users of assistive technologies sometimes need support in identifying revisions and understanding their effects.</li>
           <li><strong>REQ 14:</strong> Provide a mechanism by which authors can identify a series of changes to the content, and associate this change set with an explanatory comment.</li>
         </ul>
-        <div class="note" role="note" id="issue-container-generatedID-3"><div role="heading" class="note-title marker" id="h-note-2" aria-level="4"><span>Note</span></div><p class="">Although it may be useful to support automatic summary generation by technologies such as large language models, the state of the art as of the time of publication suggests implementers should exercise caution. Inaccurate summaries of changes may be worse for users than their absence. For this reason, summaries written by human authors are generally preferable to those authored by automated large language models.</p></div>
+        <div class="note" role="note" id="issue-container-generatedID-3"><div role="heading" class="note-title marker" id="h-note-2" aria-level="4"><span>Note</span></div><p class="">Although it may be useful to support automatic summary generation by technologies such as large language models, the state of the art as of the time of publication suggests implementers should exercise caution. Inaccurate summaries of changes may be worse for users than their absence. For this reason, summaries written by human authors are generally preferable to those authored by automated large language models. Writing accurate, clear and comprehensible summaries depends on the cooperation of participants in a content creation project (section <a href="#social" class="sec-ref"><bdi class="secno">1.5 </bdi>Social Considerations</a>). The most that can be achieved in designing the collaborative software environment is to encourage this practice.</p></div>
       </section>
     </section>
     <section id="notify"><div class="header-wrapper"><h2 id="x7-notifications-and-messages"><bdi class="secno">7. </bdi>Notifications and Messages</h2><a class="self-link" href="#notify" aria-label="Permalink for Section 7."></a></div>