Everyone is allowed to see and access metadata without restriction

Everyone is allowed to see and access metadata without restriction at GloBI

DOI comprises data and metadata as a package

This is the FIP for the WorldFAIR WP10 Plant-Pollinator.

The PRIDE PRoteomics IDEntifications (PRIDE) Archive database is a centralized, standards compliant, public data repository for mass spectrometry proteomics data, including protein and peptide identifications and the corresponding expression values, post-translational modifications and supporting mass spectra evidence (both as raw data and peak list files). PRIDE is a core member in the ProteomeXchange (PX) consortium, which provides a standardised way for submitting mass spectrometry based proteomics data to public-domain repositories. Datasets are submitted to ProteomeXchange via PRIDE and are handled by expert bio-curators. All PRIDE public datasets can also be searched in ProteomeCentral, the portal for all ProteomeXchange datasets.
The PRIDE PRoteomics IDEntifications (PRIDE)

FAIR-enabling resource: The PRIDE PRoteomics IDEntifications (PRIDE)

The Ontology Lookup Service (OLS) is a repository for biomedical ontologies that aims to provide a single point of access to the latest ontology versions. You can browse the ontologies through the website as well as programmatically via the OLS API. OLS is developed and maintained by the

FAIR-enabling resource: ontology look up service

ZonMw is preparing a demonstration (meeting on Febr 22, 2024) for the researchers and data stewards of the ME/CFS research programme. It has prepared this demo-FIP to collect a community choices that are/will be taken from a DMPs and/or project plans, submitted by the grant holders of this research programme.

The M4M Project Admin, which was developed for the COVID-19 research programme, is a generic metadata schema that can be used for each research project funded by a research funding organisation (RFO). It contains a minimal set of information that is needed for citation of the dataset (or other resource) in a research project.

The COVID-19 portal at Health-RI can be used for ME/CFS as well, but ZonMw will only require the M4M Project Admin metadata. Health-RI is currently updating/extending the portal as to include metadata from all health-related disciplines (in the Netherlands). Then it will also be suitable to expose more metadata about the ME/CFS projects.

we can refer to the ZonMw generic terms.

This FIP serves as a reference for ZonMw-funded projects related to ME/CFS (chronic fatique syndrome)

All our (meta)data are NetCDF 1.7 compliant. The definition of new CF variable names is under discussion with CF community

Metadata in JSON format through REST API

NetCDF compliant with Climate and Forecasts (CF) Metadata Convention v1.7

This is the FIP of ACTRIS ARES (representing the choices made in 2019).

metadata records have local identifiers either created locally or harvested through dif:entry_id or 'iso /gmd:MD_Metadata/gmd:fileIdentifier/gco:CharacterString'.

sios do not own data, but relies on partner repositories. UIDs is a requirement, PIDs (DOI) is a recommendation currently.

This is used to indexed data locally and expose them on the data access portal. Filters and facets are based on elements of this schema.

This is the recommended license, but support is in place for all CC licenses.

This is the FIP of SIOS (representing the choices made in 2019).

metadata records have local identifiers, either created locally or harvested through dif:entry_id or iso '/gmd:MD_Metadata/gmd:fileIdentifier/gco:CharacterString'.

This is the recommended license, but support for all creative common license in in place to support user's need.

This is the FIP of SIOS (representing the choices made in 2021).

This is the FIP of SIOS (representing the choices made in 2020).

This is the FIP of ACTRIS ARES (representing the choices made in 2020).

EPIC handle PID points to DO landing page containing the URL of the actual file for downloading, and each file contains PID to the corresponding landing page.

Open access required by the community. Easy access to metadata.

Open access required by the community. Easy access to data.

This is the FIP of ACTRIS CLU (representing the choices made in 2019).

Metadata available in the ACTRIS data portal through HTTPS.

Data download via primary repositories through HTTPS.

ACTRIS internal vocabulary is used for variable names in the ACTRIS data portal.

This is the FIP of ACTRIS DVAS (representing the choices made in 2020).

Standard in the community and recommended within ENVRI Atmospheric community

Recommended within ENVRI Atmospheric community. Automatic conversion from IAGOS metadata pivot format to datacite profile

Recommended within ENVRI Atmospheric community

Recommended within ENVRI Atmosphere community

Community standard. Used for observed variables, instrument types and platform type

