On Tue, 4 Aug 2015 12:10:32 -0400, Syd Bauman <[log in to unmask]> wrote:
>Some quick thoughts, gotta run out shortly ...
>The short (and somewhat tongue-in-cheek obnoxious) answer to why
>there is no real discussion of "why a project would use TEI in lieu
>of alternatives" is because there really aren't any alternatives.
While I am aware that XHTML is at least one possible alternative, I am interested in finding if there are any others, and if so, what would make TEI stand out as an obvious choice or the situations in which TEI would be a likely preferred choice.
Most other formats make the case that their schema has certain advantages over others, but everything I have read relates to a single schema encoding. As it is clear to me that my project will involve multiple (and possibly many) schema, each being used for their own strengths or specialities, this raises the issue of how to go about choosing a base format.
>If you are only interested in single-source publishing _Gulliver's
>Travels_, then using DocBook, XHTML, or EPUB may make more sense.
>(Personally I'd use TEI, but that's because I'm a TEI expert, not
>because those other formats don't do single-source publishing well.)
Can you elaborate on this? I'm very interested to hear a view on this from someone who is already a TEI expert. I am not (yet :)).
>But (IMHO) any significant project should have an eye towards data
>curation and longevity as well. From what little I know of all these
>other formats, TEI and its self-documenting ODD extension system wins
>hands down in this arena.
I am unsure what you mean by data curation and longevity. Please expand on this if you can.
Syd, your remaining comments have given me plenty of food for thought, so thank you. I will expand on these in a separate post.