> This is another example of the approach to be as specific as possible. The > exclude statement can be used to exclude specific archetypes and the Include > ALL in this case means that all others are allowed. If the Exclude ALL > statement is added to an archetype, it means ONLY those specifically stated > can be added.
Sam, without putting words in Adams mouth, I think he was asking about the precedence of include/exclude sections. It is a common problem is coming up with rule system like this - for instance one can look at the allow/deny pattern of the apache2.conf file for how to setup IP address ranges. In the apache case, there is an explicit clause that allows the order to be changed - either allow first then deny, or deny first then allow. In the ADL spec, this is mentioned as a "yet to be defined" (section 5.3.8). Andrew
