oceanprotocol/docs
1
0
Fork 0
mirror of https://github.com/oceanprotocol/docs.git synced 2024-11-26 19:49:26 +01:00
Code Releases Activity

Improve did

Browse Source
This commit is contained in:
trentmc 2021-08-22 09:43:36 +02:00
parent 204cf7e1a7
commit d63e9ea1df
1 changed files with 16 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
content/concepts/metadata-did.md
View File

@ -1,6 +1,15 @@
# Asset Identifiers & Objects - DIDs & DDOs ---
title: DIDs & DDOs - Asset Identifiers & Objects
description: Specifification of DIDs & DDOs in Ocean
slug: /concepts/metadata-did/
section: concepts
---
## Background # Introduction
## Overview
This document describes how Ocean assets follow the DID/DDO spec, such that Ocean assets can inherit DID/DDO benefits and enhance interoperability.
Decentralized identifiers (DIDs) are a new type of identifier that enables verifiable, decentralized digital identity. Each DID is associated with a unique entity. DIDs may represent humans, objects, and more. Decentralized identifiers (DIDs) are a new type of identifier that enables verifiable, decentralized digital identity. Each DID is associated with a unique entity. DIDs may represent humans, objects, and more.
@ -11,9 +20,7 @@ The combination of a DID and its associated DID Document forms the root record f
DIDs and DDOs follow [this specification](https://w3c-ccg.github.io/did-spec/) defined by the World Wide Web Consurtium (W3C). DIDs and DDOs follow [this specification](https://w3c-ccg.github.io/did-spec/) defined by the World Wide Web Consurtium (W3C).
This document describes how Ocean assets follow the DID spec, such that Ocean assets can inherit DID/DDO benefits and enhance interoperability. ## Rules for DIDs & DDOs in Ocean
## Specification
- An _asset_ in Ocean represents a downloadable file, compute service, or similar. Each asset is a _resource_ under control of a _publisher_. The Ocean network itself does _not_ store the actual resource (e.g. files). - An _asset_ in Ocean represents a downloadable file, compute service, or similar. Each asset is a _resource_ under control of a _publisher_. The Ocean network itself does _not_ store the actual resource (e.g. files).
- An asset should have a DID and DDO. The DDO should include metadata about the asset. - An asset should have a DID and DDO. The DDO should include metadata about the asset.
@ -22,6 +29,8 @@ This document describes how Ocean assets follow the DID spec, such that Ocean as
- The DDO is stored on-chain. It's stored in in plaintext, with two exceptions: (1) the field for resource-access url is encrypted (2) the whole DDO may be encrypted, if the publisher is willing to lose 100% of discoverability. - The DDO is stored on-chain. It's stored in in plaintext, with two exceptions: (1) the field for resource-access url is encrypted (2) the whole DDO may be encrypted, if the publisher is willing to lose 100% of discoverability.
- A metadata cache like Aquarius can help in reading and writing DDO data from the chain. - A metadata cache like Aquarius can help in reading and writing DDO data from the chain.
# DIDs in Ocean
## DID Structure ## DID Structure
In Ocean, a DID is a string that looks like: In Ocean, a DID is a string that looks like:
@ -34,6 +43,8 @@ It follows [the generic DID scheme](https://w3c-ccg.github.io/did-spec/#the-gene
The part after `did:op:` is the asset's on-chain Ethereum address (minus the "0x"). One can be computed from the other; therefore there is a 1:1 mapping between did and Ethereum address. The part after `did:op:` is the asset's on-chain Ethereum address (minus the "0x"). One can be computed from the other; therefore there is a 1:1 mapping between did and Ethereum address.
# DDOs in Ocean
## DDO Attributes ## DDO Attributes
![DDO Content](images/ddo-content.png) ![DDO Content](images/ddo-content.png)