Yes, I was going to ask Adam to show me in which way TinyMCE can handle rdfa because I know of none. And yes I understand that ProcessWire does not generate mark up. And I believe it doesn't have to in order embed the rdfa output into the html. It just needs to know where to output. Say that rdfa output could be achieved through a plugin. The plugin could be used to inject the namspaces into the doctype. And where you have a headline field, the plugin would inject rdfa attributes and so on. The markup is completely left up the you. I understand that you could add rdfa attributes to the markup yourself but I think a plugin that automatically injects rdfa attributes based on the context of the fields used in a template is a good idea. That would probably call for specific fields to used for specific types of data i.e. dedicated fields for title/headline, creator/author, post date, body, image and so forth. This is somewhat how plugins for wordpress and drupal handle rdfa. Drupal 7 have rdfa natively (as a plugin). The problem with those cms is that you HAVE to do things there way and they generate markup instead of letting you create your own. The one thing that draws me to this cms is the ability to control the way your site functions and generates its markup. But I do believe a little automation in the form of plugins can help end users.