Posted on by & filed under features.

I just added support for AdaptiveBlue’s AB Meta format on all book pages.  I’m only supporting type, author and title because that’s all the metadata I have in the source XML. Hopefully I can find some content from other sources which is tagged in more detail.

I chose to use the Dublin Core namespace (rather than AdaptiveBlue’s) because it’s more familiar to me and more widely used in the industry.

Ironically it was much simpler to add AB Meta to my Django source code than it was to even explain how to do it in WordPress, as I did in a post on the Tools of Change blog.

Tags: ab meta, adaptive blue, dublin core, microformats,

6 Responses to “AB Meta microformat support added”

  1. Andy Mabbett

    A link to a published example would be good; but in the absence of one, how is what you did different to simply adding Dublin Core metadata?

  2. liza

    Good point! An example is the Pride and Prejudice book page. If you View Source you will see three elements in the HTML head of the document:

    <meta name=”dc:type” content=”book” />
    <meta name=”dc:title” content=”Pride and Prejudice” />
    <meta name=”dc:creator” content=”Jane Austen” />

    Note that this is HTML/AB Meta using DC names, not Dublin Core itself. I could literally add Dublin Core-namespaced markup to my XHTML, but no existing tools would be able to read it, and it might confuse legacy browsers that don’t understand XML namespaces. AB Meta shoehorns Dublin Core names into HTML, which is straightforward for existing search engines to index and solves the backwards-compatibility problem.

    I could also insert Dublin Core into the source XML (which is marked up as TEI and now directly downloadable from that same book page), but I wouldn’t be adding any new information.

  3. liza

    Oh hey, look at that. Thanks. I’m now using both AB Meta’s format and Dublin Core’s.


  1.  BlueBlog: ThreePress Implements AB Meta; highlights on O’Reilly Tools of Change Blog