Re: A standard for XML - JSON mapping.

tom p. <daedulus@btconnect.com> Tue, 02 February 2016 16:42 UTC

Message-ID: <002901d15dd8$39438360$4001a8c0@gateway.2wire.net>
From: "tom p." <daedulus@btconnect.com>
To: Carsten Bormann <cabo@tzi.org>, Julian Reschke <julian.reschke@gmx.de>
References: <CAB=rKNHnJt-zExrfEjSidd1QumP+vuqHwF2S7MCWUgXmJN19hQ@mail.gmail.com> <56AF030F.3090806@gmx.de> <56AF2DC2.20005@tzi.org> <56AF3B9A.1050502@gmx.de>
Subject: Re: A standard for XML - JSON mapping.
Date: Tue, 02 Feb 2016 16:38:54 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 02 Feb 2016 16:42:08.2823 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB1567
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/eprRrIehVgCfT5ccYuYeZeaMmiY>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Feb 2016 16:42:30 -0000

----- Original Message -----
From: "Julian Reschke" <julian.reschke@gmx.de>
To: "Carsten Bormann" <cabo@tzi.org>
Cc: <ietf@ietf.org>
Sent: Monday, February 01, 2016 11:03 AM
> On 2016-02-01 11:04, Carsten Bormann wrote:
> >>
<https://www-01.ibm.com/support/knowledgecenter/SS9H2Y_7.1.0/com.ibm.dp.
doc/json_jsonx.html>?
> >
> > This is for the transport of JSON data in XML documents, not for
> > converting XML data into a JSON representation.
>
> Ack. Good point.
>
> > JSON -> JSONx:
> >
> > { "Ticker" : "IBM" }
> > ->
> > <json:object>
> >    <json:string name="Ticker">IBM</json:string>
> > </json:object>
> >
> > (In any case, I'm wondering if you are citing this because you think
we
> > should be using it or just as a vivid demonstration of how futile
these
> > efforts are...)
>
> I'm not sure about the futile part; AFAIU, there are valid use cases
for
> the above.
>
> But XML->JSON of course is much more complex; if a generic
> transformation is needed the result will be extremely ugly.

I wonder if you are familiar with restconf, which is NETCONF over HTTP
with the YANG data in either XML (which is what NETCONF uses for its RPC
and data therein) or in JSON.  There have been a number of discussions
on how to do in JSON what has previously been done in XML and while
sometimes JSON makes it easier, other times JSON lacks the functionality
that has been used previously; I have followed (but not understood) the
discussions on JSON.  The I-D is currently in WG Last Call so before too
long, it will hit this list, whereupon its ugliness, or prettiness, will
be there for all to see.

Tom Petch

> Best regards, Julian

A standard for XML - JSON mapping. Jeyan Gopalakrishnan
Re: A standard for XML - JSON mapping. Julian Reschke
Re: A standard for XML - JSON mapping. Carsten Bormann
Re: A standard for XML - JSON mapping. Julian Reschke
Re: A standard for XML - JSON mapping. Carsten Bormann
Re: A standard for XML - JSON mapping. Phillip Hallam-Baker
Re: A standard for XML - JSON mapping. tom p.
Re: A standard for XML - JSON mapping. Carsten Bormann