I’ve only started creating some test feeds to flesh out how RDFa in Atom looks. I think there are a few general ways that a developer will use RDF in Entry Resources. Pardon some missing namespaces, the following examples are illustrative.

1. To make the Atom Entry info available as RDF. For example:
<entry about=”http://example.com/myentry/id”>
<author>
<name property=”dc:author”>John Smith</name>
</author>
</entry>

2. For other metadata. That is, I have an Entry document that represents some abstract Blog Post. I want to add a geolocation to it.
<entry about=”http://example.com/myentry/id”
xmlns:geo=”geonamespace”>
<author>
<name property=”dc:author”>John Smith</name>
</author>
<meta property=’geo:lat’>51.47026</meta>
<meta property=’geo:long’>-2.59466</meta>
</entry>

3. Represent the actual resource. For example, an entry that represents some resource with the listed attributes– in this case a wooden plank.
<entry about=”http://example.com/myentry/id”
xmlns:myns=”http://example.com/myns#”>
<content type=”xhtml”>
<div>
<span property=”myns:length”>10feet</span>
<span property=”myns:width”>12feet</span>
<span property=”myns:height”>1inch</span>
<span property=”myns:material”>wood</span>
</div>
</content>
</entry>

As for #2, I still am thinking about the pros/cons/differences of RDFa and Atom Extensions. For example:

<entry about=”http://example.com/myentry/id”
xmlns:geo=”geonamespace”>
<meta property=’geo:lat’>51.47026</meta>
<meta property=’geo:long’>-2.59466</meta>
</entry>

vs

<entry about=”http://example.com/myentry/id”
xmlns:geo=”geonamespace”>
<geo :lat>51.47026</geo>
<geo :long>-2.59466</geo>
</entry>

And thanks for the heads up, I shall look at the new draft.

So just to understand what you’re doing…are you saying that when delivering content by an Atom feed, the content has metadata in it? What sort of content is it? Is it any place that others can consume it at the moment?

All the best,

Mark