Community standard. Used for observed variables

Generally relevant. Used for direct download of data.

widely used, no need for authentication.

used for fully quality controlled data, open for anybody.

This is the FIP of ACTRIS InSitu (representing the choices made in 2019).

Metadata are stored in a MongoDB database. Documents are identified by a UUID.

Handle server hosted by AERIS with a prefix obtained from ePIC

Automatic conversion from internal metadata format to Datacite

Internal metadata format compliant with standards, incl. ISO 19115

Using Thredds data server. We need to convert all data to the NetCDF format

Home made JSON format, compliant with standards

Home-made metadata format compliant with standards

HDF4 files, a conversion to NetCDF is planned for ACTRIS but both formats will be distributed because HDF is required by NDACC

This is the FIP of ACTRIS GRES (representing the choices made in 2020).

This is the FIP of ACTRIS GRES (representing the choices made in 2019).

This is the FIP of ACTRIS DVAS (representing the choices made in 2019).

DataCite DOIs are issued by EUDAT B2SHARE which is currently used to share and publish site level datasets (processing level 0 and 1). In future DataCite DOIs also will be issued by the eLTER Central Data Node (CDN) which is currently in development (plan for 2024). Implementation of DOIs for site records in addition to the deims.id is currently evaluated.

UUID are appended to the URI of the eLTER Catalogue (Digital Asset Register, DAR). UUID is also used in DEIMS-SDR to identify the MD records for sites, locations, sensors and networks

currently used for datasets shared via B2SHARE. Issuing DOI from the eLTER Digital Asset Registry (DAR) will be implemented in 2025 onwards. Services related to access to these data are documented as service records in the DAR.

persistent identification based on UUID plus URI (namespace for deims) for research sites and observation facilities implemented in DEIMS-SDR and used to unambigously identify and register sites belonging to different research infrastructures and networks

for eLTER a community profile based on the INSPIRE required fields and requirements for EML 2.0 was definded using a local schema which is mapped to ISO19115/19139 to expose metadata. For the Digital Asset Register (DAR) also sharing of ISO19115/19139 metadate is implemented - schema on read philosophy

for eLTER a community profile based on the INSPIRE required fields and requirements for EML 2.0 was definded using a local schema which is mapped to ISO19115/19139 to expose metadata. For the Digital Asset Register (DAR) metadata are held in schema-neutral json document, which allows sharing of ISO19115/19139 metadate as a schema-on-read service through a RESTful API.

this is implemented for site datasets (processing level 0 and 1) using EUDAT B2SHARE as common repository. For the eLTER Central Data Node (CDN) this is under development and will be implemented 2025 onwards.

DEIMS-SDR is operational to document physical assets of the eLTER network (sites, platforms, locations, sensors, and networks) as well as digital assets (datasets and activities). In future implementation steps (2025 onwards) digital assets will be documented and shared using the eLTER digital asset register (DAR)

EUDAT B2FIND harvests eLTER metadata from DEIMS-SDR and the related B2SHARE repository. The effort was renewed within the implementation of the EOSC-Hub project. B2FIND is used as additional domain agnostic discovery portal.

currently under development. the eLTER Digital Asset Register will be operational by end 2023 focusing n the documentation of digital assets (datasets, models, provenance) of the eLTER RI

currently within eLTER we use a combination of web services from DEIMS-SDR, DAR, B2SHARE and DataCite to disseminate metadata covering the different assets of the RI

DEIMS-SDR contains metadata to existing data repositories and linking dataset metadata to the respective eLTER facilility

the eLTER Central Data Node (CDN) currently contains storage of time series data (OGC SOS), geospatial data (OGC WMS/WFS) as well as files. The eLTER CDN is currently still under development and will be operational by mid 2024.

the eLTER DIP (EcoSense) is a web interface to view and access information on datasets shared

DEIMS-SDR REST-API shares information on sites, locations, sensors, datasets and networks as json

direct download using https/http request for datasets shared via B2SHARE

eLTER fosters an open data policy recommending CC-0 for any eLTER metadata. control of atuhorship of metadata is behind login wall of the catalogues (DEIMS-SDR, DAR). These are currently internal systems, but will be moved to an external system in the future.

General eLTER data policy fosters open data (CC-BY). Restrictions might apply for site based data under embargo before scientific publication. commercially sensitive data will have bespoke licenses.

