Microformats in Drupal

It's a little late but I figured I should still post this... There's a CodeFest this week-end where a bunch of geeks from different web applications will be present to share and implement a bunch of cool features like Microformats into their favorite CMS. This event wouldn't be possible without the sponsor, PHP Québec. It's open to anyone although it might get a little crowded at la Bande-Passante. I still hope to see you there, Saturday or Sunday :)

8655 Saint-Denis, Montréal (Québec) - exit south from Crémazie métro, walk 30 seconds and you're there.

Seeing as this group looks pretty latent, and I can't see anyone's mentioned it yet,
vcard.module is available to be patched to D5, and
I extended it to addhcard support to user profiles even if you don't use the actual vcard functions.
Just putting it out there, hopefully revive a little interest. I think microformats should be the default in drupal themes wherever possible.

Microformats are a format based on the common XHTML. There are a few popular Microformats recommendation (I refuse to call it a standard) specifications, most notable are hCard, XFN, hCalendar and XOXO.

XFN

what is XFN

If book review could implement the hreview microformat people would be more able to find book reviews on drupal sites using at least a few standard criteria.

I'm currently asking the microformats community for help in doing this, help from other people on the Drupal end would be excellent.

Most advice should probably take place over at the feature request at bookreview.module but discussion here can't hurt.

Be sure to checkout -and where possible use!- the excellent work over at factorycity.

Hey fellow Microformatters,

I've been working on a small side-element to Microformats in Drupal and it will be ready to commit to the CVS at some point tommorow.

I have created microid.module, which creates a MicroID hash in the user profile.

At the moment, it's a little hard coded. First off all, there is the function that creates the hash:

Now, what I do with this is I get $user->email to generate the email part of the hash, thats fine. But for the profile side, I have specified that there must be a field called profile_homepage. The reason for this is that the URL you want to create the hash with should be your homepage, thats how you will be identified.

A module called nodeauthor has recently been brought to my attention and is another module that could do with Microformat support.

From this screenshot you can see it add's a "About Author" at the bottom on a post regarding the node's author.

If you look at This comment on my site, it might look like nothing - but check with Tails, and you find a hidden spam hCard.

It's very easy to produce one and embed it in to a post or comment, which will then be indexed by sites such as Technorati.

So what can we do to stop this type of spam before it starts?

Disucss.

Infact, its' been posted here too:

<

p class="vcard">

I asked myself how we could use Microformats in the location module.

this is the patch which came out: Using Microformat for address output

comments and suggestions are welcome :)

I've been thinking about how to do hCards. I built a small example version which I commited to the CVS. It builds up the XHTML using JavaScript and works well as an example, but is very bulky and I can see it becoming very limited.

I'm thinking a better option may be to use the existing Profiles module to build hCards. With Profiles, you can create custom profile fields, and my idea is to build a custom hCard module that takes these fields and allows you to map them to defined hCard fields (i.e. profile-firstname = given-name, profile-company = org, etc) which this module then outputs in the correct format.

Recently I've really got excited about Microformats and how they can be used to create content that can be aggregated around the internet.

Drupal really needs to support microformats, and I am currently planning and working on a module set that allows this. But I would like your input!

If you read the description of microformats, you can see they are set pieces of information based on existing formats such as vCard and iCal, but written in semantic XHTML, which can then be styled using CSS class selectors. You then have the choice to render them to the page, for example with an event. Or you can embed them in your site, such as linking to someone you have cited on your blog by using the rel tag i.e. XFN.

Here's the low-down on the upcoming.org integration module:

Per the developers description: The upcoming.org module enables you to import events and venues from upcoming.org and display them in a calendar using the event module. Upcoming.org is a website that helps you share and keep track of your events. Synchronizing (using upcoming.org as the master repository) is also supported. Additionally, this module exposes the upcoming.org REST API, making clients written to use it interoperable with Drupal. This makes it possible to build a whole network of websites sharing their events, all using a defined API.

Update: Bumping this rather old post up and over to the Drupal Dojo in hope that it can spur some 'can drupal do this' learning and workshopping.

In the context of a music-arts community site, I'm looking to provide an easy way for registered users to create some of the following types of content: