On Wednesday, July 13, 2011 08:51:24 AM Kevin Smith wrote: > On Tue, Jul 12, 2011 at 2:15 AM, XMPP Extensions Editor <[email protected]> wrote: > > The XMPP Extensions Editor has received a proposal for a new XEP. > > I also asked Simon Tennant to comment, who remarked (reproduced with > permission): > > "I had a look through the commenting spec. There's a whole lot of > business logic in there that will really depend on the application. > They like infinite threads/bc likes one-level-deep... IMHO all we need > to do is specify: "use Atom". Well actually we don't. Everyone already > uses Atom. Sorry - I'd love to support things but this is just a > spec-fest and I don't see it adding much to XMPP."
The commenting proposal addresses the following so-far unaddressed problems: 1) We need an efficient means of displaying existing comments without having to fetch all the comments in a conversation. Livefyre conversations get into the hundreds of comments, and sometimes exceed a thousand. That's not even including "like" activity. Also, RSM by date is not enough if you expect to support nesting. 2) When several users are publishing to the same node, and asserting their own author information to be contained within an Atom payload, we have a spoofing concern. The PubSub node needs to be "smart" then, to be able to natively understand the Atom format and sanitize submissions. 3) Related to 2) and 1), we need a way of caching author information beyond merely the author JID, otherwise the viewing client has to resolve this information. 4) Handling of unsolicited event notifications. This is primarily a solution for mentions. However, it also solves the "atomic post to remote conversation and local user activity" problem. You want to comment somewhere but also have that comment show up on some user profile page of yourself. Do you submit the comment to your profile service, and that service posts it to the conversation? Or, do you submit to the conversation and that service posts it to your profile service? Or, do you submit to both individually? The proposed XEP suggests the second case. This design is based on real-world experience building a federated commenting system. Yes, it is a lot of business rules. If you're hosting comments then you follow these rules. :) Justin
