First sync round, apart from deliverables.

Author: iherman

2024/json-ld-wg/index.html

@@ -55,7 +55,7 @@
           <li><a href="#background">Background</a></li>
           <li><a href="#scope">Scope</a></li>
           <li><a href="#deliverables">Deliverables</a></li>
-		  <li><a href="#success-criteria">Success Criteria</a></li>
+		      <li><a href="#success-criteria">Success Criteria</a></li>
           <li><a href="#coordination">Coordination</a></li>
           <li><a href="#participation">Participation</a></li>
           <li><a href="#communication">Communication</a></li>
@@ -73,15 +73,20 @@
 
     <main>
       <h1 id="title"><i class=todo>DRAFT</i> JSON-LD Working Group Charter</h1>
+      <!-- replace DRAFT with PROPOSED when the AC review starts -->
+      <!-- delete PROPOSED after AC review completed -->
 
       <p class="mission">The <strong>mission</strong> of the <a href="https://www.w3.org/groups/wg/json-ld">JSON-LD Working Group</a> is to maintain and extend the <a href="https://www.w3.org/groups/wg/json-ld/publications">family of JSON-LD 1.1 Recommendations</a> and related Working Group Notes.</p>
 
       <div class="noprint">
         <p class="join"><a href="https://www.w3.org/groups/wg/json-ld/join">Join the JSON-LD Working Group.</a></p>
       </div>
 
+      <!-- replace "draft charter" with "proposed charter" when the AC review starts -->
+      <!-- replace GitHub link and issues link to the specific charter in GH and its issues repo -->
+      <!-- delete the GH link after AC review completed -->
       <p class=todo style="padding: 0.5ex; border: 1px solid green">
-        This proposed charter is available on <a href="https://github.com/json-ld/json-ld-wg-charter">GitHub</a>.
+        This draft charter is available on <a href="https://github.com/json-ld/json-ld-wg-charter">GitHub</a>.
         Feel free to raise <a href="https://github.com/json-ld/json-ld-wg-charter/issues">issues</a>.
       </p>
 
@@ -212,7 +217,8 @@ <h2>
 
         <p>Updated document status is available on the <a href="https://www.w3.org/groups/wg/json-ld/publications">group publication status page</a>.</p>
 
-        <p><i>Draft state</i> indicates the state of the deliverable at the time of the charter approval.</p>
+        <p><i>Draft state</i> indicates the state of the deliverable at the time of the charter approval.
+        <i>Expected completion</i> indicates when the deliverable is projected to become a Recommendation, or otherwise reach a stable state.</p>
 
         <section id="normative">
           <h3>
@@ -340,8 +346,11 @@ <h3>Timeline</h3>
 	<section id="success-criteria">
 	  <h2>Success Criteria</h2>
 
-	  <p>In order to advance to <a href="https://www.w3.org/policies/process/#RecsPR" title="Proposed Recommendation">Proposed Recommendation</a>, each normative specification is expected to have <a href="https://www.w3.org/policies/process/#implementation-experience">at least two independent interoperable implementations</a> of every feature defined in the specification, where interoperability can be verified by passing open test suites.</p>
+	  <p>In order to advance beyond
+		  <a href="https://www.w3.org/policies/process/#RecsCR" title="Candidate Recommendation">Candidate Recommendation</a>, each normative specification is expected to have <a href="https://www.w3.org/policies/process/#implementation-experience">at least two independent interoperable implementations</a> of every feature defined in the specification, where interoperability can be verified by passing open test suites. In order to advance beyond Candidate Recommendation, each normative specification must have an open test suite of every feature defined in the specification.</p>
+
 	  <p>There should be testing plans for each specification, starting from the earliest drafts.</p>
+
     <p>To promote interoperability, all changes made to specifications
       in Candidate Recommendation
       or to features that have deployed implementations
@@ -352,10 +361,13 @@ <h2>Success Criteria</h2>
 
 	  <p>Each specification should contain separate sections detailing all known security and privacy implications for implementers, Web authors, and end users.</p>
 
-    <!-- Design principles -->
-    <p>This Working Group expects to follow the
-    TAG <a href="https://www.w3.org/TR/design-principles/">Web Platform Design Principles</a>.
-    </p>
+    <!-- W3C Statements and Web Platform Design Principles -->
+    <p>This group is expected to be guided by the following documents:</p>
+    <ul>
+      <li><a href="https://www.w3.org/TR/ethical-web-principles/">Ethical Web Principles</a>,</li>
+      <li><a href="https://www.w3.org/TR/privacy-principles/">Privacy Principles</a>,</li>
+      <li><a href="https://www.w3.org/TR/design-principles/">Web Platform Design Principles</a>.</li>
+    </ul>
 
 	</section>
 
@@ -407,10 +419,13 @@ <h2 id="participation">
         </p>
         <p>
           The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in <a href='#communication'>Communication</a>.
+          The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the <a href="https://www.w3.org/policies/patent-policy/">W3C Patent Policy</a>.
         </p>
+
         <p>
-          The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the <a href="https://www.w3.org/policies/patent-policy/">W3C Patent Policy</a>.
+          The Chairs should periodically look through the non-Members who have contributed to the Working Group or the JSON for Linking Data Community Group and consider whether each one should be invited to participate as an <a href="https://www.w3.org/invited-experts/">Invited Expert</a>. If a non-Member contributor would like to participate in meetings, they are encouraged to <i class="todo">[update this link] <a href="https://www.w3.org/groups/wg/TODO/instructions/">apply to be an Invited Expert</a></i>.
         </p>
+
         <p>Participants in the group are required (by the <a href="https://www.w3.org/policies/process/#ParticipationCriteria">W3C Process</a>) to follow the
           W3C <a href="https://www.w3.org/policies/code-of-conduct/">Code of Ethics and Professional Conduct</a>.</p>
       </section>
@@ -426,7 +441,7 @@ <h2>
         The meetings themselves are not open to public participation, however.
         </p>
         <p>
-          Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <a href="">JSON-LD Working Group home page.</a>
+          Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <a href="https://www.w3.org/groups/wg/json-ld">JSON-LD Working Group home page.</a>
         </p>
         <p>
           Most JSON-LD Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.