IPLD refining call 3

[nicola]

IPLD stakeholders should get together to agree on some pending refinement in IPLD. These issues are not necessarily new features but restrictions that we may have to specify in the spec to make it less ambiguous.

Partecipants are expected to be informed about the different issues, they should:

• Read the different issues beforehand
• Raise concerns and give opinion offline (so that everyone is ready to agree/further discuss)

Agenda so far:

• Update on CID
• Resolution of Relative Paths in IPLD (Spec refining: Relative paths in IPLD ipld/specs#1)
• Writing of the new spec (skeleton & structure)

Other:

• Use of IPLD pointers in link object (Spec refining: Support of IPLD pointers as links ipld/specs#3)
• IPLD links must be IPLD pointers (Spec refining: IPLD pointers must point to IPLD objects only ipld/specs#8)
• Requiring prefixing of paths (Spec refining: requiring namespace in IPLD pointers ipld/specs#7)
• Mutable pointers (Spec refining: Mutable links in IPLD ipld/specs#9)

We can do this in the coming all-hands (maybe I would just add a new weekly slot for IPLD?)

---

Ping @Stebalien, @mildred, @jbenet, @dignifiedquire, @RichardLitt

[nicola]

Added notes here #207

I will close this once I create TODOs in new issues under IPLD

[nicola]

done ipld/specs#24