OGC OWS Context 1.0 Guidelines

From IMarine Wiki

Jump to: navigation, search



As a result of recent standardization efforts at OGC (to which Terradue actively contributed as co-editor of the implementation specification and author of the Conformance Test Suite), the Geospatial Cluster is considering to promote the OWS Context 1.0 specification.


In the OGC, this standard is summarised as:

The OGC OWS Context Conceptual Model describes the use cases, requirements and conceptual data model of an OGC Web Services Context Document. A context document (OWS Context) defines a fully configured set of OGC services to be consistently shared, interpreted and invoked by clients. This standard model is a core model that can be extended and encoded as defined in extensions to the standard, such as the ATOM Extension and the JSON Extension, which has not yet been released.

An OGC Web Services Context Document (OWS Context) enables a set of configured information resources (service set) to be passed between applications as a collection of services. OWS Context supports in-line content as well. This candidate standard supports 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) or others to provide multiple users with a ‘common operating picture’. Additionally OWS Context can deliver a set of configured processing services (Web Processing Service (WPS)) parameters to allow processing to be reproduced on different nodes.

The related OGC documents are available here: http://www.opengeospatial.org/standards/requests/96

Analysis for iMarine

It is a means to support the data sharing capacities of iMarine, and complement the visualisation capabilities.

It is a very good approach to display time-series data, since a single OWS Context document could have several representations of data sources in different instants.


Personal tools