intertwingly

Matt Croydon: Translating that into an XML-RPC call hurts my head. That's because the MetaWeblog API doesn't specify how to deal with required attributes.  Or with namespaces.  Or with nested XML elements...  Of couse, one could one by one address these items, and in the process reinvent XML.

For reference, here again is a RESTLog post for this item.  Now here it is in XML RPC, with the troublesome attribute included as a comment.  Finally, here a hypothetical SOAP version, with the blogger API defined control parameters passed as a SOAP header.

IMHO, if one can find a way to work with transfer level authentication and authorization, one should.  If application level control information is required, then an alternate header mechanism may be appropriate.  And this need not totally be an either/or situation.  One can use transfer level authentication and authorization with SOAP.  Ideally, the blogid would not be a parameter, but would be included in the URI.  Things like that.

And, again, the offer is open: if consensus were reached around a weblog post API which either wrapped or subsetted (or both) RSS 2.0, I would work with others to provide the validator.

Update: The XML RPC example has been updated based on the instructions in the MetaWeblog API specification.

Update: An RFC has been issued which provides different guidance as to how the text of the source element is to be passed.