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

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

open, free, and universally implementable protocol

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,

Ontology aligned for PBPK modelling in life science domain

ShowVoc is a web-based, multilingual, platform for publishing and consulting OWL ontologies, SKOS(/XL) thesauri, Ontolex-lemon lexicons and generic RDF datasets.

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQC43tmJLyR56AKqcDyyOwM4KQVEs4NlrzA2FUh8edrJ+66A5Hkyosvt2DTtcNiSZ+jIgRNHpYsteZJxaNZtjaFnh4oZt0jYa3Bm8lE24yJgNF+i3MQz71eAZhYWuwt+98r9CqxebeDKS43wpZjJ7pQ7nWXNUTbynt2XsJ+7ufdfFnPuXtx3OamCOZbLZcoml+UrYzn+5W2zVGWHpWvKgiixjy6uw0KG3Rdne4EuzfoORDFnbiakt2KVUxGobhPfPr7mCnYjC6cGB/mdzxuuc43kpD0grfD2OfbwA4SnzJ86afXlvwlKZcea40po2VkTfXnRPpDHhP10OCR1g8DxmIPgkuR23mIMMzhcSgMKx1UPhy6iCnoyF6fsU8Y6FOpZPikLT5h80geeaAywAW0xyCEnh+yVw0ZqgMFA74do0u1Rrdc6HJdxmWQfMbKdV6V/8v9csFvffIK/nQloMqBjlyQ9Ni4hv5iyiY1jwcHJ9tK7uzp7/xR/YSPp+oT3AqRRGhk= rkl25@rkl-Carbon

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

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.

PARC Human Biomonitoring Data - by (unknown)

M4M.32.W.6 | PARC HBM Metadata - by Ruben Peeters

knowledge representation and reasoning - field of artificial intelligence on representing information in a form that a computer system can use to solve complex tasks

think this is underrated: knowledge representation and reasoning

The GFTS Community aims at developing and implementing a Global Fish Tracking System (GFTS) to enhance understanding and management of wild fish stocks.
Global Fish Tracking System (GFTS) Community

Community for the members of Simula Research Laboratory.

We’re indexing through Libris, the Swedish national library catalogue, which is based on BIBFRAME 2.0.

This data format is used for the representation of data.

This data format is used when downloading results from SPARQL endpoints.

In Quebec, people mainly use the Répertoire des vedettes matières de l’Université Laval instead of LCSH.

Homosaurus uses this very strict licence.

LGBTQ+ Linked Open Vocabulary FIP: This is the FIP for the LGBTQ+ Linked Open Vocabulary community.

CMIP6 data FIP: This is the FIP of teh CMIP6 data community.

Custom built identifier system set up before other PID systems were easily available.

PID assigned via B2Handle to each datafile when stored in cloud. Please mint a B2 Handle nanopub

Extended metadataschema based on ISO19139 to accommodate for oceanography specifics

expanded with community profile, incl vocabs

used for describing the sensor by which the data was collected.

No generic system was available, and because of the ammount of metadata records DOI's are not feasible. Therefore dedicated PID-CDI identifier solution.

Aggregated records exposed to GEOSS Geoportal

Overarching services demand harvesting of metadata via OGC services

domain always requested into about preservation of data and metadata, captured in the data policy, however not machine actionable

Dedicated user interface offering facets to search the large collection of data sets (>2.7M).

sparql endpoint for aggregated and original granularity developed, updated to DCAT AP and published, in ao ENVRIHUB.

webpages with schema.org and metadata indexed by google

Linked data for CDI published to Google data set search

aggregated data as well as WMS/WFS are indexed

Aggregated records published via OpenSearch

A sparql endpoint is now available for aggregated records AND for original granularity with over 60M triples. in RDF... cdi.seadatanet.org/sparql

no actions made here, implicit in internet access.

Access via Marine-ID (CAS) authentication in the CDI service

was already implemented behind marine-id

metadata records in RDf via SparQL endpoint, updated for CDAT-AP compliance!

The NVS have been developed by BODC based on the SDN requirements and specifically fulfill the needs of the marine data community. Vocab L22 now added in the metadata to describe sensor information, and a link to sensor instance info added.

