On Wed, Jun 10, 2015 at 03:04:58PM +0200, Martin Bjorklund wrote:
> Juergen Schoenwaelder <j.schoenwael...@jacobs-university.de> wrote:
> > On Wed, Jun 10, 2015 at 09:05:07AM +0200, Ladislav Lhotka wrote:
> > >
> > > It is also important for the JSON encoding - it means there won’t
> > necessarily be a way for mapping XML-encoded instance to JSON and
> > vice versa.
> > >
> >
> > Because of two different namespace identifiers. So here we go.
>
> There are other reasons as well, e.g., <foo>42</foo> might be encoded
> as:
>
> "foo": 42
>
> or
>
> "foo": "42"
>
> or
>
> "foo": [42]
>
> or
>
> "foo": ["42"]
>
> depending on the data model.
>
> The JSON encoding process needs the data model.
Unless the receiver can be expected to do conversion as needed. (I
know Lada does not like that, no need to tell me again.)
/js
PS: Looking at large numbers and small numbers, the receiver may have
to be prepared to do some conversion anyway.
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <http://www.jacobs-university.de/>
_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
