Berin Loritsch wrote:
I would tend to agree - after reading through RFC 2141 my initial reaction was to cosider the domain compoent as "apache:avalon:...", however, it is also valid to say that we are dealing with things that are relative to the Context interface which is implicitly "avalon" as root. As such your suggestion is completely valid.From: Stephen McConnell [mailto:[EMAIL PROTECTED]]
Noel J. Bergman wrote:
However, if Avalon is going to adopt a <domain> ":" <key>notion, then I
suggest that Avalon vote to adopt RFC 2141, and incorporateit by reference.
Incorporating RFC 2141 will save you from having to gothrough all of the
arguments already dealt with during the production of theRFC, and provides
more detailed and specific information necessary for usersand implementers.
Applying RFC 2141 is fine from my point of view. As such I need to
update the examples I provided earlier to reflect marlin and phoenix
as sub domains of the Avalon domain.
Wouldn't it be fine to have "avalon:" as the root? Like this: avalon:home.work avalon:merlin:something-special.whatever avalon:phoenix:something-solid.xxx Why make the string longer than it needs to be?
Cheers, Steve.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- Stephen J. McConnell OSM SARL digital products for a global economy mailto:[EMAIL PROTECTED] http://www.osm.net -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>