Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- declaration considerations "Taxonomy of species names" assertion.
- declaration considerations "For thematic terms" assertion.
- declaration considerations "To be added to our general catalogue, but for data already in DwC-A format (EMOnet and EurOBIS only) this vocabulary is already used and correctly referenced in the data" 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 "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.
- declaration considerations "NetCDF CF supported by SDN vocabs" assertion.
- declaration considerations "Now using https://www.seadatanet.org/Data-Access/License/1.0 but will be made as GUPRI under ENVRIFAIR, plus mapping to CCBY" assertion.
- declaration considerations "Now using https://www.seadatanet.org/Data-Access/License/1.0 but will be made as GUPRI under ENVRIFAIR, plus mapping to CCBY" assertion.
- declaration considerations "ISO adopted PROV-O will be investigated, but probably better fit for data products (sextant). In CDI more info about sensors will be included." assertion.
- declaration considerations "There is already provenance info in the metadata, and more info about sensors will be included." 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 "Used for datasets shared via B2SHARE. issuing DOI from the eLTER CDN will be implemented in 2022." assertion.
- declaration considerations "Used for datasets shared via B2SHARE. issuing DOI from the eLTER CDN will be implemented in 2022." 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 "eLTER DIP is the central access point to eLTER metadata from a range of sources using geonetwork as backbone technology. " 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 "eLTER DIP is the central access point to eLTER metadata from a range of sources using geonetwork as backbone technology. " 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 "eLTER DIP is the central access point to eLTER metadata from a range of sources using geonetwork as backbone technology. " assertion.
- declaration considerations "DEIMS-SDR REST-API shares information on sites, locations, sensors, datasets and networks as json." assertion.
- declaration considerations "DEIMS-SDR REST-API shares information on sites, locations, sensors, datasets and networks as json." 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 "DEIMS-SDR REST-API shares information on sites, locations, sensors, datasets and networks as json." assertion.
- declaration considerations "DEIMS-SDR REST-API shares information on sites, locations, sensors, datasets and networks as json." assertion.
- declaration considerations "Direct download using https/http request for datasets shared via B2SHARE." assertion.
- declaration considerations "Direct download using https/http request for datasets shared via B2SHARE." assertion.
- declaration considerations "Direct download using https/http request for datasets shared via B2SHARE." assertion.
- declaration considerations "Direct download using https/http request for datasets shared via B2SHARE." assertion.
- declaration considerations "General eLTER data policy fosters open data. Restrictions might apply for site based data under embargo." assertion.
- declaration considerations "General eLTER data policy fosters open data. Restrictions might apply for site based data under embargo." assertion.