On 09/06/11 06:11, Brett Zamir wrote:
> Hello Stuart,
> On 6/7/2011 4:36 AM, stuart yeates wrote:
>> A couple of points:
>> * Given that TEI is significantly more expressive than HTML5, any
>> serialization would be lossly, and my understanding of the genetic
>> editing proposal is that this makes TEI even more expressive.
> Although it is more expressive semantically than the default HTML5
> semantics, HTML5 Microdata allows for preservation of every single
> semantic feature of TEI (literally allowing use of the TEI namespace on
> the "itemtype" attribute and all of the TEI element and attributes
> (e.g., by markup including anonymous divs or spans with the "itemprop"
> attribute or in-body <meta/> and <link/> elements), though I think we
> ought to narrow it down and determine a specific single algorithm).
> So, technically, since it can subsume it, HTML5 can more expressive than
> TEI (of course, if your TEI embeds XHTML, then it's an even, if still
> meaningless, battle).
Yes, you can technically encode TEI tags as HTML5 Microdata.
However, if you do thing for TEI standoff markup (for example) you end
up with something that is HTML only technically and breaks all of the
assumptions every system, programmer and user has about HTML. Calling it
HTLM5 seems of, at best, marginal benefit and displaying such content to
users is, I believe harder not easier in such a format.
>> * The TEI community and the digital humanities community more
>> generally are pretty closely tied to the concept of the book, so I
>> suggest targeting the flavour of HTML5 as used in ePubs.
> Do you have an online reference elaborating on an ePub HTML5 flavor? As
> far as I can see, ePub is not an HTML format.
ePub is a zip file of HTML + media files + some standardised metadata
files (including DAISY). See http://en.wikipedia.org/wiki/EPUB
Library Technology Services http://www.victoria.ac.nz/library/