Hi Juergen, On Thu, Oct 2, 2014 at 3:15 AM, Juergen Schoenwaelder < [email protected]> wrote:
> > > I am saying that YANG was designed to model data carried by NETCONF > (check the title of RFC 6020) and NETCONF uses XML as its data > encoding with a set of restrictions that were found useful to simplify > things (all data in XML elements, no mixed content, ...). Several > details of the YANG language are related to XML (e.g., much of the > type system, the usage of xpath in must/when expressions, instance > identifier as a subset of xpath, ...). > > Yes. The binding of YANG as a data description language to XML is clear. > Alternate _encodings_ are proposed (such as JSON) but the question > raised here seems to be whether we want to start an effort to turn > YANG into a schema language for JSON (which it is not today and this > is by design and not by accident). > > Good comment. My personal opinion, JSON is widely used enough to justify this effort. Richard > /js > > -- > 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/> >
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
