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

[Martin Bjorklund <[e-mail]>]

Andy Bierman <[e-mail]> wrote:
> On Thu, Mar 20, 2014 at 7:04 AM, Martin Bjorklund <[e-mail]> wrote:
> 
> > Dean Bogdanovic <[e-mail]> 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.
> >
> > 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...
> >
> >
> This is how RESTCONF encodes these attributes in a leaf:
> (see sec. 3.4.1)
> 
>    "host-name" : {
>        "@protect" : "protect",
>        "host-name" : "router"
>    }

So this means that RESTCONF does not follow the JSON mapping
document.

If we can avoid that it would be ... good.

> Lada says that this is a YANG to JSON mapping and YANG has no attributes,
> so the attribute encoding is in RESTCONF.  I think it would be better
> if there was 1 mapping, instead of a different mapping in each protocol
> that uses this JSON encoding of YANG data.

+1  I think the JSON mapping document should define how meta data are
encoded, if the protocol supports meta data.

> I do not think YANG needs to model attributes!

+1

> The protocol may need to use them to tag data with meta-data.

Yes.


/martin