This looks like it would be a long time before browsers are aware of it, and it also looks like all of these "vocabularies" would add a whole level of complexity (and bloat?) to any RDFa-aware browsers, not to mention the fun we’d have with compatibility. It’s bad enough with HTML, XHTML, CSS and Javascript! Can you imagine Microsoft’s implementation of this? Do you imagine that they would use existing commonly accepted vocabularies, as the W3C has done? The mind boggles! Simply adding the xml references to a page would slow things down quite a bit as the browser now has to request, fetch, parse and apply these definition files.
Seems to me that what it needed is a whole new approach to web semantics and web development. Which is not likely to happen any time soon. After all, standards that are over 10 years old are still not "standard" across even the top five most modern browsers.
That aside, it does look like you shouldn’t have any problem actually implementing it if you want to; MODx itself has no interest in what you add to your HTML tags.
There is a file in the assets/plugins/tinymcexxx/xconfig.js, where there are definitions for allowed attributes. This may be the place to add these extra allowable attributes to keep Tiny from nuking them.
An excellent article on the subject here:
http://www.standards-schmandards.com/category/content/
MODX Staff
☆ A M B ☆
