specs
specs copied to clipboard
ipld
Content-addressed, authenticated, immutable data structures
When serialising/deserialising blocks we currently suggest an intermediate representation, the ipld data model. This has the advantage that generic ipld tools can understand and work with this representation (eg selectors/graphsync)....
While currently a side effect of bitswap/libp2p, the main reason for introducing the concept of blocks is that they have a known finite size. An ipld library should be aware...
Logging this so that I don’t forget about it. Chatting with @warpfork today and, since you already have to use syntax when using an advanced layout to define a type...
I just found a wonderful tool called [remark-validate-links](https://github.com/remarkjs/remark-validate-links) which checks for local links. I plan to add a TravisCI job to run that on this repo to make sure we...
allows for `application/ipld+json` or `application/ipld+cbor` see: https://github.com/ipld/specs/issues/99#issuecomment-471028149
The IPLD Data Model describes a Map kind. The description should be expanded that the IPLD Data Model only allows for unique keys. There's related discussion at https://github.com/ipld/specs/issues/47.
Numbers can be represented in different ways in CBOR. We should specify how they should be encoded so that all implementations will result with the same binary representation, hence the...
@Stebalien as discussed, this would be helpful with working in standards development that demand a valid URI schema.
Links v2
We've been throwing around this idea for an improved Link for a little while now. In fact, the early specifications for links stated they had more features than we currently...
When you store data serialized as CBOR in IPLD there are restrictions on they keys that can be used in maps. This needs to be documented in the spec. The...