You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is probably a question for later, but as I ran over when changing the document to use packed CBOR:
Do we want to associate the absence of a dictionary with a dictionary-shipped-by-the-document?
Currently, that's what it says.
Unless we get a good widely usable dictionary at the start, we may want to use application/coral+cbor for unprofiled data (with no preloaded dictionary, but if there's a mechanism for that maybe it can be self-described). That will probably not even deserve a short content format identifier.
If, of course, we find an ontology / dictionary that is widely applicable, nothing against making that the default, but right now we don't have any, and I'm not sure there will be a universal one. (There might be one that captures everything we right now have brewing in CoRE, though).
The text was updated successfully, but these errors were encountered:
This is probably a question for later, but as I ran over when changing the document to use packed CBOR:
Do we want to associate the absence of a dictionary with a dictionary-shipped-by-the-document?
Currently, that's what it says.
Unless we get a good widely usable dictionary at the start, we may want to use application/coral+cbor for unprofiled data (with no preloaded dictionary, but if there's a mechanism for that maybe it can be self-described). That will probably not even deserve a short content format identifier.
If, of course, we find an ontology / dictionary that is widely applicable, nothing against making that the default, but right now we don't have any, and I'm not sure there will be a universal one. (There might be one that captures everything we right now have brewing in CoRE, though).
The text was updated successfully, but these errors were encountered: