Re: @avalon

On Saturday, March 22, 2003, at 12:33  PM, Stephen McConnell wrote:
> I would argue that the process would be more constructive if we made 
> the
> assumption that a certain set of tags exist - and from that assumption,
> work on ensuing that the respective interpretation of those tags by
> different tools and resulting meta-info are consistent.

The primary stickler seems to be over the lifestyle tag being in the 
@avalon namespace. I see Pete's argument, only things that *ALL* 
containers support go into the @avalon namespace.

As a compromise, ow about we establish an @avalon-x namespace that 
holds items that, in the future, may be promoted to the @avalon 
namespace?

That way Fortress and Merlin can both use @avalon-x (or @x-avalon) for 
the lifestyle tag, and phoenix would just ignore it. If/when the point 
in time comes that all containers are able to handle such components, 
we could promote the tag to the @avalon namespace.

I see you & Berin's point Stephen, and I see Pete's. Both are valid. I 
think a third strategy might be a proper compromise, and allow us to 
move forward. Maybe Pete will end up being correct, as he was about the 
marker interfaces. Maybe you are correct in that a simple lifestyle tag 
is enough. But if we can't agree on where to put that information 
*today*, we be able to move forward and determine through practical 
experience what will work best.
-pete