I'm working on a second post about the microformat side of things. But here goes:
Suppose you accept that idea that instead of having 10 different web analytics tags on your page it would be better to have one tag (let's assume it's jsHub), then you can move up a level.
Rather than have each vendor define the metadata they want from the page, it's better to have a single set of metadata that all the vendors can use. So the point of the microformats is that they'll simplify even more the art of page tagging.
If vendors agreed to mark up the page name, or the products shown on the page, using a microformat then a single tag could read them and then fan the data out to various vendors. That way there's no ambiguity about what's being gathered.
I have a private web spider that's been following the top 1,000 web sites by traffic (plus the Fortune 1000) and the problem is that for the big ones they've got many, many tags like this per page.
Suppose you accept that idea that instead of having 10 different web analytics tags on your page it would be better to have one tag (let's assume it's jsHub), then you can move up a level.
Rather than have each vendor define the metadata they want from the page, it's better to have a single set of metadata that all the vendors can use. So the point of the microformats is that they'll simplify even more the art of page tagging.
If vendors agreed to mark up the page name, or the products shown on the page, using a microformat then a single tag could read them and then fan the data out to various vendors. That way there's no ambiguity about what's being gathered.