[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PaceFeedEquivalence


On Jul 29, 2004, at 1:38 PM, Mark Pilgrim wrote:

(1) a note in both the Format and Protocol specs saying "when testing
URIs for equivalence, implementors should consider the discussion in
RFC2396bis section 6."  (currently
http://gbiv.com/protocols/uri/rev-2002/rfc2396bis.html#comparison).


Note that this is the first time we are actively tying ourselves to
2396bis (as opposed to PaceUriOrItsSuccessor, which only allowed us to
inherit it when it was ready).

Good point... it's just that 2396bis has this useful section 6 that goes on and on about exactly this issue, which isn't in 2396classic at all. On the other hand if we were nearly done, and 2396bis wasn't, I'd be in favor of nuking this section to get us across the finish line.

Furthermore, are you rejecting Norman Walsh's proposal that "matches"
and "matching" be more specifically defined as per Section 6.2.1
"Simple String Comparison" of 2396bis?

Yes. If I have two pointers to feeds:

http://www.example.com:80/feed.atom
http://www.Example.COM/feed.atom

I guarantee that some apps, in particular web spiders, are going to get very aggressive about schema-specific normalization and regard these as equivalent, and I don't see any reason to rule this out. Norm? -Tim