Implement the IPLD spec

[mildred]

This issue is here to track the differences between the current implementation and the IPLD spec:

• Relationship with Protocol Buffers legacy IPFS node format ipfs/specs#59 (not yet decided): Convert protobuf messages to the specified format
• IPLD CBOR tagging ipfs/specs#61 (not yet decided): Encode in CBOR using tags
• IPLD merkle-path improvements ipfs/specs#62 or Separate filesystem merkle-path from IPLD merkle-path ipfs/specs#60 (not yet decided): Implement path resolution and walking
• IPLD: precisions about canonical format ipfs/specs#63 and Question about multicodec header and object hash #15: Test that reading a protocol buffer message without the multicodec header works.
• Rename Merkle links key from mlink to link ipfs/specs#64 (not yet decided): Use the correct key for link names (link vs mlink)
• remove everything about escaping as it seems we don't need it any longer
• implement changes to spec (as in feat: upgrade to latest spec js-ipld-dag-cbor#17 and update ipld spec with new link fmt ipfs/specs#101)
• decide the structure of the code that we were discussing before

If I missed anything, please tell so I can add to the list.

[jbenet]

Hey @mildred -- let's get rolling on go-ipld. js-ipld is landing soon. See ipld/js-ipld-dag-cbor#17 and ipfs/specs#97

I think some of the above checkboxes are done? Yep. checked them.

[jbenet]

I think we now need:

• implement changes to spec (as in feat: upgrade to latest spec js-ipld-dag-cbor#17 and update ipld spec with new link fmt ipfs/specs#101)
• decide the structure of the code that we were discussing before

[mildred]

decide the structure of the code that we were discussing before

Could you elaborate? (add a reference)