SDN has developed metadata directories for organisations, cruises, research projects, databases, that are involved in, or used by, the datacenters when collecting data. In the metadata of the datasets there are refs to these metadata directories (instead of free text!).

implemented as part of sharing via ENVRIHUB

part of the metadata model, used when sharing biodiversity data via BIO-ODV format

NVS service used as main vocabulary for parameters, instruments, etc. vocab L22 - Sensor type - added in metadata.

metadata for datasets in CDI format 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.

implemented as part of envrifair work for uptake in Envrihub

included ref in metadata for providing detailed sensor instance information

added to CDI (and other metadata directories) metadata as part of envrifair work

sdn netcdf is compliant to cf1.7, always been the case.

CDI was using https://www.seadatanet.org/Data-Access/License/1.0 but now mapped to CCBY and implemented

There was already provenance info in the metadata, now added more info about sensors via L22 and link to sensor instance (SWE).

always been in use, cdi metadataformat is based on it.

extended sensor metadata, which is available from a ref from the metadata xml.

added as part for envrifair work to describe the sensor info as prov for the data

SeaDataNET CDI FIP 2022: This is the FIP of SeaDataNET CDI community recording the FERs for 2022.

CMIP6 data FIP: This is the FIP of the CMIP6 data community.

SeaDataNET Sextant FIP 2019: This is the FIP of the SeaDataNET Sextant community recording the FERs of 2019.

SeaDataNET Sextant FIP 2020: This is the FIP of the SeaDataNET Sextant community recording the FERs of 2020.

SeaDataNET Sextant FIP 2021: This is the FIP of the SeaDataNET Sextant community recording the FERs of 2021.

The URI holds the historically assigned local incremental ID in the RDBMS.

DOI's can be added upon request to the metadata records. If assigned, they function as an alias to the URI.

The URI holds the historically assigned UUID in the system.

Internally the metadata registry uses its own custom model that enables supporting multiple schemata, among which ISO 19115.

Internally the metadata registry uses its own custom model that enables supporting multiple schemata, among which EML GBIF.

Internally the metadata registry uses its own custom model that enables supporting multiple schemata, among which DataCite.

Internally the metadata registry uses its own custom model that enables supporting multiple schemata, work to support schema.org is still under way.

Internally the metadata registry uses its own custom model that enables supporting multiple schemata, work to support DCAT is still under way.

Requirement for sharing datasets with one of our partners.

Since our metadata registry has a public facing web-interface, even for anonymous users, it was straightforward to let it be indexed by Google.

Since our dataset archive has a public facing web-interface, even for anonymous users, it was straightforward to let it be indexed by Google.

Was best choice at the time for machine access.

In order to be fully m2m accessible, we aim to add this resource next year.

To be added in the future for datasets for which this service will work.

Data are added by users who require an account (uname and psswd). Data in private folders are not publically-accessible : if you click on a data link, you will get a message to that effect. Data in the public folders are accessible and a click on the link will start the download. Uses a custom SSO system called 'InovOcean-auth'.

Was best at the time for an addition to EML.

To be added to our general catalogue, but for data already in DwC-A format (EMOnet and EurOBIS only) this vocabulary is already used and correctly referenced in the data.

Darwin Core is an extension of Dublin Core, and it used EML as its metadata. In addition, DwC-Archive data format incorporates particular vocabularies that are referenced to within the archive.

For ecological data. In fact, the EML version (2.1) we currently use does not have full semantic annotation, but we are looking into adopting the version (2.2) that does introduce better support for that.

