Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- 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 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 "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 Argo ontology uses PROV-O to record provenance information. This information can be queried from Argo SPARQL endpoint : https://sparql.ifremer.fr/argo/query. Argo SPARQL endpoint : http://purl.org/np/RA1IPRCYWlzzoT4z11Fj8q3_thw4xtC_jYyMirHTKVCHc" assertion.
- declaration considerations "Widely used for data citation, mainly used by us for collections and elaborated data products" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "under way" assertion.
- declaration considerations "under way" assertion.
- declaration considerations "under way" assertion.
- declaration considerations "under way" assertion.
- declaration considerations "under way" assertion.
- declaration considerations "under way" assertion.
- declaration considerations "under way" assertion.
- declaration considerations "under way" assertion.
- declaration considerations "Used in Jupyter hub and many other applications by the community for easy access to SPARQL, ontology, metadatahttps://pypi.org/project/icoscp/" assertion.
- declaration considerations "Through ERDDAP (Ocean domain)" assertion.
- declaration considerations "Through ERDDAP (Ocean domain)" assertion.
- declaration considerations "Through ERDDAP (Ocean domain)" assertion.
- declaration considerations "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" assertion.
- declaration considerations "Through ERDDAP (Ocean domain)" assertion.
- declaration considerations "Through ERDDAP (Ocean domain)" assertion.
- declaration considerations "Ocean domain only" assertion.
- declaration considerations "Through ERDDAP (Ocean domain)" assertion.
- declaration considerations "Through ERDDAP (Ocean domain)" assertion.
- declaration considerations "For ORCID and Facebook identity providers " assertion.
- declaration considerations "For ORCID and Facebook identity providers " assertion.
- declaration considerations "For ORCID and Facebook identity providers " assertion.
- declaration considerations "For ORCID and Facebook identity providers " assertion.
- declaration considerations "For ORCID and Facebook identity providers " assertion.
- declaration considerations "All ICOS data is available open and free." assertion.
- declaration considerations "All ICOS data is available open and free." assertion.
- declaration considerations "All ICOS data is available open and free." assertion.
- declaration considerations "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." assertion.
- declaration considerations "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." assertion.
- declaration considerations "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." assertion.
- declaration considerations "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." assertion.
- declaration considerations "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." assertion.
- declaration considerations "CF-1.7 compliant netcdf metadata included in the netcdf data objects" assertion.
- declaration considerations "http://meta.icos-cp.eu/ontologies/cpmeta/" assertion.
- declaration considerations "For the atmosphere domain" assertion.
- declaration considerations "For the atmosphere domain" assertion.
- declaration considerations "For the atmosphere domain" assertion.
- declaration considerations "For the atmosphere domain" assertion.
- declaration considerations "For the atmosphere domain" assertion.
- declaration considerations "For the atmosphere domain" 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 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 "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 "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 "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 "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 "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 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 "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 "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 "NetCDF CF supported by SDN vocabs" assertion.