4 ms·
The main reason that I use XML (occasionally) is because of XML Schema. It's a very precise data description that can be semantically verified. Otherwise, I tr
by ChrisMarshallNY 7y ago
The main reason that I use XML (occasionally) is because of XML Schema. It's a very precise data description that can be semantically verified.
Otherwise, I try to use JSON, where possible, because I am not a masochist.
- arethuza 7y agoJSON Schema is pretty useful and is well supported by tools like VS Code
- laggan 7y agoI actually found JSON Schema to be FAR FAR FAR easier to use than XML Schema. https://json-schema.org/ https://json-schema.org/
- ChrisMarshallNY 7y agoYou are correct. I LOATHE XML Schema. I have used it for years, and have never memorized it. I still need to look it up like a n00b, every time I use it. But the simple fact of the matter is, is that so many people and projects have inculcated it into hundreds (if not thousands) of toolsets and specs (Like -Ick- WSDL), that it really is the only viable game. People tend to like JSON precisely because it eschews the kind of overhead that is the definition of XML Schema.
- ChrisMarshallNY 7y agoHuh. I just realized that JSON Schema is STILL not a published spec. It is currently in draft, and has been, for a long time.
- halfdan 7y agoDoes https://json-schema.org/ https://json-schema.org/ not work for you?
- sacado2 7y agoI don't know JSON schema really well; Can you say you want a `price` value to be a non-negative decimal value with at most two digits after the comma, and you want the `currency` value be exactly one of the following : "EUR", "USD", "GBP", the default if not specified being "EUR"?
- itafroma 7y agoYes: { "$schema": "http://json-schema.org/draft-07/schema#", "type": "object", "properties": { "price": { "type": "number", "multipleOf": 0.01, "minimum": 0 }, "currency": { "type": "string", "enum": ["EUR", "USD", "GBP"], "default": "EUR" } } }
- ChrisMarshallNY 7y agoIt would, if anyone used it. The thing about XML Schema, is that it is completely "baked into" pretty much every tool and library out there, so you can do "on-the-fly" runtime validation. JSON is really about minimizing text. It works really well for this. Another issue, is that JSON doesn't have comments, so it can be difficult to annotate a JSON file.