At the moment, the DAG and all of the objects in the DAG are opaque to IPLD, as everything is in a custom binary format. While data should still be encoded in that format (it's kind of the whole point of this project), links should be broken out and made transparent to tools that speak IPLD.
Probably the solution to this is to use DAG-CBOR to express the parts of the DAG that link to other DAG nodes. Subchunks, being leaf nodes with no links, could remain in the same encoding as now. Superchunks can use a CBOR structure like:
{ "links": {...}, "data": }
Where "data" is current binary encoded data structures excluding external links.
Commits, Spans, and Datasets, may not need a "data" blob, as they're mostly just links and metadata.
At the moment, the DAG and all of the objects in the DAG are opaque to IPLD, as everything is in a custom binary format. While data should still be encoded in that format (it's kind of the whole point of this project), links should be broken out and made transparent to tools that speak IPLD.
Probably the solution to this is to use DAG-CBOR to express the parts of the DAG that link to other DAG nodes. Subchunks, being leaf nodes with no links, could remain in the same encoding as now. Superchunks can use a CBOR structure like:
{ "links": {...}, "data": }
Where "data" is current binary encoded data structures excluding external links.
Commits, Spans, and Datasets, may not need a "data" blob, as they're mostly just links and metadata.