® © 2006 Open Geospatial Consortium, Inc. OGC Catalog CEOS WGISS September 2006 Chuck Heazel

OGC ® © 2006 Open Geospatial Consortium, Inc.2 What is the OGC? Open Geospatial Consortium, Inc. (OGC) Not-for-profit, international voluntary consensus standards organization Founded in 1994, Incorporated in US, UK, Australia 320+ (up from 270 last year) industry, government, research and university members OGC Mission To lead in the development, promotion and harmonization of open spatial standards …

OGC ® © 2006 Open Geospatial Consortium, Inc.3 OGCs Approach for Advancing Interoperability Specification Development Program – Consensus standards process similar to other Industry consortia (World Wide Web Consortium, OMA etc.). Outreach and Community Adoption Program – education and training, encourage take up of OGC specifications, business development, communications programs Interoperability Program – a global, innovative hands-on rapid prototyping and testing program designed to accelerate interface development and validation and to bring interoperability to the market.

OGC ® © 2006 Open Geospatial Consortium, Inc.4 Iterative Development Yielding Tested Specifications Interoperability Program Specification Program Outreach Program Draft Specifications Adopted Specifications Holes and Enhancements SCOTS Implementations Prototype Implementations Requirements

OGC ® © 2006 Open Geospatial Consortium, Inc.5 OGC Catalog History In February 1999, MITRE and USGS/NASA both presented proposals to the OGC Technical Committee for a Catalog service. A tiger team was formed to converge the two proposals into a single specification. The resulting OGC Catalog Specification was presented and approved at the OGC Technical Committee meeting of August At this meeting prototype implementations of the specification were demonstrated interacting with each other.

OGC ® © 2006 Open Geospatial Consortium, Inc.6 OGC Catalog Background Catalog specification contains an abstract model (captured in UML) and Distributed Computing Platform (DCP) specific profile specifications. Goal was to enable cross-DCP access to a catalog service. Initial set of supported profiles were for: –CORBA –DCOM –Z39.50 Catalogs are data model agnostic. An explain collection interface describes the data model. An explain service interface returns a service description.

OGC ® © 2006 Open Geospatial Consortium, Inc.7 OGC Catalog Background Mandatory interfaces were defined for: –Explain Service –Explain Collection –Query Optional interfaces were defined for: –Management (population and update) –Federation (delegating a query to other catalogs and aggregating the responses) A language was defined for geospatial data queries.

OGC ® © 2006 Open Geospatial Consortium, Inc.8 Web Services In 1999 the OGC began work on Web Services in the Web Map Server testbed (WMS-1). The OGC Catalog Specification did not provide stateless interfaces which are required for Web Services. The basic Catalog (Registry) technology was evaluated over subsequent testbeds. OGC Catalog Services is the current version

OGC ® © 2006 Open Geospatial Consortium, Inc.9 OGC Catalog Interfaces Get Capabilities Interface –Required for all services –Advertises the service and provides sufficient detail for Bind operations –Is invoked by some Catalogs to maintain metadata currency Query Interface –Required for Catalogs –Returns metadata on Catalog entries satisfying a filter criteria Transaction Interface –Optional for Catalogs –Supports maintenance of the Catalog entries Distributed Query (still being worked) –Optional for Catalogs –Supports distribution of a query over multiple Catalogs

OGC ® © 2006 Open Geospatial Consortium, Inc.10 Web Resources Model My Resource Information Framework Resource Publish Find Bind

OGC ® © 2006 Open Geospatial Consortium, Inc.11 The Model Requires --- A forum where resources can advertise their capabilities and users can find the resources they need. Self describing resources so that user applications can bind at run-time to the resources that they have found.

OGC ® © 2006 Open Geospatial Consortium, Inc.12 Self Describing Resources Resources are provided by Services. Each service supports a get capabilities interface. Get Capabilities provides a robust set of metadata (a Capabilities Document) describing the service, the behavior, contents, and how to bind to it. Services that provide access to data also describe their data holdings through the content section of the Capabilities Document. Goal is to enable binding with or without human intervention

OGC ® © 2006 Open Geospatial Consortium, Inc.13 Web Resources Model (with automated update) My Resource Resource URL Find() Execute Get_Capabilities() Metadata Doc. Results Get_Capabilities() Capabilities Doc. Catalog Application

OGC ® © 2006 Open Geospatial Consortium, Inc.14 OGC Catalog layered standard OGC_Service, Discovery, Manager, Record Abstract Interfaces and Operations (technology and information agnostic HTTP (Catalog Service / Web) Protocol Bindings (information agnostic) ebRIM* Profile, ISO191xx Profile Information Model * incoming records representing different metadata standards are managed within a single catalog schema or registry information model, ebRIM. Ingestion, Search, Presentation (Lifecycle) Domain Services

OGC ® © 2006 Open Geospatial Consortium, Inc.15 Catalog Metadata Registry Metadata Model –ebXML Based (EbRIM) Metadata for Data Resources –ISO –FGDC-STD Metadata for Services –WSDL - interface and binding –ISO service taxonomy –Services Information Model - full service description Metadata for Sensors –Developed for stationary sensors under OWS 1.1 –Extended for mobile sensors under OWS 1.2 –Matured under OWS-3

OGC ® © 2006 Open Geospatial Consortium, Inc.16 OWS-4 Catalog Work Items Catalog –CS/W ebRIM - SOAP Data registry Services registry Style registry Sensor registry –Query at Feature Level –Support for DGIWG Portal Compliance Testing –Beta test new Open Source engine –Develop Scripts & Tests for CS/W –Develop CS/W Reference Implementation

OGC ® © 2006 Open Geospatial Consortium, Inc.17 Comments Requested OGC Catalog Working Group and JAG proposed at the October 2006 Technical Comittee that: –the ebRIM be adopted as the only (cataloguing) metamodel for all OGC CS-W Catalogue implementations –Application Profile as understood in CSW be redefined to mean an extension package of ebRIM –ISO Metadata AP be migrated to an ebRIM extension package consistent with the previous two items