Re: [Json] serializing sequences of JSON values

[Matt Miller <[e-mail]>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 3/13/14, 3:23 PM, Larry Masinter wrote:
> I wonder if there is any lesson from XMPP--  which wanted
> sequence-of-XML-values in an indefinite length stream -- that would
> apply to JSON. What would XMPP look like if it were redone in JSON
> instead of XML?
> 

/me exchanges JSON chair hat for XMPP enthusiast hat ...

If XMPP didn't exist and we instead did JMPP, it might be a series of
discrete objects.  However, the direction of the later "XMPP over <x>"
adaptations (e.g., [BOSH] and [XMPP-WS]) speak toward wanting to use
an existing transport that provides block-oriented framing around
complete structures.

Dealing with partial XML-like structures in XMPP has ranged from
inconvenient to impractical because the vast majority of existing XML
software has assumed a whole XML document when parsing starts.  There
are few libraries that truly allow one to feed XML in fits and starts
and get timely output without some amount of modification or
preprocessing.  When the XMPP community took efforts to apply XMPP
over other transports, the direction has so far leaned toward the
whole documents that most implementations expect; even though the
preprocessing required is rather small, the ability to re-use existing
implementations without first considering oft-unpublished details was
a very powerful motivator.


> If there a tendency to standardize on JSON as a replacement to XML
> in protocols, then would providing guidelines for how to do so be
> in scope?
> 
> 
>> 

/me continues with no hat whatsoever

I think there is value in a guidelines document similar to BCP 79 --
particularly a "don't use JSON for <y>" part.  I'm somewhat
unconcerned on how that is done -- whether that means I-JSON morphs
into that or it is its own separate thing.


- -- 
- - m&m

Matt Miller < [e-mail] >
Cisco Systems, Inc.

[BOSH] "XEP-0124: Bidirectional-streams Over Synchronous HTTP (BOSH)"
< http://xmpp.org/extensions/xep-0124.html >
[XMPP-WS] "An XMPP Sub-protocol for WebSocket" <
https://datatracker.ietf.org/doc/draft-ietf-xmpp-websocket/ >
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - https://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJTIi/8AAoJEDWi+S0W7cO1VHYIAITNDfwKhROU4cafb1y/2FqG
ZBCopL+hhZQ6PtFExRrnMji7bkwjhLRoDBwC1Md+JLq4mRlPMUFtyNO3Ew6x8ZvH
YjiZXQ753+jea9VHnNS1kz3+MXNhz2U2kpVUOn1Cn97BYW3GEdixks7YM7nxc2kA
GKGKomxQwMF67ghfFZLXl+n2ga7aDPqTvdD4gQc/pmVUnzOInu33dr/xfQL5V5ai
B/QYPIyI7UO8wRbuy0uDChW16/+ZE96RD69Zf1/NOEw4V+ZfsZciWVm3bJk1Gl3t
ZuHE0u+HLfbfbJT/IB359RuUnRs3342kePuvYd0nMCnmJ8+V0Z/eDNzY9+nZ4iI=
=Fv5M
-----END PGP SIGNATURE-----