Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- declaration considerations "A metadata longevity plan is still under definition." assertion.
- declaration considerations "RDF schema is actually in improvement status in the LifeWatch ERIC Metadata Catalogue to describe the metadata of all LifeWatch ERIC resources (e.g., datasets, services, Virtual Research Environments, workflows, research sites)." assertion.
- declaration considerations "The XML allows us to exchange metadata records among distributed sources. This format is used to download metadata records both in the LifeWatch ERIC Metadata Catalogue and EcoPortal." assertion.
- declaration considerations "EcoPortal API returns JSON as the default content type." assertion.
- declaration considerations "The knowledge representation languages used for datasets depend on the LifeWatch ERIC national node. Some examples are XMLS, CSV, DwC-A, NetCDF, etc." assertion.
- declaration considerations "The knowledge representation languages used for datasets depend from the LifeWatch ERIC national node. Some examples are XMLS, CSV, DwC-A, NetCDF, etc." assertion.
- declaration considerations "The knowledge representation languages used for datasets depend from the LifeWatch ERIC national node. Some examples are XMLS, CSV, DwC-A, NetCDF, etc." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node. " assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node. " assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node." assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node." assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node. " assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node. " assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node. " assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node. " assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node. " assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node. " assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node. " assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node. " assertion.
- declaration considerations "We use the ISO 19139:2007 profile for several kinds of resources (e.g., services, workflows, virtual research environments, etc.)" assertion.
- declaration considerations "We use the EML 2.2.0 standard for datasets metadata records." assertion.
- declaration considerations "The LifeWatch ERIC UPper Ontology (LUPO) defines the core set of LifeWatch ERIC elements." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.
- declaration considerations "The models, schemas used for datasets depend on the LifeWatch ERIC national node. Some examples are DwC-A, NetCDF, etc." assertion.
- declaration considerations "The models, schemas used for datasets depend on the LifeWatch ERIC national node. Some examples are DwC-A, NetCDF, etc." assertion.
- declaration considerations "Metadata records can be accessed and downloaded with a CC0 license both on LifeWatch ERIC Metadata Catalogue and on EcoPortal." assertion.
- declaration considerations "A mixture between mostly CC-BY, CC-0 and CC-BY-NC is used, it depends on the LifeWatch ERIC national node." assertion.
- declaration considerations "A mixture between mostly CC-BY, CC-0 and CC-BY-NC is used, it depends on the LifeWatch ERIC national node." assertion.
- declaration considerations "A mixture between mostly CC-BY, CC-0 and CC-BY-NC is used, it depends on the LifeWatch ERIC national node." assertion.
- declaration considerations "We don't use a metadata schema for describing the provenance of our metadata records at the moment." assertion.
- declaration considerations "We don't use a metadata schema for describing the provenance of our datasets at the moment." assertion.
- declaration considerations "Benchmark submissions are given a number unique across MLCommons benchmarks. However, they are not resolvable by machines. The convention used is the benchmark round hyphenated with a unique submission number, e.g., 3.1-2000 for benchmark 3.1, first submission. Different benchmarks begin with different number spans, such as training begins at 2000 and HPC begins at 8000." assertion.
- declaration considerations "Similar to metadata, benchmark submissions are given a number unique across MLCommons benchmarks. However, they are not resolvable by machines. The convention used is the benchmark round hyphenated with a unique submission number, e.g., 3.1-2000 for benchmark 3.1, first submission. Different benchmarks begin with different number spans, such as training begins at 2000 and HPC begins at 8000. It would be optimal if each benchmark and round had a PID." assertion.
- declaration considerations "While there is no comprehensive metadata schema, a portion has been defined to describe systems used in benchmark submissions. That is documented at https://github.com/mlcommons/policies/blob/master/submission_rules.adoc#system_desc_id-json-metadata . Further, for a subset of benchmarks, rather than metadata (which would be better), meaning is embedded in directory structures. See https://github.com/mlcommons/policies/blob/master/submission_rules.adoc#directory-structure" assertion.
- declaration considerations "While there is no comprehensive metadata schema, a portion has been defined to describe systems used in benchmark submissions. That is documented at https://github.com/mlcommons/policies/blob/master/submission_rules.adoc#system_desc_id-json-metadata . Further, for a subset of benchmarks, rather than metadata (which would be better), meaning is embedded in directory structures. See https://github.com/mlcommons/policies/blob/master/submission_rules.adoc#directory-structure" assertion.
- declaration considerations "To some extent, the metadata can be searched programmatically on GitHub. However, in practice the data (JSON system description files) must be downloaded and a custom script used for querying." assertion.
- declaration considerations "GitHub is the platform used for publishing the data, which is comprised of text and JSON files." assertion.
- declaration considerations "Partial metadata available (as described under Findability) via https via GitHub." assertion.
- declaration considerations "https via GitHub" assertion.
- declaration considerations "not applicable - all data openly available" assertion.
- declaration considerations "not applicable - all data openly available" assertion.
- declaration considerations "not applicable - all data openly available" assertion.
- declaration considerations "JSON used to describe the system profiles for submitted benchmarks" assertion.
- declaration considerations "Uses mllog" assertion.
- declaration considerations "This is an area of great need." assertion.
- declaration considerations "This is an area of great need." assertion.
- declaration considerations "This is an area of great need." assertion.
- declaration considerations "This is an area of great need." assertion.
- declaration considerations "This is an area of great need." assertion.
- declaration considerations "This is an area of great need." assertion.
- declaration considerations "Using internally defined MLCommons schema for system logs. mllog provides standardized log output." assertion.
- declaration considerations "Uses mllog" 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 "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "DataCite DOIs are issued by EUDAT B2SHARE which is currently used to share and publish site level datasets (processing level 0 and 1). In future DataCite DOIs also will be issued by the eLTER Central Data Node (CDN) which is currently in development (plan for 2024). Implementation of DOIs for site records in addition to the deims.id is currently evaluated." assertion.
- declaration considerations "DataCite DOIs are issued by EUDAT B2SHARE which is currently used to share and publish site level datasets (processing level 0 and 1). In future DataCite DOIs also will be issued by the eLTER Central Data Node (CDN) which is currently in development (plan for 2024). Implementation of DOIs for site records in addition to the deims.id is currently evaluated." assertion.
- declaration considerations "UUID are appended to the URI of the eLTER Catalogue (Digital Asset Register, DAR). UUID is also used in DEIMS-SDR to identify the MD records for sites, locations, sensors and networks" 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. Services related to access to these data are documented as service records in the DAR." 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. Services related to access to these data are documented as service records in the DAR." assertion.
- declaration considerations "persistent identification based on UUID plus URI (namespace for deims) for research sites and observation facilities implemented in DEIMS-SDR and used to unambigously identify and register sites belonging to different research infrastructures and networks" assertion.
- declaration considerations "for eLTER a community profile based on the INSPIRE required fields and requirements for EML 2.0 was definded using a local schema which is mapped to ISO19115/19139 to expose metadata. For the Digital Asset Register (DAR) also sharing of ISO19115/19139 metadate is implemented - schema on read philosophy" assertion.
- declaration considerations "for eLTER a community profile based on the INSPIRE required fields and requirements for EML 2.0 was definded using a local schema which is mapped to ISO19115/19139 to expose metadata. For the Digital Asset Register (DAR) metadata are held in schema-neutral json document, which allows sharing of ISO19115/19139 metadate as a schema-on-read service through a RESTful API. " assertion.
- declaration considerations "this is implemented for site datasets (processing level 0 and 1) using EUDAT B2SHARE as common repository. For the eLTER Central Data Node (CDN) this is under development and will be implemented 2025 onwards." assertion.
- declaration considerations "DEIMS-SDR is operational to document physical assets of the eLTER network (sites, platforms, locations, sensors, and networks) as well as digital assets (datasets and activities). In future implementation steps (2025 onwards) digital assets will be documented and shared using the eLTER digital asset register (DAR)" 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 "currently under development. the eLTER Digital Asset Register will be operational by end 2023 focusing n the documentation of digital assets (datasets, models, provenance) of the eLTER RI" assertion.
- declaration considerations "currently within eLTER we use a combination of web services from DEIMS-SDR, DAR, B2SHARE and DataCite to disseminate metadata covering the different assets of the RI" assertion.
- declaration considerations "DEIMS-SDR contains metadata to existing data repositories and linking dataset metadata to the respective eLTER facilility" assertion.
- declaration considerations "the eLTER Central Data Node (CDN) currently contains storage of time series data (OGC SOS), geospatial data (OGC WMS/WFS) as well as files. The eLTER CDN is currently still under development and will be operational by mid 2024." assertion.
- declaration considerations "the eLTER DIP (EcoSense) is a web interface to view and access information on datasets shared" assertion.