Home Login Create account Contact Help
Close

Login to your account

Other Options

John Millikin's BeContrary Profile


John Millikin is chairing the following debate

JSON or XML for structured data serialization

Recent arguments by John Millikin

" After parsing, a JSON data set can be accessed directly within a browser through standard syntax. XML requires use of the DOM for traversal, which is complex enough to have tutorials . " - in JSON or XML for structured data serialization

" JSON does not support any comment syntax. XML has !-- ... --. " - in JSON or XML for structured data serialization

" One way to do it. In XML, it is a choice of the programmer on whether to use attributes or child elements to store associated data. Each has its own advantages and disadvantages (generality v. simplicity). The child element method provides both [...] " - in JSON or XML for structured data serialization

" XML has standard facilities for metadata such as the text encoding and language, and can be serialized in any encoding. JSON relies on encoding autodetection, and therefore may only be serialized to one of the UTF-* encodings. " - in JSON or XML for structured data serialization

" JSON has semantics for data types beyond text, such as numbers, lists, and associative maps. This allows data structures without complex objects to be serialized with very little fuss. Even moderately complex objects may be serialized if they can be [...] " - in JSON or XML for structured data serialization

" XML has superior library support, and there are generally multiple performant and compliant XML (de)serializers for any given language. " - in JSON or XML for structured data serialization

" XML-based templates allow serving valid HTML and XHTML pages from the same template source. Consider the following Genshi template: ?xml version=1.0 encoding=UTF-8? !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.1//EN [...] " - in XML or Text for Python Templates?