ATOM encoded OWS Context in a JavaScript smart clients ATOM encoded OWS Context in desktop implementations. Transform a WMC document into an OWS Context document.

Copyright © 2012 Open Geospatial Consortium. 73 Figure 7 — OWS Context document translated to HTML by just using XLST.

8.4 ATOM encoded OWS Context in a JavaScript smart clients

In the OWS-9 interoperability experiments, we have added the OWS Context support to a web map browser application called MiraMon Map Browser. The application is able to write a context document and read it again to recover the context of the previous view, it can even load a context generated by another application. When a context file is opened, the user is able to select the layer heshe wants to add to the current view. Figure 8 — A map browser build with JavaScript is presenting a context document for content selection. 74 Copyright © 2012 Open Geospatial Consortium.

8.5 ATOM encoded OWS Context in desktop implementations.

The possibility to store direct links to content in OWS Context is particularly interesting for GIS desktop solutions. This paper also presents the development made in the MiraMon desktop GIS solution to include OWS Context. MiraMon software is able to deal either with local files, web services and database connections. As in any other GIS solution, MiraMon team designed its own file for storing and sharing the status of a GIS session that is called MiraMon map MMM. The new OWS Context format is now adopted as a way to migrate the current MMM project file to an OWS interoperable format that can be shared with other future applications implementing OWS Context. The extensibility of the format makes it possible to map concepts in the MMM to current OWS Context elements such as titles, data links, extent, etc and to generate new elements that are able to include all extra content not currently covered by OWS Context. Figure 9 — A MiraMon GIS pro presenting the content of a context document.

8.6 Transform a WMC document into an OWS Context document.

In the section 6.3 Comparison between WMC and OWS Context we have been discussing the similarities and differences of WMC and OWS Context. Both documents can be encoded in XML so, in principle it is possible to develop an XSLT conversion between them for the WMS offerings. However, this is not a straightforward exercise, thus it is going to require a character string analysis of the server URLs. The realization of this transformation was discarded during the timeframe of OWS-9. Copyright © 2012 Open Geospatial Consortium. 75

8.7 Transform a WMSWFS Capabilities document into an OWS Context document