> On 29 Oct 2014, at 13:54, Kalvesmaki, Joel <[log in to unmask]> wrote:
> I would do b.
> As I understand it HTML was designed to let <html:div> be a generic
> segmenting tool for anything that might (but not necessarily) deserve new
> lines (blocks), and <html:span> be anything that definitely didnąt (inline
> segments). I think it would be a mistake to assign <tei:p> to <html:span>,
buit isn’t it just as abusive to map <tei:hi> to <html:div>? swings and roundabouts.
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.
the downside of the more semantically pure “put the notes in a separate container anyway”
is that marginal labels like “Tim. II 21” or “234 BC” are not <aside>s in the same
sense as normal marginal notes.
hmm, this may affect my entire workflow. aargh.