Re: [ogpx] LLSD JSON compatibility

it is compatible with the 'value' non-terminal instead of the
'JSON-text' non-terminal defined in RFC4627. this is because we wanted
to allow a JSON serialized LLSD message to encode non-collections.
(RFC4627 REQUIRES valid JSON-text messages to begin with a '[' or
'{'.)

as described in the draft, valid JSON serialized LLSD messages are a
subset of valid JSON messages since LLSD REQUIRES UTF8. ergo, it is
possible to have a message that is valid under RFC4627 but an invalid
JSON serialized LLSD message.

however, given JavaScript parsing rules, a client which respects the
UTF-8 requirement of LLSD will be able to parse messages described by
the 'value' non-terminal in RFC4627 with the code given in the RFC.

in other words, we allow servers to give us JSON messages that are not
strictly compliant with RFC4627, and like virtually every web browser
in common use, we do not require JSON messages to be collections.

On Thu, Jun 25, 2009 at 12:07 PM, Hurliman, John<john.hurliman@intel.com> wrote:
> In what ways is the JSON that is created when serializing LLSD messages not compatible with RFC 4627?
>
> John
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx
>