Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- declaration considerations "ORCID is a much used ID provider for researchers, using this enabling automated data sets addition to personal ORCID library of publications and data sets" assertion.
- declaration considerations "All ICOS data is available open and free." assertion.
- declaration considerations "Simple login using email address and password, confirmation of account through email, forgotten password routine with confirmation by email" assertion.
- declaration considerations "Allows to federate account with many universities and RPOs" 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 metadata ontology is modelled in OWL and represented in a triple store using RDF. Using our sparql endpoint metadata can be queried and results can be presented as RDF, turtle, CSV and XML. The ICOS metadata scheme is published at LOV: https://lov.linkeddata.es/dataset/lov/vocabs/cpmeta" assertion.
- declaration considerations "ICOS metadata ontology is modelled in OWL and represented in a triple store using RDF. Using our sparql endpoint metadata can be queried and results can be presented as RDF, json, turtle, CSV and XML" assertion.
- declaration considerations "ICOS metadata ontology is modelled in OWL and represented in a triple store using RDF. Using our sparql endpoint metadata can be queried and results can be presented as RDF, json, turtle, CSV and XML" assertion.
- declaration considerations "ICOS metadata ontology is modelled in OWL and represented in a triple store using RDF. Using our sparql endpoint metadata can be queried and results can be presented as RDF, json, turtle, CSV and XML" assertion.
- declaration considerations "ICOS metadata ontology is modelled in OWL and represented in a triple store using RDF. Using our sparql endpoint metadata can be queried and results can be presented as RDF, json, turtle, CSV and XML" 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/. The ICOS metadata scheme is also published at LOV: https://lov.linkeddata.es/dataset/lov/vocabs/cpmeta" assertion.
- declaration considerations "http://meta.icos-cp.eu/ontologies/cpmeta/" assertion.
- declaration considerations "http://meta.icos-cp.eu/ontologies/cpmeta/" 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 "Implemented as content negotiated XML returned for each data object landing page" assertion.
- declaration considerations "As implicitly described by the ICOS statutes and formally decided by the ICOS GA in 2021" assertion.
- declaration considerations "All ICOS data is licensed using the CCBY4 licence, as prescribed by the ICOS Statutes and decided by ICOS GA and described in the ICOS data policy (https://doi.org/10.18160/JDEE-PZNY)" assertion.
- declaration considerations "Required for some data publications" assertion.
- declaration considerations "Required for traceability and attribution to data providers" assertion.
- declaration considerations "Required for traceability and attribution to data providers" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "At the moment there is only one direction link - metadata link to data " assertion.
- declaration considerations "Not yet implemented - will be a institutional platform " assertion.
- declaration considerations "Not yet implemented - will be a institutional platform " assertion.
- declaration considerations "Not yet implemented - will be a institutional platform " assertion.
- declaration considerations "Not yet implemented - will be a institutional platform " assertion.
- declaration considerations "Not yet implemented - will be a institutional platform " assertion.
- declaration considerations "Not yet implemented - will be a institutional platform " assertion.
- declaration considerations "To be developed" assertion.
- declaration considerations "To be developed" assertion.
- declaration considerations "To be developed" assertion.
- declaration considerations "To be developed" assertion.
- declaration considerations "To be developed" assertion.
- declaration considerations "To be developed" assertion.
- declaration considerations "To be developed" assertion.
- declaration considerations "To be developed" assertion.
- declaration considerations "To be developed" assertion.
- declaration considerations "To be developed" assertion.
- declaration considerations "To be developed" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "SPSS, Stata, SAS, R, CSV are being used. But they are not considered KR languages. Thus removed in this version. " assertion.
- declaration considerations "SPSS, Stata, SAS, R, CSV are being used. But they are not considered KR languages. Thus removed in this version. " assertion.
- declaration considerations "SPSS, Stata, SAS, R, CSV are being used. But they are not considered KR languages. Thus removed in this version. " assertion.
- declaration considerations "SPSS, Stata, SAS, R, CSV are being used. But they are not considered KR languages. Thus removed in this version. " assertion.
- declaration considerations "SPSS, Stata, SAS, R, CSV are being used. But they are not considered KR languages. Thus removed in this version. " assertion.
- declaration considerations "SPSS, Stata, SAS, R, CSV are being used. But they are not considered KR languages. Thus removed in this version. " assertion.
- declaration considerations "SPSS, Stata, SAS, R, CSV are being used. But they are not considered KR languages. Thus removed in this version. " assertion.
- declaration considerations "SPSS, Stata, SAS, R, CSV are being used. But they are not considered KR languages. Thus removed in this version. " assertion.
- declaration considerations "SPSS, Stata, SAS, R, CSV are being used. But they are not considered KR languages. Thus removed in this version. " assertion.
- declaration considerations "SPSS, Stata, SAS, R, CSV are being used. But they are not considered KR languages. Thus removed in this version. " assertion.
- declaration considerations "SPSS, Stata, SAS, R, CSV are being used. But they are not considered KR languages. Thus removed in this version. " assertion.
- declaration considerations "SPSS, Stata, SAS, R, CSV are being used. But they are not considered KR languages. Thus removed in this version. " assertion.
- declaration considerations "" assertion.
- declaration considerations "Our federated metadata handling system relays the metadata PIDs (given to JSON-LD records) from our partners. The PID services used are diverse, including PURLs run by trusted and sustained organisations (e.g. OBO Foundry), DOIs, W3IDs, and IDs issued by trusted aggregators (e.g. OBIS). Not all metadata records integrated into our knowledge graph are assigned PIDs, a scenario we are gradually changing now that metadata records exist for use in Ocean InfoHub and ODIS." assertion.
- declaration considerations "Our federated metadata handling system relays the metadata PIDs (given to JSON-LD records) from our partners. The PID services used are diverse, including PURLs run by trusted and sustained organisations (e.g. OBO Foundry), DOIs, W3IDs, and IDs issued by trusted aggregators (e.g. OBIS). Not all metadata records integrated into our knowledge graph are assigned PIDs, a scenario we are gradually changing now that metadata records exist for use in Ocean InfoHub and ODIS." assertion.
- declaration considerations "Our federated metadata handling system relays the metadata PIDs (given to JSON-LD records) from our partners. The PID services used are diverse, including PURLs run by trusted and sustained organisations (e.g. OBO Foundry), DOIs, W3IDs, and IDs issued by trusted aggregators (e.g. OBIS). Not all metadata records integrated into our knowledge graph are assigned PIDs, a scenario we are gradually changing now that metadata records exist for use in Ocean InfoHub and ODIS." assertion.
- declaration considerations "Our federated metadata handling system relays the metadata PIDs (given to JSON-LD records) from our partners. The PID services used are diverse, including PURLs run by trusted and sustained organisations (e.g. OBO Foundry), DOIs, W3IDs, and IDs issued by trusted aggregators (e.g. OBIS). Not all metadata records integrated into our knowledge graph are assigned PIDs, a scenario we are gradually changing now that metadata records exist for use in Ocean InfoHub and ODIS." assertion.
- declaration considerations "Our federated metadata handling system relays the data-focused PIDs (given to the datasets described by our ODIS-Arch compliant JSON-LD records) from our partners. The PID services used are diverse, including PURLs run by trusted and sustained organisations (e.g. OBO Foundry), DOIs, W3IDs, and IDs issued by trusted aggregators (e.g. OBIS). We encourage the use of both human- and machine-friendly PIDs, or those with content negotiation enabled." assertion.
- declaration considerations "Members of our federation publish their own records as JSON-LD following the ODIS Arch specifications. These are harvested by Ocean InfoHub (for searchability and integration), but are also visible to all schema.org crawlers, including those from Google. Ocean InfoHub provides both a web front-end and a SPARQL endpoint for querying our knowledge graph." assertion.
- declaration considerations "Members of our federation publish their own records as JSON-LD following the ODIS Arch specifications. These are harvested by Ocean InfoHub (for searchability and integration), but are also visible to all schema.org crawlers, including those from Google. Ocean InfoHub provides both a web front-end and a SPARQL endpoint for querying our knowledge graph." assertion.
- declaration considerations "The partners we federate use or maintain a wide range of services to publish the datasets they administer. Our knowledge graph technology does not republish the datasets, but links to the human-friendly distribution points (e.g. landing pages) and - where the partners provide it - the direct download distribution and its associated MIMEtype." assertion.
- declaration considerations "All exchanges use foundational web architecture and TCP/IP protocols, HTTP, HTTPS. Further details are provided here: https://book.oceaninfohub.org/content.html" assertion.
- declaration considerations "All exchanges use foundational web architecture and TCP/IP protocols, HTTP, HTTPS. Further details are provided here: https://book.oceaninfohub.org/content.html" assertion.
- declaration considerations "TCP/IP family protocols, HTTP, HTTPS. Further details are provided here: https://book.oceaninfohub.org/content.html" assertion.
- declaration considerations "TCP/IP family protocols, HTTP, HTTPS. Further details are provided here: https://book.oceaninfohub.org/content.html" assertion.
- declaration considerations "Not Applicable - (meta)data shared do not require authorisation / authentication" assertion.
- declaration considerations "Not Applicable as OIH does not store any data, but rather links to the locations of the data as hosted by providers." assertion.
- declaration considerations "We have the ability to preserve and version metadata shared by all partners in ODIS via our OIH indexer. We have not yet co-designed a policy with our stakeholders on the governance of this solution. There may be sensitivities on what should be archived and preserved for security, traditional/indigenous knowledge, conservation/protection, and other concerns." assertion.
- declaration considerations "Our federated stakeholders will all use schema.org and JSON Schema as lightweight KR languages. We provide guidance on how to embed more expressive KR languages in schema.org JSON-LD records, including the SKOS-level NERC vocabularies and OBO Foundry OWL ontologies. See more detaIls here: https://book.oceaninfohub.org/foundation/foundation.html" assertion.
- declaration considerations "Our federated stakeholders will all use schema.org and JSON Schema as lightweight KR languages. We provide guidance on how to embed more expressive KR languages in schema.org JSON-LD records, including the SKOS-level NERC vocabularies and OBO Foundry OWL ontologies. See more detaIls here: https://book.oceaninfohub.org/foundation/foundation.html" assertion.
- declaration considerations "Our federated stakeholders will all use schema.org and JSON Schema as lightweight KR languages. We provide guidance on how to embed more expressive KR languages in schema.org JSON-LD records, including the SKOS-level NERC vocabularies and OBO Foundry OWL ontologies. See more detaIls here: https://book.oceaninfohub.org/foundation/foundation.html" assertion.
- declaration considerations "Not applicable as OIH does not handle data only metadata. NA - our solution is driven by metadata sharing. While access to datasets is provided (via links to the providers), we do not constrain what KR solutions stakeholders use on their data. Common semantics include the NERC vocabularies/SKOS resources and the Climate and Forecasting Variables, as well as environmentally-focused KR solutions from ESIP and OBO (GCMD, SWEET, ENVO)." assertion.
- declaration considerations "Our federated stakeholders will all use schema.org and JSON Schema as lightweight KR languages. We provide guidance on how to embed more expressive KR languages in schema.org JSON-LD records, including the SKOS-level NERC vocabularies and OBO Foundry OWL ontologies. " assertion.
- declaration considerations "Our solution is driven by metadata sharing. While access to datasets is provided (see responses F subprinciples), we do not constrain what KR solutions stakeholders use on their data. Common semantics include the NERC vocabularies/SKOS resources and the Climate and Forecasting Variables, as well as environmentally-focused KR solutions from ESIP and OBO (GCMD, SWEET, ENVO)." assertion.
- declaration considerations "Our solution is driven by metadata sharing. While access to datasets is provided (see responses F subprinciples), we do not constrain what KR solutions stakeholders use on their data. Common semantics include the NERC vocabularies/SKOS resources and the Climate and Forecasting Variables, as well as environmentally-focused KR solutions from ESIP and OBO (GCMD, SWEET, ENVO)." assertion.
- declaration considerations "Our solution is driven by metadata sharing. While access to datasets is provided (see responses F subprinciples), we do not constrain what KR solutions stakeholders use on their data. Common semantics include the NERC vocabularies/SKOS resources and the Climate and Forecasting Variables, as well as environmentally-focused KR solutions from ESIP and OBO (GCMD, SWEET, ENVO)." assertion.
- declaration considerations "Our solution is driven by metadata sharing. While access to datasets is provided (see responses F subprinciples), we do not constrain what KR solutions stakeholders use on their data. Common semantics include the NERC vocabularies/SKOS resources and the Climate and Forecasting Variables, as well as environmentally-focused KR solutions from ESIP and OBO (GCMD, SWEET, ENVO)." assertion.
- declaration considerations "The terminology resources recommended do, themselves, follow the FAIR Principles to a high degree, with some exceptions. " assertion.
- declaration considerations "Our solution is driven by metadata sharing. While access to datasets is provided (see responses F subprinciples), we do not constrain what KR solutions stakeholders use on their data. Common semantics include the NERC vocabularies/SKOS resources and the Climate and Forecasting Variables, as well as environmentally-focused KR solutions from ESIP and OBO (GCMD, SWEET, ENVO)." assertion.
- declaration considerations "Our solution is driven by metadata sharing. While access to datasets is provided (see responses F subprinciples), we do not constrain what KR solutions stakeholders use on their data. Common semantics include the NERC vocabularies/SKOS resources and the Climate and Forecasting Variables, as well as environmentally-focused KR solutions from ESIP and OBO (GCMD, SWEET, ENVO)." assertion.
- declaration considerations "We use schema.org serialised in JSON-LD, based on guidance from the Earth Science Information Partners' Science on Schema Cluster. We have expanded this with regularised patterns in the ODIS Architecture (ODIS-Arch) to increase consistency and actionability." assertion.
- declaration considerations "OIH does not constrain the semantic qualifications or data linking practices of our partners." assertion.
- declaration considerations "All metadata records are released openly on the web. The partners which share these may annotate them with license information, if they so wish" assertion.