This is a draft only, has no formal standing and should not be cited. However; the hope is that this will evolve into the charter for a joint W3C/OGC Working Group. Negotiations between the two organizations to facilitate this are at an advanced stage but are not yet finalized and therefore such an agreement should not be considered to exist.

Comments on this charter are welcome via public-gdw-comments@w3.org [subscribe] [archive].

W3C  Open Geospatial Consortium Logo

Spatial Data on the Web Working Group Charter

What are the best examples of data-driven Web applications you've ever seen? The updates to Open Street Map after the Haiti earthquake? The mapping of all 9,966,539 buildings in the Netherlands? The NHS Prescription data? Things like SF Park that help you 'park your car smarter' in San Francisco using real time data? The maps, satellite and street level images offered by search engines?

All these and many, many more data-driven applications have geospatial information (GI) at their core; it is a major element in defining context for knowledge that can then be exposed in many different ways to end users. The societal, economic and scientific benefits of integrating GI into commercial and institutional processes is potentially huge. Very often the common factor across multiple datasets is the location data, and maps are crucial in visualizing correlations between data sets that may otherwise be hidden.

Having a clear strategy as to how GI is best integrated with data on the Web is paramount. Commercial operators, including search engines, invest a great deal of time and effort in generating geographical databases which are mirrors to Web content with the geographical context often added manually or at best semi-automatically. This process would be substantially aided if data were published on the Web with the appropriate geographic information at the source, thus allowing discovery and access using the standard mechanisms of the Web.

'Geo' is not the only spatial data. In healthcare, for example, polygons may represent pathology tissue segmentation extractions that can be subjected to spatial analysis. Whilst prioritizing geospatial use cases, in so far as is practical, the WG will take account of the needs of other users of spatial technologies.

The term coverage is used to describe a feature whose properties vary with space and / or time; for example, the variation of air temperature within a given geographic region, or the variation of flow rate with time at a hydrological monitoring station.

The Linking Geospatial Data workshop recognized that many relevant standards already exist. These include informal 'community standards' that enjoy widespread adoption (GeoJSON being the prime example) and others for which the formal standardization process has not been completed. Where standards have been completed there are competing ideas and engineers are often unsure which ones to adopt. With these factors in mind, the mission of the joint OGC/W3C Spatial Data on the Web working group is to clarify and formalize the standards landscape around spatial data on the Web. In particular:

  1. to determine how spatial information can best be integrated with other data on the Web;
  2. to determine how machines and people can discover that different facts in different datasets relate to the same place, especially when 'place' is expressed in different ways and at different levels of granularity;
  3. to identify and assess existing methods and tools and then create a set of best practices for their use;
  4. to complete the standardization of informal technologies already in widespread use.

Within W3C, the Spatial Data on the Web WG is part of the Data Activity.

@@@Join the Spatial Data on the Web Working Group@@@.

End date 30 July 2016
Confidentiality Proceedings are public
Initial Chairs Kerry Taylor, CSIRO
Ed Parsons, Google
Initial Team Contacts
(FTE %: 20)
Phil Archer
Usual Meeting Schedule Teleconferences: weekly
Face-to-face: twice annually, ideally alternating between an OGC TC and W3C's TPAC

Scope

The scope of the Spatial Data on the Web Working Group will focus specifically on Web technologies as they may be applied to location. Where relevant, it will promote Linked Data using the 5 Stars of Linked Data paradigm, but this will not be to the exclusion of other technologies.

Out of Scope

The Spatial Data on the Web Working Group must be mindful of the needs of front end Web developers, (see Dependencies & Liaisons) however, it will not develop any geospatial or map rendering technologies. In other words, this WG is focused specifically on the intersection of the issues facing OGC and W3C members.

Relationship with OGC

The SDWWG is a joint W3C/OGC Working Group Outputs will be co-branded with copyright owned by both standards bodies. W3C and OGC will adapt their respective contribution copyright regime in order to allow the contributions to be published by both standards bodies.

Organizations that are members of only one standards body will be strongly encouraged to join the other. It is expected that the WG's chairs and editors will represent organizations that are members of both standards bodies.

The working group will operate according to the Memoradum of Understanding signed by W3C and OGC on DATE.

Deliverables

The titles of the deliverables are not final; the Working Group will have to decide on the final titles as well as the structures of the documents. The Working Group may also decide to merge some deliverables into one document or produce several documents that together constitute one of the deliverables.

Where deliverables build on prior work, any variance developed by the Spatial Data on the Web WG will be backwards compatible with the existing work. The aim is to formalize existing work, not to replace or compete with it.

