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.
* If you're looking for repositories, I suggest you start with
* 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.
On 06/06/11 00:45, Brett Zamir wrote:
> Hello all,
> I am interested in seeing web apps develop to support TEI. I haven't had
> a chance to check out the XQuery tool someone mentioned here, though I
> did a little work on my own (at http://brettz9.github.com/xqueryeditor/
> ) utilizing the XQIB library in more of a proof of concept (though one
> for which I have a perhaps vain hope of finding time to develop it into
> something more).
> Besides being written using web standards, I would hope such a tool
> could obtain TEI texts in a central, open repository. While there may be
> some custom initiatives to bring TEI to the web, my thinking was that it
> might be more effective for open (and especially potentially
> collaborative markup) projects to use an HTML5 serialization which
> preserves all of the semantic data, especially as it would allow texts
> to be shared without need for tools supporting stylesheets. While
> microformats and RDFa seem to still be around, it looks more like
> microdata is going to win out. Microdata offers a systematic way to
> include the TEI namespace (albeit with instead of an xmlns attribute)
> and besides the itemprop global attributes, the HTML5 spec also
> specifically now allows <meta/> and <link/> in the document body which I
> think should be rich enough to define an official means of serializing
> TEI into HTML (and if contenting oneself to a subset of HTML,
> serializing back into TEI). But whatever could get consensus I think
> could work.
> I think such a serialization would offer such benefits as:
> a) It would _not require customizable software to be previewed_; TEI
> texts could be made available at public sites such as Wikisource or
> sites based on the same Mediawiki software, assuming
> https://bugzilla.wikimedia.org/show_bug.cgi?id=28776 would be
> implemented (something more likely to be possible than expecting the
> less familiar and non-historically-web-oriented language TEI to be
> accepted). The texts could thus be previewed as structured HTML+CSS,
> allowing for conveniently succinct wiki markup to be used to create such
> documents, while still allowing incremental improvements (and revision
> control and history) to the semantic mark-up as well.
> b) It would be encoded in the format already most _familiar to the web
> community_, albeit enhanced, in a standardly outlined manner, by
> TEI-based semantic markup. It does add the additional burden that
> mark-up creators must learn both HTML and TEI (though applications could
> utilize TEI as the primary format, converting back to HTML when sending
> text to the wikis, and merely storing HTML on the wiki)
> c) _Search engines_ such as Google (see
> http://www.google.com/support/webmasters/bin/answer.py?answer=99170 )
> can discover such markup in a semantically-aware manner.
> Does something like this interest anyone else?
> I don't know whether it ought to be done as a modification of the
> default TEI stylesheets, a simpler more predictable format (e.g., using
> divs for pretty much everything rather than native HTML like
> blockquote), a schema or what. Feedback on the idea is most welcome....
> Best wishes,
Library Technology Services http://www.victoria.ac.nz/library/