Supporting DCAT makes us align with growing use within the EU (as prescribed through the semic-eu DCAT-A -- https://github.com/SEMICeu/DCAT-AP.

Historic support for this standard has been built in for quite some time.

Data format used by EurOBIS and EMODNet/Bio.

Working being done in H2020 ENVRI-FAIR project.

Data in our Marine Data Archive, on EurOBIS, and EMODnet Biology, always belong to the data owner, not the system. Hence we wish to allow them a full range of licences, although we encourage CC BY (especially EurOBIS and EMODnet). LifeWatch.be data are also mostly CC BY.

In some cases CC0 is concidered 'too open' - and since the academic context has a tendency for proper citation and attribution this step up is considered very mild.

In some cases, people like this 'viral' addition. Making sure we all play with the same openness rules in mind.

Our data are ecological, so we use EML. There are fields in EML to accommodate provenance, and we are hoping that this can be expanded on in the near future.

To expand on the options we offer (albeit the amount of provenance included in the json export is quite sparse).

This is only for data provided via EurOBIS.

LifeWatch Marine FIP 2020: The formal FIP description of the IMIS and MDA systems in use by Lifewatch Marine - Status 2020

Requirement for sharing datasets with one of our partners. Progress since 2020 has been made, but is not fully operational yet. Required fields are added to the database, exposing the inspire format is in test a

In use and harvested by Lifewatch-ERIC catalogue

LifeWatch Marine FIP 2021: The formal FIP description of the IMIS and MDA systems in use by Lifewatch Marine - Status 2020

LifeWatch Marine FIP 2019: The formal FIP description of the IMIS and MDA systems in use by Lifewatch Marine - Status 2020

Requirement for sharing datasets with one of our partners. Completed development in 2022.

FAIR-signposting approach nicely fits our focus on applying Linked Open Data principles and techniques

Since we are embracing more and more Linked Open Data strategies, we are now adding this LDES change feed of our metadata-records next to the existing OAI-PMH implmentation) This will become available under the domain marineinfo.org

Implementation deployed as part of the WP9 work for ENVRI-FAIR

We do a best effort to keep metadata available and describe what will happen in case we can no longer guarantee.

Deployed as part of the ENVRI-FAIR project

maintained metadata records are fully open

LifeWatch Marine FIP 2022: The formal FIP description of the IMIS and MDA systems in use by Lifewatch Marine - Status 2020

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 defined by the CP white paper and to implement the open data sharing defined by the statutes of ICOS ERIC.

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 document at the CP github repository at pages https://github.com/ICOS-Carbon-Portal/meta and https://github.com/ICOS-Carbon-Portal/data

For ORCID and Facebook identity providers

ICOS will be 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.

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

ICOS FIP 2019: This is the FIP of the ICOS community.recording the FERs of 2019.

Access via Marine-ID authentication in the CDI service

metadata records in RDf via SparQL endpoint

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

also available - flattened for the sdn community profile

Now using https://www.seadatanet.org/Data-Access/License/1.0 but will be made as GUPRI under ENVRIFAIR, plus mapping to CCBY. Mapping has been made as preparation.

There is already provenance info in the metadata, but more info about sensors involved will be included.

SeaDataNET CDI FIP 2020: This is the FIP of the SeaDataNET CDI commjnity recording the RERs for 2020.

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

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/

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 FIP 2020: This is the FIP of the ICOS community recording the FERs for 2020.

FIP.21.T.3 | FIP Facilitator training - by Andrea Tarallo

M4M.32.W.2 | PARC HBM Metadata - by Ruben Peeters

M4M.32.W.5 | PARC HBM Metadata - by Ruben Peeters

M4M.32.W.1 | PARC Human Biomonitoring - by Ruben Peeters

M4M.32.W.3 | PARC HBM Metadata - by Ruben Peeters

M4M.30.IOP.T.2 | PARC WP7 M4M Training - I-ADOPT - Part 2 - by Jana Boruvkova

nanopublication for Lorentz workshop on FAIR 2024

Pubinfo template: nanopublication for Lorentz workshop on FAIR 2024

The Lorentz workshop on 'The Road to FAIR and Equitable Science' has started!

Participation of: the-road-to-fair-and-equitable-science.html

participated in - Connects a person (left) an event (right) he/she participated in.

The creator of such a nanopublication declares to have participated in the specified event.

Template: Declaring the participation in an event

Participation in: the-road-to-fair-and-equitable-science.html

link your message is about or with additional info

Template: Publishing a plain-text message

Check out my video about machine actionability and FAIR: https://www.youtube.com/watch?v=JuFhyc9cdUQ

Check out this video of mine about nanopublications: https://www.youtube.com/watch?v=4eM1bTdnSfA&t=10s

Check out this video of mine about nanopublications: https://www.youtube.com/watch?v=4eM1bTdnSfA&...

