Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Error: Mandatory object 'enable' not allowed in external augment statement
ieee802-ethernet-link-oam.yang:1025.11: error(335): mandatory object not allowed
(and several other leafs cited with an error(335)
Hi Mark,
Thanks for the work and help. We will start the next ballot cycle after the September meeting and then open to collect comments to update our modules and draft.
You can comment on the modules at github now (https://github.com/YangModels/yang/tree/master/standard/ieee/802.3/draft ) and I will collect them (including issues and how to resolve them) from github for the group to consider in the next ballot cycle.
Otherwise, you can also provide comments against the modules/draft directly and send your comments to our Editor Marek Hajduczenia (Marek.Hajduczenia@xxxxxxxxxxx) and myself. Both are good.
For the revision date update, even a single “revision” statement, we would have to submit a comment every time to change the dates…
Thank you very much.
Best Regards,
Yan
From: Mark Ellison [mailto:mark@xxxxxxxxxxxxxxxxxxx]
Sent: Friday, August 31, 2018 10:24 PM
To: Zhuangyan (Yan) <zhuangyan.zhuang@xxxxxxxxxx>
Cc: STDS-802-3-YANG@xxxxxxxxxxxxxxxxx
Subject: Re: [802.3_YANG] IEEE 802 compilation report (yang catalog)
Hello Yan,
I am available to work with the group on other warnings as well as module metadata.
Regarding the omission of a "revision" statement- I understand not wanting to have an accumulating number of revision statements for a module in development. Note there is a middle path between all or nothing, the following excerpt appears on page 12 of RFC 6087, "Guidelines for Authors and Reviewers of YANG Data Model Documents":
"It is acceptable to reuse the same revision statement within
unpublished versions (i.e., Internet-Drafts), but the revision date
MUST be updated to a higher value each time the Internet-Draft is re-
posted."
Thus, an alternative would be to maintain a single "revision" sub-statement across iterations of a work-in-progress and just change the revision date each iteration.
Regards,
Mark
On Wed, Aug 29, 2018 at 10:44 PM Zhuangyan (Yan) <zhuangyan.zhuang@xxxxxxxxxx> wrote:
Hi Mark,
Thank you for the email and report.
Regarding the error of missing “revision” sub-statement, we had a discussion in the group and decided to add this revision statements to all modules once the modules are finalized. It avoids adding too much revision statements into modules and comments to these revisions every time.
For the other warnings and metadata, it would be good to work with you to resolve them.
Thank you very much.
Best Regards,
Yan
From: Mark Ellison [mailto:mark@xxxxxxxxxxxxxxxxxxx]
Sent: Thursday, August 30, 2018 3:18 AM
To: STDS-802-3-YANG@xxxxxxxxxxxxxxxxx
Subject: [802.3_YANG] IEEE 802 compilation report (yang catalog)
Hi,
Following up on my action item from our call this morning-
Here is a link to the IEEE compilation report from the YANG Catalog. There are a number of reported errors and warnings, plus a need to add metadata about the modules for the catalog.
http://www.claise.be/IEEEStandardYANGPageCompilation.html
I am happy to work on resolution of these issues.
Regards,
Mark
Mark Ellison
Ellison Software Consulting, Inc.
38 Salem Road
Atkinson, NH 03811, USA
To unsubscribe from the STDS-802-3-YANG list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-YANG&A=1
To unsubscribe from the STDS-802-3-YANG list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-YANG&A=1