Subject to its capacity, the working group may choose to develop additional relevant vocabularies and specifications in response to community demand. For example: a standard method for converting between spatial ontologies; methods to access a subset of a large dataset in terms of its spatial component.

Best Practice Success Criteria

To advance to Proposed Recommendation, evidence will be adduced that each of the best practices have been followed or recommended in at least two environments.

Vocabulary Success Criteria

To advance to Proposed Recommendation, evidence will be adduced that each term in the vocabulary has been used in multiple environments. This will be most strictly applied to terms developed by the WG, less strictly to terms originating from the prior work whose use or otherwise may not be knowable.

Milestones

Milestones
Note: The group will document significant changes from this initial schedule on the group home page.
Deliverable FPWD LC CR PR Rec
Use Cases and Requirements December 2014 March 2015
Best Practices March 2015 September 2015 December 2015 April 2016 June 2016
Time Ontology in OWL March 2015 September 2015 December 2015 April 2016 June 2016
Semantic Sensor Network June 2015 December 2015 February 2016 April 2016 June 2016
Coverage in Linked Data June 2015 December 2015 February 2016 April 2016 June 2016

Timeline View Summary

Dependencies and Liaisons

W3C Groups

Data on the Web Best Practices Working Group
Coordinate on best practices, especially in areas of potential overlap.
Geolocation API Working Group
The group defining the Level 2 Geolocation API to cover geofencing, and the Device Orientation API.
Annotations WG
Particularly with reference to annotating maps
SVG Working Group
Ensure compatibility with SVG
Web Applications Working Group
Ensure spatial data is readily and conveniently available to application developers.
Internationalization Activity
Ensure that multilinguality concerns are properly reflected in the best practices. The WG should also take note of the work of the Best Practices for Multilingual Linked Open Data Community Group.
Privacy Interest Group
Ensure that the privacy concerns are properly included in the best practices.
Data Activity Coordination Group
Ensure that the WG operates in cooperation with others working in related fields.
RDF Stream Processing
Not directly in scope for the SPWG but relevant to the Web of Things which is in turn highly relevant.

OGC Groups

Bart to supply suitable list here

Other Groups & Projects

SmartOpenData, GeoKnow, MELODIES, DaPaas, InGeoCloudS
A range of EU-funded projects are working in closely related areas, the list above is not exhaustive.
stSPARQL
The Strabon platform implements stSPARQL that offer a number of spatial and temporal extension functions.

Furthermore, the Spatial Data on the Web Working Group expects to follow these W3C Recommendations:

Participation

To be successful, the Spatial Data on the Web Working Group is expected to have 20 or more active participants for its duration. To get the most out of this work, participants should expect to devote several hours a week; for budgeting purposes, we recommend at least half a day a week. For chairs and document editors the commitment will be higher, say, 1-2 days a week. Participants who follow the work less closely should be aware that if they miss decisions through inattention further discussion of those issues may be ruled out of order. However, most participants follow some areas of discussion more closely than others, and the time needed to stay in good standing therefore varies from week to week. The Working Group will also allocate the necessary resources for building Test Suites for each specification.

Communication

This group primarily conducts its work on the @@@public mailing list@@@. Administrative tasks may be conducted in @@@Member-only@@@ communications. Comments on the group's work will be welcome via public-gdw-comments@w3.org [subscribe] [archive]

Information about the group (deliverables, participants, face-to-face meetings, teleconferences, etc.) is available from the @@@Spatial Data on the Web Working Group@@@ home page.

Decision Policy

As explained in the Process Document (section 3.3), this group will seek to make decisions when there is consensus. When the Chair puts a question and observes dissent, after due consideration of different opinions, the Chair should record a decision (possibly after a formal vote) and any objections, and move on.

A formal vote should allow for remote asynchronous participation—using, for example, email and/or web-based survey techniques. Any resolution taken in a face-to-face meeting or teleconference is to be considered provisional until 5 working days after the publication of the resolution in draft minutes sent to the group's mailing list.

This charter is written in accordance with Section 3.4, Votes of the W3C Process Document and includes no voting procedures beyond what the Process Document requires.

Patent Policy

This Working Group operates under the W3C Patent Policy (5 February 2004 Version). To promote the widest adoption of Web standards, W3C seeks to issue Recommendations that can be implemented, according to this policy, on a Royalty-Free basis.

For more information about disclosure obligations for this group, please see the W3C Patent Policy Implementation.

About this Charter

This charter for the Spatial Data on the Web Working Group has been created according to section 6.2 of the Process Document. 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.


$Id: geo-charter.html,v 1.27 2014-07-14 08:51:39 phila Exp $