Re: [netmod] yang-json document

[Ladislav Lhotka <[e-mail]>]

> On 09 Feb 2015, at 13:56, Martin Bjorklund <[e-mail]> wrote:
> 
> Ladislav Lhotka <[e-mail]> wrote:
>> 
>>> On 09 Feb 2015, at 09:59, Andy Bierman <[e-mail]> wrote:
>>> 
>>> On Mon, Feb 9, 2015 at 12:18 AM, Martin Bjorklund <[e-mail]>
>>> wrote:
>>>> Phil Shafer <[e-mail]> wrote:
>>>>> Andy Bierman writes:
>>>>>> Solution Y34-06
>>>>>>  - do not deprecate anyxml
>>>>>>  - do not add anydata (no agreement on rules)
>>>>>>  - implementations MAY restrict the XML accepted in anyxml
>>>>>>     - MAY ignore processing instructions
>>>>>>     - MAY reject mixed mode input
>>>>>>  - document in YANG 1.1 that anyxml is not considered interoperable
>>>>>>    if PIs and mixed mode XML are used
>>>>> 
>>>>> This is essenially "be aware that server implementations might not
>>>>> implement all of YANG".
>>>>> 
>>> 
>>> Isn't this already the case?
>>> Why is it that not all servers fully support anyxml?
>>> 
>>> 
>>>>>>  - The guidelines document should say that YANG Doctors will review
>>>>>>    each use of anyxml in IETF modules
>>>>> 
>>>>> This part I completely agree with.
>>>>> 
>>>>> Here's my proposal:
>>>>> 
>>>>> Solution Y34-07
>>>>> - do not change YANG
>>>>> - Change the JSON encoding rules to encode anyxml nodes as strings
>>>>> - The guidelines document should say that YANG Doctors will review
>>>>>   each use of anyxml in IETF modules (lifted from Y34-06)
>>>> 
>>>> This is fine (*) as one part of the solution, but by itself it isn't
>>>> sufficient.
>>>> 
>>>> The problem is illustrated in YANG PATCH, which is supposed to work
>>>> for both XML and JSON.  If YANG PATCH uses anyxml, it means that the
>>>> JSON encoding of a YANG PATCH is pretty much useless (since the edit
>>>> would be expressed as XML, but the reast in JSON).
>>>> 
>>>> This is why we have suggested to add anydata, which YANG PATCH then
>>>> should use instead of anyxml.
>>>> 
>>> 
>>> 
>>> I strongly object to making YANG Patch YANG 1.1 only.
>>> I would rather drop JSON support.
>> 
>> I think you can continue using anyxml in YANG PATCH, IMO there is
>> nothing wrong with it. If the module gets upgraded to YANG 1.1, the
>> descriptions could perhaps be made shorter, and that’s all.
> 
> I think you're missing the context.  Phil suggested that anyxml should
> be encoded as a string in json, and we're discussing the implications
> of that.  In this context, I do not think that anyxml can be used in
> YANG PATCH - or we do what Andy suggests, drop json support.

OK. Anyway, I am opposed to that encoding of anyxml in JSON. Apart from the problems you mentioned it is also asymmetric: no equivalent is available for JSON.

Lada

> 
> 
> /martin

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