review discovery metadata and search standards

[tomkralidis]

Summary and Purpose
As part of our efforts on the next version of WCMP (#101), we need to perform an analysis and inventory or metadata and search standards used in various portals/websites in the earth science domain.

Proposal
@wmo-im/tt-wismd members to provide examples of search portals/website in their respective countries (and/or other countries if they are involved/aware).

Reason
Having a better idea of the use of search and metadata standards will help in the definition of future WCMP as well as search standards for WIS 2.0.

cc @efucile @amilan17 @joergklausen

[amilan17]

• https://www.data.gov
  • https://www.data.gov/developers/harvesting / https://resources.data.gov/
  • DCAT?
• https://data.noaa.gov/dataset/
  • DCAT?
• https://data.noaa.gov/onestop
  • ISO 19115-2
• ESRI Geoportal Server
  • Federal Geographic Data Committee (FGDC)
  • ISO
  • Dublin Core

[tomkralidis]

• https://woudc.org
  • Metadata: WCMP 1.3
  • Search: OGC:CSW, OAI-PMH, SRU, OpenSearch
• https://open.canada.ca
  • Metadata: DCAT, ISO HNAP
  • Search: CSW

[tomkralidis]

Comments on @amilan17 's entries:

• data.gov also supports ISO 19115 and OGC:CSW, OAI-PMH, SRU, OpenSearch
• same with data.noaa.gov

[tomkralidis]

2021-05-21

• from @josusky

  • ICAO SWIM
    • registry of services
  • may be difficult to decipher what's being used

• @jsieland

  • service descriptions/metadata
  • XML -> JSON

[jsieland]

Here are some links regarding SWIM:

• SWIM Registry: https://eur-registry.swim.aero/home
• SWIM References/Resources: https://reference.swim.aero/resources.html
• SWIM Supporting Material (Confluence): https://ext.eurocontrol.int/swim_confluence/display/SWIM/SWIM+Supporting+Material
• recent JSON Schema for SWIM-compliant services: https://reference.swim.aero/resources/SWIMRegistrySchema_v0.0.3d-Compliant.json

Additional quick background info (from what I can recall):

• There are three Specifications for SWIM Services:
  • TI Yellow Profile: foundation for technical implementation
  • Service Description: how to describe a service
  • Information Definition: how to describe the information/data provided by the service; an Information Definition is part of a SWIM Service Description
• it is (at least to me) not clear how the SWIM Registry validate the uploaded JSON Service Descriptions
  • the JSON Schema is somehow based on that validation.....
• a service is SWIM compliant if it passes the validation against the JSON schema for compliant SWIM Services
  • the minimum set which is necessary to publish a service is a so-called Candidate (it requires less mandatory elements). A Candidate need to evolve to compliant within two years.
  • there are also Service Definitions. These types can be seen as some kind of templates which should promote best practice. This type has the least mandatory elements.
  • there are seperate JSON schema files for "compliant / candidate / definition"
• to include some ICAO context there is ongoing work on Service Overview (https://ext.eurocontrol.int/swim_confluence/display/SWIM/Service+Overview)

[josusky]

Many thanks, @jsieland . I will need some time to read and digest all this.

[martaguti]

Hi there,
I thought I drop this in here as it is an interesting "metadata crosswalk across different metadata formats for Earth Sciences,marine,climate and general purpose. ISO19115-2, CMIP6, DataCite, schema.org, DCAT, OGC EO (among others)

https://zenodo.org/record/4744768#.YOGJ4C1Q3T8

It was presented at the Metadata Task Force group for the EOSC symposium 2021. Work done by the UPM (Universidad Politècnica de Madrid) for the Reliance project. Presentations in YouTube available

ps:I have not escaped the metadata catalogues world :-)

[gaubert]

@martaguti interesting Thanks a lot. Could you also link the youtube presentation because the zenodo record only links to a very dry spreadsheet.

Thanks a lot and sorry for the fact that you still have to deal with metadata catalogue :-D

[martaguti]

@gaubert
see deliverable D4.1 DataCube Metadata model
https://box.pionier.net.pl/d/529599305c0e43d9bf28/

Youtube
https://www.youtube.com/watch?v=qvtWJWsMLRg&list=PLbISfqJh3Tstmx6CgrBmYI7lyyVXiY5VE&index=13

metadata: it's our fate , like a boomerang comes back to us :-)

[gaubert]

@martaguti Great many thanks for the links.

[amilan17]

@tomkralidis I think we can close this

[tomkralidis]

Summary: given the current state of the art and the scope / granularity of resource discovery for WIS2, OGC API - Records has been adopted for resource discovery (datasets, services, processes), for both the model (i.e. WCMP2 as a profile of the "Record Core" requirements class) and the API machinery ("Record API" requirements class) as part of the WIS2 Global Discovery Catalogue (GDC).