- OGC® Standards
- OGC Standards List
- Specification Profiles
- Abstract Specification
- OGC Reference Model
- OGC Schema Updates
- Public Engineering Reports
- TC Policy Directives
- GeoDRM Reference Model
- Best Practices
- Discussion Papers
- Deprecated Documents
- Retired Documents
- Requests (RFP's, RFQ's...)
- White Papers
- Change Requests
- Submit Change Request or Requirement
The OGC requests comment on the candidate "I15" standard providing ebRIM extension to OGC Catalog Services Interface Standard
The Open Geospatial Consortium (OGC®) is seeking comments on the candidate OGC standard, "OGC I15 (ISO19115 Metadata) Extension Package of the OGC Catalogue Services 2.0 (CS-W) ebRIM Profile."
The OGC Catalogue Services Standard establishes a general framework for implementing catalogue services used for publishing and discovering geospatial data and geoprocessing services.
The candidate I15 standard provides an extension package aligned with the ebRIM application profile of CS-W for the cataloguing of data and services whose metadata implements ISO geospatial metadata standards. The I15 Extension Package defines mechanisms that allow an ebRIM catalogue to manage and search ISO conformant metadata in ways that enable arbitrary, complex and deep searches involving multiple metadata elements.
The draft standard was initially produced during the ESA HMA (Heterogeneous Missions Accessibility) initiative (HMA) and related projects. The OGC OWS-9 testbed initiative tested the draft standard and provided input.
Download the candidate OGC I15 (ISO19115 Metadata) Extension Package of the OGC Catalogue Services 2.0 (CS-W) ebRIM Profile below:
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists [dot] opengeospatial [dot] org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template