The OGC requests comments on the OWS Context Encoding Standard
The Open Geospatial Consortium (OGC®) is seeking comments on the candidate OGC OWS Context Encoding Standard. This standard is comprised of three documents:
The OGC Web Services Context Document (OWS Context) standard was created to allow a set of configured information resources (service set) to be passed between applications primarily as a collection of services. OWS Context is designed to support limited in-line content as well. The goal is to support use cases such as the distribution of search results and the exchange of a set of resources such as OGC Web Feature Service (WFS), Web Map Service (WMS), Web Map Tile Service (WMTS), Web Coverage Service (WCS) and others in a ‘common operating picture’ supporting situational awareness. Additionally OWS Context can deliver a set of configured processing services (Web Processing Service (WPS)) parameters to allow the processing to be reproduced on different nodes.
This initial call for comment is for two (2) OWS Context documents: A Conceptual Model and the ATOM encoding for the conceptual model. The Conceptual model document describes the use cases, requirements, conceptual data model of the OWS Context encoding standard. The goal of the model is to provide a core model, which is extended and encoded as defined in extensions to this standard. A Context reference is a fully configured service set to be defined and consistently interpreted by clients. The ATOM encoding is the first extension of the core (conceptual model).
The OGC OWS Context Standards Working Group will consider all comments when preparing a final draft of the candidate standard. The comment period ends 8 August 2013.
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: 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