Re: [NGO] external module properties

Phil Shafer wrote:
> Andy Bierman writes:
>> The YANG spec is silent on finding the module associated
>> with an import or include.  That doesn't mean a robust,
>> interoperable, standards-based CM system can be silent on the issue.
> 
> This was intentional, in the same manner that the ANSI C spec doesn't
> tell you about /usr/include, /usr/local/include, or the -I flag.
> The language spec should be defining the language and the model of
> operation.  Your tool set will dictate where and how it searches
> for files.
> 
> Heck, my tool set may not even use files.
> 

Fine.
But if module FOO in any NETCONF system imports module X,
and module BAR imports module X, can we say in the YANG spec
that they MUST refer to the same exact module X?

Likewise, if FOO includes FOO-A and FOO-B, and both FOO-A
and FOO-B include FOO-TYPES, are they including the exact same
module (i.e., exact same sequence of YANG language tokens)?

This is a different issue than which particular X or FOO-TYPES is used.

> Thanks,
>  Phil
> 
> 
> 

Andy

_______________________________________________
NGO mailing list
NGO@ietf.org
https://www.ietf.org/mailman/listinfo/ngo