I thought it might also be so as not to impose a module naming convention
on external organisations?

On Wed, 17 Mar 2021, 18:47 Andy Bierman, <[email protected]> wrote:

>
>
> On Wed, Mar 17, 2021 at 11:36 AM William Lupton <
> [email protected]> wrote:
>
>> Also note that the YANG catalog keys modules by (name, revision,
>> organization).
>>
>
> This 3rd key implies that some organizations have their own versions of
> YANG modules from SDOs.
> We have a bit of that only to fix known Errara in some IETF modules.
> YANG has deviations so vendors can change the modules from other
> organizations
> without hacking the original modules.
>
>
> Andy
>
>
>
>> On Wed, 17 Mar 2021 at 18:21, Andy Bierman <[email protected]> wrote:
>>
>>>
>>>
>>> On Wed, Mar 17, 2021 at 8:36 AM Vladimir Vassilev <
>>> [email protected]> wrote:
>>>
>>>>
>>>> On 16/03/2021 13.36, Vladimir Vassilev wrote:
>>>> > Hei,
>>>> >
>>>> > Many drafts and RFCs are flagged with warnings by the tracker
>>>> > validation tools:
>>>> >
>>>> > ...
>>>> > yanglint SO 1.6.7: yanglint --verbose -p {tmplib} -p {rfclib} -p
>>>> > {draftlib} -p {ianalib} -p {cataloglib} {model} -i:
>>>> > warn: Module's revisions are not unique (2018-06-28).
>>>> >
>>>> > ...
>>>> >
>>>> > Does anyone know what causes this warning?
>>>>
>>>> Seems the warning is issued when [email protected] is
>>>> processed. It contains 2 revision (history) statements with identical
>>>> dates 2018-06-28.
>>>>
>>>> IMO Multiple revision statements with the same date are valid so the
>>>> tool reporting the warning has to be fixed.
>>>>
>>>>
>>>
>>> I disagree.  Our compiler has a similar warning.
>>>
>>> The YANG Library treats entries with the exact same module name and
>>> revision-date as
>>> the same module.  The protocols that currently advertise YANG module
>>> capabilities
>>> all use module name and revision-date to identify a unique module
>>> revision.
>>>
>>> A compiler warning simply means "Are you sure you meant to do this?"
>>> This is usually a cut-and-paste error.
>>>
>>>
>>>
>>>>
>>>> Vladimir
>>>>
>>>>
>>> Andy
>>>
>>>
>>>> _______________________________________________
>>>> netmod mailing list
>>>> [email protected]
>>>> https://www.ietf.org/mailman/listinfo/netmod
>>>>
>>> _______________________________________________
>>> netmod mailing list
>>> [email protected]
>>> https://www.ietf.org/mailman/listinfo/netmod
>>>
>>
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod

Reply via email to