4 ms·
In a world where there's only a few primitive types no one can share uuids or dates across the wire without both sides knowing which fields are dates or uuids a
by slifin 6y ago
In a world where there's only a few primitive types no one can share uuids or dates across the wire without both sides knowing which fields are dates or uuids ahead of time
JSON is too simple we need more primitive types and an extensible data notation to formalise data sharing of unknown types
- viraptor 6y agoThat's one way to go, but there are other options. You want inline annotation of types. On the other side you can have an external jsonschema which provides the same information. Realistically, you can't do "data sharing of unknown types" - at that point you're just sharing binary blobs.
- goatinaboat 6y agoRealistically, you can't do "data sharing of unknown types" - at that point you're just sharing binary blobs. ASN.1 and CORBA both let you share types that are unknown ahead of receiving.
- viraptor 6y agoI don't know much corba, but in asn.1 it's basically "a field tag and a binary blob". It could be also a standard structure tagged with an unknown id, but either way I don't really see it as much more than json `{"uid": "blob-data"}` in practice. If it's unknown data, you can do almost nothing with it apart from passing it on. If I recall correctly, x509 doesn't even want to deal with any complicated tagging and embeds each extension value as a serialised DER itself.
- kstenerud 6y agoI had the same complaints, thus https://concise-encoding.org/ https://concise-encoding.org/