Re: [xml-dev] XML -- information architect, JSON -- program objects,HTML

[Ihe Onwuka <ihe.onwuka@gmail.com>]

On Mon, Nov 18, 2013 at 5:14 AM, Ihe Onwuka <ihe.onwuka@gmail.com> wrote:
> On Sat, Nov 16, 2013 at 10:32 AM, Costello, Roger L. <costello@mitre.org> wrote:
>> Hi Folks,
>>
>> The words below from Liam Quinn deserve to be in the xml-dev Hall of Fame. Brilliant insights Liam!
>>
>> ----------------------------------------------------------
>> On November 15, 2013 Liam Quinn wrote
>> ----------------------------------------------------------
>>
>> XQuery is so interesting because it straddles all the worlds. Where the XML DOM takes the programmer-unfriendly aspects of XML and forces the programmer to deal with them, XQuery hides many of them.
>>
>> But for now at least yes, many programmers have good reasons to dislike XML, and it helps all of us in the XML world to understand these reasons.
>>
>
> Dislike XML and anything related to XML
>
> http://www.reddit.com/r/programming/comments/1152ur/jsoniq_the_json_query_language/
>
> Some excerpts
>
> http://www.reddit.com/r/programming/comments/1152ur/jsoniq_the_json_query_language/c6jii08
>
> http://www.reddit.com/r/programming/comments/1152ur/jsoniq_the_json_query_language/c6k1pdu
>

I was almost able to work that into something catchy like.

"The JSON communities attitude can be summed up as Blairite. Tough on
XML and tough on the causes of XML".

Consequently their tools seem to be mostly whatever you can find in
personal github repositories and are often targeted at one particular
programming environment.

Does anybody know if a translation from an XML based schema to JSON
schema would be semantically lossless.  I appreciate that even if it
were at the moment it might be a bit much to expect the maintainers of
JSON schema to consider that a property  worth preserving, but it
would be useful if somebody definitively knew this.