Ok, so how's this (not word-for-word as I would write it in the spec,
but you should get the idea)
The ref attribute MUST be an absolute URI that matches a the resolved
href URI of a replies link character-for-character (case sensitive)
In other words;
<link rel="replies" href="comments.xml"
xml:base="http://example.org/foo"; />
<thr:replies ref="http://example.org/comments.xml"; ... />
- James
A. Pagaltzis wrote:
> Hi David,
>
> * David Powell <[EMAIL PROTECTED]> [2006-05-03 01:15]:
>> I don't think you should do URI normalisation. The ref is being
>> used as an identifier, you don't do protocol level
>> normalisation on namespace URIs or Atom ids why do it here?
>
> That’s a good point; though there’s a slight difference as
> namespace URIs must be absolute in the first place.
>
> The `href` isn’t necessarily unique, now that I think about it,
> if you play games with `xml:base`:
>
> <link href="comments.xml" rel="replies" />
> <link href="comments.xml" rel="replies" xml:base="./foo/" />
>
> Of course, it’s entirely reasonable to declare this madness and
> refuse to support it.
>
> Maybe we need something like _A Plea for Sanity_ that Joe English
> wrote about namespaces, for xml:base.
>
>> The draft should specify character-by-character comparison of
>> the resolved URI's.
>
> Yeah, probably.
>
> Regards,
