This repository has been archived by the owner on Jun 29, 2022. It is now read-only.
[WIP] Refactor all IPLD specifications #72
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lanzafame
reviewed
Oct 1, 2018
vmx
reviewed
Oct 1, 2018
vmx
reviewed
Oct 1, 2018
daviddias
reviewed
Oct 19, 2018
daviddias
reviewed
Oct 19, 2018
|
There is the start of a glossary at the bottom of this PR.
…On Fri., 19 Oct. 2018, 20:28 Eoghan Ó Carragáin, ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In README.md <#72 (comment)>
:
> + | | | Structured Data w/ indexes |
+ | unixfs v2 | | VR, Geo, SQL, etc. | +----------+
+ | | | | | |
+ +-------------+ +-----------------------------+ | MFS in |
+ | | | | | IPFS |
+ | HAMT | | Sorted Index (sharded) | | |
+ | | | | +----------+
+ +-------------+-+-----------------------------+ | |
+ | | | unixfs |
+ | Complex Data Structures | | v1 |
+ | | | |
++------------------------------------------------------------------------------+
+| | | | |
+| | dag-json dag-cbor | | |
+| | | | |
+| Codecs +---------------------------------------------+ git | dag-pb |
It would be great to have some definitions and examples to illustrate the
IPFS/IPLD usage of: codecs; formats; types/typing; schema. I've seen them
all used in IPLD discussions but depending on your background these can
have different meanings and connotations that don't exactly match IPLD/IPFS
usage.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#72 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFpnaPvk-jEA0rDNoboEiFIVBDXX4hLmks5umalmgaJpZM4XAMcP>
.
|
|
Ok, just pushed lots of fixes. I'd like to move this towards a merge. It isn't perfect, but it's a lot closer to how we're now talking about IPLD than the current state of the repo. |
|
@diasdavid I disagreed with the codec/format terminology and you haven't responded to my prior reply so I resolved that conversation for now. If you want to continue to discuss we can start a new thread, PR, or we can just have a quick call to resolve it. |
vmx
reviewed
Nov 6, 2018
warpfork
reviewed
Nov 6, 2018
warpfork
reviewed
Nov 6, 2018
warpfork
reviewed
Nov 6, 2018
vmx
approved these changes
Nov 7, 2018
|
Ok, I think we're ready to merge now. All pending discussions have been closed. |
|
What teams have merge access in this repo? |
|
@mikeal I've added the IPLD JS Team. |
This was referenced Aug 14, 2019
Closed
prataprc
pushed a commit
to iprs-dev/ipld-specs
that referenced
this pull request
Oct 13, 2020
Retcon of all IPLD specifications.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following up on the new direction I've started to refactor the specifications.
Based on comments by @diasdavid I'm also removing the out of date or deprecated specs as I go.