2010 June NOAA Silver Spring OGC Meetings
Document and Policy Motions approved at the June OGC Technical Committee meetings, sponsored by NOAA, Silver Spring Maryland. All approved documents will be made publicly available by mid July.
OGC Fast Track Document Process
The OGC Members approved the Draft OGC Fast Track Process [OGC 10-78r1] as an addition to the official OGC Policies and Procedures. Thye OGC Fast Track process is designed to facilitate the processing of candidates standards that are either profiles of existing OGC standards or are widely implemented and accepted de-facto standards developed by organizations other than the OGC. The process as drafted is to be refined over time to reflect experience and market requirements.
Iberian Latin America Forum formation
The OGC Members approved formation of an Iberian and Latin American Forum (ILAF) as described in the ILAF Charter [OGC document 10-101].
Retire Feature Portrayal Service Discussion Paper
The Technical Committee recommends that the Planning Committee approve retiring Feature Portrayal Service [OGC 05-110]. This Discussion Paper has been superseded by Styled Layer Descriptor Profile of the Web Map Service Implementation Specification [OGC 05-078r4]. OGC Retired documents may be viewed in the Retired Documents folder on the OGC web site.
Dissolve Review Board
The OGC Members approved dissolving the OGC Review Board. The Review Board as not been active in two years. The Review Board function will be incorporated in the OGC Architecture Board Policies and Procedures.
OWS-7 Event Architecture Engineering Report
The OGC Members approved the release of OWS-7 Event Architecture Engineering Report [OGC 10-060r1] be released as an OGC Engineering Report, with the provision that it is clear that the document is only a summary of Pilot results and is not on a standards track. The document specifies publish/subscribe functionality for OGC web services. This is done by first defining an abstract publish / subscribe model and then deriving functional requirements from this model.
OWS-7 Aviation Architecture ER
The OGC Members approved releases of “OWS-7 Aviation Architecture ER” [OGC 10-079r2], as an OGC Public Engineering Report. The document describes the architecture that was implemented in the Aviation thread of OWS-7 and provides an overview of the architecture and describes the implemented components. In addition it discusses eventing and notification techniques relevant for the aviation domain.
Compliance Testing Program Policies & Procedures
The OGC Members approved release of “Compliance Testing Program Policies & Procedures” [OGC 08-134r3] as an update to the current policies and procedures.
OWS-7 Engineering Report – Geosynchronization Service
The Technical Committee recommends that the OGC Planning Committee approve the release of “OWS-7 Engineering Report – Geosynchronization Service” [OGC 10-069r2] as an OGC Public Engineering Report. A Geosynchronization service, deployed by a data provider, sits between the provider's data store(s) and data collectors. It allows data collectors to submit new data or make modifications to existing data without directly affecting the data in the provider's data store(s) until validation has been applied thus ensuring that the data published by the provider is of high quality.
GML Simple Features Profile Motion
The OGC Members approved the use of the OGC Fast Track process (without comment) for the “GML simple feature profile” 2.0 [OGC 10-100r2]. This candidate OpenGIS® Implementation Standard defines a Simple Features profile of the Geography Markup Language version 3.2. This Simple Features Profile has been aligned with the OpenGIS Implementation Specification Simple Features for SQL version 1.2. Simple Features include: Point, Curve (LineString), Surface (Polygon), Geometry, MultiPoint, MultiCurve, MultiSurface, and MultiGeometry.
GeoAPI Adoption Vote
The Technical Committee recommends that the Planning Committee approve an adoption vote for the OGC GeoAPI Candidate Standard 3.00 [OGC 9-083r3], pending minor edits, as an OGC standard. This standard complements existing OGC standards by defining a new, language specific layer of normalization. This standard does not replace the core standards developing theISO/OGC abstract model but complements those documents for developers who use the Java language by documenting the mapping of types and methods from the abstract model into Java and explaining the use of the GeoAPI library.
Harmonising Standards for Water Observation Data
The OGC Members approved release of “Harmonising Standards for Water Observation Data - Discussion Paper” [OGC 09-124r2] as an OGC Discussion Paper. This discussion paper has two broad goals. Firstly, it will investigate the core requirements for an information model which describes the results of hydrological observations, focusing on time series. Secondly, the discussion paper will provide an approach for developing a harmonised core conceptual model for hydrological observations.
Adoption vote for Observations and Measurements model as Abstract Specification
The OGC Members approved an electronic vote to approve release of “ISO/CD 19156 - Geographic Information – Observations and Measurements” [OGC 10-004r2] as a Topic Volume 20 of the OGC Abstract Specification. This document defines a conceptual schema for observations, and for features involved in sampling when making observations. These provide models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities.
O&M SWG Motion to release document for public comment
The OGC Members approved release of “Observations and Measurements – XML Implementation” [OGC 10-025] for public comment, in preparation for adoption as an OGC Standard. This Candidate Standard specifies an XML implementation for the Observations and Measurements conceptual model, including a schema for Sampling Features.
OGC-NA Name type specification - specification elements v2
The TC OGC Members approved release of “OGC-NA Name type specification - specification elements v2” [OGC 10-103] as an OGC Policy Document. An OGC name must be provided for each normative element within an OGC specification, as described in the OGC Specification Model – Modular Specifications (OGC 08-131r3). This document specifies the rules.
OGC Identifiers – the case for http URIs’
The OGC Members approved release of ‘OGC Identifiers – the case for http URIs’ [OGC 10-124r1] as an OGC Whitepaper. .According to the current OGC policy either URNs or http URIs may be used in OGC standards. However, the use of http URIs (a) resolves some deployment challenges and (b) provides an opportunity for easier engagement with broader communities. So OGC should now consider taking the next step, and mandate the use of http URIs for persistent identifiers in OGC specifications. This whitepaper canvasses a number of issues around this proposal.
http URI Policy
The OGC Members approved the following as official OGC policy to be included in the OGC Policies related to OGC standards [OGC 06-135rN]:
- OGC TC directs the OGC-NA that all new OGC identifiers issued for persistent public OGC resources shall be http URIs, instead of URNs
- New standards and new major versions of existing standards shall use http URIs for persistent public OGC resources to replace OGC URN identifiers defined in previous standards and versions, unless OGC-NA approves an exception
Operational Implications: OGC should carefully manage (maintain for the long term) the http://www.opengis.net domain and identifiers in this domain
OWS-7 Dynamic Sensor Notification
The OGC Members approved release of “OWS-7 Dynamic Sensor Notification Engineering Report” [OGC 10-061r1] as an OGC Engineering Report. The document presents a detailed discussion of different approaches for encoding tracked object position. Two approaches for implementing dynamic sensor tracking and notification are described, one based on the Sensor Alert Service specification and the other based on the Sensor Event Service specification.
OWS-7 CCSI-SWE Engineering Report
The OGC Members approved release of “OWS-7 CCSI-SWE Engineering Report” [OGC 10-073] as an OGC Engineering Report. This document seeks to define the Best Practices for integrating Common Chemical, Biological, Radiological, and Nuclear (CBRN) Sensor Interface (CCSI) compliant and potentially other CBRN-based sensors into an OGC Sensor Web Enablement (SWE)-based environment.
Sensor Interface Descriptors
The OGC Members approved the release of Sensor Interface Descriptors [OGC 10-134] as an OGC Discussion Paper. This document presents the Sensor Interface Descriptor (SID) schema which enables the declarative description of sensor interfaces, including the definition of the communication protocol, sensor commands, processing steps and metadata association.
Web Map Service 1.3.0 Corrigendum
The OGC Members approved an electronic vote to approve release of OGC “OGC Web Map Service 1.3.0 Corrigendum 1” [OGC 09-111] as a corrigendum to the OWC WMS 1.3 standard. OGC Staff needs to notify ISO TC211.