Request Closed: May 31, 2024 9:00 am — June 30, 2024 11:59 pm
The Open Geospatial Consortium (OGC) seeks public comment on the candidate OGC API – Records – Part 1: Core Standard. The Standard enables the discovery of geospatial resources by standardizing the way that collections of descriptive information (metadata) about the resources is exposed. Comments are due by June 30, 2024.
OGC API – Records is a multi-part Standard that offers the capability to create, modify, and query metadata on the Web. This part, Part 1 of the Standard, covers read-only access to metadata records and simple query capabilities. Additional capabilities that address specific needs will be covered in additional parts. Similarly, capabilities for richer queries, or to create, update, or delete records, will be covered in additional parts.
An implementation of the OGC API – Records Standard provides a way to browse or search a curated collection of ‘records’ known as a ‘catalog.’ A record contains descriptive information (metadata) about a geospatial ‘resource’ such as a title, a human readable description of the resource, the nature or genre of the resource, keywords associated with the resource, information about the publisher or provider of the resource, links to access the resource, and more.
Records make resources Findable by providing searchable metadata about them. In this context, the resources described by records are things that would be useful to a user or developer. These could be features, coverages, tiles/maps, styles, assets, machine models, services, processes, widgets, notebooks, and many others.
By standardizing the way all kinds of records are exposed and managed, OGC API – Records also enables the discovery and sharing of related resources, as they, too, can be referenced from geospatial resources or their metadata.
Catalogs can be deployed via a Web API for retrieving information about the catalog, retrieving records from the catalog, and searching the catalog for subsets of records that satisfy user-defined search criteria (area of interest, temporal extent, keywords, etc.). Catalogs may also be deployed as a static collection of records that can be browsed using a web browser, indexed by search engines, or traversed by automated tools.
To learn more about how the family of OGC API Standards work together to provide modular “building blocks for location” that address both simple and the most complex use-cases, visit ogcapi.org.
OGC Members interested in staying up to date on the progress of this standard, or contributing to its development, are encouraged to join the OGC API – Records Standards Working Group via the OGC Portal. Non-OGC members who would like to know more about participating in this SWG are encouraged to contact the OGC Standards Program.
The candidate OGC API – Records – Part 1: Core Standard (OGC 20-004) (.HTML) is available for review and comment on the OGC Portal. Comments are due by June 30, 2024, and should be submitted via the method below.
To Comment:
Comments can be submitted as an issue on the OGC API – Records GitHub repository for a period ending on the “Close request date” listed above. Comments received will be consolidated and reviewed by OGC members for incorporation into the document.