DeSci Nodes FIP
FAIR Implementation Profile for DeSci Nodes
The full DeSci Nodes FIP can be found at the FIP Wizard. The content from the FIP Wizard which comprise the FIP for DeSci Nodes can be found below:
| Question | RDF Comment |
|---|---|
F1 MD: What globally unique, persistent, resolvable identifiers do you use for metadata records? | DeSci Nodes has built the dPID resolver which enables the creation of versionable, secure, decentralized, and human readable GUPRIs. dPIDs uses blockchain to allow for the resolution of an unsigned 256 bit integer and a prefix to a content addressed manifest file which contains versioned CIDs for individual components. The identifiers residing in the manifest file for each component in a research object can be considered the ultimate GUPRI for individual components, resolved by the IPFS network for content addressed storage. Comment #2: While DOIs are not technically persistent, they are used to resolve to dPIDs for backwards compatibility to legacy systems. |
F1 D: What globally unique, persistent, resolvable identifiers do you use for datasets? | DeSci Nodes has built the dPID resolver which enables the creation of versionable, secure, decentralized, and human readable GUPRIs. dPIDs allow the resolution of an unsigned 256 bit integer and a prefix to a content addressed manifest file which contains versioned CIDs for individual components. The identifiers residing in the manifest file for each component in a research object can be considered the ultimate GUPRI for individual components, resolved by the IPFS network for content addressed storage. |
F2: Which metadata schemas do you use for findability? | DeSci Nodes uses JSON-LD through an IPLD-compliant version of RO-Crate. |
F3: What is the technology that links the persistent identifiers of your data to the metadata description? | Directed Acyclic Graphs and IPLD have been retrofitted with JSON-LD to allow for machine actionable linkages between metadata in manifest files and the CIDs referencing data. |
F4 MD: In which search engines are your metadata records indexed? | Metadata record are indexed and searchable through the dPID Indexer service. Blockchain functions as a permanent record on which metadata is indexed. It functions in a BC/DR capability for the scientific record. Attaching DOIs to Nodes allow for metadata to be indexed through DataCite in legacy systems. |
F4 D: In which search engines are your datasets indexed? | Datasets are indexed and searchable through the dPID Indexer service. Blockchain functions as a permanent record on which metadata is indexed. It functions in a BC/DR capability for the scientific record. Attaching DOIs to Nodes allow for metadata to be indexed through DataCite in legacy systems. |
A1.1 MD: Which standardized communication protocol do you use for metadata records? | Metadata is transferred primarily through IPFS but allows HTTP-based clients to access content stored on the IPFS network through an HTTP API. |
A1.1 D: Which standardized communication protocol do you use for datasets? | Data is transferred primarily through IPFS but allows HTTP-based clients to access content stored on the IPFS network through an HTTP API. |
A1.2 MD: Which authentication & authorisation technique do you use for metadata records? | Write access on Metadata records is provisioned through ownership of a Node's underlying ERC-721 token. The standard for read authorization on metadata is public and open. |
A1.2 D: Which authentication & authorisation technique do you use for datasets? | Both read and write access on datasets is provisioned through ownership of a Node's underlying ERC-721 token. |
A2: Which metadata longevity plan do you use? | |
I1 MD: Which knowledge representation languages (allowing machine interoperation) do you use for metadata records? | DeSci nodes uses JSON-LD to allow machine interoperability in metadata records |
I1 D: Which knowledge representation languages (allowing machine interoperation) do you use for datasets? | DeSci nodes uses JSON-LD to allow machine interoperability in metadata records |
I2 MD: Which structured vocabularies do you use to annotate your metadata records? | DeSci nodes uses an IPLD compliant implementation of RO-Crate. RO-Crate context information for types can be found at https://w3id.org/ro/crate/1.1/context |
I2 D: Which structured vocabularies do you use to encode your datasets? | DeSci nodes uses an IPLD compliant implementation of RO-Crate. RO-Crate context information for types can be found at https://w3id.org/ro/crate/1.1/context |
I3 MD: Which models, schema(s) do you use for your metadata records? | DeSci nodes uses an IPLD compliant implementation of RO-Crate. |
I3 D: Which models, schema(s) do you use for your datasets? | DeSci nodes uses an IPLD compliant implementation of RO-Crate. |
R1.1 MD: Which usage license do you use for your metadata records? | Metadata for DeSci Nodes is always under a CC0 License |
R1.1 D: Which usage license do you use for your datasets? | DeSci Nodes allows users to enter a variety of licenses on different component types. The options for pdfs include a variety of CC licenses such as CC0 and CC BY. The options for code and datasets include (but are not limited to) MIT, GPL, and CC0. |
R1.2 MD: Which metadata schemas do you use for describing the provenance of your metadata records? | DeSci nodes uses an IPLD compliant implementation of RO-Crate. RO-Crate versioning information can be found through https://w3id.org/ro/crate/1.1/context |
R1.2 D: Which metadata schemas do you use for describing the provenance of your datasets? | DeSci nodes uses an IPLD compliant implementation of RO-Crate. RO-Crate versioning information can be found through https://w3id.org/ro/crate/1.1/context |
Last updated