Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- declaration considerations "We might need to use different licenses for certain attributes of the objects. At the moment, our idea is as open as possible and as closed legally necessary. For example, hiding location data for endangered species. " assertion.
- declaration considerations "Training and education for the data providers, managers, stewards for understanding different aspects of open data licenses. " assertion.
- declaration considerations "There are other alternatives and options out there (Cloudevents, distributed ledgers, other transactional systems). How to combine these?" assertion.
- declaration considerations "There are other alternatives and options out there (Cloudevents, distributed ledgers, other transactional systems). How to combine these?" 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 "The URI holds the historically assigned local incremental ID in the RDBMS. " assertion.
- declaration considerations "DOI's can be added upon request to the metadata records. If assigned, they function as an alias to the URI." assertion.
- declaration considerations "The URI holds the historically assigned UUID in the system." assertion.
- declaration considerations "Internally the metadata registry uses its own custom model that enables supporting multiple schemata, among which ISO 19115" assertion.
- declaration considerations "Internally the metadata registry uses its own custom model that enables supporting multiple schemata, among which EML GBIF" assertion.
- declaration considerations "Internally the metadata registry uses its own custom model that enables supporting multiple schemata, among which DataCite" assertion.
- declaration considerations "Internally the metadata registry uses its own custom model that enables supporting multiple schemata, work to support schema.org is still under way" assertion.
- declaration considerations "Since our metadata registry has a public facing web-interface, even for anonymous users, it was straightforward to let it be indexed by Google." assertion.
- declaration considerations "Since our dataset archive has a public facing web-interface, even for anonymous users, it was straightforward to let it be indexed by Google." assertion.
- declaration considerations "Was best choice at the time for machine access" assertion.
- declaration considerations "No AAI required" assertion.
- declaration considerations "Data are added by users who require an account (uname and psswd). Data in private folders are not publically-accessible : if you click on a data link, you will get a message to that effect. Data in the public folders are accessible and a click on the link will start the download. Uses a custom SSO system called 'InovOcean-auth'" assertion.
- declaration considerations "Data are added by users who require an account (uname and psswd). Data in private folders are not publically-accessible : if you click on a data link, you will get a message to that effect. Data in the public folders are accessible and a click on the link will start the download. Uses a custom SSO system called 'InovOcean-auth'" assertion.
- declaration considerations "Was best at the time for an addition to EML" assertion.
- declaration considerations "Data formats from EMODnet biology" assertion.
- declaration considerations "For geography" assertion.
- declaration considerations "Taxonomy of species names" assertion.
- declaration considerations "For thematic terms" assertion.
- declaration considerations "Darwin Core is an extension of Dublin Core, and it used EML as its metadata. In addition, DwC-Archive data format incorporates particular vocabularies that are referenced to within the archive. " assertion.
- declaration considerations "For ecological data. In fact, the EML version (2.1) we currently use does not have full semantic annotation, but we are looking into adopting the version (2.2) that does introduce better support for that." assertion.
- declaration considerations "Supporting DCAT makes us align with growing use within the EU (as prescribed through the semic-eu DCAT-A -- https://github.com/SEMICeu/DCAT-AP" assertion.
- declaration considerations "Historic support for this standard has been built in for quite some time." assertion.
- declaration considerations "Data format used by EurOBIS and EMODNet/Bio" assertion.
- declaration considerations "Working being done in H2020 ENVRI-FAIR project" assertion.
- declaration considerations "Data in our Marine Data Archive, on EurOBIS, and EMODnet Biology, always belong to the data owner, not the system. Hence we wish to allow them a full range of licences, although we encourage CC BY (especially EurOBIS and EMODnet). LifeWatch.be data are also mostly CC BY." assertion.
- declaration considerations "In some cases CC0 is concidered 'too open' - and since the academic context has a tendency for proper citation and attribution this step up is considered very mild." assertion.
- declaration considerations "In some cases, people like this 'viral' addition. Making sure we all play with the same openness rules in mind." assertion.
- declaration considerations "under consideration in special cases" assertion.
- declaration considerations "under consideration" assertion.
- declaration considerations "under consideration" assertion.
- declaration considerations "Our data are ecological, so we use EML. There are fields in EML to accommodate provenance, and we are hoping that this can be expanded on in the near future" assertion.
- declaration considerations "To expand on the options we offer (albeit the amount of provenance included in the json export is quite sparse)" assertion.
- declaration considerations "This is only for data provided via EurOBIS" assertion.
- declaration considerations "metadata records have local identifiers either created locally or harvested through dif:entry_id or 'iso /gmd:MD_Metadata/gmd:fileIdentifier/gco:CharacterString'." assertion.
- declaration considerations "sios do not own data, but relies on partner repositories. UIDs is a requirement, PIDs (DOI) is a recommendation currently." assertion.
- declaration considerations "sios do not own data, but relies on partner repositories. UIDs is a requirement, PIDs (DOI) is a recommendation currently." assertion.
- declaration considerations "This is used to indexed data locally and expose them on the data access portal. Filters and facets are based on elements of this schema." assertion.
- declaration considerations "This is used to indexed data locally and expose them on the data access portal. Filters and facets are based on elements of this schema." assertion.
- declaration considerations "This is used to indexed data locally and expose them on the data access portal. Filters and facets are based on elements of this schema." assertion.
- declaration considerations "This is used to indexed data locally and expose them on the data access portal. Filters and facets are based on elements of this schema." assertion.
- declaration considerations "This is used to indexed data locally and expose them on the data access portal. Filters and facets are based on elements of this schema." assertion.