Something like JSON-LD, so a general application can understand the data model of the structured data.
Instead of JSON, I prefer CBOR, so binary strings can be handled directly.
The goal here is to give a understandable metalanguage that exposes the structure of data.
More specifically, say when a generic repo obtains a data object, the repo can understand there are fields in the data object, and get the rough idea (field name, field type, and value without application semantics). It can also decide whether to follow a link and fetch another object.
The goal does not include copying or imitating any existing feature of JSON-LD/CBOR-LD.
After that, the inner data objects design should be replaced by it.
zjkmxy
commented
2 months ago
Something like JSON-LD, so a general application can understand the data model of the structured data. Instead of JSON, I prefer CBOR, so binary strings can be handled directly. The goal here is to give a understandable metalanguage that exposes the structure of data. More specifically, say when a generic repo obtains a data object, the repo can understand there are fields in the data object, and get the rough idea (field name, field type, and value without application semantics). It can also decide whether to follow a link and fetch another object. The goal does not include copying or imitating any existing feature of JSON-LD/CBOR-LD.
After that, the inner data objects design should be replaced by it.
Challenge: