The concept of target-group seems confusing for the moment. I would like to try to prpopose an other view to see if it bring more concensus.
Instead of having one special type of target to define a new concept, maybe we need 2 : target-group and target-part. With the caracteristics that : * target-group and target-part can both have depends to any target. * target-part can declare that they are part of 1 or more target-group. * target-group have no content (not sure that's require for the view that we want). At execution, everything behave like if the content of the target-part were executed inside that target-groups (possible multiple time if the part is part of multiple group). The depends of the part being transfered to the group. I think this view support the high granularity build, with a clear layering without conflicting with the current depends relationships. -- Gilles Scokart --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
