Peter Donald wrote:
> On Sat, 14 Dec 2002 03:31, Leo Sutic wrote:
> > When a component specifies:
> >
> > <entry key="avalon:work" type="java.io.File"/>
>
> Shouldn't that just be
>
> <entry intent="avalon:work" type="java.io.File"/>
>
> and you only specify key if it differs from the intent.
It doesn't matter for the proposal, but the idea is that since avalon:work
is global, it made more sense to specify that as a key, and then map it
into the component's namespace via an alias="" parameter.
The Metainfo and DTD issues are coming up - so we can have a good go at all
that then.
/LS
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
- [Avalon4:PROPOSAL] Context Consensus (version 5) Leo Sutic
- Re: [Avalon4:PROPOSAL] Context Consensus (version 5... Stephen McConnell
- RE: [Avalon4:PROPOSAL] Context Consensus (versi... Berin Loritsch
- RE: [Avalon4:PROPOSAL] Context Consensus (v... Leo Sutic
- RE: [Avalon4:PROPOSAL] Context Consensu... Leo Sutic
- Re: [Avalon4:PROPOSAL] Context Con... Stephen McConnell
- RE: [Avalon4:PROPOSAL] Context... Leo Sutic
- Re: [Avalon4:PROPOSAL] Context Consensus (version 5... Peter Donald
- Re: [Avalon4:PROPOSAL] Context Consensus (version 5... Leo Sutic
- Re: [Avalon4:PROPOSAL] Context Consensus (versi... Peter Donald
- Re: [Avalon4:PROPOSAL] Context Consensus (version 5... Leo Sutic
