Re: [xml-dev] Michael Kay: simple designs make easy things easier,diffic

[Bob Jolliffe <bobjolliffe@gmail.com>]

I am working with a relatively simple interoperability scenario where I must consume health facilities from a health facility registry api (which churns out json), transform them into a different format and post them through to the api of another system.

What makes this irritating is that I have to maintain a model of the health facility registry object which I have to unmarshall the json to, in order to transform it.  I don't want these objects and I don't want to be unmarshalling anything.  Thats extra code to maintain so, as ever, the simplicity catches up with you.  I just want to transform the representation.  With an xml source I have one xslt to maintain.  With json I have both the code to unmarshall plus the code to transform. 

Bob

On 12 November 2013 14:16, Costello, Roger L. <costello@mitre.org> wrote:

I'll accept that JSON is a simple data design that makes easy programming tasks easier.

Would you give a concrete example of where JSON makes a difficult programming task more difficult please? And bonus points if you show how a more complex data design (e.g., XML) would not make the programming task more difficult.

And many bonus points if you can show (through some argument or a pointer to some research) how Michael's statement is always true, or at least true most of the time.

/Roger

-----Original Message-----
From: Ihe Onwuka [mailto:ihe.onwuka@gmail.com]
Sent: Tuesday, November 12, 2013 8:47 AM
To: Costello, Roger L.
Cc: xml-dev@lists.xml.org
Subject: Re: [xml-dev] Michael Kay: simple designs make easy things easier, difficult things more difficult

JSON

On Tue, Nov 12, 2013 at 12:36 PM, Costello, Roger L. <costello@mitre.org> wrote:
> Michael Kay wrote:
>
>> I think they made it simple deliberately,
>> knowing full well that when you keep a
>> design simple, you make easy things easier,
>> and difficult things more difficult.
>
> That is a fascinating statement.
>
> I am very interested in seeing concrete examples of a simple design making difficult things more difficult.
>
> Does anyone have examples of this please?
>
> /Roger
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
> subscribe: xml-dev-subscribe@lists.xml.org
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php