Re: [Json] Fwd: Blog: YANG Takes Off in the Industry

On 01 Aug 2014, at 14:35, John Cowan <cowan@mercury.ccil.org> wrote:

> Carsten Bormann scripsit:
> 
>> That vacuum is filled by draft-ietf-netmod-yang-json-00.  (Nature
>> abhors vacuum.)
> 
> Neither here nor there: that is merely a JSON expression of the XML.  It

Not really: the XML-JSON translation is schema-driven so that, for instance, XML leaf element text can become a string, numeric or boolean value in JSON depending on the type of that leaf node in the YANG data model. Also, an XML element may be mapped to a JSON name/object or name/array depending on whether it is defined as a container or list in YANG.

So, YANG can and does really act as a domain-specific schema language for both XML and JSON.

Lada

> has nothing to do with modeling JSON.
> 
> Phillip Hallam-Baker scripsit:
> 
>> But you could use it to create a data model that was represented in
>> JSON.
> 
> I haven't read the RFC in any detail, but the model given in 4.2.2 does
> not seem to be a JSON model: it is far more complicated.
> 
>> And that community refuses to make any changes to XML or XML schema to
>> support protocol work.
> 
> Or for any other purpose.  Ghu knows I tried.
> 
>> So XML is a bad choice for protocol design.
> 
> That conclusion I believe to be unwarranted.  The problems with XML are
> mostly the hard-to-use APIs, of which one of the worst is that embedded
> in all browsers.  If anything is carved in stone these days, it is the
> DOM.
> 
> -- 
> John Cowan          http://www.ccil.org/~cowan        cowan@ccil.org
> Yakka foob mog.  Grug pubbawup zink wattoom gazork.  Chumble spuzz.
>    --Calvin, giving Newton's First Law "in his own words"
> 
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json

--
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C