Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- declaration considerations "Central location for data storage and analysis for the neurodegenerative disease community." assertion.
- declaration considerations "Public landing point for the EPND platform created for the alzheimer community and other interested parties ." assertion.
- declaration considerations "European node for data storage and analysis for the neurodegenerative disease community." assertion.
- declaration considerations "Widely accepted protocol of communication for web services, REST aims for fast performance, reliability, and the ability to grow." assertion.
- declaration considerations "Widely accepted protocol of communication for web services, REST aims for fast performance, reliability, and the ability to grow." assertion.
- declaration considerations "OpenID is an open standard and decentralized authentication protocol promoted by the non-profit OpenID Foundation. It is widely accepted and used to perform authentication, i.e. identity verification of a user." assertion.
- declaration considerations "OAuth 2.0 is a widely accepted open standard for access delegation and it allows clients to access data without sharing user's credentials, it is thus a protocol for authorisation purposes." assertion.
- declaration considerations "OpenID is an open standard and decentralized authentication protocol promoted by the non-profit OpenID Foundation. It is widely accepted and used to perform authentication, i.e. identity verification of a user." assertion.
- declaration considerations "OAuth 2.0 is a widely accepted open standard for access delegation and it allows clients to access data without sharing user's credentials, it is thus a protocol for authorisation purposes." assertion.
- declaration considerations "OAuth 2.0 is a widely accepted open standard for access delegation and it allows clients to access data without sharing user's credentials, it is thus a protocol for authorisation purposes." assertion.
- declaration considerations "JSON is a language-independent and open standard file format and data interchange format that uses human-readable text. It is therefore chosen due to its flexibility." assertion.
- declaration considerations "RDF is a directed graph composed of triple statements and the format of choice for the semantic web community." assertion.
- declaration considerations "OWL is the recommended language by W3C to represent ontologies and we use medical ontologies to make data semantically interoperable." assertion.
- declaration considerations "DCAT is widely used in the medical domain, and we plan to use fair data points that also rely on DCAT." assertion.
- declaration considerations "We use shacl to go from an open world concept in ontologies to a more closed world solution that guarantees interoperability between datasets. " assertion.
- declaration considerations "We use the cedar workbench to reuse and create metadata json templates, then export these to the github page of the community. " assertion.
- declaration considerations "SNOMED is the most used vocabulary in the medical domain." assertion.
- declaration considerations "SNOMED is the most used vocabulary in the medical domain." assertion.
- declaration considerations "SNOMED is the most used vocabulary in the medical domain." assertion.
- declaration considerations "FAIR data points take care of a lot of the the metadata needed for Findability and Reusability, and a uniform open way of Accessing the data. The FAIR data point also addresses the Interoperability of the metadata it stores, but it leaves the Interoperability aspects for the data itself to the data provider." assertion.
- declaration considerations "FAIR data points take care of a lot of the the metadata needed for Findability and Reusability, and a uniform open way of Accessing the data. The FAIR data point also addresses the Interoperability of the metadata it stores, but it leaves the Interoperability aspects for the data itself to the data provider." assertion.
- declaration considerations "" assertion.
- declaration considerations "Dataset can be identified by URI and downloaded." assertion.
- declaration considerations "We are going to FAIRify it" assertion.
- declaration considerations "We are going to FAIRify it" assertion.
- declaration considerations "We are going to FAIRify it" assertion.
- declaration considerations "We are going to FAIRify it" assertion.
- declaration considerations "In the future we are going to use FAIR Data Point or/and SPARQL API" assertion.
- declaration considerations "In the future we are going to use FAIR Data Point or/and SPARQL API" assertion.
- declaration considerations "In the future we are going to use FAIR Data Point or/and SPARQL API" assertion.
- declaration considerations "In the future we are going to use FAIR Data Point or/and SPARQL API" assertion.
- declaration considerations "All resources are publicly available." assertion.
- declaration considerations "All data are publicly available" assertion.
- declaration considerations "All data are publicly available" assertion.
- declaration considerations "All data are publicly available" assertion.
- declaration considerations "All data are publicly available" assertion.
- declaration considerations "Not FAIR enough. Will be transformed into vacabulary." assertion.
- declaration considerations "Not FAIR enough. Will be transformed into vacabulary." assertion.
- declaration considerations "Not FAIR enough. Will be transformed into vacabulary." assertion.
- declaration considerations "Not FAIR enough. Will be transformed into vacabulary." assertion.
- declaration considerations "Needs to be fully clarified" assertion.
- declaration considerations "Needs to be fully confirmed" assertion.
- declaration considerations "Needs to be fully confirmed" assertion.
- declaration considerations "Needs to be fully confirmed" 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 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 "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 "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 "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 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 have planned to establish an agreement with DataCite in the near future." 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 "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 "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 knowledge representation languages used for datasets depend from the LifeWatch ERIC national node. Some examples are JSON, XMLS, DwC-A, NetCDF, etc." assertion.