Rectangle 27 0

html Microdata: moving from microformats to schema.org (example hAtom news markup)?


<div itemscope itemtype="http://schema.org/Blog">
  ...
  <article  itemprop="blogPost" itemscope itemtype="http://schema.org/BlogPosting">
    ...
  </article>

  <article  itemprop="blogPost" itemscope itemtype="http://schema.org/BlogPosting">
    ...
  </article>
</div>

Here is a very simple example:

You have to choose a page type, like for example http://schema.org/Blog and then add the article/blogposts http://schema.org/BlogPosting

Note
Rectangle 27 0

html Microdata: moving from microformats to schema.org (example hAtom news markup)?


Sign up for our newsletter and get our top new questions delivered to your inbox (see an example).

Thanks. When I say 'a better separation', what I mean is that classes are now exclusively used for styling their intrinsic purpose, and the itemprop attribute exclusively for microdata. Meaning a clearer metadata layer. I also prefer the clarity of the clearly defined start point of the microdata sort using: itemscope itemtype="http://schema.org/MicrodataType"

i'd like to know what about schema.org is better at separation of concerns vs. microformats? schema.org has meta elements within the body element. microformats are html classes and and as such natively support separation. also, every major search provider already provided coverage of microformats and it hasn't decreased. curious, i am.

question 01: Creativeworks -> Blog is schema's equivalent to hatom. no clue if anyone's used it or written about it yet.

Note