Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add sprint results for https://github.com/opengeospatial/GeoDCAT-SWG/issues/17#issuecomment-2434553700 #5

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Add sprint results for https://github.com/opengeospatial/GeoDCAT-SWG/issues/17#issuecomment-2434553700 #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion 2024/Metadata-Codesprint-Nov24/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
The OGC GeoDCAT SWG (with the OGC MetaCata DWG) ran a two day code sprint, as described at https://github.com/opengeospatial/GeoDCAT-SWG/tree/main/workshops/2024/OGC_Metadata_Codesprint
A lot of possible work items had been proposed as issues (https://github.com/opengeospatial/GeoDCAT-SWG/issues) in that repository & as comments on one specific issue (https://github.com/opengeospatial/GeoDCAT-SWG/issues/17). With two developers in the room, two in the Americas and the promise of some joining from Europe, it seemed that the favourite topic areas were:
* alignment with PROV - GeoDCAT & PROV or OGC API Records & PROV
* metadata for AI / OGC API Processes & Large Language Models (#18)(
* metadata for AI / OGC API Processes & Large Language Models (#18)
* ISO 19115-1 to (Geo)DCAT mapping

Others present thought to start on this engineering report
Expand All @@ -26,3 +26,12 @@ A lot of 'prior art' exists, mapping from various editions of ISO 19115 (or at l
* EU mapping from ISO 19139 (encoding of ISO 19115:2003) (EU INSPIRE subset) to EU GeoDCAT-AP (an AP of DCAT v2): https://github.com/GeoCat/iso-19139-to-dcat-ap/blob/master/documentation/Mappings.md
* UK (draft) mapping from ISO 19115:2003 (EU INSPIRE subset) to DCAT v3: https://github.com/agiorguk/gemini/issues/41 (less detailed than above)
* implementations (XSLT) in GeoNetwork microservices e.g. https://github.com/geonetwork/geonetwork-microservices/tree/main/modules/services/ogc-api-records/src/main/resources/xslt/ogcapir/formats/copy for ISO 19115-1:2014 / ISO 19115-3 (UK / INSPIRE subset) to DCAT v3

## Make OGC API Record from pygeoapi-CSWFacade upliftable to GeoDCAT

Developers: Jan Speckamp <[email protected]>

Idea: [https://github.com/opengeospatial/GeoDCAT-SWG/issues/17#issuecomment-2434553700](https://github.com/opengeospatial/GeoDCAT-SWG/issues/17#issuecomment-2434553700)

The [pygeoapi](https://github.com/geopython/pygeoapi) provides an implementation of the OGC API Records, e.g. using a [CSWFacadeProvider](https://github.com/geopython/pygeoapi/blob/31480af845dd770b22f2e5616f7fd1f67b65938a/pygeoapi/provider/csw_facade.py). It also natively supports output of data in json-ld format, but this is only used internally and for SEO and is specifically adapted for this usecase. The output is therefore unfortunately natively semantically upliftable to GeoDCAT and does not follow the draft https://github.com/ogcincubator/geodcat-ogcapi-records.