Rob Hooft: "AI is just a modern name for expert systems." :)

Very interesting: "Cross-Domain Interoperability Framework" https://worldfair-project.eu/cross-domain-interoperability-framework/

Very interesting: "Cross-Domain Interoperability Framework" https://worldfair-project.eu/cross-do...

Learned that SciELO is working on using nanopublications. Very interesting development.

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

The most common PID mechanism is indicated above.

Harmonized EMSO ERIC data services also use other mechanisms for identification of data and products.

EMSO ERIC uses a harmonized metadata schema based on OceanSites specifications, CF and other conventions. The final document is not publicly available yet. The schema is used through different mechanisms such as NetCDF (below) and ERDDAP.

Metadata are registered in NetCDF files and text, available through https from portal and ERDDAP.

Datasets are provided in NetCDF files and text (CSV), available through https from portal and ERDDAP.

Metadata records are publicly available.

Most of datasets are made publicly available; however, some functionalities requires authentication and authorization.

Metadata records using DOIs are compliant with RDF.

Datasets using DOIs are compliant with RDF.

Harmonized metadata uses NERC Vocabulary Server (NVS).

Harmonized datasets use NERC Vocabulary Server (NVS)

EMSO ERIC uses a harmonized metadata schema based on OceanSites specifications, CF and other conventions. The final document is not publicly available yet.

Use license is currently being harmonized across EMSO ERIC regional facilities; however, the most common is provided above.

Provenance is currently being harmonized across EMSO ERIC regional facilities; however, the most common mechanism is currently via NetCDF.

EMSO ERIC FIP 2022: This is the FIP of EMSO ERIC (representing the choices made in 2022).

EMSO ERIC FIP 2021: This is the FIP of EMSO ERIC (representing the choices made in 2021).

EMSO ERIC FIP 2020 bm: This is the FIP of EMSO ERIC bm (representing the choices made in 2020).

Datasets are indexed in different engines such as google data search, SEANOE, PANGAEA, and aggregators.

EMSO ERIC FIP 2019 bm: This is the FIP of EMSCO ERIC bm (representing the choices made in 2019).

Social Science Survey Research V2: This is the FIP of Social Science Survey Research V2

The current URI pattern for the IPCHEM metadata page is the following: https://ipchem.jrc.ec.europa.eu/#showmetadata/<DATASET> (e.g. https://ipchem.jrc.ec.europa.eu/#showmetadata/HBM4EUALIGNEDSTUDIES). And for the corresponding JSON version, the URI pattern is the following: https://ipchem.jrc.ec.europa.eu/public/<DATASET>/IPCheM_<DATASET>_metadata.json (e.g. https://ipchem.jrc.ec.europa.eu/public/HBM4EUALIGNEDSTUDIES/IPCheM_HBM4EUALIGNEDSTUDIES_metadata.json). With the transfer of the IPCHEM functionalities to the upcoming CPDC platform, new URIs could be implemented by using the Persistent URI service of the Publication Office (https://op.europa.eu/en/web/webguide/uris#persistive-uri)

The current URI for the IPCHEM public dataset package summary is the following: https://ipchem.jrc.ec.europa.eu/public/IPCHEM_public_dataset_packages.csv. And for each dataset, the partial package summary URI pattern is the following: https://ipchem.jrc.ec.europa.eu/public/<DATASET>/IPCHEM_<DATASET>_package_summary.csv (e.g. https://ipchem.jrc.ec.europa.eu/public/HBM4EUALIGNEDSTUDIES/IPCHEM_HBM4EUALIGNEDSTUDIES_package_summary.csv). The package summaries contain the list of data packages available for each public dataset. Highest granularity data packages are split by chemical/media/period; cumulative data packages are available as well, split by period in the case of regular collections (e.g. yearly). The package name patterns are the following: a) https://ipchem.jrc.ec.europa.eu/public/<DATASET>/IPCHEM_<DATASET>_<UUID>.zip [datasets collected irregularly] (e.g. https://ipchem.jrc.ec.europa.eu/public/CNRPFAS/IPCHEM_CNRPFAS_3185f1f5-212c-4a2b-917a-4a8060115dd6.zip); b) https://ipchem.jrc.ec.europa.eu/public/<DATASET>/<PERIOD>/IPCHEM_<DATASET>_<UUID>.zip [datasets collected periodically] (e.g. https://ipchem.jrc.ec.europa.eu/public/WATERQUALITY/2014/IPCHEM_WATERQUALITY_519b7aba-2c74-40a3-a8a1-01b18eb55cd6.zip). With the transfer of the IPCHEM functionalities to the upcoming CPDC platform, new URIs could be implemented by using the Persistent URI service of the Publication Office (https://op.europa.eu/en/web/webguide/uris#persistive-uri).

