Fwd: six OpenGIS® Specifications - now adopted (fwd)

[Brent Wood]

May be of interest to some people here (if you haven't alread heard)....

  Brent Wood



> Subject: six OpenGIS® Specifications - now adopted (fwd)

>
> Subject: [ISO-8859-1] six OpenGIS® Specifications - now adopted
>
> Wayland, MA, May 05, 2005 - The Open Geospatial
> Consortium (OGC) announces that the OGC membership has
> adopted six OpenGIS® Specifications. Each of the newly
> adopted specifications enhances the existing open body of
> knowledge and furthers the OGC vision of a world where
> geographic data and services are easily shareable via the variety
> of networks and devices available today and into the future. All
> of the newly adopted specifications are or will soon be available
> online at http://www.opengeospatial.org/specs/?page=specs.
>
> The Web Map Context Documents Implementation
> Specification 1.1 (WMC) defines how a map created using
> geospatial data from one or more map servers can be described
> in a portable document and shared with other software
> packages. This description is known as a "Web Map Context
> Document," or simply a "context." Currently, context
> documents are primarily designed for use with Web Map
> Services, but extensibility is envisioned for binding to other
> services.
>
> A context document includes information about the server(s)
> providing layer(s) in the overall map, the bounding box and map
> projection shared by all the maps, and sufficient operational
> metadata for client software to reproduce the map. The
> document may also include ancillary metadata used to annotate
> or describe the maps and their provenance for the benefit of
> human viewers. The document is structured using eXtensible
> Markup Language (XML).
>
> The Filter Encoding Implementation Specification 1.1 (FES)
> defines an XML encoding to express a combined spatial and
> attribute query for retrieving features from one or more
> geospatial databases. The goal, typically, is to operate on just
> those objects by, for example, rendering them in a different
> color or saving them to another format.
>
> The expressions are built on the BNF definition (Backus-Naur
> Form, a method of defining a syntax) described in the Catalog
> Services Specification. FES was originally part of the Web
> Feature Service Specification, but was separated since it is
> applicable to other types of services including Web Map
> Service, Web Coverage Service and others.
>
> The Geographic Objects-1 Application Implementation
> Specification (GO-1) allows developers to define an
> interoperable geospatial application once, and then build that
> application for use on multiple development platform, such as
> C++ or Java. The packages support a small set of geometries
> (points, lines and other shapes needed in mapping), graphics
> that can be used to visualize the geometries, the ability to work
> with hardware like displays, mice and keyboards and other
> necessary components. Once developers create software that
> adheres to this specification, they will be able to draw maps
> with detailed symbols, support changing data on maps and offer
> animation on any development platform.
>
> The high-level interface models allow developers to take
> advantage of the valuable components on any development
> platform or distributed computing platform. GO-1 sponsors and
> supporters from the public and private sectors sought these
> models because they allow straightforward reuse of existing
> capabilities for new projects, an important goal of software
> systems development because it saves time and money.
>
> The OpenGIS Location Services: Core Services Implementation
> Specification 1.1 (OpenLS) enhances six interfaces for location
> based services applications including geocoding, routing,
> directory (yellow pages), and location gateway. This version of
> the specification updates version 1.0 based on the OpenLS
> 1/1.1 testbed initiatives, held between 2001 and 2002, and
> reflects lessons learned and the results of these efforts. It also
> includes enhancements and fixes made subsequent to the testbed
> efforts by an ad hoc work group.
>
> The Web Feature Service Implementation Specification 1.1
> (WFS) defines and updates interfaces for data access and
> manipulation operations on geographic features. Via these
> interfaces, a Web user or service can combine, use and manage
> geodata. WFS operations include: deleting a feature instance,
> updating a feature instance, locking a feature instance and
> retrieving or querying features based on spatial and non-spatial
> constraints. This revision provides updates based on several
> change requests.
>
> The OGC Web Services Common Implementation Specification
> 1.0 specifies best practices for common definitions that are or
> will be used within OGC Web Service (OWS) interface
> Implementation Specifications. This specification will act as a
> base on which each such Implementation Specification will be
> built.
>
> The OGC is an international voluntary consensus standards
> organization of more than 270 companies, government agencies
> and universities participating in a consensus process to develop
> publicly available geoprocessing interface specifications. OGC's
> Specifications support interoperable solutions that "geo-enable"
> the Web, wireless and location-based services, and mainstream
> IT. Visit the OGC website at http://www.opengeospatial.org
> [http://www.opengeospatial.org/].
>
>
>