I've updated the draft of the comments extension. I think this is just about ready to submit as an I-D.
 http://www.snellspace.com/public/draft-snell-atompub-feed-thread-00.txt

The major change is a refactoring of the in-reply-to and replies-source following the extensive discussion here on the list.

 <!-- originalfeed.xml -->
 <feed xmlns="http://www.w3.org/2005/Atom";>
   ...
   <link rel="replies"
         type="application/atom+xml"
         href="http://www.example.com/myotherfeed.xml"; />
   <entry>
     <id>tag:example.com,2005:1</id>
     ...
   </entry>
 </feed>


 <feed xmlns="http://www.w3.org/2005/Atom";>
   ...
   <entry>
     <id>tag:example.com,2005:2</id>
     <in-reply-to
       xmlns="http://purl.org/syndication/thread/1.0/";
       id="tag:example.com,2005:1"
       type="application/atom+xml"
       src="http://www.example.com/originalfeed.xml"; />
   </entry>
   <entry>
     <id>tag:example.com,2005:3</id>
     <in-reply-to
       xmlns="http://purl.org/syndication/thread/1.0/";
       href="http://www.example.com/entries/1.atom";
       type="application/atom+xml" />
   </entry>
 </feed>

The second feed illustrates the two forms of the in-reply-to element. The dereferenceable form uses the href attribute to locate the entity being responded to. The nondereferenceable form uses a combination of a required id attribute and an optional src attribute.

I'll likely go ahead and submit this as an I-D in the morning.

As always, comments welcome.

- James

Reply via email to