Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- declaration considerations "information on metadata creation and update is provided as part of the MD model" assertion.
- declaration considerations "information on metadata creation and update is provided as part of the MD model" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "currently used for datasets shared via B2SHARE. issuing DOI from the eLTER Digital Asset Registry (DAR) will be implemented in 2025 onwards" assertion.
- declaration considerations "currently used for datasets shared via B2SHARE. issuing DOI from the eLTER Digital Asset Registry (DAR) will be implemented in 2025 onwards" assertion.
- declaration considerations "persistent identification for research sites and observation facilities implemented in DEIMS-SDR" assertion.
- declaration considerations "persistent identification for research sites and observation facilities implemented in DEIMS-SDR" assertion.
- declaration considerations "persistent identification for research sites and observation facilities implemented in DEIMS-SDR" assertion.
- declaration considerations "persistent identification for research sites and observation facilities implemented in DEIMS-SDR" assertion.
- declaration considerations "currently under development. draft prototype ready " assertion.
- declaration considerations "EUDAT B2FIND harvests eLTER metadata from DEIMS-SDR and the related B2SHARE repository. The effort was renewed within the implementation of the EOSC-Hub project. B2FIND is used as additional domain agnostic discovery portal." assertion.
- declaration considerations "eLTER DIP is the central access point to eLTER metadata from a range of sources using geonetwork as backbone technology. " assertion.
- declaration considerations "currently under development. draft prototype ready " assertion.
- declaration considerations "under development, protoype ready" assertion.
- declaration considerations "under development, protoype ready" assertion.
- declaration considerations "under development, protoype ready" assertion.
- declaration considerations "under development, protoype ready" assertion.
- declaration considerations "see also DEIMS REST-API" assertion.
- declaration considerations "see also DEIMS REST-API" assertion.
- declaration considerations "see also DEIMS REST-API" assertion.
- declaration considerations "see also DEIMS REST-API" assertion.
- declaration considerations "DEIMS-SDR REST-API shares information on sites, locations, sensors, datasets and networks as json" assertion.
- declaration considerations "see also DEIMS REST-API" assertion.
- declaration considerations "currently under testing" assertion.
- declaration considerations "direct download using https/http request for datasets shared via B2SHARE" assertion.
- declaration considerations "currently under testing" assertion.
- declaration considerations "currently under testing" assertion.
- declaration considerations "General eLTER data policy fosters open data. Restrictions might apply for site based data under embargo." assertion.
- declaration considerations "updates are worked out in eLTER-PPP WP3 Data Management Plan and Data Policy. Will be available by 2025" assertion.
- declaration considerations "updates are worked out in eLTER-PPP WP3 Data Management Plan and Data Policy. Will be available by 2025" assertion.
- declaration considerations "updates are worked out in eLTER-PPP WP3 Data Management Plan and Data Policy. Will be available by 2025" assertion.
- declaration considerations "updates are worked out in eLTER-PPP WP3 Data Management Plan and Data Policy. Will be available by 2025" assertion.
- declaration considerations "updates are worked out in eLTER-PPP WP3 Data Management Plan and Data Policy. Will be available by 2025" assertion.
- declaration considerations "updates are worked out in eLTER-PPP WP3 Data Management Plan and Data Policy. Will be available by 2025" assertion.
- declaration considerations "updates are worked out in eLTER-PPP WP3 Data Management Plan and Data Policy. Will be available by 2025" assertion.
- declaration considerations "updates are worked out in eLTER-PPP WP3 Data Management Plan and Data Policy. Will be available by 2025" assertion.
- declaration considerations "updates are worked out in eLTER-PPP WP3 Data Management Plan and Data Policy. Will be available by 2025" assertion.
- declaration considerations "will be replaced by the eLTER RI Data Specification latest by 2025" assertion.
- declaration considerations "will be replaced by the eLTER RI Data Specification latest by 2025" assertion.
- declaration considerations "will be replaced by the eLTER RI Data Specification latest by 2025" assertion.
- declaration considerations "will be replaced by the eLTER RI Data Specification latest by 2025" assertion.
- declaration considerations "local data provision could derive from that" assertion.
- declaration considerations "information on metadata creation and update is provided as part of the MD model" assertion.
- declaration considerations "information on metadata creation and update is provided as part of the MD model" assertion.
- declaration considerations "information on metadata creation and update is provided as part of the MD model" 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.