Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- declaration considerations "Not yet implemented. The objective is to add PROVenance elements to the semantic characterisation already in use in AnaEE for the description of data and their contexts, and to implement it using the developped pipelines" assertion.
- declaration considerations "The one-click download of Argo data and metadata is available from this DOI: https://doi.org/10.17882/42182.These are monthly snapshot of the whole Argo dataset (GDAC data)" assertion.
- declaration considerations "We think that a persistent identifier for individual cycle file (2 million of them) should be provided. It won't be DOI, it should be a handle." assertion.
- declaration considerations "There should be one pid per Argo float cycle. There are more than 2 million cycles. The pid will be resolved by an Ifremer 'argo data selection' web landing page." assertion.
- declaration considerations "The one-click download of Argo data and metadata is avilable from this DOI: https://doi.org/10.17882/42182" assertion.
- declaration considerations "The data and metadata organization are described in: Argo user's manual, http://dx.doi.org/10.13155/29825. It describes the NetCDF CF implementation for Argo data" assertion.
- declaration considerations "The Argo GDAC DOI (https://doi.org/10.17882/42182) uses the schema.org metadata schema." assertion.
- declaration considerations "The DOI DataCite schemas" assertion.
- declaration considerations "Google dataset search is efficient for cross domain search." assertion.
- declaration considerations "The Argo data selection is a dedicated and specialized to our Argo community" assertion.
- declaration considerations "The Argo floats dashboard interactively provides Argo metadata from the Argo GDAC. https://fleetmonitoring.euro-argo.eu" assertion.
- declaration considerations "This is the Argo ERDDAP server.This API provides access to Argo data and metadata. https://www.ifremer.fr/erddap" assertion.
- declaration considerations "The Argo Opensearch engine is available on : https://opensearch.ifremer.fr/" assertion.
- declaration considerations "Argo DOI is indexed on Google, Bing, Seanoe, OpenSearch, google dataset search" assertion.
- declaration considerations "This is a data selection tool with Argo specific subsetting criteria (parameters, deployment years, network). Its API is : https://dataselection.euro-argo.eu/swagger-ui.html#" assertion.
- declaration considerations "Metadata are registered in NetCDF files available from https or ftp" assertion.
- declaration considerations "Data are registered in NetCDF files available from https or ftp" assertion.
- declaration considerations "The metadata access is anonymous. The download statistics from https and ftp servers are analyzed without user identification." assertion.
- declaration considerations "The data access is anonymous. The download statistics from https and ftp servers are analyzed without user identification." assertion.
- declaration considerations "The long term preservation of Argo dataset is shared by Ifremer and US-NCEI. Both sites preserve and mint regular DOIs of the whole dataset (monthly snapshots)" assertion.
- declaration considerations "The Argo DOI representation language is compliant with DataCite RDF schema and RDF Schema.org " assertion.
- declaration considerations "The Argo DOI representation language is compliant with DataCite RDF schema and RDF Schema.org " assertion.
- declaration considerations "The Argo community decided 20 years ago to distribute data and metadata in NetCDF files. The Argo NetCDF format is regularly improved." assertion.
- declaration considerations "Argo metadata such as sensor type, history records are recorded in Argo NetCDF self descriptive variables. The controlled vocabularies are published on NVS vocab server." assertion.
- declaration considerations "The Argo vocabularies used in NetCDF files are published on NVS vocab server" assertion.
- declaration considerations "We use DataCite and Schema.org for Argo data and metadata DOI" assertion.
- declaration considerations "The Argo data DOI is based on DataCite Metadata scheme" assertion.
- declaration considerations "We use DataCite and Schema.org for Argo data and metadata DOI" assertion.
- declaration considerations "Argo data and metadata are distributed with a CC-By license" assertion.
- declaration considerations "Argo data and metadata are distributed with a CC-By license" assertion.
- declaration considerations "The Argo NetCDF implementation contains detailed provenance information : data state, processing state, history of adjustements" assertion.
- declaration considerations "The provenance information is recorded in Argo NetCDF implementation documented on http://dx.doi.org/10.13155/29825" assertion.
- declaration considerations "The Argo ontology uses PROV-O to record provenance information. This information can be queried from Argo SPARQL endpoint: https://sparql.ifremer.fr/argo/query." assertion.
- declaration considerations "The digital object identifier (DOI) system is widely used within the biomedical domain." assertion.
- declaration considerations "The digital object identifier (DOI) system is widely used within the biomedical domain." assertion.
- declaration considerations "DCAT is recommended by W3C and DCAT is the foundation for open dataset descriptions in the European Union public sector and was adapted by the ISA programme (Interoperability solutions for public administrations) of the European Commission." assertion.
- declaration considerations "The digital object identifier (DOI) system is widely used within the biomedical domain." assertion.
- declaration considerations "Central location for data storage and analysis for the neurodegenerative disease community." assertion.
- declaration considerations "Public landing point for the EPND platform created for the alzheimer community and other interested parties ." assertion.
- declaration considerations "European node for data storage and analysis for the neurodegenerative disease community." assertion.
- declaration considerations "Widely accepted protocol of communication for web services, REST aims for fast performance, reliability, and the ability to grow." assertion.
- declaration considerations "Widely accepted protocol of communication for web services, REST aims for fast performance, reliability, and the ability to grow." assertion.
- declaration considerations "OpenID is an open standard and decentralized authentication protocol promoted by the non-profit OpenID Foundation. It is widely accepted and used to perform authentication, i.e. identity verification of a user." assertion.
- declaration considerations "OAuth 2.0 is a widely accepted open standard for access delegation and it allows clients to access data without sharing user's credentials, it is thus a protocol for authorisation purposes." assertion.
- declaration considerations "OpenID is an open standard and decentralized authentication protocol promoted by the non-profit OpenID Foundation. It is widely accepted and used to perform authentication, i.e. identity verification of a user." assertion.
- declaration considerations "OAuth 2.0 is a widely accepted open standard for access delegation and it allows clients to access data without sharing user's credentials, it is thus a protocol for authorisation purposes." assertion.
- declaration considerations "OAuth 2.0 is a widely accepted open standard for access delegation and it allows clients to access data without sharing user's credentials, it is thus a protocol for authorisation purposes." assertion.
- declaration considerations "JSON is a language-independent and open standard file format and data interchange format that uses human-readable text. It is therefore chosen due to its flexibility." assertion.
- declaration considerations "RDF is a directed graph composed of triple statements and the format of choice for the semantic web community." assertion.
- declaration considerations "OWL is the recommended language by W3C to represent ontologies and we use medical ontologies to make data semantically interoperable." assertion.
- declaration considerations "DCAT is widely used in the medical domain, and we plan to use fair data points that also rely on DCAT." assertion.
- declaration considerations "We use shacl to go from an open world concept in ontologies to a more closed world solution that guarantees interoperability between datasets. " assertion.
- declaration considerations "We use the cedar workbench to reuse and create metadata json templates, then export these to the github page of the community. " assertion.
- declaration considerations "SNOMED is the most used vocabulary in the medical domain." assertion.
- declaration considerations "SNOMED is the most used vocabulary in the medical domain." assertion.
- declaration considerations "SNOMED is the most used vocabulary in the medical domain." assertion.
- declaration considerations "FAIR data points take care of a lot of the the metadata needed for Findability and Reusability, and a uniform open way of Accessing the data. The FAIR data point also addresses the Interoperability of the metadata it stores, but it leaves the Interoperability aspects for the data itself to the data provider." assertion.
- declaration considerations "FAIR data points take care of a lot of the the metadata needed for Findability and Reusability, and a uniform open way of Accessing the data. The FAIR data point also addresses the Interoperability of the metadata it stores, but it leaves the Interoperability aspects for the data itself to the data provider." assertion.
- declaration considerations "" assertion.
- declaration considerations "Dataset can be identified by URI and downloaded." assertion.
- declaration considerations "We are going to FAIRify it" assertion.
- declaration considerations "We are going to FAIRify it" assertion.
- declaration considerations "We are going to FAIRify it" assertion.
- declaration considerations "We are going to FAIRify it" assertion.
- declaration considerations "In the future we are going to use FAIR Data Point or/and SPARQL API" assertion.
- declaration considerations "In the future we are going to use FAIR Data Point or/and SPARQL API" assertion.
- declaration considerations "In the future we are going to use FAIR Data Point or/and SPARQL API" assertion.
- declaration considerations "In the future we are going to use FAIR Data Point or/and SPARQL API" assertion.
- declaration considerations "All resources are publicly available." assertion.
- declaration considerations "All data are publicly available" assertion.
- declaration considerations "All data are publicly available" assertion.
- declaration considerations "All data are publicly available" assertion.
- declaration considerations "All data are publicly available" assertion.
- declaration considerations "Not FAIR enough. Will be transformed into vacabulary." assertion.
- declaration considerations "Not FAIR enough. Will be transformed into vacabulary." assertion.
- declaration considerations "Not FAIR enough. Will be transformed into vacabulary." assertion.
- declaration considerations "The DOIs are the best way to permanently identify a given digital object, in a format controlled by the International DOI Foundation. We have an agreement with DataCite and this will guarantee the cross-domain findability. When a DOI is not available, users can specify a persistent internal identifier." assertion.
- declaration considerations "The DOIs are the best way to permanently identify a given digital object, in a format controlled by the International DOI Foundation. We have an agreement with DataCite and this will guarantee the cross-domain findability. When a DOI is not available, users can specify a persistent internal identifier." assertion.
- declaration considerations "We use the ISO 19139:2007 profile for several kinds of metadata resources, that are: services, workflows, virtual research environments, and research sites." assertion.
- declaration considerations "We use the EML 2.2.0 standard for datasets metadata records." assertion.
- declaration considerations "We have an agreement with DataCite." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue is based on GeoNetwork 3.10, that has been customized according to our different needs and requirements. It allows to manage and publish metadata records of five types of digital resources, that are research sites, datasets, services, workflows, and Virtual Research Environments. LifeWatch ERIC is a direct member of DataCite and it can provide a Digital Object Identifier (DOI) for metadata records that do not have it, taking advantage of the GeoNetwork – DataCite connection." assertion.
- declaration considerations "EcoPortal is based on OntoPortal Virtual Appliance, version 3.1.1 that has been customized according to our different needs and requirements. It is a repository for semantic resources in the ecological domain, 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. LifeWatch ERIC is a direct member of DataCite and it can provide a Digital Object Identifier (DOI) for semantic resources that do not have it, taking advantage of the EcoPortal – DataCite connection." assertion.
- declaration considerations "It represents the search engine of DataCite (https://search.datacite.org), hence it allows to find, access and reuse all LifeWatch ERIC research digital objects that have a DOI. " assertion.
- declaration considerations "Being the LifeWatch ERIC Metadata Catalogue published online, Google automatically indexes its main pages. " assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue is based on GeoNetwork 3.10, that has been customized according to our different needs and requirements. It allows to manage and publish dataset metadata records and to provide a Digital Object Identifier (DOI) when needed, taking advantage of the GeoNetwork – DataCite connection. The dataset metadata records are automatically harvested by the LifeWatch ERIC national nodes data repositories (e.g., LifeWatch Italy: https://dataportal.lifewatchitaly.eu/data; LifeWatch Belgium: https://www.lifewatch.be/en/data; LifeWatch Portugal and Greece: http://ipt.gbif.pt/ipt/; etc.)." assertion.
- declaration considerations "It represents the search engine of DataCite (https://search.datacite.org), hence it allows to find, access and reuse all LifeWatch ERIC research digital objects that have a DOI. " assertion.
- declaration considerations "Being the LifeWatch ERIC Metadata Catalogue published online, Google automatically indexes its main pages. " assertion.
- declaration considerations "It represents the standard de facto as secure communication protocol." assertion.
- declaration considerations "It represents the standard de facto as secure communication protocol." assertion.
- declaration considerations "Metadata records are freely accessible in the LifeWatch ERIC Metadata Catalogue and in EcoPortal, hence no login is required. The authentication and authorization are needed to add and manage metadata records and resources and currently are performed by using a traditional login mechanism that identifies and authenticates users through the couple of credentials (username and password). We are developing the Keycloak Single-Sign On that will allow to login with different identity providers (e.g., Google, ORCID, etc.). " assertion.
- declaration considerations "Dataset metadata records are freely accessible in the LifeWatch ERIC Metadata Catalogue, hence no login is required. The authentication and authorization are needed to add and manage dataset metadata records and currently are performed by using a traditional login mechanism that identifies and authenticates users through the couple of credentials (username and password). We are developing the Keycloak Single-Sign On that will allow to login with different identity providers (e.g., Google, ORCID, etc.). To access datasets, the authentication & authorisation service depends on the LifeWatch ERIC national node." assertion.
- declaration considerations "A metadata longevity plan is still under definition." assertion.
- declaration considerations "RDF schema is actually in improvement status in the LifeWatch ERIC Metadata Catalogue to describe the metadata of all LifeWatch ERIC resources (e.g., datasets, services, Virtual Research Environments, workflows, research sites)." assertion.
- declaration considerations "The XML allows us to exchange metadata records among distributed sources. This format is used to download metadata records both in the LifeWatch ERIC Metadata Catalogue and EcoPortal." assertion.
- declaration considerations "EcoPortal API returns JSON as the default content type." assertion.
- declaration considerations "The knowledge representation languages used for datasets depend on the LifeWatch ERIC national node. Some examples are XMLS, CSV, DwC-A, NetCDF, etc." assertion.
- declaration considerations "The knowledge representation languages used for datasets depend from the LifeWatch ERIC national node. Some examples are XMLS, CSV, DwC-A, NetCDF, etc." assertion.
- declaration considerations "The knowledge representation languages used for datasets depend from the LifeWatch ERIC national node. Some examples are XMLS, CSV, DwC-A, NetCDF, etc." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.