Merge pull request #345 from himorin/charter-2023

JL-TF charter 2023-2024

charter/index.html

@@ -34,7 +34,7 @@
 
 <h1 id="title"> Japanese Layout Task Force Charter</h1>
 <p class="mission">The <strong>mission</strong> of this task force  is to discuss and document gaps and requirements, and offer advice for the layout and presentation of text in   Japanese  when those languages  are used by Web standards and technologies, such as HTML,  CSS, Mobile Web, Digital Publications and Unicode. </p>
-<p class="mission">The Task Force is part of the W3C Internationalization Interest Group. The Task Force will report the results of its activities as a group back to the <a href="https://w3c.github.io/i18n-activity/i18n-wg/">W3C Internationalization Working Group</a>, as well as to other relevant groups and to the W3C membership and community.</p>
+<p class="mission">The Task Force is part of the W3C Internationalization Interest Group. The Task Force will report the results of its activities as a group back to the <a href="https://www.w3.org/International/i18n-activity/i18n-wg/">W3C Internationalization Working Group</a>, as well as to other relevant groups and to the W3C membership and community.</p>
 <p class="mission">This charter is intended to reflect the current direction of the group, so that there is common agreement. It may be altered at any point in order to reflect new priorities or work items.</p>
 <div class="noprint">
 <p class="join"><a href="https://w3c.github.io/jlreq/home#participate--%E5%8F%82%E5%8A%A0%E3%81%99%E3%82%8B%E6%96%B9%E6%B3%95">Join the Japanese Text Layout Task Force</a>.</p>
@@ -43,12 +43,12 @@ <h1 id="title"> Japanese Layout Task Force Charter</h1>
   <tbody>
     <tr id="Duration">
       <th rowspan="1" colspan="1">End date</th>
-      <td rowspan="1" colspan="1">31 December 2022</td>
+      <td rowspan="1" colspan="1">31 December 2024</td>
     </tr>
     <tr>
       <th rowspan="1" colspan="1">Confidentiality</th>
       <td rowspan="1" colspan="1">Proceedings are <a
-        href="https://www.w3.org/2020/Process-20200915/#confidentiality-levels">public</a></td>
+        href="https://www.w3.org/Consortium/Process/#confidentiality-levels">public</a></td>
     </tr>
     <tr>
       <th rowspan="1" colspan="1">Initial Chair</th>
@@ -62,8 +62,7 @@ <h1 id="title"> Japanese Layout Task Force Charter</h1>
     <tr>
       <th rowspan="1" colspan="1">Usual Meeting Schedule</th>
       <td rowspan="1" colspan="1">Teleconferences: On an as-needed basis. Preferably, a minimum of one status meeting per month.<br/>
-         Face-to-face meetings: On an as-needed basis.<br/>
-        Video Conferences: On an as-needed basis.<br/></td>
+         Face-to-face meetings: On an as-needed basis.<br/></td>
     </tr>
   </tbody>
 </table>
@@ -81,7 +80,9 @@ <h2 id="deliverables">Deliverables</h2>
 <p>The Japanese Text Layout Task Force will not produce Recommendation-track deliverables but will work on or produce documents that can be published by the Internationalization Working Group as Working Group Notes. Such work is expected to include the following. The completion of the work depends upon resource availability.</p>
 <ul>
 <li>Augment the contents of the <a href="https://www.w3.org/TR/jpan-gap/" rel="nofollow"> gap-analysis document</a>, which is one of many similar documents that radiate out from the <a href="https://www.w3.org/International/typography/gap-analysis/language-matrix.html" rel="nofollow">language matrix</a> to help us track areas where better support is needed. The gap analysis document uses a standard structure to list issues that content users and content authors face relating to particular apects of text layout, provide pointers to tests, and prioritise the importance of the barriers documented.</li>
