Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- declaration considerations "Widely accepted. " assertion.
- declaration considerations "Will follow ENVRI recommendations" assertion.
- declaration considerations "Will follow ENVRI recommendations" assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "Metadata available in the ACTRIS data portal through HTTPS." assertion.
- declaration considerations "Data download via primary repositories through HTTPS." assertion.
- declaration considerations "ACTRIS internal vocabulary is used for variable names in the ACTRIS data portal." assertion.
- declaration considerations "Commonly used within the community" assertion.
- declaration considerations "For some of the ACTRIS datasets, DOIs are still not available" assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "Datacite is used by the parts of ACTRIS that have implemented DOIs for their datasets." assertion.
- declaration considerations "The metadata of the ACTRIS metadata catalog is indexed in WMO Information System (WIS) and available through their search engine." assertion.
- declaration considerations "The metadata of the ACTRIS metadata catalog is indexed in WMO Information System (WIS) and available through their search engine." assertion.
- declaration considerations "Metadata available in the ACTRIS data portal through HTTPS." assertion.
- declaration considerations "Direct download via primary repositories through HTTPS." assertion.
- declaration considerations "Streaming of data using OPeNDAP." assertion.
- declaration considerations "Requirement by European Commision." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "ACTRIS internal vocabulary is used for variable names in the ACTRIS data portal." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "Custom built identifier system set up before other PID systems were easily available." assertion.
- declaration considerations "PID assigned via B2Handle to each datafile when stored in cloud. Please mint a B2 Handle nanopub" assertion.
- declaration considerations "Extended metadataschema based on ISO19139 to accommodate for oceanography specifics" assertion.
- declaration considerations "No generic system was available, and because of the ammount of metadata records DOI's are not feasible. Therefore dedicated PID-CDI identifier solution." assertion.
- declaration considerations "Aggregated records exposed to GEOSS Geoportal" assertion.
- declaration considerations "Dedicated user interface offering facets to search the large collection of data sets (>2.7M). " assertion.
- declaration considerations "Aggregations exposed via OAI-PMH" assertion.
- declaration considerations "Overarching services demand harvesting of metadata via OGC services" assertion.
- declaration considerations "Aggregated records published via OpenSearch" assertion.
- declaration considerations "Aggregated CDI records will be distributed via spra" assertion.
- declaration considerations "Marine-ID is generally accepted method and solution for AAA in the marine domain" assertion.
- declaration considerations "Access via Marine-ID authentication in the CDI service " assertion.
- declaration considerations "Metadata records available in XML" assertion.
- declaration considerations "metadata records for aggregated CDI metadata in RDF via SparQL endpoint, original granularity will follow. as well as DCAT-AP compliance that will be introduced." assertion.
- declaration considerations "Datafiles in ODV format are in ASCII" assertion.
- declaration considerations "Datafiles in NetCDF format are binary" assertion.
- declaration considerations "The NVS have been developed by BODC based on the SDN requirements and specifically fulfill the needs of the marine data community. However for provenance the used vocabs will be expanded with L22 (sensor type) as well as links to the Sensor Instance! (cant make this)" assertion.
- declaration considerations "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!)." assertion.
- declaration considerations "NVS service used as main vocabulary for parameters, instruments, etc. " assertion.
- declaration considerations "metadata directories used as vocabularies to describe organisations, cruises, projects with relation to the data" assertion.
- declaration considerations "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." assertion.
- declaration considerations "ODV data transport format " assertion.
- declaration considerations "NetCDF CF supported by SDN vocabs" assertion.
- declaration considerations "Now using https://www.seadatanet.org/Data-Access/License/1.0 but will be made as GUPRI under ENVRIFAIR, plus mapping to CCBY" assertion.
- declaration considerations "Now using https://www.seadatanet.org/Data-Access/License/1.0 but will be made as GUPRI under ENVRIFAIR, plus mapping to CCBY" assertion.
- declaration considerations "ISO adopted PROV-O will be investigated, but probably better fit for data products (sextant). In CDI more info about sensors will be included." assertion.
- declaration considerations "There is already provenance info in the metadata, and more info about sensors will be included." assertion.
- declaration considerations "Custom built identifier system set up before other PID systems were easily available." assertion.
- declaration considerations "PID assigned via B2Handle to each datafile when stored in cloud. Please mint a B2 Handle nanopub" assertion.
- declaration considerations "Extended metadataschema based on ISO19139 to accommodate for oceanography specifics" assertion.
- declaration considerations "No generic system was available, and because of the ammount of metadata records DOI's are not feasible. Therefore dedicated PID-CDI identifier solution." assertion.
- declaration considerations "Aggregated records exposed to GEOSS Geoportal" assertion.
- declaration considerations "Dedicated user interface offering facets to search the large collection of data sets (>2.7M). " assertion.
- declaration considerations "sparql endpoint for aggregated and original granularity developed, updated to DCAT AP and published, in ao ENVRIHUB." assertion.
- declaration considerations "Matadata records published in B2FIND. " assertion.
- declaration considerations "Linked data for CDI published to Google data set search" assertion.
- declaration considerations "Aggregations exposed via OAI-PMH" assertion.
- declaration considerations "Overarching services demand harvesting of metadata via OGC services" assertion.
- declaration considerations "Aggregated records published via OpenSearch" assertion.
- declaration considerations "A sparql endpoint is now available for aggregated records AND for original granularity with over 60M triples. in RDF... cdi.seadatanet.org/" assertion.
- declaration considerations "Marine-ID is generally accepted method and solution for AAA in the marine domain" assertion.
- declaration considerations "Access via Marine-ID (CAS) authentication in the CDI service " assertion.
- declaration considerations "Metadata records available in XML" assertion.
- declaration considerations "metadata records in RDf via SparQL endpoint, updated for CDAT-AP compliance!" assertion.
- declaration considerations "Datafiles in ODV format are in ASCII" assertion.
- declaration considerations "Datafiles in NetCDF format are binary" assertion.
- declaration considerations "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." assertion.
- declaration considerations "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!)." assertion.
- declaration considerations "NVS service used as main vocabulary for parameters, instruments, etc. vocab L22 - Sensor type - added in metadata." assertion.
- declaration considerations "metadata directories used as vocabularies to describe organisations, cruises, projects with relation to the data" assertion.
- declaration considerations "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." assertion.
- declaration considerations "ODV data transport format " assertion.
- declaration considerations "NetCDF CF supported by SDN vocabs" assertion.
- declaration considerations "CDI was using https://www.seadatanet.org/Data-Access/License/1.0 but now mapped to CCBY and implemented" assertion.
- declaration considerations "CDI was using https://www.seadatanet.org/Data-Access/License/1.0 but now mapped to CCBY and implemented." assertion.
- declaration considerations "There was already provenance info in the metadata, now added more info about sensors via L22 and link to sensor instance (SWE)." assertion.
- declaration considerations "There was already provenance info in the metadata, now added more info about sensors via L22 and link to sensor instance (SWE)." 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 "Argo data is hosted in Ifremer Sismer service. Sismer is a RDA Core-Trust Seal certified data centre. Our long-term data and metadata longevity plan is a commitment of our RDA-CTS certification. " 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.