intertwingly

Dare Obasanjo: I'll definitely add support to Joe's CommentAPI to RSS Bandit but I doubt I'll be doing the same for Sam's alternative SOAP version since I can't see any motivation for supporting both besides buzzword compliance.

At the cost of optionally supporting an SOAP envelope and responding in kind, I get better and easier integration with tools and languages like Radio and C#.  If two elements and future extensibility is too heavyweight for you, then no problem.  That's what optional means.

As to your uncertainty about which version of XHTML is meant by <xhtml:body>, wouldn't the same concern (and more) apply to <content:encoded>?

My weblog now validates as XHTML strict, and my implementation of the Comment API will now produce and consume XHTML bodies.

Users of back-level browsers may find that the comment form doesn't remember you any more.  If this function is important to you, you will need to find a browser that passes this test.

My WSDLs for the comment API (example) simply declare xhtml bodies as mixed sequences of any for now.  Let me know if it would help if this were restricted in some manner.