A. Pagaltzis wrote:
>It worked for David Powell; his
> concerns about technical flaws in the Thread extension convinced
> James to revise the draft, where your vociferous unsubstantiated
> objections had previously failed.
>

Speaking of which, I'm not very happy about it, but I just sent off an
updated version of the Feed thread draft for publication that does away
with the thr;count and thr:when attributes on the link and introduces a
thr:replies element.

The example below appears within the updated draft,

   <feed xmlns="http://www.w3.org/2005/Atom";
       xmlns:thr="http://purl.org/syndication/thread/1.0";>
       <id>tag:example.org,2006</id>
       <title>Entries and Comments</title>
       ...
       <entry>
         <id>tag:example.org,2006:1</id>
         <title>My Post</title>
         <updated>2006-05-01T08:08:08Z</updated>
         <link rel="replies" href="/comments"
           type="application/atom+xml" />
         <thr:replies ref="tag:example.org,2006:comments"
           label="Comments and Trackbacks"
           count="2" updated="2006-05-01T12:12:12Z"/>
         <thr:replies ref="tag:example.org,2006"
           label="Follow-ups and Corrections"
           count="1" updated="2006-05-01T09:09:09Z" />
         ...
       </entry>
       <entry>
         <id>tag:example.org,2006:2</id>
         <title>My Second Post</title>
         <updated>2006-05-01T09:09:09Z</updated>
         <link rel="replies" href="/comments"
           type="application/atom+xml" />
         <thr:replies ref="tag:example.org,2006:comments"
           label="Comments and Trackbacks"
           count="1" updated="2006-05-01T10:10:10Z" />
         <thr:in-reply-to ref="tag:example.org,2006:1" />
         ...
       </entry>
     </feed>

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.  When going
through and trying to implement the original concept with href, the
xml:base issues proved to be more hassle than it was worth.

Look for the updated draft to publish in the next day or so.

- James

Reply via email to