Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- 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 "The identifier should be able to handle Digital Specimens (a specific type of Digital Object) and related metadata. " assertion.
- declaration considerations "A Registration Agency for Digital Specimen and Natural Science Collections data is needed given the diverse and cross-cutting needs for specimen data. A global engagement is required to realise the potential power of persistent identifiers. " assertion.
- declaration considerations "The identifier should be able to handle Digital Specimens (a specific type of Digital Object) and related metadata. " assertion.
- declaration considerations "DiSSCo does not specifically distinguish between data and metadata for digital specimen, allowing most data fields to be used also as metadata for discovery. " assertion.
- declaration considerations "Understanding how schema.org works with the Digital Object Architecture." assertion.
- declaration considerations "The FAIR Digital Object model should be able to handle Digital Specimens (a specific type of Digital Object) and related metadata and a wide variety of collections and specimens data. For Digital Specimens, often there is no distinction between data and metadata, the attributes for the digital object should be index and discoverable. " assertion.
- declaration considerations "A FAIR service providing access to Digital Specimens and Collections. Harmonising data from different types of collections and institutions of different sizes can be a challenge. " assertion.
- declaration considerations "Ensuring interoperability between DiSSCo and GBIF infrastructures. " assertion.
- declaration considerations "A FAIR service providing access to Digital Specimens and Collections. Harmonising data from different types of collections and institutions of different sizes can be a challenge. As each individual specimen is described as Digital Object, the dataset concept for DiSSCo is not clearly defined. Collection Object (group of Digital Specimens) can be thought of as datasets. " assertion.
- declaration considerations "Different systems (bata providers are not aware of DOIP and not compatible yet. " assertion.
- declaration considerations "A common guidelines and recommendations for application programming interfaces (APIs) is lac." assertion.
- declaration considerations "DOIP is not natively supported in the systems currently used in the community. At the moment it only provides JSON response." assertion.
- declaration considerations "REST is widely use however, not all systems will have a REST API endpoint. Alternative would be to import the data." assertion.
- declaration considerations "A single sign on (SSO) interface that is compatible with EOSC and AARC guidelines. Not all the institutions are AAI federation ready so alternative federated login options need to be provided (such as orcid, google). " assertion.
- declaration considerations "A single sign on (SSO) interface that is compatible with EOSC and AARC guidelines. Not all the institutions are AAI federation ready so alternative federated login options need to be provided (such as orcid, google). " assertion.
- declaration considerations "A policy to help the community understand what data should be open or not. How to handle ethical and legal issues. " assertion.
- declaration considerations "The Data Management Plan is a living document. Proper training, resources need to be in place for." assertion.
- declaration considerations "DarwinCore Archive provides a mechanism to share data in a tab delimited format. " assertion.
- declaration considerations "JSON Schema alone is not enough for validation, need semantic validation (JSON-LD etc.)." assertion.
- declaration considerations "How to maintain the standards and vocabularies? How to make it usable for different systems? " assertion.
- declaration considerations "How to maintain the standards and vocabularies? How to make it usable for different systems? " assertion.
- declaration considerations "Again, concept of datasets need to be defined within our community. " assertion.
- declaration considerations "currently under development. Needs to align with existing specifications and also efforts from other research infrastructure in the biodiversity domain. " assertion.
- declaration considerations "The specification design work in openDS is an iterative process. There will be pilots and testing done of the concepts via the cordra software implementation at nsidr.org." assertion.
- declaration considerations "Each object contains a minimum of mandatory terms consistent with its formal object type definition, with the possibility to include optional additional terms and enrichments as necessary." assertion.
- 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 "" 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 "The DOIs are the best way to permanently identify a given digital object, in a format controlled by the International DOI Foundation. We plan to to establish an agreement with DataCite in the near future." 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 plan to to establish an agreement with DataCite in the near future." assertion.
- declaration considerations "We plan to use the ISO 19139:2007 standard in order to describe the LifeWatch ERIC resources (e.g., services, workflows, virtual research environments, etc.). Such resources are currently listed in the LifeWatch ERIC Web Portal and described with a common set of metadata but no catalogue is implemented yet." assertion.
- declaration considerations "We plan to use the EML standard in the near future to describe the LifeWatch ERIC datasets." assertion.
- declaration considerations "We have planned to establish an agreement with DataCite in the near future." assertion.
- declaration considerations "We will use the HTTPS being it the standard de facto as secure communication protocol." assertion.
- declaration considerations "We will use the HTTPS being it the standard de facto as secure communication protocol." assertion.
- declaration considerations "The authentication & authorisation technique depends on the specific national node of the LifeWatch ERIC. Considering the LifeWatch Italy Data Portal for example, it uses a local LDAP as major access technology, mainly based on the couple of credentials username and password." assertion.
- declaration considerations "We plan to use the RDF schema to describe the metadata of all LifeWatch ERIC resources." assertion.
- declaration considerations "We plan to use XML to describe the metadata of all LifeWatch ERIC resources." assertion.
- declaration considerations "The knowledge representation languages used for datasets depend from the LifeWatch ERIC national node. Some examples are JSON, XMLS, DwC-A, NetCDF, etc." assertion.
- declaration considerations "The knowledge representation languages used for datasets depend from the LifeWatch ERIC national node. Some examples are JSON, XMLS, DwC-A, NetCDF, etc." assertion.
- declaration considerations "The knowledge representation languages used for datasets depend from the LifeWatch ERIC national node. Some examples are JSON, XMLS, DwC-A, NetCDF, etc." assertion.
- declaration considerations "The knowledge representation languages used for datasets depend from the LifeWatch ERIC national node. Some examples are JSON, XMLS, DwC-A, NetCDF, etc." assertion.
- declaration considerations "The structured vocabularies and thesauri used to encode datasets depend on the LifeWatch ERIC national node. Some examples are PHYTOTRAITS, FISHTRAITS, MACROALGAETRAITS, ALIENSPECIES, EUNIS, Marine Regions, WoRMS, etc." assertion.
- declaration considerations "The structured vocabularies and thesauri used to encode datasets depend on the LifeWatch ERIC national node. Some examples are PHYTOTRAITS, FISHTRAITS, MACROALGAETRAITS, ALIENSPECIES, EUNIS, Marine Regions, WoRMS, etc." assertion.
- declaration considerations "The structured vocabularies and thesauri used to encode datasets depend on the LifeWatch ERIC national node. Some examples are PHYTOTRAITS, FISHTRAITS, MACROALGAETRAITS, ALIENSPECIES, EUNIS, Marine Regions, WoRMS, etc." assertion.
- declaration considerations "The structured vocabularies and thesauri used to encode datasets depend on the LifeWatch ERIC national node. Some examples are PHYTOTRAITS, FISHTRAITS, MACROALGAETRAITS, ALIENSPECIES, EUNIS, Marine Regions, WoRMS, etc." assertion.
- declaration considerations "The structured vocabularies and thesauri used to encode datasets depend on the LifeWatch ERIC national node. Some examples are PHYTOTRAITS, FISHTRAITS, MACROALGAETRAITS, ALIENSPECIES, EUNIS, Marine Regions, WoRMS, etc." assertion.
- declaration considerations "The structured vocabularies and thesauri used to encode datasets depend on the LifeWatch ERIC national node. Some examples are PHYTOTRAITS, FISHTRAITS, MACROALGAETRAITS, ALIENSPECIES, EUNIS, Marine Regions, WoRMS, etc." assertion.
- declaration considerations "The structured vocabularies and thesauri used to encode datasets depend on the LifeWatch ERIC national node. Some examples are PHYTOTRAITS, FISHTRAITS, MACROALGAETRAITS, ALIENSPECIES, EUNIS, Marine Regions, WoRMS, etc." assertion.
- declaration considerations "We plan to use the ISO 19139:2007 standard in order to describe the LifeWatch ERIC resources (e.g., services, workflows, virtual research environments, etc.). Such resources are currently listed in the LifeWatch ERIC Web Portal and described with a common set of metadata but no catalogue is implemented yet." assertion.
- declaration considerations "We plan to use the EML standard in order to describe the LifeWatch ERIC datasets." assertion.
- declaration considerations "The models, schemas used for datasets depend from the LifeWatch ERIC national node. Some examples are DwC-A, NetCDF, EML2.0, etc." assertion.
- declaration considerations "The models, schemas used for datasets depend from the LifeWatch ERIC national node. Some examples are DwC-A, NetCDF, EML2.0, etc." assertion.
- declaration considerations "The models, schemas used for datasets depend from the LifeWatch ERIC national node. Some examples are DwC-A, NetCDF, EML2.0, etc." assertion.
- declaration considerations "A mixture between mostly CC-BY and CC-BY-NC is planned to be used for the LifeWatch ERIC resources." assertion.
- declaration considerations "A mixture between mostly CC-BY and CC-BY-NC is planned to be used for the LifeWatch ERIC resources." 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 "DOI assigned via Sextant to each metadata. Example : http://dx.doi.org/10.12770/a7b7d13f-0b95-445b-ba83-fe9357c9e154" assertion.
- declaration considerations "DOI assigned via Sextant to each metadata" assertion.
- declaration considerations "Metadata uses schema based on ISO19115/139" assertion.
- declaration considerations "Metadata uses schema based on ISO19115/139" assertion.
- declaration considerations "Dedicated search interface : https://www.seadatanet.org/Products#/search?from=1&to=30" assertion.
- declaration considerations "sparql endpoint for Seadatanet products : https://sextant.seadatanet.org/sparql/" assertion.
- declaration considerations "https://www.seadatanet.org/Products#/search?from=1&to=30" assertion.
- declaration considerations "Harvesting of the catalogue bu using CSW : https://sextant.ifremer.fr/geonetwork/SEADATANET/eng/csw?SERVICE=CSW&REQUEST=GetCapabilities" assertion.
- declaration considerations "https://sextant.seadatanet.org/sparql/" assertion.
- declaration considerations "https://www.ifremer.fr/erddap/griddap/index.html?page=1&itemsPerPage=1000" assertion.
- declaration considerations "open, free, and universally implementable protocol" assertion.
- declaration considerations "Metadata are open anf fre" assertion.
- declaration considerations "Marine-ID is generally accepted method and solution for AAA in the marine domain" assertion.