Berin:
Thanks for the update. Concerning the phased voting suggestion. I think this is unnecessary and may easily lead to inconsitency. The "partial" AMTAGS solution to-date has prevented the utility of tags in a multi-container environment. Without a full and complete specification we cannot consider the impact of the specification on either container interoperability or the development overhead that the tags represent.
How about kicking off with any points you want to raise concerning:
@context @logger @configuration @stage @extension
Cheers, Steve.
Berin Loritsch wrote:
I updated the AMTAGS to include the @avalon.component information as we have
discussed it so far, as well as the version attributes for the existing tags.
This is step one of a three step process. The first step is to get the easy
stuff voted in. The second step is to come to agreement on the validation
level tags (@avalon.context, @avalon.logger, @avalon.configuration). The last
step is to come to agreement on the lifecycle extension attributes.
The updated AMTAGS proposal is listed here:
http://nagoya.apache.org/wiki/apachewiki.cgi?AMTAGS
Please review the document and if there are any clarifications to it that we
need to address, please respond. If there are no comments on this set of
tags (@avalon.component, @avalon.dependency, @avalon.service) then I will put
it up for vote.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
Sent via James running under Merlin as an NT service. http://avalon.apache.org/sandbox/merlin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
