THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- CRUD on weblog entry commentsDon't invent if protocol already exists
- e.g. consider this http://xml.coverpages.org/draft-snell-atompub-feed-thread-12.txt)Build on the Atom Threading Extension, hereinafter referer to as ATE
Issues
- What about entries that do not allow comments or limit time that they are allowed
Design
New comment collection
Currently, these URIs are supported for entries collections:
Code Block |
---|
/roller-services/app/[weblog-handle>/entries Entry collection for a blog /roller-services/app/[weblog-handle]/entries/[offset] Entry collection for a blog, with offset /roller-services/app/[weblog-handle]/entry/[id] Individual entry (i.e. edit URI) |
We will add these URIs for commentscomment collections:
Code Block |
---|
/roller-services/app/[weblog-handle]/entry/[id]/comments Comments collection for entry with id /roller-services/app/[weblog-handle]/entry/[id]/comments/offset Comments collection for entry with id /roller-services/app/[weblog-handle]/entry/[id]/comment/[id] Individual comment |
Entries link relation 'replies' to indicate comment collection
We will use the techniques defined in the ATE for indicating entry to comment relationships. Each entry will include a <link> with relation 'replies' that points to the entry's comment collection.
Code Block |
---|
<entry> <!-- representing a weblog entry -->
...
<link rel="replies" type="application/atom+xml"
href="http://examples.com/roller/roller-services/app/myblog/entry/454/comments" />
</entry>
|
Comments will use <thr:in-reply-to> element to indicate entry
We'll use the ATE's <thr:in-reply-to> element in each comment to point back the the entry which the comment is in-reply-to.
Code Block |
---|
<entry> <!-- representing a comment--> ... <thr:in-reply-to rel="replies" type="application/atom+xml" href="http://examples.com/roller/roller-services/app/myblog/entry/454" /> </entry> |
Comments
Please comment on the Roller dev mailing list.