updates are worked out in eLTER-PPP WP3 Data Management Plan and Data Policy. Will be available by 2025

implemented for DEIMS-SDR (API) as well as eLTER DAR

will be replaced by the eLTER RI Data Specification latest by 2025

local data provision could derive from that

information on metadata creation and update is provided as part of the MD model

eLTER FIP 2022: This is the FIP for the eLTER Community representing the choices made in 2022.

currently implemented within the eLTER Digital Asset Register (DAR)

participant in - event in which a person or organization was/is a participant; inverse of P710 or P1923

Provenance Loves Wiki 2024 - workshop taking place on 12-14 January 2024 in Berlin and online

Laurel Zuckerman - participant in - Provenance Loves Wiki 2024

International Conference Collect and Connect: Archives and Collections in a Digital Age - academic conference

Laurel Zuckerman - participant in - International Conference Collect and Connect: Archives and Collections in a Digital Age

Graph Technologies in the Humanities 2022 - academic conference

Laurel Zuckerman - participant in - Graph Technologies in the Humanities 2022

FIP.15.T3 | PARC FIP1 T3 - by Barbara Magagna

FIP.15.T9 | PARC FIP1 T9 - by Barbara Magagna

FIP15.T5 | PARC FIP1 T5 - by Barbara Magagna

FIP.15.T4 | PARC FIP1 T4 - by Barbara Magagna

M4M.29.T.1 | M4M Vocabulary Training for PARC - by Panče Panov

M4M.26.INT1| PARC M4M Introduction event 1 - by Barbara Magagna

M4M.28.T3 | PARC M4M Schema Training 3 - by Anjana Elapavalore

M4M.24.T2 | PARC M4M Training 2 - by Barbara Magagna

Direct download via primary repositories through HTTPS.

For some of the ACTRIS datasets, DOIs are still not available

Datacite is used by the parts of ACTRIS that have implemented DOIs for their datasets.

The metadata of the ACTRIS metadata catalog is indexed in WMO Information System (WIS) and available through their search engine.

ACTRIS DVAS FIP 2022: This is the FIP of ACTRIS DVAS (representing the choices made in 2022).

Benchmark submissions are given a number unique across MLCommons benchmarks. However, they are not resolvable by machines. The convention used is the benchmark round hyphenated with a unique submission number, e.g., 3.1-2000 for benchmark 3.1, first submission. Different benchmarks begin with different number spans, such as training begins at 2000 and HPC begins at 8000.

Similar to metadata, benchmark submissions are given a number unique across MLCommons benchmarks. However, they are not resolvable by machines. The convention used is the benchmark round hyphenated with a unique submission number, e.g., 3.1-2000 for benchmark 3.1, first submission. Different benchmarks begin with different number spans, such as training begins at 2000 and HPC begins at 8000. It would be optimal if each benchmark and round had a PID.

While there is no comprehensive metadata schema, a portion has been defined to describe systems used in benchmark submissions. That is documented at https://github.com/mlcommons/policies/blob/master/submission_rules.adoc#system_desc_id-json-metadata . Further, for a subset of benchmarks, rather than metadata (which would be better), meaning is embedded in directory structures. See https://github.com/mlcommons/policies/blob/master/submission_rules.adoc#directory-structure

To some extent, the metadata can be searched programmatically on GitHub. However, in practice the data (JSON system description files) must be downloaded and a custom script used for querying.

GitHub is the platform used for publishing the data, which is comprised of text and JSON files.

Partial metadata available (as described under Findability) via https via GitHub.

not applicable - all data openly available

JSON used to describe the system profiles for submitted benchmarks

Using internally defined MLCommons schema for system logs. mllog provides standardized log output.

At the moment there is only one direction link - metadata link to data

Not yet implemented - will be a institutional platform

ADVANCE FIP: This is the FAIR Implementation profile of the ADVANCE project within the scope of the Helmholtz Metadata Collaboraion

