There are only a few months left before the code freeze on September 1st. Now that Fields API has settled in core, it's time to extend it with some RDF semantics. DERI Galway is hosting an RDF in Drupal code sprint from May 11th until May 14th.

This sprint builds on Dries' ideas expressed in his recent posts Drupal, the semantic web and search and RDFa and Drupal. With RDF in the core of Drupal and RDFa output by default, it's dozens of thousands of websites which will all of a sudden start publishing their data as RDF.

So far 8 people have signed up. How about you?

• Stéphane Corlosquet, DERI (organizer)
• Florian Loretan, HappyPixels (organizer)
• Rolf Guescini, Cerpus
• Benjamin Melançon, Agaric Design
• Stefan Freudenberg, Agaric Design
• Frédéric G. Marand, OSInet
• Mark Birbeck, webBackplane
• John Morahan, io1

Some others are willing to come but cannot afford the trip until some funding is secured. To help us fund the sprint and bring more Drupal rockstars on board, please consider making a donation using the ChipIn widget on this page. The money will be used to cover flight, food and hotel costs for the sprinters. All sprinters are generously donating their time to make this happen. It would also be great to fly in a few additional people with extensive testing and Fields experience. Any excess money will be used to add more people, or will be donated to the Drupal Association.

Goals of the code sprint

The RDF code sprint will focus on Drupal core and aim at integrating RDF semantics in it.

1. Extend Fields API to integrate RDF mappings for each field instance. The semantics of a field can differ from a bundle to another. This can be stored either in the existing settings property or by adding a rdf_mappings property to the Field Instance objects.
2. Modify the Fields UI (contrib) to allow RDF mappings editing.
3. Define the appropriate mappings for the core modules, based on the RDF core mapping proposal.
4. Patch core modules with the mappings defined above.
5. Export these mappings in RDFa via the theme layer and keep it as generic as possible in order to ease the work of the themers.
6. Write tests for RDF in core.
7. Identify other non-fieldable entities in core which could benefit from being RDF-ized, and see how to annotate them. Comment is one example. Terms also, though they might become fieldable.
8. RSS 1 (RDF) in core. Arto volunteered to get started with that.

See a list of current open RDF issues in RDF issues in core.
See also the RDF code sprint wiki page where we will keep an up to date list of goals.