OWS Context (OWC)
The OGC Web Services Context Document (OWS Context) 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 developed to support in-line content as well. The goal is to support use cases such as the distribution of search results, 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’. 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.
OWS Context is aimed at replacing previous OGC attempts at providing such a capability (the Web Map Context WMC) which was reasonably successful but limited to WMS. Other work on the ‘Location Organizer Folder (LOF)’ was also taken into consideration. The
concept of OWS Context, and the first prototype document was produced as part of OGC testbed OWS-7. See 10-035r1, Information Sharing Engineering Report. In order to achieve mass market appeal, as well as being useful to a wider community, the use of OWS Context support to other existing standards was considered.
The first concrete encoding of OWS Context extends the Atom XML encoding format. It adds the following requirements:
- each feed MUST have an atom:link with the relation of "profile" (to identify the version of the specification)
- each entry MUST have atom:content (recommended of type "html")
- each entry MAY have one or more links with the relations "via",
"alternate", "enclosure", "icon" (that have defined notions/mappings in
- each entry MAY have links with any other type of relations that respect the Atom rules
- schemas and examples
- Conceptual model
- Atom encoding
- GeoJSON encoding (currently being developed in OWS-10 and the Context SWG...)