Add Community Extension: SKOS Registry #9
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adds a new community extension to support a **SKOS Semantic Registry** for STAC APIs. **Repository:** https://github.com/Healy-Hyperspatial/stac-api-extensions-skos-registry ### Motivation This extension defines a standard mechanism to expose **SKOS (Simple Knowledge Organization System)** hierarchies as navigable **Virtual Catalogs**. Currently, the standard [Themes Extension](https://github.com/stac-extensions/themes) allows providers to tag data with controlled vocabularies (e.g., "Forestry", "Disaster", "Optical"). However, these tags remain "dead metadata"—useful for advanced search filtering, but invisible in the API's browsing structure. Users cannot "click through" a concept to explore related datasets. ### The Solution: "Live Folders" This extension solves that discoverability gap by generating **"Virtual Catalogs"** for SKOS concepts. * **Input:** An Item tagged with `themes: [{id: "forestry"}]`. * **Output:** A browseable Catalog resource at `/catalogs/theme::forestry`. ### Key Capabilities 1. **Poly-Hierarchy:** Enables items to belong to multiple parents simultaneously (e.g., *Physical Parent*=`USGS` and *Semantic Parent*=`Forestry`) without data duplication. 2. **Taxonomy Navigation:** Supports traversing the SKOS graph (Broader/Narrower concepts) via standard STAC `child` and `parent` links. 3. [cite_start]**Interoperability:** Aligns with research on geospatial interoperability (such as the [UN-GGIM Data Themes](https://arxiv.org/abs/2110.06883) [cite: 7]), facilitating "meaningful relations" between disparate datasets from different organizations. **Implementation:** We are currently looking at implementing this specification in the `stac-fastapi-elasticsearch-opensearch` project. The implementation leverages the **Catalogs Endpoint Extension** to provide the routing infrastructure for these virtual resources.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a new community extension to support a SKOS Semantic Registry for STAC APIs.
Repository: https://github.com/Healy-Hyperspatial/stac-api-extensions-skos-registry
Motivation
This extension defines a standard mechanism to expose SKOS (Simple Knowledge Organization System) hierarchies as navigable Virtual Catalogs.
Currently, the standard Themes Extension allows providers to tag data with controlled vocabularies (e.g., "Forestry", "Disaster", "Optical"). However, these tags remain "dead metadata"—useful for advanced search filtering, but invisible in the API's browsing structure. Users cannot "click through" a concept to explore related datasets.
The Solution: "Live Folders"
This extension solves that discoverability gap by generating "Virtual Catalogs" for SKOS concepts.
themes: [{id: "forestry"}]./catalogs/theme::forestry.Key Capabilities
USGSand Semantic Parent=Forestry) without data duplication.childandparentlinks.Implementation:
We are currently looking at implementing this specification in the
stac-fastapi-elasticsearch-opensearchproject. The implementation leverages the Catalogs Endpoint Extension to provide the routing infrastructure for these virtual resources.