Skip to content
This repository was archived by the owner on Jun 2, 2020. It is now read-only.

Improve CID concept doc #95

Closed
Mr0grog opened this issue Jul 25, 2018 · 0 comments
Closed

Improve CID concept doc #95

Mr0grog opened this issue Jul 25, 2018 · 0 comments

Comments

@Mr0grog
Copy link
Collaborator

Mr0grog commented Jul 25, 2018

At the Berlin developer summit, we noted some shortcomings with the CID concept doc:

  • Should clarify that a CID specifies:

    • How to decode/interpret* content (“interpret” might not be a great term here; CIDs aren’t necessarily super-specific)
    • A version (but not a version of the data they identify)
    • A unique identifier (usually a [multi]hash)
  • We should explain how CIDs relate to “content addressing,” but need to be careful around the term “address” so as not to confuse it with either a multiaddress/peer address or with a full content address (e.g. /ipfs/<cid> or /ipfs/<cid>/some/sub/path).

rjharmon added a commit to rjharmon/docs that referenced this issue Aug 11, 2018
rjharmon added a commit to rjharmon/docs that referenced this issue Aug 11, 2018
rjharmon added a commit to rjharmon/docs that referenced this issue Aug 18, 2018
License: MIT
Signed-off-by: Randall Harmon <[email protected]>
rjharmon added a commit to rjharmon/docs that referenced this issue Aug 18, 2018
License: MIT
Signed-off-by: Randall Harmon <[email protected]>
Mr0grog added a commit that referenced this issue Aug 21, 2018
Improve CID concept doc (fixes #95).

- Explain format and components of a CID
- Explain how CIDs relate to label/address content
- Add more relevant links to specs and concept docs
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant