Indeed, I think there is a natural mapping here between block names (such as example or admonition) and roles with the microdata. Additional mappings could be expressed through block and inline node attributes. If still not enough, a custom macro is always an option.
There's been discussion about a modern HTML 5 backend that fully leverages the semantics of HTML 5. I think we should start working on it in the asciidoctor-backends repo, preferably using slim. It makes sense to get it right, then later integrate it as a built-in option.
The tricky part is a name for it, oddly enough, since html5 is already in use. I was thinking something like shtml5 for semantic HTML 5. I'm open to other suggestions.
There is an open issue on this subject, which I also encourage you to check out to see other proposed ideas.
Cheers,
-Dan
On Feb 3, 2014 4:18 AM, "melix [via Asciidoctor :: Discussion]" <
[hidden email]> wrote:
Hi,
I was wondering if there was any effort ongoing to support HTML5 microdata? As a markup language processor, asciidoctor seems quite appropriate to support that, what do you think?
http://schema.org/docs/gs.html
Of course I could support it thanks to the new extensions mechanism too :)