New release of the RDFa 1.1 Distiller and Validator
Author(s) and publish date
- By:
-
-
Ivan Herman
-
- Published:
Back in May I have already blogged on the release of a new, RDFa 1.1 version of the distiller code. Many things have happened since May, however, with changes in RDFa, introduction of RDFa 1.1 Lite, etc. I have also blogged about those changes, and what they mean for Schema.org, for example, a few days ago. I have followed the changes on the specs with my code for the distiller; I have now updated the service. It implements the latest editors’ draft of RDFa 1.1 Core.
As also announced in my blog in May, I have also made an accompanying service called the (RDFa) validator. It relies on the same code as the distiller, except that it catches the possible error and warning triples and makes a human-readable version of those. Note that the validator can also be instructed to check RDFa 1.1 Lite, ie, it issues warning if the RDFa content uses RDFa attributes that are not part of RDFa 1.1 Lite.
The usual caveat applies, of course: this is still a service under development; it may change as the specification of RDFa evolves and, obviously, if contains bugs that I do not know about…
It's not clear why one would use this. Just looks like adding metadata for the fun of it. If there was some evidence of return on labor, then it would be more appealing to devs. If the semantics are really that useful, then they should be first class elements in HTML5... If you want a number or , then use real elements and not broken complexity and URI indirection.