JSONx sent to the IETF
John Boyer <[email protected]> Tue, 3 May 2011 11:58:18 -0700
| Newsgroups | gmane.comp.web.xforms |
|---|---|
| Message-ID | <OFD93CC483.6176F062-ON88257885.0066EEEC-88257885.006836E1@ca.ibm.com> |
This is a multipart message in MIME format.
--=_alternative 0068367E88257885_=
Content-Type: text/plain; charset="US-ASCII"
Hi Everyone,
Further to our thread on JSON here:
[1] http://www.w3.org/MarkUp/Forms/wiki/Json
I've recently learned of an IBM submission to IETF here:
http://datatracker.ietf.org/doc/draft-rsalz-jsonx/
Further info:
https://www.ibm.com/developerworks/mydeveloperworks/blogs/soma/entry/jsonx_threat_or_menace23?lang=en
FYI, I don't happen to be involved in this effort in any way.
I would recommend that the group consider this submission and comment on
it.
You will notice that it seems to take the approach of perfect encoding at
the expense of easy readability, both of markup and of xpath references
thereto. For example, the following appears in the IETF draft:
{ "Ticker" : "IBM" }
<json:object>
<json:string name="Ticker">IBM</json:string>
</json:object>
This would mean it would be necessary to reference this using
"json:string[@name='Ticker']" in our usual XPaths, which take the root
element node for granted.
In my view, the approach in the above mentioned wiki page [1] should be
suggested as an important alternative that enables XML-based processing to
operate more succinctly over the data. The above example would be encoded
as
<json>
<Ticker>IBM</Ticker>
</json>
Which yields the much more respectable reference "Ticker" in our usual
XPaths, which take the root element for granted. Even when using absolute
references, we get "/json/Ticker".
Granted this approach is not 100% achievable on all JSON, but [1] also
clarifies what to do with JSON names that are not XML, and the result is
still far more intelligible and achieves coverage of the edge cases while
not polluting the usual cases with unnecessary and confusing use of both
structure and namespacing.
John M. Boyer, Ph.D.
Distinguished Engineer, IBM Forms and Smarter Web Applications
IBM Canada Software Lab, Victoria
E-Mail: [email protected]
Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
Blog RSS feed:
http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw
----- Forwarded by John Boyer/CanWest/IBM on 05/03/2011 11:44 AM -----
From: Richard Salz/Cambridge/IBM@IBMUS
To: XMLStds
Date: 05/03/2011 09:22 AM
Subject: Fw: JSONx sent to the IETF
FYI.
--
STSM, WebSphere Appliance Architect
https://www.ibm.com/developerworks/mydeveloperworks/blogs/soma/
----- Forwarded by Richard Salz/Cambridge/IBM on 05/03/2011 12:22 PM -----
From: Richard Salz/Cambridge/IBM
To: [email protected]
Date: 05/03/2011 11:51 AM
Subject: JSONx sent to the IETF
We've published JSONx, the XML/JSON mapping some IBM products use, as an
IETF draft. Some rationale, pointers to other discussion, etc., can be
found in the following (shameless self-promotion :) link:
https://www.ibm.com/developerworks/mydeveloperworks/blogs/soma/entry/jsonx_threat_or_menace23?lang=en
Or just cut straight to the draft:
http://datatracker.ietf.org/doc/draft-rsalz-jsonx/
If there are things we can do to encourage its adoption and use, please
post or comment. Hope you find it useful.
Thanks.
/r$
--
STSM, WebSphere Appliance Architect
https://www.ibm.com/developerworks/mydeveloperworks/blogs/soma/
--=_alternative 0068367E88257885_=
Content-Type: text/html; charset="US-ASCII"
<font size=2 face="sans-serif">Hi Everyone,</font>
<br>
<br><font size=2 face="sans-serif">Further to our thread on JSON here:</font>
<br><font size=2 face="sans-serif">[1] </font><a href=http://www.w3.org/MarkUp/Forms/wiki/Json><font size=2 face="sans-serif">http://www.w3.org/MarkUp/Forms/wiki/Json</font></a>
<br>
<br><font size=2 face="sans-serif">I've recently learned of an IBM submission
to IETF here:</font>
<br><a href="http://datatracker.ietf.org/doc/draft-rsalz-jsonx/"><font size=2 face="sans-serif">http://datatracker.ietf.org/doc/draft-rsalz-jsonx/</font></a>
<br>
<br><font size=2 face="sans-serif">Further info:</font>
<br><a href="https://www.ibm.com/developerworks/mydeveloperworks/blogs/soma/entry/jsonx_threat_or_menace23?lang=en"><font size=2 face="sans-serif">https://www.ibm.com/developerworks/mydeveloperworks/blogs/soma/entry/jsonx_threat_or_menace23?lang=en</font></a>
<br>
<br><font size=2 face="sans-serif">FYI, I don't happen to be involved in
this effort in any way.</font>
<br><font size=2 face="sans-serif">I would recommend that the group consider
this submission and comment on it.</font>
<br>
<br><font size=2 face="sans-serif">You will notice that it seems to take
the approach of perfect encoding at the expense of easy readability, both
of markup and of xpath references thereto. For example, the following
appears in the IETF draft:</font>
<br>
<br><font size=2 face="sans-serif">{ "Ticker" : "IBM"
}</font>
<br>
<br><font size=2 face="sans-serif"> <json:object></font>
<br><font size=2 face="sans-serif"> <json:string
name="Ticker">IBM</json:string></font>
<br><font size=2 face="sans-serif"> </json:object></font>
<br>
<br><font size=2 face="sans-serif">This would mean it would be necessary
to reference this using "json:string[@name='Ticker']" in our
usual XPaths, which take the root element node for granted.</font>
<br>
<br><font size=2 face="sans-serif">In my view, the approach in the above
mentioned wiki page [1] should be suggested as an important alternative
that enables XML-based processing to operate more succinctly over the data.
The above example would be encoded as</font>
<br>
<br><font size=2 face="sans-serif"><json></font>
<br><font size=2 face="sans-serif"> <Ticker>IBM</Ticker></font>
<br><font size=2 face="sans-serif"></json></font>
<br>
<br><font size=2 face="sans-serif">Which yields the much more respectable
reference "Ticker" in our usual XPaths, which take the root element
for granted. Even when using absolute references, we get "/json/Ticker".
</font>
<br>
<br><font size=2 face="sans-serif">Granted this approach is not 100% achievable
on all JSON, but [1] also clarifies what to do with JSON names that are
not XML, and the result is still far more intelligible and achieves coverage
of the edge cases while not polluting the usual cases with unnecessary
and confusing use of both structure and namespacing. </font>
<br>
<br><font size=2 face="sans-serif">John M. Boyer, Ph.D.<br>
Distinguished Engineer, IBM Forms and Smarter Web Applications<br>
IBM Canada Software Lab, Victoria<br>
E-Mail: [email protected] <br>
<br>
Blog: </font><a href=http://www.ibm.com/developerworks/blogs/page/JohnBoyer><font size=2 face="sans-serif">http://www.ibm.com/developerworks/blogs/page/JohnBoyer</font></a><font size=2 face="sans-serif"><br>
Blog RSS feed: </font><a href="http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw"><font size=2 face="sans-serif">http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw</font></a><font size=2 face="sans-serif"><br>
<br>
</font>
<br><font size=1 color=#800080 face="sans-serif">----- Forwarded by John
Boyer/CanWest/IBM on 05/03/2011 11:44 AM -----</font>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Richard Salz/Cambridge/IBM@IBMUS</font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">XMLStds</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">05/03/2011 09:22 AM</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Fw: JSONx sent
to the IETF</font>
<br>
<hr noshade>
<br>
<br><font size=2 face="sans-serif">FYI.</font>
<br><font size=2 face="sans-serif">--<br>
STSM, WebSphere Appliance Architect<br>
</font><a href=https://www.ibm.com/developerworks/mydeveloperworks/blogs/soma/><font size=2 face="sans-serif">https://www.ibm.com/developerworks/mydeveloperworks/blogs/soma/</font></a><font size=2 face="sans-serif"><br>
</font>
<br><font size=1 color=#800080 face="sans-serif">----- Forwarded by Richard
Salz/Cambridge/IBM on 05/03/2011 12:22 PM -----</font>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Richard Salz/Cambridge/IBM</font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">[email protected]</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">05/03/2011 11:51 AM</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">JSONx sent to
the IETF</font>
<br>
<hr noshade>
<br>
<br><font size=2 face="sans-serif">We've published JSONx, the XML/JSON
mapping some IBM products use, as an IETF draft. Some rationale, pointers
to other discussion, etc., can be found in the following (shameless self-promotion
:) link:</font>
<br><font size=2 face="sans-serif"> </font><a href="https://www.ibm.com/developerworks/mydeveloperworks/blogs/soma/entry/jsonx_threat_or_menace23?lang=en"><font size=2 face="sans-serif">https://www.ibm.com/developerworks/mydeveloperworks/blogs/soma/entry/jsonx_threat_or_menace23?lang=en</font></a>
<br>
<br><font size=2 face="sans-serif">Or just cut straight to the draft:</font>
<br><font size=2 face="sans-serif"> </font><a href="http://datatracker.ietf.org/doc/draft-rsalz-jsonx/"><font size=2 face="sans-serif">http://datatracker.ietf.org/doc/draft-rsalz-jsonx/</font></a>
<br>
<br><font size=2 face="sans-serif">If there are things we can do to encourage
its adoption and use, please post or comment. Hope you find it useful.</font>
<br>
<br><font size=2 face="sans-serif">Thanks.</font>
<br>
<br><font size=2 face="sans-serif"> /r$</font>
<br>
<br><font size=2 face="sans-serif">--<br>
STSM, WebSphere Appliance Architect<br>
</font><a href=https://www.ibm.com/developerworks/mydeveloperworks/blogs/soma/><font size=2 face="sans-serif">https://www.ibm.com/developerworks/mydeveloperworks/blogs/soma/</font></a><font size=2 face="sans-serif"><br>
</font>
--=_alternative 0068367E88257885_=--