On 6/9/2011 4:05 AM, stuart yeates wrote:
> On 09/06/11 07:34, Martin Mueller wrote:
>> This has been a very helpful and interesting discussion that I think I
>> sort of understand. But I don't really understand it, and I am fairly
>> that few of my friends and colleagues in English departments or academic
>> libraries understand it either.
>> Is there somebody out there who can explain layman's language what is at
>> stake in using microdata to manage the TEI/HTML5 relationship and why or
>> how this would help scholars as they work with textual data in digital
> The HTML community(-ies) realised that there were existing XML schemas
> which had lives independent of HTML that HTML was never going to be
> able to encode. So they created a method for wrapping third-party XML
> tags in HTML so that the third-party XML can be used in HTML5.
> This works really well for XML that is effective semantic annotation
> of running text. Things like <tei:person/> and <tei:w type="verb"/>.
> These are pretty much the motivating use case for microdata.
Very well said.
> How it would work for things like standoff markup and genetic
> editions, is another question. Certainly you can map the TEI to HTML5.
> It doesn't, however, solve the question of how you display it to the
This is true, but as with XML, HTML doesn't need to be committal about
how to display markup (if at all). You can use CSS to hide content, meta
tags to represent hidden attributes, divs or spans to represent the
hierarchy of elements.
For example, to take your examples:
...firstly, the namespace would be defined probably on an ancestor
element, so as opposed to:
...you might have this:
<html itemscope="itemscope" itemtype="http://www.tei-c.org/ns/1.0">
Then to the elements:
...might map to:
...might map to:
<span itemprop="w"><meta itemprop="type" content="verb"/>runs</span>
And where there is no consensus in the community about a logical default
way to display some functionality such as you mention, it can be left to
the application to determine. Styles and scripting are well supported in
browsers with respect to HTML (less so, for XML), so the application can
have its freedom to do as it likes.
Still, having default mappings of tags like <quote/> to <blockquote/>
(as in the default stylesheets) and default CSS interpretations is
helpful even if TEI might not require or officially endorse such
interpretations (and again, HTML, as with XML can use its own CSS to
overwrite the defaults).