Hi, On Sat, 10 Jan 2004 21:58:00 -0800, Tim Showalter <[EMAIL PROTECTED]> wrote... > Mark Crispin wrote: > > > Am I correct in believing that we have concensus in recommending that, > > giving a hierarchy delimiter of "/", that > > tag LIST a/b c/d > > SHOULD resolve to a/b/c/d or a/c/d, but not a/bc/d? > > Yes, I'd agree. > > I would cheerfully consider counterarguments, but I can't imagine why we > would ever want a/bc/d. > > Tim >
Is there a reason why only a/b/c/d can not be recommended while having a/c/d be possible and a/bc/d be frowned upon? My reasoning is that with the current situation, servers can implement one of three behaviors. With the improvement, servers can implement one of two behaviors. Having two possibilities isn't much different from having three because the client still doesn't know which it will get. Having the trailing delimiter be implied if not present in the reference is more intuitive while chopping off the 'b' is more of an "Oh, I gotcha" case. At least for me anyway. Regards, Mark Keasling <[EMAIL PROTECTED]>