-<li>Update the <a href="https://www.w3.org/TR/jlreq/">Japanese Layout Requirements</a> document to fix errata, or improve the accessibility and user-friendliness of the document.</li>
+<li>Develop the <a href="https://github.com/w3c/jlreq-d/">Requirements for Japanese Digital Text Layout</a> document to capture requirements and new items to be considered in digital text, better accessibility using digital features, and necessity technologies for Japanese text layout in internalionalized environment.</li>
+<li>Develop the <a href="https://w3c.github.io/ruby-t2s-req/">Text to Speech of Electronic Documents Containing Ruby: User Requirements</a> to capture accessibility user requirements for Ruby.</li>
+<li>Update the <a href="https://www.w3.org/TR/jlreq/">Japanese Layout Requirements</a> document to fix errata.</li>
 <li>Update the <a href="https://www.w3.org/TR/simple-ruby/">Rules for Simple Placement of Japanese Ruby</a> document to fix errata.</li>
 <li>Produce other documents advising standards developers and application developers on how to cater for Japanese needs. Some of those documents may be developed elsewhere, such as at the Advanced Publishing Lab in Japan, and brought to this group for review and subsequent publication.</li>
 </ul>
@@ -123,9 +124,6 @@ <h2 id="participation">Participation</h2>
 <p><strong>Followers</strong> are subscribed to the <a href="https://lists.w3.org/Archives/Public/public-i18n-japanese/" rel="nofollow">public-i18n-japanese</a> mailing list, where they can track discussions, and contribute opinions via the <a href="https://github.com/w3c/jlreq/issues">GitHub issue list</a>. Rather than just 'Watch' the GitHub repository, it is best to subscribe to the  mailing list, because that list is notified once a day (in digest form) about activity in the jlreq repository, but also about  activity for other W3C Working Group issues related to Japanese. (Participants are expected to use github issues rather than the mailing list to send feedback.)</p>
 <p><strong>Task force members</strong> are expert contributors who participate actively in producing the work of the group, contributing text and advice to create the outputs, and participating in any meetings. These people are subscribed to the task force group by W3C staff.</p>
 <p>All TF members and people making contributions (via issues or pull requests) must read and agree with <a href="https://github.com/w3c/jlreq/blob/gh-pages/CONTRIBUTING.md">CONTRIBUTING.md</a>.</p>
-<p>Participants are reminded of the <a
-href="https://www.w3.org/2005/10/Process-20051014/groups.html#good-standing">Good
-Standing requirements</a> of the W3C Process.</p>
 </div>
 
 <div class="communication">
@@ -135,7 +133,7 @@ <h2 id="communication">Communication</h2>
 <p>The <a href="https://lists.w3.org/Archives/Public/public-i18n-japanese/">public-i18n-japanese@w3.org</a> list receives notifications of changes in the jlreq repository, and also of changes to issues in other repositories when those issues are tagged with a jlreq label. This includes the CSS and HTML repositories, amongst others. That mailing list should not be used for technical discussion. The public-i18n-cjk list must archive or point to minutes and summaries of all teleconferences and face-to-face meetings. Meeting minutes will list all attendees at a given meeting.</p>
 <p>An administrative list, <a href="https://lists.w3.org/Archives/Public/public-jlreq-admin/">public-jlreq-admin</a>, will be used for internal communication about practical matters, such as meeting agenda, which should be published before each teleconference or face-to-face meeting.</p>
 
-<p>The group will use the <a href="https://www.w3.org/International/"> W3C Internationalization  home page </a>to provide updated public information about its activities.
+<p>The group will use the <a href="https://www.w3.org/International/">W3C Internationalization home page</a> to provide updated public information about its activities.
 </p>
 
 <p> Information about the group (deliverables, participants, face-to-face meetings, teleconferences, etc.) is available from the <a href="https://github.com/w3c/jlreq">jlreq GitHub repository</a>.</p>