UUIDs are currently used in the package name patterns, as described in the previous FER (i.e. data URI). No versioning mechanism is implemented to persist the formerly created and subsequently amended packages, the previous UUIDs are simply lost. A possible enhancement could be to introduce versioning date as an additional field of the package summary, and to keep track of the former package UUIDs and corresponding files, for better traceability and replicability.

Dataset metadata fiches are currently compiled by filling three alternative templates: IPCHEM basic, HBM4EU and Indoor Air (xlsx). These are transformed automatically into JSON, and deployed to the public data package repository, as described in the previous FER (i.e. metadata URI). A possible evolution could be the JSON-LD enhancement, thus including the scheme within the same metadata JSON. With the transfer of the IPCHEM functionalities to the upcoming CPDC platform, the DCAT-AP scheme could be implemented through the dataset registration via the Data Provider Interface service of the data.europa.eu platform (https://dataeuropa.gitlab.io/data-provider-manual/data-provider-interface).

Currently the link between metadata and data in IPCHEM is based on the unique identification codes of datasets in the platform, that can be used to identify harmonised data packages and specific records picked-up from the dataset console. Possible future implementation of DCAT in the context of CDPC.

Currently IPCHEM public dataset metadata are accessible through the public dataset package repository in the form of JSON files: ipchem.jrc.ec.europa.eu/public. Possible registry service implementation in the context of CDPC

Currently IPCHEM public dataset packages are accessible through the public dataset package repository in the form of CSV (zip) files: ipchem.jrc.ec.europa.eu/public. Possible registry service implementation in the context of CDPC

The current URI pattern for the IPCHEM metadata page is the following: https://ipchem.jrc.ec.europa.eu/#showmetadata/<DATASET> (e.g. https://ipchem.jrc.ec.europa.eu/#showmetadata/HBM4EUALIGNEDSTUDIES). And for the corresponding JSON version, the URI pattern is the following: https://ipchem.jrc.ec.europa.eu/public/<DATASET>/IPCheM_<DATASET>_metadata.json (e.g. https://ipchem.jrc.ec.europa.eu/public/HBM4EUALIGNEDSTUDIES/IPCheM_HBM4EUALIGNEDSTUDIES_metadata.json). With the transfer of the IPCHEM functionalities to the upcoming CPDC platform, the SPARQL communication protocol could be implemented through the dataset registration via the Data Provider Interface service of the data.europa.eu platform (https://dataeuropa.gitlab.io/data-provider-manual/data-provider-interface).

Possible implementation in the context of CDPC

Not explicitly stated in IPCHEM; However, in the JRC Data Catalogue the 'Use conditions' for AIRMEX are 'European Commission Reuse and Copyright Notice' (https://data.jrc.ec.europa.eu/licence/com_reuse). Maybe EUPL_1_2 is applicable as alternative (http://publications.europa.eu/resource/authority/licence/EUPL_1_2, https://opensource.org/license/eupl-1-2/)

the usage license for datasets in IPCHEM is stated by the data provider in the participation form and in the metadata fiche

The IPCHEM metadata fiche, in addition to the general description of the dataset, includes the following specific fields which aim to support its possible reuse: Monitoring reason(s), Sampling method(s), Analytical method(s), Responsible organization (name and PoC), Other Contributors, General Links, Linked resources about the data collection. Future DCAT-AP compliance is to be considered in the context of the CDPC.

Cost effective solution, our data portal requires lots of PIDs due to large number of digital objects.

DOIs required for collections, e.g. yearly data sets.

Our data portal already assigns PIDs (EPIC handle) for any arbitrary data collection downloaded by the user.

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.

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

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