This post originated from an RSS feed registered with Python Buzz
by Phillip Pearson.
Original Post: How do you send blog posts with complicated RSS over the metaWeblog API?
Feed Title: Second p0st
Feed URL: http://www.myelin.co.nz/post/rss.xml
Feed Description: Tech notes and web hackery from the guy that brought you bzero, Python Community Server, the Blogging Ecosystem and the Internet Topic Exchange
title, link, guid and
description are all part of the spec. You can put in
other things if you like, as long as you put them in a namespace. Say, if
you want to categorise this item under the Topic Exchange's Software channel, you could say
that this way:
Now, if you want to post something like this to a weblog, what are
your options? Basically, you can use the metaWeblog API or make up
your own one. If you use the existing API, you will be compatible with
many existing blogging tools, and if you make up your own one, you won't.
In Python, the call to post a normal blog post looks like this:
BLOGID, for Radio, is 'home'.
LOGIN and PASSWORD are the values you
configure here.
TITLE, LINK and DESCRIPTION
are the values that show in the title, link
and description elements in the resulting RSS.
If you want to include the ENT classification, it gets a bit
trickier. I think this is how it should work:
I've never seen any code using this, but there are hooks in
Radio (see radio.weblog.metaWeblog.* and weblogData.callbacks.*) for plugins to
handle extra values, so it's likely that someone is using it somewhere.
The spec isn't clear as to whether namespaces have to be re-specified for
attributes (e.g. the ent:href under the
ent:cloud) or sub-elements (e.g. the ent:topic
under the ent:cloud), so this looks a little weird.
Does anybody know of any real-life examples of this sort of thing?
I'd be very interested to hear from you, as I'm not at all sure if I got the
above example correct.