Hi, Lou Berger <lber...@labn.net> wrote: > Lada, > Thank you for the response. See below. > > > On February 4, 2016 6:39:11 AM Ladislav Lhotka <lho...@nic.cz> wrote: > > > Hi Lou, > > > > Lou Berger <lber...@labn.net> writes: > > > >> I thought it would be worth summarizing what we're looking for in our > >> draft, draft-rtgyangdt-rtgwg-device-model-02 (note new version in case > >> you missed it) with respect to the draft-lhotka-netmod-ysdl and > >> draft-bjorklund-netmod-structural-mount drafts. This is just my view, > >> so > >> my co-authors may wish to chime in and correct me. > >> > >> I'd be interested in hearing from the authors of YSDL and > >> structural-mount, or anyone else for that matter, on how they see to > >> best meet these needs. > >> > >> Here's what I think our draft needs: > >> > >> 1. that there be a mechanism that allows the incorporation (or > >> 'mounting') of the data model defined by one top-level module > >> within another module. > >> > >> The implication here is that when information is instantiated > >> for the parent model it is also instantiated for the > >> incorporated/mounted model. In our case we expect to do this on > >> list element creation. Both solutions drafts cover the path > >> implications, so these are not repeated here. > > > > Both structural-mount and YSDL satisfy this. > > > > Agree on the 1st paragraph but not the second. I think that like 2, > neither support the second paragraph.
I think that both structural-mount and ysdl satistfy this, in the sense that they support the schema defintion for this use case. The instantiation is something that happens in the implementation. /martin _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
