How to Avoid Being Called a Bozo When Producing XML (2005)

Re:How to Avoid Being Called a Bozo When Producing XML (2005) by Nuffinatall on Sunday July 31, 2016 @11:28AM (#12197363)

Compared to the problems when dealing with 'delimited text', XML is great.

Also it's flexible where you can specify properties as attributes or child nodes, depending on wildcard specifications.

So I have dealt with lots of edge-case XML situations, but the solutions are always straight forward. Also it helps to have a client vs. trying to parse out raw XML, which means programming and scripting sometimes relies on personal tool development. XML handles scope creep well.

[ Parent | on HN ]

Re:How to Avoid Being Called a Bozo When Producing XML (2005) by DougN7 on Sunday July 31, 2016 @01:00PM (#12197713)

Handling scope creep is my favorite feature. With XML, it's easy to deserialize even if an expected element is not there, or if there is an extra one you're not expecting, at least that's been my experience. I haven't done much JSON but I'm not sure how that would work with it.

[ Parent | on HN ]

Re:How to Avoid Being Called a Bozo When Producing XML (2005) by QuercusMax on Sunday July 31, 2016 @09:48PM (#12199798)

Pretty much any "real" serialization format should handle that situation fine. Protobuf, JSON, YAML, Thrift, heck, even Java serialization can handle that, provided you set a serialVersionUID.

[ Parent | on HN ]

Re:How to Avoid Being Called a Bozo When Producing XML (2005) by beagle3 on Sunday July 31, 2016 @04:33PM (#12198693)

JSON deserialization would basically be the same. XML does not score here.

[ Parent | on HN ]