From 06d327c2c79d30b282563db3e36b7cd8ed60fde0 Mon Sep 17 00:00:00 2001 From: Bert Bos Date: Fri, 30 Aug 2024 17:12:36 +0200 Subject: [PATCH] Removed some todo's, added a short timeline, added chnages from the previous charter. --- 2024/sdw-wg.html | 50 ++++++++++++++---------------------------------- 1 file changed, 14 insertions(+), 36 deletions(-) diff --git a/2024/sdw-wg.html b/2024/sdw-wg.html index 8ac53b8..7dee71e 100644 --- a/2024/sdw-wg.html +++ b/2024/sdw-wg.html @@ -153,12 +153,12 @@

PROPOSED Spatial Data on the Web Working Group Teleconferences: weekly
Face-to-face: - The WG will meet in conjunction with the relevant + The WG will meet in conjunction with the relevant - OGC Working Group(s) during OGC's Member Meetings (up to 3 per year). + OGC Working Group(s) during OGC's Member Meetings (up to 3 per year).
- Optionally during - the W3C's annual Technical Plenary week. + Optionally during + the W3C's annual Technical Plenary week.
additional face-to-face meetings may be scheduled by consent of the participants, usually no more than 3 per year @@ -454,20 +454,16 @@

Other Deliverables

Timeline

-

Put here a timeline view of all deliverables. - -

@@ -487,8 +483,7 @@

Success Criteria

There should be testing plans for each specification, starting from the earliest drafts. -

Consider adopting a healthy testing - policy, such as: To promote interoperability, all +

To promote interoperability, all changes made to specifications in Candidate Recommendation or to features that have deployed implementations should have tests. Testing efforts should be conducted via the @@ -500,10 +495,7 @@

Success Criteria

known security and privacy implications for implementers, Web authors, and end users. -

For specifications of technologies that - directly impact user experience, such as content - technologies, as well as protocols and APIs which impact - content: Where appropriate, specifications should contain a section on +

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 @@

Coordination

will be made, per the W3C Process Document: -

In addition to the above catch-all reference to - horizontal review which includes accessibility review, please - check with chairs and staff contacts of the Accessible Platform - Architectures Working Group to determine if an - additional liaison statement with more specific information - about concrete review issues is needed in the list below. -

W3C Groups

@@ -649,12 +634,7 @@

OGC Groups

External Organizations

-
-
[other name] Working - Group - -
[specific nature of liaison] -
+

None.

@@ -840,9 +820,7 @@

Charter History

[dd monthname yyyy] -

[description of change to charter, - with link to new deliverable item in charter] Note: use the class new for - all new deliverables, for ease of recognition. +

Narrowed the scope to work related to ontologies. Dropped Time Ontology,, Best Practices, WebVMT and Responsible Use of Spatial Data. Added GeoDCAT, OGC GeoSPARQL and Coordinate Reference System Ontology