SIG:Text&Graphic

Text & Graphics Special Interest Group

Description

Text and Graphics Special Interest Group

The TEI Guidelines are used to encode many diverse, graphically rich documents, including illuminated manuscripts, laboratory notebooks, art books, children's illustrated books, comics and graphic novels, and so on. These types of graphically rich documents present special concerns, considerations, and challenges, both conceptually at the encoding level and technically at the transformation, presentation, and publishing layers of digital document development.

The purpose of this SIG will be to discuss, develop, and document various strategies and best practices for implementing the digital facsimile structures available in TEI P5, especially as relates to graphically rich texts, and for developing methods to extend the TEI when existing structures are not suitable.

Visit our page on the TEI Website: http://www.tei-c.org/Activities/SIG/Graphics/

Convenors

Martin de la Iglesia, mdelaig@sub.uni-goettingen.de
John Walsh, jawalsh@indiana.edu

Meetings

The Text & Graphics SIG first convened at the third annual TEI Member's Meeting in Nancy, 2003. Other meetings:

• eighth annual TEI Member's Meeting in London, England, November 6-8, 2008.
• TEI Members' Meeting in Würzburg, Germany, October 11-16, 2011.
• TEI Members' Meeting in Rome, Italy, October 2-5, 2013.

Listserv

Web site: http://listserv.brown.edu/?A0=TEI-GRAPHICS-SIG
To post to list: tei-graphics-sig@listserv.brown.edu
To send mail to list owners: tei-graphics-sig-request@listserv.brown.edu

Extending TEI Grapgics Encoding

On March 10, 2010, Martin Holmes re-raised the question of how to encode polygons in TEI. Suggestions:

1. Use SVG. Pro: existing standard. Against: verbose

2. Use GML or KML Pro: existing standard Against: Not the intended usage of these standards

3. Use zone/desc/dim@type='point' to define each point of the polygon Pro: no modification to TEI Against: possible abuse; not obvious how the points fit together.

4. <tei:polygon> as a child of <zone> Against (quoting Sebastian)

a) the validatability is identical, if its just a string
b) if you keep in the same area (attributes) its very easy for us to say "supply EITHER @path OR @urx, @ury etc". managing constraints of attributes vs content is a pain
c) you have to change content model of <zone> *and all other att.coordinated things*, which is a pain

5. @path added to att.coordinated, containing a set of space-separated coordinates as alternatives to ulx, uly etc Pro: simple and flexible Against: ?

Other issues raised on the listserv include circles and indicating 3D.

Facsimile Markup

This page was created in 2006-2007 during the development of TEI P5 Facsimile. It gives examples of several previously existing methods and tools for linking text with image.

TEI Guidelines 11.1, Digital Facsimiles: Description of Facsimile markup in TEI P5

A Guide to Images in TEI

This page is a proposal for a specialized tutorial. Please contribute and discuss.