Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- 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 "" 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.