@@ -147,24 +145,29 @@ <h2 id="communication">Communication</h2>
 <h2 id="decisions">Decision Policy</h2>
 
 <p>As explained in the Process Document (<a
-href="https://www.w3.org/Consortium/Process/policies#Consensus">section 3.3</a>),
+href="https://www.w3.org/Consortium/Process/#Consensus">section 5.2.1</a>),
 this group will seek to make decisions when there is consensus. In cases where there is a need to formally produce a group resolution about a particular issue, its Chair will put a question about the issue to the group and gather responses (including any formal objections); then, after due consideration of all the responses, the Chair will record a group resolution (possibly after a formal vote and also along with responding to any formal objections).</p>
 </div>
 
 <div class="patent">
 <h2 id="patentpolicy">Patent Policy </h2>
 
-<p>Participants in the Japanese Text Layout Task Force are obligated to comply with W3C patent-disclosure policy as outlined  in <a href="https://www.w3.org/Consortium/Patent-Policy-20200915/#sec-Disclosure">Section 6</a> of the W3C Patent Policy document. Although the Japanese Text Layout Task Force is not chartered to produce Recommendation-track documents that themselves require patent disclosure, participants in the group are nevertheless obligated to comply with W3C patent-disclosure policy for any Recommendation-track specifications that they review or comment on.</p>
+<p>Participants in the Japanese Text Layout Task Force are obligated to comply with W3C patent-disclosure policy as outlined in <a href="https://www.w3.org/Consortium/Patent-Policy-20200915/#sec-Disclosure">Section 6</a> of the W3C Patent Policy document. Although the Japanese Text Layout Task Force is not chartered to produce Recommendation-track documents that themselves require patent disclosure, participants in the group are nevertheless obligated to comply with W3C patent-disclosure policy for any Recommendation-track specifications that they review or comment on.</p>
         <p>For more information about disclosure obligations for this group, please see
 the <a href="https://www.w3.org/2004/01/pp-impl/">W3C Patent Policy
 Implementation</a>.</p>
 </div>
 
+<section id="licensing">
+<h2>Licensing</h2>
+<p>This Task Force will use the <a href="https://www.w3.org/Consortium/Legal/copyright-software">W3C Software and Document license</a> for all its deliverables.</p>
+</section>
+
 <h2 id="about">About this Charter</h2>
 
 <p>This charter for the Japanese Layout Task Force within the Internationalization Interest Group has been
-created according to <a href="https://www.w3.org/Consortium/Process/groups#GAGeneral">section
-  6.2</a> of the <a href="https://www.w3.org/Consortium/Process">Process Document</a>.  In the event
+created according to <a href="https://www.w3.org/Consortium/Process/#GAGeneral">section
+  3.4</a> of the <a href="https://www.w3.org/Consortium/Process">Process Document</a>.  In the event
 of a conflict between this document or the provisions of any charter and the W3C Process, the W3C
 Process shall take precedence.</p>
 
@@ -176,7 +179,7 @@ <h3 id="history">
   The following table lists details of all changes from the initial
   charter, per the <a href=
   "https://www.w3.org/Consortium/Process/#CharterReview">W3C Process
-  Document (section 5.2.3)</a>:
+  Document (section 4.3)</a>:
 </p>
 <table class="history">
   <tbody>
@@ -221,6 +224,19 @@ <h3 id="history">
         Added <a href="https://www.w3.org/TR/simple-ruby/">Rules for Simple Placement of Japanese Ruby</a>.
       </td>
     </tr>
+    <tr>
+      <th>
+        Rechartered
+      </th>
+      <td>
+      </td>
+      <td>
+        31 December 2024
+      </td>
+      <td>
+        Added <a href="https://github.com/w3c/jlreq-d/">Requirements for Japanese Digital Text Layout</a> and <a href="https://w3c.github.io/ruby-t2s-req/">Text to Speech of Electronic Documents Containing Ruby: User Requirements</a>.
+      </td>
+    </tr>
   </tbody>
 </table>