Each term in the IUPAC Gold Book has a registered DOI in CrossRef as a book chapter (https://www.crossref.org/documentation/research-nexus/books-and-chapters/); IUPAC Gold Book is overall 'book' (http://doi.org/10.1351/goldbook); term DOI metadata must include source PAC citations.

Locally developed and supported by IUPAC.

CrossRef metadata retrieval (free options), https://www.crossref.org/services/metadata-retrieval/

CrossRef metadata schema for book chapters (https://www.crossref.org/documentation/research-nexus/books-and-chapters/)

Presently being reviewed in an IUPAC project for the Gold Book.

CrossRef Events data (e.g., Wikipedia), https://www.crossref.org/services/event-data/

Per CrossRef: https://www.crossref.org/documentation/retrieve-metadata/rest-api/rest-api-metadata-license-information/

IUPAC default license is CC-BY-NC-ND. Authoritative chemistry concepts are defined and ratified by IUPAC; ND for no derivations of definitions without approval (including formatting and translations); NC for no use of terms in commercial settings without review.

IUPAC Gold Book (original FIP): This is the FIP of IUPAC Gold Book

Widely used for data citation, mainly used by us for collections and elaborated data products

Handle PIDs are used for all data objects at the highest possible granularity

As far as possible and provided by the persons we include ORCID ids with all personal metadata for attribution

All entries in the ICOS ontology are represented by PIDs or URIs

ePIC handles are generated to create persistent identifiers for instruments and other artefactsthat need to be persistently linked to data objects

DOIs are minted for data object that require citation, this can be documents, major higher level data products, important collections or supplemental data for scientific publications.

ePIC Handle PIDs are minted for each data object ingested at carbon portal, including collections

Services to be registered in the ENVRI Hub catalogue of services are described using the DCAT AP vocabulary using the EPOS extension. We also provide a direct mapping of ICOS metadata for L2 data objects to DCAT AP at https://meta.icos-cp.eu/sparqlclient/?q=DCAT%20metadata%20demo&type=XML

All ICOS data object landing pages have the metadata tagged in schema.org and indexed in Google Dataset search through the index page registered with Google.

All ICOS data object landing pages have the metadata available as XML encoded iso19115 through content negotiation and download button in the HTML landing page. The iso19115 XML metadata is dynamically brokered.

As defined by the CP white paper and to implement the open data sharing defined by the statutes of ICOS ERIC.

B2FIND harvested the ICOS metadata through the Datacite records for prefix 10.18160. See http://demo-b2find.cloud.dkrz.de/organization/icos

Will be implemented completely as soon as the OAI-PMH service at CP is ready, for now OpenAire indexed the ICOS data through Datacite for prefix 10.18160

All schema.org metadata from the ICOS data objects is indexed by Google Dataset Search

Dimensions indexes the ICOS Handle and Datacite prefixes

WIGOS will soon move from WMDR to WMDR2 (based on ISO19156 plus iAdopt) and as data transfer mechanism shift to WIS2. ICOS plans to follow this development.

The main faceted search data portal to find and access all ICOS and ICOS related data based on our ICOS ontology and sparql endpoint

ICOS Carbon Portal is from the start registered at re3data as community repository

Dimensions indexes and tracks citations of ICOS data objects registered at Datacite

Erddap is used as data publishing portal for the Ocean community to publish ICOS Ocean observations

open, free, and universally implementable protocol

We plan to run an instance of Viringo (https://github.com/datacite/viringo) that will serve both the ICOS Datacite DOI metadata as the iso19115 metadata from the ICOS L2+L3 products. Anyway metadata on ICOS data is harvestable through OAI-PMH through OpenAire and soon through B2FIND

The ICOS SPARQL open endpoint https://meta.icos-cp.eu/sparql serves (read-only) the complete ICOS ontology and all metadata in RDF format. It is used by most back-end and front-end services of the ICOS Carbon Portal. A GUI version is served at https://meta.icos-cp.eu/sparqlclient/

The m2m interfaces to interact with the meta and data services and other back end services are based on REST 'inspired' https calls. The calls are documented at the CP github repository at pages https://github.com/ICOS-Carbon-Portal/meta and https://github.com/ICOS-Carbon-Portal/data

Used in Jupyter hub and many other applications by the community for easy access to SPARQL, ontology, metadatahttps://pypi.org/project/icoscp/

Simple login using email address and password, confirmation of account through email, forgotten password routine with confirmation by email

For ORCID and Facebook identity providers

ORCID is a much used ID provider for researchers, using this enabling automated data sets addition to personal ORCID library of publications and data sets

Allows to federate account with many universities and RPOs

All ICOS data is available open and free.

ICOS is set up for the long term, 20-25 years starting from 2015. Statutes and data policy mention that data and metadata should be preserved also after that. In case ICOS ERIC is wound down in the future there will be a one year period to develop the contingency plan. All current landing pages generated dynamically by our metadata system can then be generated as static html pages that will together form a frozen metadata system which can be served by a simple static website at very low cost or be integrated as sub-site in another permanent website.

ICOS metadata ontology is modelled in OWL and represented in a triple store using RDF. Using our sparql endpoint metadata can be queried and results can be presented as RDF, turtle, CSV and XML. The ICOS metadata scheme is published at LOV: https://lov.linkeddata.es/dataset/lov/vocabs/cpmeta

ICOS metadata ontology is modelled in OWL and represented in a triple store using RDF. Using our sparql endpoint metadata can be queried and results can be presented as RDF, json, turtle, CSV and XML

CF-1.7 compliant netcdf metadata included in the netcdf data objects

http://meta.icos-cp.eu/ontologies/cpmeta/. The ICOS metadata scheme is also published at LOV: https://lov.linkeddata.es/dataset/lov/vocabs/cpmeta

Implemented as content negotiated XML returned for each data object landing page

As implicitly described by the ICOS statutes and formally decided by the ICOS GA in 2021

All ICOS data is licensed using the CCBY4 licence, as prescribed by the ICOS Statutes and decided by ICOS GA and described in the ICOS data policy (https://doi.org/10.18160/JDEE-PZNY)

Required for traceability and attribution to data providers

ICOS FIP 2023: This is the FIP of ICOS (representing the choices made in 2023).

GBIF uses DOIs in two distinct ways worth mentioning here: - DOI resolves to a Digital Object/package that includes structured metadata for the dataset and structured data files conforming to a schema. - GBIF assigns a DOI to search results when a user requests a download

Google Dataset Search indexes both described and downloaded datasets.

GBIF is currently expanding its use of community-curated controlled vocabularies within the framework of Darwin Core.

WorldFAIR WP09 Biodiversity FIP01: This is the FIP of WorldFAIR WP09 Biodiversity

Convenient web-based retrieval based on assigned material ID. e.g. <https://materialsproject.org/materials/mp-1234>.

URLs for raw data minted and served by NOMAD Laboratory <https://nomad-lab.eu/>.

The OSTI DOI Identifier Service (http://purl.org/np/RAyIQx7rn1CDYgTqRlSbsZY0yQz46VxRzSgfMp138QInM) provides a schema.org Dataset profile via DataCite.

http://datacite.org/schema/kernel-4 is provided

Links from data are either to material DOIs via https://doi.org/ URLs or material entities via https://materialsproject.org/ URLs.

Seemed like a good idea to register here.

Materials Project: This is the FIP of Materials Project

Persistent identification of research sites and observation facilities.

eLTER DIP is the central access point to eLTER metadata from a range of sources using geonetwork as backbone technology.

General eLTER data policy fosters open data. Restrictions might apply for site based data under embargo.

Will be replaced in the long run by the final eLTER RI Data Spec.

eLTER FIP 2019: This is the FIP of eLITER (representing the choices made in 2019).

Currently not using a findability metadata schema

PARC HBM | PARC Human Biomonitoring Data

PARC HBM | PARC Human Biomonitoring Data: This is the FIP of PARC HBM | PARC Human Biomonitoring Data

The architecture of the dataset schema fits with the metadata that we wish to create for our resource.

The architecture of the data base matching the data schema.

We want to provide an unrestricted access to the data

PandemicPACT FIP: This is the FIP of PandemicPACT

GalaxyClimate: FIP for the Galaxy Climate Community

Files are encrypted by themselves with private and public keys.

HBM4EU | Human BioMonitoring 4 EU Project

HBM4EU | Human BioMonitoring 4 EU Project: This is the FIP of HBM4EU | Human BioMonitoring 4 EU Project

Ontology aligned for PBPK modelling in life science domain

transport to non-native range decreases number of enemies

number of enemies - concept in invasion biology

transport to non-native range - concept in invasion biology

biological invasion - process in which organisms become established in a region where they previously did not exist and then rapidly expand their range

reduced pressure by generalist enemies in the non-native range contributes to invasion success

invasion success - concept in invasion biology

reduced pressure by generalist enemies in the non-native range - concept in invasion biology

reduced pressure by specialist enemies in the non-native range contributes to invasion success

reduced pressure by specialist enemies in the non-native range - concept in invasion biology

Physiologicaly based pharmacokinetic modelling community for toxicology.
Physiology Based Pharmacokinetic modelling community for PARC

number of enemies of invasive species has smaller value than number of enemies of native species

number of enemies of invasive species - concept in invasion biology

number of enemies of native species - concept in invasion biology

number of enemies of invasive species in its non-native range has smaller value than number of enemies of invasive species in its native range

number of enemies of invasive species in its non-native range - concept in invasion biology

number of enemies of invasive species in its native range - concept in invasion biology

reduced pressure by enemies in the non-native range increases performance of non-native species

reduced pressure by enemies in the non-native range - by Daniel Mietchen

performance of non-native species - ecological concept

RDF-XML is a syntax, defined by the W3C, to express (i.e. serialize) an RDF graph as an XML document.

O’FAIRe is a web service designed to evaluate the conformity of semantic artefacts like ontologies and SKOS vocabularies to the FAIR principles. It is integrated to the Ontoportal solution and available on the Agroportal, BiodivPortal, EarthPortal, EcoPortal, SIFR BioPortal and IndustryPortal semantic resource repositories. It is based on Emna Amdouni, Syphax Bouazzouni, Clement Jonquet. O'FAIRe makes you an offer: Metadata-based Automatic FAIRness Assessment for Ontologies and Semantic Resources. International Journal of Metadata, Semantics and Ontologies, 2022, 16 (1), pp.16-46. ⟨10.1504/IJMSO.2022.131133⟩. ⟨lirmm-03630233v2⟩

Ecoportal is a repository for semantic resources in the ecological domain, developed by LifeWatch ERIC, for different kinds of stakeholders (researchers, vocabularies managers, data managers, ontologists, etc.). Ecoportal supports the community in the creation, management, mapping and alignment of its semantic resources and subsequently also of its data.

absence of enemies in the non-native range contributes to invasion success

absence of enemies in the non-native range - concept in ecology

We are producing guidelines that incorporate some fundamental principles in order to guide the users in creating FAIR resources. O'FAIRe tool has been implemented in the last version of EcoPortal in order to check the level of FAIRness of the published resources and it assess weak points, allowing the user to improve it.

Metadata for Ontology Description is used as schema for semantic artefacts (i.e. thesauri and ontologies) metadata exposed on the LifeWatch ERIC Ecoportal.

We are producing guidelines incorporating the suggestions coming from the European projects like FAIR-IMAPCT, FAIRsFAIR, etc. O'FAIRe tool has been implemented in the last version of EcoPortal in order to check the level of FAIRness of the published resources and it assess weak points, allowing the user to improve it.

Ecoportal is an instance of OntoPortal, and it uses its interface to guide the writing and the editing of the metadata deposited on Ecoportal.

VocBench is a web-based, multilingual, collaborative development platform for managing OWL ontologies, SKOS(/XL) thesauri, Ontolex-lemon lexicons and generic RDF datasets.

FIP.15.T7 | PARC FIP Training - nanopublications - by Barbara Magagna

FIP.21.T.1 | Training for FIP Facilitators - by Juliana Menger

DOI assigned via Sextant to each metadata. Example : http://dx.doi.org/10.12770/a7b7d13f-0b95-445b-ba83-fe9357c9e154

DOI assigned via Sextant to each metadata

Metadata uses schema based on ISO19115/139

Dedicated search interface : https://www.seadatanet.org/Products#/search?from=1&to=30

Harvesting of the catalogue bu using CSW : https://sextant.ifremer.fr/geonetwork/SEADATANET/eng/csw?SERVICE=CSW&REQUEST=GetCapabilities

Marine-ID is generally accepted method and solution for AAA in the marine domain

Metadata records available in RDF via SPARQL endpoint : https://sextant.seadatanet.org/sparql/

The NVS have been developed by BODC based on the SDN requirements and specifically fulfill the needs of the marine data community.

NVS service used as main vocabulary for parameters, instruments etc.

metadata directories used as vocabularies to describe organisations, cruises, projects with relation to the data

metadata for products are based on ISO19115/19139, extended with the domain profile with vocabs etc. The ISO requirement originates from the overarching infrastructures that demanded inspire standards.

Seadatanet products have implemented CC-BY

There was already provenance info in the metadata,