Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- declaration considerations "For the atmosphere domain" assertion.
- declaration considerations "For the atmosphere domain" assertion.
- declaration considerations "The DOIs are the best way to permanently identify a given digital object, in a format controlled by the International DOI Foundation. We have an agreement with DataCite and this will guarantee the cross-domain findability. When a DOI is not available, users can specify a persistent internal identifier." assertion.
- declaration considerations "The DOIs are the best way to permanently identify a given digital object, in a format controlled by the International DOI Foundation. We have an agreement with DataCite and this will guarantee the cross-domain findability. When a DOI is not available, users can specify a persistent internal identifier." assertion.
- declaration considerations "We use the ISO 19139:2007 profile for several kinds of metadata 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 "We have an agreement with DataCite." assertion.
- declaration considerations "Being the LifeWatch ERIC Metadata Catalogue published online, Google automatically indexes its main pages. " assertion.
- declaration considerations "It represents the search engine of DataCite (https://search.datacite.org), hence it allows to find, access and reuse all Life" assertion.
- declaration considerations "Being the LifeWatch ERIC Metadata Catalogue published online, Google automatically indexes its main pages. " assertion.
- declaration considerations "It represents the search engine of DataCite (https://search.datacite.org), hence it allows to find, access and reuse all LifeWatch ERIC research digital objects that have a DOI. " assertion.
- declaration considerations "It represents the standard de facto as secure communication protocol." assertion.
- declaration considerations "It represents the standard de facto as secure communication protocol." assertion.
- declaration considerations "Metadata records are freely accessible in the LifeWatch ERIC Metadata Catalogue, based on GeoNetwork, hence no login is required. The authentication and authorization are needed to add and manage metadata records and currently are performed by using a traditional login mechanism that identifies and authenticates users through the couple of credentials (username and password). It will adopt the SAML 2.0 protocol, with a multifactor authentication and is going to analyse the OAUTH infrastructure (analysis of providers, costs, issues, etc.)." assertion.
- declaration considerations "The authentication & authorisation technique for datasets depends from the LifeWatch ERIC national node. For example, in some cases the access through ORCID is currently used, in other cases the traditional login mechanism that identifies and authenticates users through the couple of credentials (username and password) is used." 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." 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 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 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 "In the future we will use the PARTHENOS Entities (PE) to extend the ontological model and the RDF schema of different assets." 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 from the LifeWatch ERIC national node. Some examples are DwC-A, NetCDF, etc." assertion.
- declaration considerations "The models, schemas used for datasets depend from the LifeWatch ERIC national node. Some examples are DwC-A, NetCDF, etc." 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 "This license is used particularly for services and VREs." 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 "" 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 "In the future we will use Prov" assertion.
- declaration considerations "In the future we will use Prov" 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.