bedeviled mojo slop

Litefeeds seems to be in the mobile device aggregator business. Looks like they have an online reader where you can select those that you want to target for your mobile device. Along with that there's a mobile newsreader application. Good deal.

They're running 3 blogs at the moment. General, John Goodall, and Darren Inouye.

I'm sure they can school me on targeting syndication feeds for mobile devices. Thanks for choosing blojsom.

Practice Doctorate - A forum for information related to the AACN position on the Practice Doctorate.

Thanks for choosing blojsom.

Dave Johnson links to some good discussion about uses of the Atom API. Via Dare Obasanjo's post on Build Contentcentric Applications on RSS, Atom, and the Atom API. In particular:

During the break, Marc Canter and I talked about the fact that both the Atom syndication format and Atom publishing protocol are simply not rich enough to support existing blogging tools let alone future advances in blogging technologies. For example, in MSN Spaces we already have data types such as music lists and photo albums which don't fit in the traditional blog entry syndication paradigm that Atom is based upon. More importantly it is unclear how one would even extend to do this in an acceptable way. Similar issues exist with the API.

Hmmmm ... Seems the folks over at SixApart, behind TypePad, are using Atom for music lists, photo albums, and more.

For the TypeList API, we use the standard Atom namespace for certain elements, and custom namespaces for additional metadata.

In designing the namespaces for TypeLists, we have tried to leverage existing specifications such as RVW and bio, as well as using as much of the Atom format as possible. This has been balanced with a desire to encapsulate as much information as possible about the item itself (a book, for example) in its own namespace.

It all seems pretty reasonable and straightforward to me.

I'd like individual Velocity macro lookup loading to work similar to resource lookup with Java's resource bundle facility. Take, for example, the following Velocity setup.

// velocity.properties
resource.loader=file, class

// defined file and class resource loaders

velocimacro.library=user-macros.vm

So, if you've got a user-macros.vm file in one of the paths defined by the file resource loader, then the first path containing that file will be used. If Velocity can't find a given macro in that user-macros.vm file, it fails gracefully (it prints out the macro name in your template). In this example, I'd just like it to search the other file resource paths for another user-macros.vm file to see if the requested macro is in that file, and failing that, check the the user-macros.vm file from the classpath resource loader to see if the requested macro is available there.

Concrete example:

/some/file/resource/path/user-macros.vm - Contains Velocity macro #Baz
/some/file/path/user-macros.vm - Contains Velocity macros #Foo and #Bar
/WEB-INF/lib/velocity-macro-lib.jar - Contains a user-macros.vm file with Velocity macros #Boggle and #Fraggle

As the first path contains a user-macros.vm file, you can only use the #Baz macro in your templates. The #Foo, #Bar, #Boggle, and #Fraggle macros are "hidden". It's definitely more of a nice-to-have at this point.

Unless I'm missing something and there is a way to actually do this ...