Re: Resolution: Avalon metainformation tags

[Peter Royal]

On Monday, March 24, 2003, at 05:06  PM, Berin Loritsch wrote:
Peter Donald wrote:
On Tue, 25 Mar 2003 08:56, Berin Loritsch wrote:
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;
Can you describe what you mean by @avalon.service?
A marker tag for the service work interface (as is current).  I
believe that in Pheonix, it is an external reference to the same
thing.
Lets build an example of how we expect the markup to appear....

/**
 * @avalon.service name="my.favorite.service"
 */
public interface MyService
and

/**
 * @avalon.component name="my.favorite.service"
 */
public class MyServiceImpl implements MyService, Serviceable
{
    /**
     * @avalon.dependency name="my.other.favorite.service"
     */
    public void service(){}
}
I would use x- prefix to get inline with other standards bodies. 
Especially given that Merlin uses extensions to refer to something 
else.
Ok,  That's easy enough to do.
+1 to the x-prefix


I think this is the best compromise, and it will allow us to have
an "incubation" period for new tags.
And how does something get out of the x- namespace? And where do you 
expect it to go when it does get out of it?
Comunity consensus.

It goes where the community wants it.
Yup. My view would be that any thing that all containers 
support/recognize would be in @avalon. Items would leave x-avalon when 
either:
 1) All containers support them
 2) The containers that used to support it go away and it dies off.

-pete

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]