Re: TEI next

I agree that TEI needs better integration with IIIF.

In a recent discussion on Facebook around IIIF and TEI, I suggested that a
tool for generating TEI from IIIF would also be useful. If we had tools for
converting in both directions; i.e. IIIF→TEI and TEI→IIIF, it would allow
TEI-oriented tools to be inserted into the existing IIIF stack, allowing
TEI processing software written in XSLT and XQuery, etc, to be used to
enhance existing IIIF client-server systems. Another thing in its favour
would be the wonderful acronym TEIIIIF.



On 28 September 2016 at 02:03, MLH <[email protected]> wrote:

> The increasing importance of IIIF as a way of delivering digitised content
> raises particular questions about TEI/JSON tools. A tool to generate an
> IIIF manifest from a TEI manuscript description could greatly improve the
> quality of existing manifests (many of which are just lists of image
> sequences with little or not information about manuscript contents etc) and
> would support the continuing relevance of TEI
>
> Matthew
>
> Get Outlook for Android <https://aka.ms/ghei36>
>



-- 
Conal Tuohy
http://conaltuohy.com/
@conal_tuohy
+61-466-324297