OGC requests comments on the OWS Context Conceptual Model and ATOM Extension candidate standards

18 January 2013 – The Open Geospatial Consortium (OGC®) is seeking comments on the OGC OWS (OGC Web Services) Context Conceptual Model and the associated ATOM Extension document candidate standards.

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 OGC OWS Context Conceptual Model and the associated ATOM Extension document candidate standards are available for public review and comment at http://www.opengeospatial.org/standards/requests/96. Comments are due by 17 February 2012.

The OGC is an international consortium of more than 480 companies, government agencies, research organizations, and universities participating in a consensus process to develop publicly available geospatial standards. OGC Standards support interoperable solutions that "geo-enable" the Web, wireless and location-based services, and mainstream IT. OGC Standards empower technology developers to make geospatial information and services accessible and useful with any application that needs to be geospatially enabled. Visit the OGC website at http://www.opengeospatial.org/contact.

 

image_pdfimage_print
Share SHARE
Editor (18230 Posts)

Glenn is a geographer and a GIS professional with over 20 years experience in the industry. He's the co-founder of GISuser and several other technology web publications.


Editor’s Picks

Leica RCD30: Better Resolution with More Details for 3D City Modeling

Leica RCD30: Better Resolution with More Details for 3D City Modeling

(Norcross,GA, 6 October, 2014) – Leica Geosystems’ RCD30 Penta Oblique system is now available with new optics. Compared to the previous configuration, which consists of lenses with 50 mm focal length for nadir and 80 mm for oblique images, the camera isnow available with 80 mm and 150 mm focal length respectively.  In combination with the new 80 MP CCD sensor, the RCD30 nowprovides data with even more detail. These new features make the RCD30 the only oblique system able to acquire 4-channel RGBNmultispectral data with 10 centimeter Ground Sampling Distance (GSD) from an altitude of 3,000 meters. No other camera on the market today offers these performance parameters. Compared to other systems, users can fly higher and achieve the same high resolution. […]

tripomatic

Tripomatic – Custom Maps Built entirely with OpenSource Mapping Tools

An interesting update comes our way from the developers of Tripomatic – custom maps for iOS, Android or BlackBerry that focus on the features tourists really appreciate! What’s way cool about this app is that Tripomatic is based on OpenStreetMap and the Mapnik rendering toolkit while the symbology was designed using TileMill software developed by […]

More Posts from this Category

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>