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
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.

You don't have to listen to the WG, but if one or two WG members are
going to deploy and then standardize whatever they've done, that's an
informational document.

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.

now is the time to step up and make your case.

You've merely stated you "believe" that moving these attributes back
to the original location is the right decision. That is not a
technical rationale. I would expect to see a more compelling reason,
given the clear, technical rationales of those against your decision.

On an unrelated note, this document contains sections copied verbatim
from RFC 4287, and it would be polite and honest to acknowledge that.

--

Robert Sayre

Reply via email to