On Tue, 2018-06-26 at 15:58 +0200, Balazs Lengyel wrote: > Hello Lada, > I don't insist on using yang-data-ext, but I like it. Isn't this the exact > use case for it: defining yang structured data that will never be loaded into > a datastore. In this case the structure of the instance-data-set fits.
On the other hand, if it's never loaded into a datastore, there is no need to encapsulate the data and break tools that don't support yang-data-ext. The encapsulation is really needed only if such data is mixed with "real" YANG data node definitions in the same module - for example, if error-message schemas are defined along with datastore contents, operations etc. > If I would remove the yd:yang-data instance-data-format statement it would > not affect the actual file content. It just serves as an indication that this > is not a datastore definition. A comment in the module should perfecty suffice. Andy argued with machine readability, but I don't see how it can be useful here. And, after all, if a server implementor for whatever weird reason decides to implement this module, what's wrong on doing so? Lada > regards Balazs > > On 6/15/2018 9:41 AM, Ladislav Lhotka wrote: > > Hi, > > > > I support the adoption of this I-D as a workgroup item and my plan is to > > implement it. > > > > However, my suggestion is to avoid the use of yang-data-ext. It is > > absolutely useless in this case and only complicates things that are > > otherwise pretty trivial. > > > > Lada > > > > Balazs Lengyel <[email protected]> writes: > > > > > Hello, > > > > > > I submitted a new version of the yang-instance-data draft updated with > > > comments from the last > > > IETF and others. I would like to get this adopted as a workgroup item. > > > Please review it and if you > > > like it please indicate that you support it as a workgroup item. > > > > > > Changes: > > > o Redefined using yang-data-ext > > > o Moved meta data into ordinary leafs/leaf-lists > > > o Corrections, clarifications > > > > > > regards Balazs > > > > > > -------- Forwarded Message -------- > > > > > > Subject: New Version Notification for draft-lengyel-netmod-yang- > > > instance-data-01.txt > > > Date: Wed, 13 Jun 2018 06:47:16 -0700 > > > From: [email protected] > > > To: Benoit Claise <[email protected]>, Balazs Lengyel > > > <[email protected]> > > > > > > A new version of I-D, draft-lengyel-netmod-yang-instance-data-01.txt > > > has been successfully submitted by Balazs Lengyel and posted to the > > > IETF repository. > > > > > > Name: draft-lengyel-netmod-yang-instance-data > > > Revision: 01 > > > Title: YANG Instance Data Files and their use for > > > Documenting Server Capabilities > > > Document date: 2018-06-13 > > > Group: Individual Submission > > > Pages: 10 > > > URL: https://www.ietf.org/internet-drafts/draft-lengyel-netmod- > > > yang-instance-data-01.txt > > > Status: https://datatracker.ietf.org/doc/draft-lengyel-netmod-yang > > > -instance-data/ > > > Htmlized: https://tools.ietf.org/html/draft-lengyel-netmod-yang-inst > > > ance-data-01 > > > Htmlized: https://datatracker.ietf.org/doc/html/draft-lengyel-netmod > > > -yang-instance-data > > > Diff: https://www.ietf.org/rfcdiff?url2=draft-lengyel-netmod-yan > > > g-instance-data-01 > > > > > > Abstract: > > > This document specifies a standard file format for YANG instance > > > data, that is data that could be stored in a datastore and whose > > > syntax and semantics is defined by YANG models. Instance data files > > > can be used to provide information that is defined in design time. > > > There is a need to document Server capabilities (which are often > > > specified in design time), which should be done using instance data > > > files. > > > > > > > > > > > > > > > > > > Please note that it may take a couple of minutes from the time of > > > submission > > > until the htmlized version and diff are available at tools.ietf.org. > > > > > > The IETF Secretariat > > > > > > _______________________________________________ > > > netmod mailing list > > > [email protected] > > > https://www.ietf.org/mailman/listinfo/netmod -- Ladislav Lhotka Head, CZ.NIC Labs PGP Key ID: 0xB8F92B08A9F76C67 _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
