XML versus RDF

Serialization techniques for Resource Description Framework confused basic lexical functionality of Extensible Markup Language. Simply, RDF does not describe formats as XML lets us, extensively.

RDF follows this kind of sequence:

<root version="1.1">
  <book type="indexed">
    <title>How to Win Monkeys and Influence Groggers</title> 
    <author>The Cannibals</author> 
    <date>2012 MIT</date>
  </book>
  <book type="lost">
    <title>The Carrot and The Snowman</title> 
    <author>Drake</author> 
    <date>MCMXCIX</date>
  </book>
</root>

Notice the RDF elements do not represent any code or format.

Compare that with XHTML elements with microdata:

<div itemscope itemtype="http://schema.org/Movie">
  <h1 itemprop="name">Avatar</h1>
  <div itemprop="director" itemscope itemtype="http://schema.org/Person">
  Director: <span itemprop="name">James Cameron</span> (born <span itemprop="birthDate">August 16, 1954)</span>
  </div>
  <div>Genre: <span itemprop="genre">Science fiction</span></div>
  <a href="../movies/avatar-theatrical-trailer.html" itemprop="trailer">Trailer</a>
</div>

See how it renders:

***

Avatar

Director: James Cameron (born August 16, 1954)

Genre: Science fiction

Trailer

***

That is still human readable, unlike how RDF renders:

*** <title>How to Win Monkeys and Influence Groggers</title> The Cannibals 2012 MIT <title>The Carrot and The Snowman</title> Drake MCMXCIX ***