@yoanngrange Microdata is much better for tool consumption, as you can consume the data even without knowing the schema.
1
@LeaVerou @yoanngrange The same is true with #Microformats2, the result of parsing is a data structure that is agnostic of its vocabulary.
1
@aaronpk @yoanngrange Isn’t it all still defined with class names? How would a tool know that an unknown class name is defining data?
1
@LeaVerou @yoanngrange That was part of the v2 change, only prefixed class names indicate data now. See microformats.org/wiki/microf… for more
2
@aaronpk @yoanngrange Still, it’s pretty invasive to assume that an author class is part of a microformat because it’s using a given prefix
2
@LeaVerou @yoanngrange In practice it hasn't been invasive at all. The prefixes haven't conflicted with anything else in the wild yet.
1
@aaronpk @yoanngrange I find that hard to believe. How was this tested? Is it a case of “I haven’t seen conflicts, ergo they do not exist"?
1
@LeaVerou @yoanngrange I believe the research was all documented on the #microformats wiki microformats.org/wiki/microf…
Apr 28, 2015 · 12:36 AM UTC

