Exported Content

OGC Standards

Below is a list of OGC Implementation Standards.

Implementation Standards are different from the Abstract Specification. They are written for a more technical audience and detail the interface structure between software components. An interface specification is considered to be at the implementation level of detail if, when implemented by two different software engineers in ignorance of each other, the resulting components plug and play with each other at that interface.

OGC Web Services Context Document (OWS Context)

This standard describes the use cases, requirements and conceptual model for the OWS Context encoding standard. The goal of this standard is to provide a core model, which is extended and encoded as defined in extensions to this standard. A ‘context document’ specifies a fully configured service set which can be exchanged (with a consistent interpretation) among clients supporting the standard. 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 serv...

OGC Web Services Initiative, Phase 1.1

Testbed. After the events of September 11, the OWS 1.1 sponsors agreed to align OWS 1.1 to address interoperability challenges defined by officials in New York City. The OWS 1.1 demonstration scenario developed by the sponsors challenged participating technology developers and integrators to implement interoperability capabilities that address specific critical disaster management needs involving New York City data. Specification development focused on: OGC Common Architecture, Web Mapping, Imagery Exploitation and Sensor Web.