> >we had already been over the best way to format
> > the lookup string back in august
> On formatting, the concensus as I seem to remember was :
> <domain> ":" <key>
I'm slowly digesting the recent volume of discussions, but I just to toss in
an idea on this specific issue.
(1) There is the existing property convention, using the
standard java qualified name convention, e.g.,
org.apache.avalon.<local-name>
(2) Alternatively, there is RFC 2141, which appears to be
the direction you're indicating.
(http://www.ietf.org/rfc/rfc2141.txt)
As I understand it, Avalon has already gone over the choice between the
existing "Java" convention and a <domain> ":" <key> convention, and Stephen
indicates that he believes that the latter was chosen. Fine.
However, if Avalon is going to adopt a <domain> ":" <key> notion, then I
suggest that Avalon vote to adopt RFC 2141, and incorporate it by reference.
Incorporating RFC 2141 will save you from having to go through all of the
arguments already dealt with during the production of the RFC, and provides
more detailed and specific information necessary for users and implementors.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
