RE: Rolling the personalization SC into 4.1.2

[Jason] I think that approach is too restrictive, and that any text we adopt should be open to having multiple, domain-specific taxonomies.

That would be a good thing in general, but what I don’t get about this idea (and John’s suggestion that the AA one is open, and the AAA is more specific), is how you test it?

If I’m testing a site, do I have to search around schema.org, W3C specs, industry specific places to work out what taxonomy to use? What if you come up with a different answer to the author? Does the site have to declare what it uses?

I thought the point of this SC (at least a narrowly scoped version) was to add machine readable, pre-defined terms to common features & functions. That makes it easier for an extension to actually do something with it, and makes it easier to implement on the site.

Cheers,

-Alastair