Re: [NGO] external module properties

On Tue, Apr 29, 2008 at 06:43:24PM -0400, Phil Shafer wrote:
> "David Harrington" writes:
> >I think we might need the capability of specifying version in the
> >include statement (if the version dependency is important, but it
> >should be able to be left out when it is not important)
> 
> I keep coming back to this also, for the "import" statement.
> Consider this scenario/timeline:
> 
> - module A defines a cool feature
> - modules B and C import A to use that feature
> - module A gets rev'd to add a new leaf to a grouping
> - module B wants the new leaf
> - module C doesn't want it
> 
> Without revision-specific imports, this scenario is unworkable.
> 
> With revisions, module B would get rev'd to import the new revision
> of A.  Module C would continue to import the previous revision.

Or a user of a grouping has to be explicit what he is using; with
this, even within module A, you can use different subsets of a
grouping defined in A.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
_______________________________________________
NGO mailing list
NGO@ietf.org
https://www.ietf.org/mailman/listinfo/ngo