Re: [netmod] attributes in draft-lhotka-netmod-yang-json

On 20 Mar 2014, at 15:04, Martin Bjorklund <mbj@tail-f.com> wrote:

> Dean Bogdanovic <deanb@juniper.net> wrote:
>> Hi, 
>> 
>> In draft yang leaf node is defined as name value pair in json
>> 
>> If it would be represented, as an object then we can assign attributes to it.
>> 
>> Example
>> "host-name" {
>>   "data" : "router",
>> 	"attributes" : { "protect" : protect}
>> }
>> 
>> We need attributes for several things, so lets try to figure out how to enable
>> them.
> 
> I agree that the lack of attributes is a problem with the JSON
> mapping.

YANG doesn’t model XML attributes, so attributes are out of scope for the mapping. I’d be happy to provide decent place for attributes, but I don’t like Dean’s proposal - it just makes JSON text terribly messy.

> 
> The problem with your solution is that it adds noise to the normal
> case where there are no attributes.  We're using another encoding:
> 
>   "host-name": "router",
>   "@host-name": {
>       "protect": "protect",
>       ...
>    }
> 
> Yep, not very elegant…

But still much much better. As you say, it spoils only places where attributes are really needed. I am inclined to include this kind of attribute mapping in the draft, if we can reach a rough consensus on it.

Lada

> 
> 
> /martin
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

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