Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Avalon Developers List" <dev@avalon.apache.org>
Message-ID: <3E7F7F18.4070805@apache.org>
Date: Mon, 24 Mar 2003 16:56:40 -0500
From: Berin Loritsch <bloritsch@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.2.1) Gecko/20021130
MIME-Version: 1.0
To: dev@avalon.apache.org
Subject: Resolution: Avalon metainformation tags
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Fortress uses some tags in a non-standard way, and it adds one that is
not in existence.  Peter objects to poluting the Avalon namespace--I
agree on differing contracts for @avalon.component and @avalon.service;
however, we have a disagreement on @avalon.lifestyle.

I like Peter Royal's suggestion, so I propose the following:

1) Fortress gets in line with @avalon.component and @avalon.service
2) We introduce an @avalon-ext namespace for extensions we are wanting
    to experiment with that are not supposed to be container specific.
    In this case the first addition is the @avalon-ext.lifecycle.

I think this is the best compromise, and it will allow us to have
an "incubation" period for new tags.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org