Today I released a new feature for OPML Comments, which is explained with links, on this Scripting News post.
The core feature is of course the new RSS feed for comments.
If you poke around the feeds, you may find some things that raise questions or possibilities.
1. The JSON and JSONP versions.
2. The microblog namespace, which is used by the feed.
3. The roadmap post that shows where we're going.
4. A screen shot of a permalink on comments, a necessary feature for the feed.
5. My personal river, which subscribes to the feed, so it's an easy place to find the latest comments on the threads site (along with news from quite a few other sources).
6. What's next? There's a full CMS behind the comments, with a templating system for designers. Lots of formats and protocols for developers. The only part that's visible is the writing tool. And that's as it should be, because the people we are doing this for are writers and readers.
Please post comments here, either in OPML or Disqus.
This thing is pretty neat
in the vein of feature requests, it would be nice if there was a context menu options to navigate to the post from within the comments workspace. Since we've already got the url I think everything we need is there.
barring having that in the editor itself, I'll try a script to add to the right-click menu....
good to know that comment outline elements in the opml editor do not show up in the comment as a comment (or otherwise)
When I'm looking at the comments workspace and I right-click on the top-level node of a comment outline (the one that represents the post the comment is for, and has the title attribute set to the post's title and the url attribute of the post's address) I would love to see a context menu option called "Go to post" or "Navigate" or something of the sort, that would open the url specified in the url attribute in my system's default browser
Dave: yep, that's exactly what I'm talking about.
comment rendering makes perfect sense, but I didn't know it was a built-in of the type. Good to know.
Cori, I think that feature already exists in a more convenient form.
Follow-up: I see. What you want goes in the other direction. You're looking at a comment and would like to go to the page. I would do that with a View button on the window, to be consistent with other contexts. I've put it on my short to-do list (if it's easy, and I think it is,).
If you click the green OPML button, we check if there already is a comment on that post in the Comments Workspace, and if there is we seek to that instead of creating a new one.
About comments in comments not being rendered, that's a standard feature of the CMS. Unless a type specifically turns it on, comments are not rendered.
An example of a type where you would want comments rendered are code types.
Here's an example of one of those.
Kyle, glad you found the Microblog namespace.
Also I have to get that information to flow through to the comments server.
Still a lot of loose-ends, plumbing-wise. Always are.
Looking good Dave!
Feed looks good.
Comment source OPML file contains attribution which is good.
Is the microblog:source element part of the RSS 2.0 spec?
Thanks for the link Matt!