This repository was archived by the owner on Jan 8, 2026. It is now read-only.
doc: add motivation section to data model spec #191
Merged
Conversation
This file contains hidden or 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
dvc94ch
approved these changes
Sep 10, 2019
rvagg
approved these changes
Sep 11, 2019
| by common programming languages.** This provides the foundation for block format agnostic tools | ||
| to be built using familiar native types in a programmer's preferred language. As such, there | ||
| is an element of "lowest common denominator" to the IPLD Data Model in that it cannot support | ||
| some advanced features (like non-string keys for Maps) because support for such a feature |
Member
There was a problem hiding this comment.
could also add "or unsigned integers" inside those parens to drive home the point
Contributor
Author
There was a problem hiding this comment.
i’d rather not litigate that particular point in this PR :)
Contributor
Author
|
I’m gonna merge in 48 hours unless there are objections. |
Stebalien
pushed a commit
to Stebalien/specs
that referenced
this pull request
Sep 18, 2019
…delay added soft block delay
prataprc
pushed a commit
to iprs-dev/ipld-specs
that referenced
this pull request
Oct 13, 2020
doc: add motivation section to data model spec
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.
After commenting on #184 (comment) I realized that we’re missing some of the key motivations for the data model in the spec itself.
This is some draft text on the “block format agnostic” motivation and how it impacts the data model spec.