Re:Schemastore.org – schemas for all commonly known JSON fil...
by willtim on Thursday July 30, 2020 @08:36AM
(#23997356)
> Pretending it doesn't exist would cause more trouble in the real world than letting it be
I don't agree at all with this point. RDBMS types for example are non-nullable by default. Protobufs, XML and many other exchange formats also have optional types but not null added to every type. If you want better interoperability with programming languages, I think it would be better to go after e.g. IEE754 support.
Re:Schemastore.org – schemas for all commonly known JSON fil...
by kstenerud on Thursday July 30, 2020 @08:59AM
(#23997579)
The default nullability of RDBMS types is implementation-specific. Protobufs requires a lot of ugly workarounds for languages such as Java to handle the language's nullable types. You can't eliminate the complexity; only move it, and protobufs moved it in a way that punishes languages with nullable types. XML at least works via omission, but that doesn't handle the case of explicitly signalling "no data", which is a valid signal in many languages.
Concise Encoding does support IEEE754.
Re:Schemastore.org – schemas for all commonly known JSON fil...
by willtim on Saturday August 01, 2020 @02:56AM
(#24018293)
> You can't eliminate the complexity; only move it,
Yes and by using null-in-every type for your messaging, now you've pushed the problem out of your app and published it to the world.
The string-type prefixing is there so that you don't actually need a schema for 80% of use cases (schemaless data is usually enough). A schema can be added later if desired, and I've been thinking of what that might look like, but it's at a different level than the encoding format and can be developed independently.
The primary purpose of this format is to serve the 80% use case (general purpose, ad-hoc, hierarchical, schemaless data with fundamental type support - or something that easily fits within this paradigm). For the remaining more complicated 20%, there are custom types and at some point in the future, schemas.