Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- 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 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 "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 provenance information is recorded in Argo NetCDF implementation documented on http://dx.doi.org/10.13155/29825." 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 "There is one and only Argo GDAC DOI to cite and access Argo data: (Argo (2023). Argo float data and metadata from Global Data Assembly Centre (Argo GDAC). SEANOE. 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://erddap.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#. Its web interface is: https://dataselection.euro-argo.eu " assertion.
- declaration considerations "Metadata are registered in NetCDF files available from https or ftp from Argo GDAC https://doi.org/10.17882/42182" assertion.
- declaration considerations "Data are registered in NetCDF files available from https or ftp from Argo GDAC https://doi.org/10.17882/42182" 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 ontology RDF is available on https://www.ifremer.fr/co/argo-linked-data/doc/argo-floats.ttl. This ontology is used by Argo SPARQL endpoint : https://co.ifremer.fr/co//argo-linked-data/html/Argo-HTML-SPARQL/" 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 "The Argo ontology RDF is available on https://www.ifremer.fr/co/argo-linked-data/doc/argo-floats.ttl. This ontology is used by Argo SPARQL endpoint : https://co.ifremer.fr/co//argo-linked-data/html/Argo-HTML-SPARQL/" 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. Example of Argo parameter codes (Terms describing individual measured phenomena, used to mark up sets of data in Argo NetCDF arrays) : https://vocab.nerc.ac.uk/search_nvs/R03/" assertion.
- declaration considerations "The Argo vocabularies used in NetCDF files are published on NVS vocab server. Example of Argo parameter codes (Terms describing individual measured phenomena, used to mark up sets of data in Argo NetCDF arrays) : https://vocab.nerc.ac.uk/search_nvs/R03/" 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 "The DCAT-AP description of Argo dataset is part of the more general RDF-OWL Argo ontology. http://www.argodatamgt.org/Documentation/Argo-vocabulary-server/Argo-linked-data-and-SPARQL-endpoint" assertion.
- declaration considerations "The Argo ERDDAP server semantic is available from : https://erddap.ifremer.fr/erddap" assertion.
- declaration considerations "I-ADOPT semantic broker is use by ENVRI-FAIR EOV broker which queries Argo vocabularies (among others). https://github.com/envri-fair/marine-eov-broker" assertion.
- declaration considerations "Argo data and metadata follows the NetCDF-CF conventions" assertion.
- declaration considerations "The Argo OGC-sensorthings API is : https://sextant.ifremer.fr/examind/WS/sts/coriolis/v1.1" assertion.
- declaration considerations "We use DataCite and Schema.org for Argo data and metadata DOI" assertion.
- declaration considerations "Here is the Argo ontology which is a semantic model for Argo datasets, the datasets acess is expressed with DCAT-AP. https://www.ifremer.fr/co/argo-linked-data/doc/argo-floats.ttl" assertion.
- declaration considerations "I-Adopt framework used for cross-domain queries." 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://co.ifremer.fr/co/argo-linked-data/html/Argo-HTML-SPARQL/" assertion.
- declaration considerations "The one-click download of Argo data and metadata is available from this DOI: https://doi.org/10.17882/42182." 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 "We shall investigate the use of ePIC as data identifier." assertion.
- declaration considerations "The one-click download of Argo data and metadata is available 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 DOI DataCite schemas" assertion.
- declaration considerations "" assertion.
- declaration considerations "The data selection tool is under validation, should be operational in 2021." assertion.
- declaration considerations "Argo DOI is indexed on Google, Bing, Seanoe, OpenSearch, google dataset search." assertion.
- declaration considerations "Interface under development" 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 "NetCDF contain knowledge representation features." assertion.
- declaration considerations "Argo metadata such as sensor type, history records are recorded in Argo NetCDF self descriptive variables. The vocabularies will be published in the NVS vocab server." assertion.
- declaration considerations "We plan to use the NVS vocab server." assertion.
- declaration considerations "We use DataCite and Schema.org for Argo data and metadata DOI." assertion.
- declaration considerations "is datacite a " 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 "We use NetCDF CF metadata." 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 identifier should be able to handle Digital Specimens (a specific type of Digital Object) and related metadata. " assertion.
- declaration considerations "A Registration Agency for Digital Specimen and Natural Science Collections data is needed given the diverse and cross-cutting needs for specimen data. A global engagement is required to realise the potential power of persistent identifiers. " assertion.
- declaration considerations "The identifier should be able to handle Digital Specimens (a specific type of Digital Object) and related metadata. " assertion.
- declaration considerations "DiSSCo does not specifically distinguish between data and metadata for digital specimen, allowing most data fields to be used also as metadata for discovery. " assertion.
- declaration considerations "Understanding how schema.org works with the Digital Object Architecture." assertion.
- declaration considerations "The FAIR Digital Object model should be able to handle Digital Specimens (a specific type of Digital Object) and related metadata and a wide variety of collections and specimens data. For Digital Specimens, often there is no distinction between data and metadata, the attributes for the digital object should be index and discoverable. " assertion.
- declaration considerations "A FAIR service providing access to Digital Specimens and Collections. Harmonising data from different types of collections and institutions of different sizes can be a challenge. " assertion.
- declaration considerations "Ensuring interoperability between DiSSCo and GBIF infrastructures. " assertion.
- declaration considerations "A FAIR service providing access to Digital Specimens and Collections. Harmonising data from different types of collections and institutions of different sizes can be a challenge. As each individual specimen is described as Digital Object, the dataset concept for DiSSCo is not clearly defined. Collection Object (group of Digital Specimens) can be thought of as datasets. " assertion.
- declaration considerations "Different systems (bata providers are not aware of DOIP and not compatible yet. " assertion.
- declaration considerations "A common guidelines and recommendations for application programming interfaces (APIs) is lac." assertion.
- declaration considerations "DOIP is not natively supported in the systems currently used in the community. At the moment it only provides JSON response." assertion.
- declaration considerations "REST is widely use however, not all systems will have a REST API endpoint. Alternative would be to import the data." assertion.
- declaration considerations "A single sign on (SSO) interface that is compatible with EOSC and AARC guidelines. Not all the institutions are AAI federation ready so alternative federated login options need to be provided (such as orcid, google). " assertion.
- declaration considerations "A single sign on (SSO) interface that is compatible with EOSC and AARC guidelines. Not all the institutions are AAI federation ready so alternative federated login options need to be provided (such as orcid, google). " assertion.
- declaration considerations "A policy to help the community understand what data should be open or not. How to handle ethical and legal issues. " assertion.
- declaration considerations "How to maintain the standards and vocabularies? How to make it usable for different systems? " assertion.
- declaration considerations "How to maintain the standards and vocabularies? How to make it usable for different systems? " assertion.