Thougt I'd share this OGC announcement with you folks as it seems to straddle into, or wish to, the semweb world... Can piggybank read GML ? is GML 3.1 going to be RDFized ???;>)
Here's the source material:
http://www.opengeospatial.org/initiatives/?iid=162
Wayland, MA, February 11, 2005 - The Open Geospatial Consortium Inc.
(OGC) announced a Request For Quotations (RFQ) from technology
developers interested in a major Interoperability Initiative to
develop and enhance OGC Web Services (OWS) standards that enable easy
discovery, access and use of geographic data and geoprocessing
services. The OGC Web Services Phase 3 (OWS-3) testbed advances OGC
Web Services, the set of OpenGIS(R) Specifications for interfaces,
schemas and encodings that comprise the interoperability framework for
the emerging "Spatial Web."
Building on previous work in other OGC initiatives and technical
working groups, selected OWS-3 participants will work collaboratively
to extend and "ruggedize" existing and draft OpenGIS standards into a
robust and complete interoperability framework for implementing
multi-vendor enterprise -- and enterprise-to-enterprise -- solutions
in government and business. The work will address a rich set of
requirements provided by OWS-3's public and private sector sponsors.
Sponsors include: BAE Systems, IONIC Software, GeoConnections
(Canada), Lockheed Martin, MAGIC Services Initiative, National
Aeronautic and Space Administration (NASA), National Technology
Alliance (NTA), Oak Ridge National Laboratory, NAVTEQ, Questerra, US
Geological Survey (USGS) and other organizations.
Participants will work in the following areas:
-- Common Architecture: Refining the OWS architecture for "publishing,
finding and binding" geoprocessing services using the OGC Catalog
Service for the Web (CS/W), profiles of CS/W, and the Business Process
Execution Language.
-- Sensor Web Enablement (SWE): Extending the SWE architecture for
access to a wide variety of sensor types and for scalability to
nationwide sensor deployment. SWE will include in-situ and remote
sensors; on fixed and moving platforms; with some sensors requiring
tasking. SWE will include work on TransducerML and IEEE 1451. Work on
SWE will result in mature specifications for SensorML, Sensor
Observation Service, Sensor Planning Service and using CS/W to
register sensors.
-- Geo-Decision Support Services (GeoDSS): Providing the distributed
services necessary for a analyst to marshal distributed services from
the spatial web to support decision making. GeoDSS includes
Information Interoperability providing tools and techniques for making
Geography Markup Language (GML) data compliant with application
schemas available through WFS for high performance applications. Key
will be development of a GeoDSS client for integrated access to
numerous OGC services, control of service chaining, and for portrayal
of geospatial information.
-- Geo-Digital Rights Management (GeoDRM): Augmenting the existing OWS
access services with digital rights management. This will enable a
broader distribution of geospatial data. While data providers are
making more and more geospatial data accessible via OGC services, a
limiting factor to further growth has become the need to manage the
rights to that information.
-- Open Location Services (OpenLS). New additions and enhancements
will be made to the existing Open Location Services framework.
The Request for Quotations can be downloaded from
http://www.opengeospatial.org/initiatives/?iid=162. A Bidder's
Conference (a conference call) will be held, as announced in the RFQ,
on February 22, 2005. Questions for the call must be sent to
bidder_at_opengis.org by 2200 GMT on February 18, 2005. The response
period begins February 11, 2005 and ends March 18, 2005. The OWS-3
kickoff will take place April 18-22, 2005 and the final demonstration
of capabilities will take place in October, 2005. The initiative
manager will be Chuck Heazel. For more information on the OWS-3
Initiative, please contact George Percivall,
percivall_at_opengeospatial.org
This one is of particular interest for Ontology devs...
4.5.4.3.1 Semantic Catalog Services
Relevant Specifications: OpenGISŪ Catalog Service Implementation Specification, v 2.0
W3C Web Ontology Language (OWL)
The purpose of a semantically-enabled Catalog is to allow a user, operating within one information
community, to discover resources published by another community. This is currently difficult because the
terms and constraints used by the user to build the query do not match the metadata model used by the
catalog. To solve this problem, a semantically-enabled catalog will be capable of mapping the query terms
into the information model of the catalog. Like-wise, the query result set should be mapped back into the
terms familiar to the user. This mapping between information models (ontologies) will be achieved using
techniques developed through the W3C Semantic Web work, the Web Ontology Language (OWL).
Participants in the semantically-enabled catalog effort will face two tasks. First of all it is necessary to build
the semantic translation capabilities into an OGC Catalog and verify that they work. Secondly, the
participants will identify what (if any) modifications are needed to the Catalog 2.0 specification to support
the management of the ontologies. For example, how does a user specify the ontology that is being used to
build a query?
Received on Wed Feb 16 2005 - 16:29:35 EST