Robert Sayre wrote:
> On 5/16/06, James M Snell <[EMAIL PROTECTED]> wrote:
>>
>> At this point, Feed Thread support has been deployed in Friendster,
>> Typepad, and MovableType.
>
> I thought the working group was fairly clear about the dubious value
A few of the individuals on the WG had a problem with the placement of
the attributes due to various limitations of a few existing Atom 1.0
implementations. None of the folks I know of that have actually
implemented support for the extension has had any problems with them.
> and placement of these attributes, and you yourself posted that no one
> was implementing them, they were "strictly informational", and free to
> be ignored. So you don't think they're important or needed, and then
> WG doesn't have consensus on them. Even Tim's comments were in the
> abstract, and not related to feed thread at all.
>
I never posted that no one was implementing the attributes. Quite on the
contrary, you can pull up quite a few TypePad and Friendster feeds that
are using them. You can also look at Sam Ruby's personal blog... or
look at my wordpress and roller blog feeds. The attributes are being used.
What I did say was that I wasn't aware of anyone using multiple replies
links in a single entry and that I personally did not intend on
publishing any feeds that used multiple replies links in a single entry.
>> From a technical perspective, the interactions between multiple links
> with the extension attributes remain unspecified. As a client
> implementor, I suppose I'll find out what exactly they're for whenever
> I see the already-completed implementations deployed. In my opinion,
> the document should do more to inform the community on the role of
> these attributes.
>
The interaction is unspecified because there is no interaction. As I've
said before, the thr:count and thr:when attributes apply only to the
atom:link element to which they belong.
The slash:comments extension element can be used to provide a global
comment count that operates independently of the replies link.
The roles of the attributes are clearly specified in the spec. There
are existing feeds in deployment that demonstrate their use.
.
> On an unrelated note, this document contains sections copied verbatim
> from RFC 4287, and it would be polite and honest to acknowledge that.
>
My apologies, I thought I had already done so. It will be fixed in the
next revision.
- James
