Aristotle, I'm not 100% happy with it yet so it may change at least one more time. But I did want to get this out and in front of y'all to get initial reactions.
I'll go ahead and make the ref attribute optional. Regarding the ref vs. href, issue, I really want to discourage client implementors from using the thr:replies as a link to the comment feed. Having and href attribute in there is inviting headaches. Suggestions on possible ways of wording the spec / attribute naming / etc would be greatly appreciated. - James A. Pagaltzis wrote: > * James M Snell <[EMAIL PROTECTED]> [2006-05-02 07:15]: >> As you can see from the example, the thr:replies/@ref attribute >> points to an atom:id value, and not the URI used by the link. > > So fetching and parsing all relevant links is the only way to > know which `thr:replies` element applies to which link, and no > way to indicate a global reply count is available? > > Regards,
