specs
specs copied to clipboard
ipld
Content-addressed, authenticated, immutable data structures
A couple of todos to keep our docs up to date: - There's still a few places in the specs and docs prose that refers to "default", which we've long...
**background / current status** In IPLD Schemas, we already have the `keyed`, `kinded`, `envelope`, `inline`, and even `byteprefix` representations available for unions. Each of these representation strategies does something slightly...
A couple month ago there was a pretty lengthy discussion on floats: https://github.com/ipld/specs/pull/236#issuecomment-579015374 The consensus (as far as I understand) was that while floats are a necessary evil - we...
Similar to “FlexibeByteLayout” we have numerous cases in which we need a union for a regular `kind` or a more advanced multi-block layout. It would be good to standardize the...
Could IPLD Schemas include complex qualifiers and constraints, like regexps? Maybe! (Meta: This may spawn an exploration report or other docs, but I'm starting with an issue for now, as...
Continuing a discussion from elsewhere where we're trying to clarify this graphic:  Without quoting semi-private discussion, there is disagreement about the place of ADLs here. @mikeal wants to...
Currently, when a peer doesn't support a selector, the query fails. This isn't an issue at the moment given that there's only one implementation, but it'll be come an issue...
Clients may want to query for a specific byte range from a block that contains an ordered collection of blocks. Sizes of the blocks in that collection may not be...
I finally got around to adding support of enums to my schema validator and I’m a little perplexed by the JSON representation. Here’s the default: ```sh type TestEnum enum {...
Observations: 1. The CIDv1/v0 split ends up infecting our code and specs with quite a bit of CIDv1/v0 specific logic. I'd prefer to isolate this logic as much as possible....