The OGC seeks comment on GeoSynchronization Best Practices
The Open Geospatial Consortium (OGC®) seeks public comment on the candidate OGC GeoSynchronization Best Practices Document.
Frequently, geospatial content providers must collaborate with outside entities to collect new data and/or update their existing data holdings. This may be the case, for example, when municipal, state/provincial and/or federal agencies synchronize their data with closest-to-source providers. Another case is when content providers are crowdsourcing (see http://en.wikipedia.org/wiki/Crowdsourcing) elements of their data production or supporting volunteer geographic information (VGI).
This candidate OGC Best Practice describes how to use the OGC's open interface and encoding standards to implement services that mediate interaction between geospatial data providers, the content repositories, and the external entities acting as data collectors. Such services support data entry with validation, notification of changes to interested parties and replication of the data content submitted to multiple repositories.
This document defines an OGC Best Practice on a particular technology or approach related to OGC standards. This document is not an OGC standard and may not be referred to as an OGC standard. It is subject to change without notice. However, this document is an official position of the OGC membership on this particular technology topic.
The following organizations submitted this Best Practice to the OGC: The Carbon Project, OpenGeo.org and CubeWerx Inc.
The candidate OGC GeoSynchronization Best Practices document is available for public review and comment below.
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template