Ian Hickson i...@hixie.ch wrote:
The solution John proposed would indeed not handle cross-origin
extensions, which could be problematic.
Cross-origin extensions can still be handled with full URIs for the
extension properties.
I dont see how you can solve the itemtype=foo collision case for
In the user feedback from the schema.org proposal, which uses microdata as
its syntax, we have seen several use cases that would seem to require
multiple itemtypes per itemscope.
Currently the microdata spec only allows one itemtype which defines the
meaning of the vocabulary for subsequent
