Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- declaration considerations "Working being done in H2020 ENVRI-FAIR project." 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 "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 "Internally the metadata registry uses its own custom model that enables supporting multiple schemata, work to support DCAT is still under way" assertion.
- declaration considerations "Requirement for sharing datasets with one of our partners. Completed development in 2022." assertion.
- declaration considerations "FAIR-signposting approach nicely fits our focus on applying Linked Open Data principles and techniques" 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 "In use and harvested by Lifewatch-ERIC catalogue" assertion.
- declaration considerations "Since we are embracing more and more Linked Open Data strategies, we are now adding this LDES change feed of our metadata-records next to the existing OAI-PMH implmentation) This will become available under the domain marineinfo.org " assertion.
- declaration considerations "Implementation deployed as part of the WP9 work for ENVRI-FAIR" 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 "We do a best effort to keep metadata available and describe what will happen in case we can no longer guarantee." 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 "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 "Deployed as part of the ENVRI-FAIR project" assertion.
- declaration considerations "maintained metadata records are fully open" 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 "Widely used for data citation, mainly used by us for collections and elaborated data products" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "As defined by the CP white paper and to implement the open data sharing defined by the statutes of ICOS ERIC. " assertion.
- declaration considerations "As defined by the CP white paper and to implement the open data sharing defined by the statutes of ICOS ERIC. " assertion.
- declaration considerations "As defined by the CP white paper and to implement the open data sharing defined by the statutes of ICOS ERIC. " assertion.
- declaration considerations "As defined by the CP white paper and to implement the open data sharing defined by the statutes of ICOS ERIC. " assertion.
- declaration considerations "As defined by the CP white paper and to implement the open data sharing defined by the statutes of ICOS ERIC. " assertion.
- declaration considerations "The m2m interfaces to interact with the meta and data services and other back end services are based on REST 'inspired' https calls. The calls are document at the CP github repository at pages https://github.com/ICOS-Carbon-Portal/meta and https://github.com/ICOS-Carbon-Portal/data" assertion.
- declaration considerations "Through ERDDAP (Ocean domain)" assertion.
- declaration considerations "Through ERDDAP (Ocean domain)" assertion.
- declaration considerations "The m2m interfaces to interact with the meta and data services and other back end services are based on REST 'inspired' https calls. The calls are document at the CP github repository at pages https://github.com/ICOS-Carbon-Portal/meta and https://github.com/ICOS-Carbon-Portal/data" assertion.
- declaration considerations "The m2m interfaces to interact with the meta and data services and other back end services are based on REST 'inspired' https calls. The calls are document at the CP github repository at pages https://github.com/ICOS-Carbon-Portal/meta and https://github.com/ICOS-Carbon-Portal/data" assertion.
- declaration considerations "For ORCID and Facebook identity providers " assertion.
- declaration considerations "For ORCID and Facebook identity providers " assertion.
- declaration considerations "For ORCID and Facebook identity providers " assertion.
- declaration considerations "For ORCID and Facebook identity providers " assertion.
- declaration considerations "ICOS will be set up for the long term, 20-25 years starting from 2015. Statutes and data policy mention that data and metadata should be preserved also after that. In case ICOS ERIC is wound down in the future there will be a one year period to develop the contingency plan. All current landing pages generated dynamically by our metadata system can then be generated as static html pages that will together form a frozen metadata system which can be served by a simple static website at very low cost or be integrated as sub-site in another permanent website." assertion.
- declaration considerations "ICOS will be set up for the long term, 20-25 years starting from 2015. Statutes and data policy mention that data and metadata should be preserved also after that. In case ICOS ERIC is wound down in the future there will be a one year period to develop the contingency plan. All current landing pages generated dynamically by our metadata system can then be generated as static html pages that will together form a frozen metadata system which can be served by a simple static website at very low cost or be integrated as sub-site in another permanent website." assertion.
- declaration considerations "ICOS will be set up for the long term, 20-25 years starting from 2015. Statutes and data policy mention that data and metadata should be preserved also after that. In case ICOS ERIC is wound down in the future there will be a one year period to develop the contingency plan. All current landing pages generated dynamically by our metadata system can then be generated as static html pages that will together form a frozen metadata system which can be served by a simple static website at very low cost or be integrated as sub-site in another permanent website." assertion.
- declaration considerations "ICOS will be set up for the long term, 20-25 years starting from 2015. Statutes and data policy mention that data and metadata should be preserved also after that. In case ICOS ERIC is wound down in the future there will be a one year period to develop the contingency plan. All current landing pages generated dynamically by our metadata system can then be generated as static html pages that will together form a frozen metadata system which can be served by a simple static website at very low cost or be integrated as sub-site in another permanent website." assertion.
- declaration considerations "ICOS will be set up for the long term, 20-25 years starting from 2015. Statutes and data policy mention that data and metadata should be preserved also after that. In case ICOS ERIC is wound down in the future there will be a one year period to develop the contingency plan. All current landing pages generated dynamically by our metadata system can then be generated as static html pages that will together form a frozen metadata system which can be served by a simple static website at very low cost or be integrated as sub-site in another permanent website." assertion.
- declaration considerations "CF-1.7 compliant netcdf metadata included in the netcdf data objects" assertion.
- declaration considerations "CF-1.7 compliant netcdf metadata included in the netcdf data objects" assertion.
- declaration considerations "http://meta.icos-cp.eu/ontologies/cpmeta/" assertion.
- declaration considerations "http://meta.icos-cp.eu/ontologies/cpmeta/" assertion.
- declaration considerations "http://meta.icos-cp.eu/ontologies/cpmeta/" assertion.
- declaration considerations "http://meta.icos-cp.eu/ontologies/cpmeta/" assertion.
- declaration considerations "http://meta.icos-cp.eu/ontologies/cpmeta/" assertion.
- declaration considerations "http://meta.icos-cp.eu/ontologies/cpmeta/" assertion.
- declaration considerations "http://meta.icos-cp.eu/ontologies/cpmeta/" assertion.
- declaration considerations "http://meta.icos-cp.eu/ontologies/cpmeta/" assertion.
- declaration considerations "http://meta.icos-cp.eu/ontologies/cpmeta/" assertion.
- declaration considerations "http://meta.icos-cp.eu/ontologies/cpmeta/" assertion.
- declaration considerations "http://meta.icos-cp.eu/ontologies/cpmeta/" 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.