Inline IPLD: A Human-Legible Alternative to CAR Files
summary
A human-readable serialization that inlines linked IPLD nodes into JSON/CBOR trees using / . and & delimiters to mark embedded blocks and CID contexts, with a left-leaning spanning tree as the default and an optional saturation mode that duplicates shared nodes for easiest reading. Works with dag-json, dag-cbor, dag-pb, dag-yaml, stays fully interoperable with CAR files and vanilla IPLD, and ships as a Rust/Wasm implementation built in a few days.
AI-written summary · about
chapters (7)
- 0:00Introduction and IPLD basics
- 3:35Problem with IPLD links
- 5:44Inline IPLD concept
- 7:12Tree representations
- 9:20Saturation vs spanning trees
- 10:45Extracting to block store
- 11:53Implementation and resources
related talks
17mBring Your Own Data Structures to Datalog
15mIncremental Processing of Structured Data in Datalog
21mA Typed Multi-Level Datalog IR and its Compiler Framework
39mData-centric Metaprogramming
36mData Driven UIs, Incrementally
52mI See What You Mean
51mBinary Object Serialization with Data Structure Traversal & Reconstruction in Cpp
42mWhy JSON-LD and what is it?