There's still a few places in the specs and docs prose that refers to "default", which we've long ago renamed "implicit" (to avoid the connotations of mutation which the word "default" seems to carry). We need to track down and fix all those up.
(A few of those might still use the older, more verbose drafts of schema DSL syntax which places that info in the representation block rather than parenthetically after the field. We should clean all those up too.)
I'm not sure if there are many references to "undefined" when discussing keys/values that are absent in contexts where they're expected, but we should do a pass checking for those as well. I've now consistently updated all the code in go-ipld-prime to call this concept "absent", which better reflects what it means, and sounds a lot less mysterious.
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 ago renamed "implicit" (to avoid the connotations of mutation which the word "default" seems to carry). We need to track down and fix all those up.
(A few of those might still use the older, more verbose drafts of schema DSL syntax which places that info in the representation block rather than parenthetically after the field. We should clean all those up too.)
I'm not sure if there are many references to "undefined" when discussing keys/values that are absent in contexts where they're expected, but we should do a pass checking for those as well. I've now consistently updated all the code in go-ipld-prime to call this concept "absent", which better reflects what it means, and sounds a lot less mysterious.