Roger B. wrote:
James: Given that this kind of thing is pretty near-n-dear to me, I'm
quite interested. A couple observations and/or thoughts:
(1) I like this much, much better than the proposed ThreadsML mess of
years past. Simple is good.
Absolutely.
(2) Implementation might be a hard sell, so don't get your hopes too
high. wfw:commentRss has been around for years, and RSS Bandit,
Newzcrawler, and (I think) Sharpreader are all on board. But since
more popular feed readers like NetNewsWire and Feeddemon don't support
it, getting individual bloggers to care can be challenging. Which is
kinda silly, since WordPress does per-entry comment feeds out of the
box, but whatcha gonna do?
Evangelism through implementation is all we can do. Whatever mechanism
we choose to go with, I'll likely implement support for it in my
personal blogs WordPress environment and will likely share the code.
(3) The link @rel="in-reply-to" @href="{$original-entry/atom:id}"
construct makes sense to me. Particularly since it doesn't just
duplicate wfw:commentRss, which would be kinda pointless.
Right. The goal is to keep it as simple as commentRss while leveraging
Atom's specific model. The link element is a natural fit for this.
(4) RE: @rel="comments" vs. @rel="related"
I generally feel like more specific is more better, but I can see
arguments both ways.
I definitely agree that more specific is better. In a separate note I
proposed "related-feed" as a possible
more-specific-than-related-but-not-as-specific-as-comments alternative.
Whatcha think? Still not specific enough?
- James
