This is the repository for the Spatial Data on the Web Working Group, a collaborative project between W3C and OGC.
The repo has been used for developing editors drafts of the Working Group's deliverables and related resources.
The Working Group follows in the footsteps of the Spatial Data on the Web Interest Group and the Spatial Data on the Web Working Group, and some of the material in this repository was initially developed and published by these predecessors.
Work on a new edition of the Semantic Sensor Network (SSN) Ontology is in a separate repo: https://github.com/w3c/sdw-sosa-ssn.
Name | URL |
---|---|
Group homepage | https://www.w3.org/2021/sdw/ |
SDW Strategy Funnel | https://github.com/w3c/strategy/projects/2?card_filter_query=label%3Ageospatial |
SDW Projects | https://github.com/w3c/sdw/projects |
Intro for new members | https://github.com/w3c/sdw/blob/gh-pages/memberwelcome.md |
Each deliverable has its own folder. The issue tracker uses labels to distinguish between work items. The current structure is as follows:
- UseCases
-
The Spatial Data on the Web Use Cases & Requirements document that guided the Spatial Data on the Web Working Group.
Editor's Draft
Working Group Note - bp
-
The Spatial Data on the Web Best Practices Note initially developed by the Spatial Data on the Web Working Group.
Editor's Draft
Working Group Note
Meeting minutes - coverage-json
-
The Overview of the CoverageJSON format Note initially developed by the Spatial Data on the Web Working Group.
Editor's Draft
Working Group Note - eo-qb
-
The Note on Publishing and Using Earth Observation Data with the RDF Data Cube and the Discrete Global Grid System initially developed by the Spatial Data on the Web Working Group.
Editor's Draft
Working Group Note - jwoc
-
The draft charter of the Spatial Data on the Web Interest Group. Used to discuss possible updates to the scope of the group.
Draft charter
Approved IG charter - meetings
-
Logistic and agenda information for face-to-face meetings
Note: current online meeting details are in the W3C SDW calendar. - proposals
-
Container for new topic proposals under discussion in the IG.
WebVMT: The Web Video Map Tracks Format - qb4st
-
The QB4ST: RDF Data Cube extensions for spatio-temporal components document initially developed by the Spatial Data on the Web Working Group.
Editor's Draft
Working Group Note - responsible-use
-
Working folder for the Responsible use of Geo document that discusses ethic issues of Geo Technology.
Editor's Draft
W3C Interest Group Note - roadmap
- Working folder for the SDW roadmap.
- ssn-extensions
-
Extensions to the SSN ontology to enable linking directly to the ultimate feature-of-interest alongside the link to the (proximate) feature-of-interest; and homogeneous collections of observations.
Editor's Draft
Working Draft - ssn-usage
-
The implementation report for the Semantic Sensor Network Ontology, initially developed by the Spatial Data on the Web Working Group.
Implementation report - ssn-usecases
-
A use cases document describing the reasons and new use cases for a proposed update to SSN in 2023.
SSN Use cases - ssn
-
This folder is no longer used actively. It contains the state of things as they were left after SOSA/SSN was published by the Spatial Data on the Web Working Group in October 2017. Development of The Semantic Sensor Network Ontology Recommendation continues in a separate Github repository "sdw-sosa-ssn".
Editor's Draft
W3C Recommendation - time-aggregates
-
Extension to the Time Ontology in OWL defining a class for temporal aggregates.
Editor's Draft
W3C Interest Group Note - time-entity-relations
-
Extension to the Time Ontology in OWL defining additional relations between time intervals.
Editor's Draft
W3C Interest Group Note - time
-
The Time Ontology in OWL Recommendation initially developed by the Spatial Data on the Web Working Group.
Editor's Draft
W3C Candidate Recommendation
The published-snapshots
, stats-bp
and subsetting
folder should be considered as historical.
Comments are welcome as issues raised against this repository. WG members should use the primary [email protected] mailing list [archive].