Removed some todo's, added a short timeline, added chnages from the p…

…revious charter.

2024/sdw-wg.html

@@ -153,12 +153,12 @@ <h1 id=title>PROPOSED Spatial Data on the Web Working Group
 
             <td> <strong>Teleconferences:</strong> weekly <br>
               <strong>Face-to-face:</strong>
-              <i class=todo>The WG will meet in conjunction with the relevant
+              The WG will meet in conjunction with the relevant
                 <a href="https://www.ogc.org/about-ogc/committees/swg/">
-                  OGC Working Group(s)</a> during OGC's Member Meetings (up to 3 per year).</i>
+                  OGC Working Group(s)</a> during OGC's Member Meetings (up to 3 per year).
               <br>
-              <i class=todo>Optionally during
-                the W3C's annual Technical Plenary week.</i>
+              Optionally during
+                the W3C's annual Technical Plenary week.
               <br>
               additional face-to-face meetings may be scheduled
               by consent of the participants, usually no more than 3 per year
@@ -454,20 +454,16 @@ <h3>Other Deliverables</h3>
       <section id=timeline>
         <h3>Timeline</h3>
 
-        <p class=todo>Put here a timeline view of all deliverables.
-
-        <ul class=todo>
-          <li>Month YYYY: First teleconference
-
-          <li>Month YYYY: First face-to-face meeting
+        <ul>
+          <li>Oct 2024: First teleconference
 
-          <li>Month YYYY: Requirements and Use Cases for FooML
+          <li>Dec 2024: CR for Semantic Sensor Network Ontology
 
-          <li>Month YYYY: FPWD for FooML
+          <li>Dec 2024: CR for GeoSPARQL
 
-          <li>Month YYYY: Requirements and Use Cases for BarML
+	  <li>Mar 2025: CR for Coordinate Reference System Ontology
 
-          <li>Month YYYY: FPWD FooML Primer
+          <li>Dec 2025: CR for GeoDCAT
         </ul>
       </section>
     </section>
@@ -487,8 +483,7 @@ <h2>Success Criteria</h2>
       <p>There should be testing plans for each specification,
         starting from the earliest drafts.
 
-      <p><span class=todo>Consider adopting a healthy testing
-          policy, such as:</span> To promote interoperability, all
+      <p>To promote interoperability, all
         changes made to specifications in Candidate Recommendation or
         to features that have deployed implementations should have <a
           href="https://www.w3.org/2019/02/testing-policy.html">tests</a>. Testing efforts should be conducted via the
@@ -500,10 +495,7 @@ <h2>Success Criteria</h2>
         known security and privacy implications for implementers, Web
         authors, and end users.
 
-      <p><i class=todo>For specifications of technologies that
-          directly impact user experience, such as content
-          technologies, as well as protocols and APIs which impact
-          content: </i> Where appropriate, specifications should contain a section on
+      <p>Where appropriate, specifications should contain a section on
         accessibility that describes the benefits and impacts,
         including ways specification features can be used to address
         them, and recommendations for maximising accessibility in
@@ -545,13 +537,6 @@ <h2>Coordination</h2>
         will be made, per the <a href="https://www.w3.org/policies/process/#WGCharter">W3C
           Process Document</a>:
 
-      <p class=todo>In addition to the above catch-all reference to
-        horizontal review which includes accessibility review, please
-        check with chairs and staff contacts of the <a href="https://www.w3.org/WAI/APA/">Accessible Platform
-          Architectures Working Group</a> to determine if an
-        additional liaison statement with more specific information
-        about concrete review issues is needed in the list below.
-
       <section>
         <h3 id=w3c-coordination>W3C Groups</h3>
 
@@ -649,12 +634,7 @@ <h3 id=ogc-coordination>OGC Groups</h3>
       <section>
         <h3 id=external-coordination>External Organizations</h3>
 
-        <dl>
-          <dt><a href=""><i class=todo>[other name]</i> Working
-              Group</a>
-
-          <dd><i class=todo>[specific nature of liaison]</i>
-        </dl>
+	<p>None.
       </section>
     </section>
 
@@ -840,9 +820,7 @@ <h3> Charter History</h3>
               <td> <i class=todo>[dd monthname yyyy]</i>
 
               <td>
-                <p class=todo>[description of change to charter,
-                  with link to new deliverable item in charter] <b>Note:</b> use the class <code>new</code> for
-                  all new deliverables, for ease of recognition.
+                <p>Narrowed the scope to work related to ontologies. Dropped <cite>Time Ontology,</cite>, <cite>Best Practices,</cite> <cite>WebVMT</cite> and <cite>Responsible Use of Spatial Data.</cite> Added <cite class=new>GeoDCAT,</cite>  <cite class=new>OGC GeoSPARQL</cite> and <cite class=new>Coordinate Reference System Ontology</cite>
         </table>
       </section>