Perhaps a dumb question. But in that case why not deemphasise the html? I.e. serve out the xml and either style as is or do client side transformations?
It seems to me that the problem you are setting yourself is rapidly becoming how can I preserve the semantic granularity of the original TEI in an HTML text that is used for interchange without negotiation, and I'd guess the answer is going to be 'you
should design something like the TEI to do it.'
How do I do this in HTML in this specific context I'd one question. How do I do it so that it maintains its semantic integrity in unknown contexts is a whole other one.
Sent from my phone using swipe typographical error production technology.
Daniel Paul O'Donnell
Department of English
University of Lethbridge
-------- Original message --------
From: Peter Boot <[log in to unmask]
Date: 2014-10-29 08:17 (GMT-06:00)
To: [log in to unmask]
Subject: Re: html from TEI, technical question about marginal notes
> I am operating on the assumption that we had better be prepared for the
> CSS not being applied as we intended (someone may swap in a different one
> for audio rendering, for example), so preserving the basic div/span
> distinction in HTML seems pretty important to me. I may well be wrong-
> headed there.
I think it's a reasonable assumption (the css not always being applied). E.g. a web archive environment might leave it out, or a tool for text analysis.