TEIWiki - User contributions [en]

SIG Text and Graphics 2023 meeting

2023-09-06T16:30:54Z

Martin de la Iglesia: summary

at the [https://teimec2023.uni-paderborn.de/ MEC and TEI Conference in Paderborn, Germany, September 4-8, 2023].

'''when''': Wednesday 6 September, 11:15 - 12:45

'''where''': Main Campus, L 1.201

==Summary==
Topics discussed:
* Interplay between TEI and other formats (IIIF, SVG, (Geo)JSON, ...): when to use what? How to connect? (cf. [https://github.com/TEIC/TEI/issues/1508 #1508])
* Are we describing physical objects or digital representations? Or both? How to distinguish? (cf. [https://github.com/TEIC/TEI/issues/2148 #2148])
* facsimile//zone vs. sourceDoc//zone (Release [https://tei-c.org/Vault/P5/current/doc/tei-p5-doc/readme-4.5.0.html 4.5.0], cf. [https://github.com/TEIC/TEI/issues/2300 #2300])
* proposed new element <listFigure> (cf. [https://github.com/TEIC/TEI/issues/1861 #1861])

SIG Text and Graphics 2023 meeting

2023-09-06T07:16:58Z

Martin de la Iglesia: Created page with "at the [https://teimec2023.uni-paderborn.de/ MEC and TEI Conference in Paderborn, Germany, September 4-8, 2023]. '''when''': Wednesday 6 September, 11:15 - 12:45 '''where'''..."

at the [https://teimec2023.uni-paderborn.de/ MEC and TEI Conference in Paderborn, Germany, September 4-8, 2023].

'''when''': Wednesday 6 September, 11:15 - 12:45

'''where''': Main Campus, L 1.201

SIG:Text&Graphic

2023-09-06T07:12:30Z

Martin de la Iglesia: /* Meetings */ +1

= 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, [mailto:iglesia@hab.de iglesia@hab.de]<br/>
John Walsh, [mailto:jawalsh@indiana.edu 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.
* [[SIG Text and Graphics 2013 meeting|TEI Members' Meeting in Rome, Italy, October 2-5, 2013.]]
* [[SIG Text and Graphics 2015 meeting|TEI Conference and Members' Meeting in Lyon, France, October 28-31, 2015.]]
* [[SIG Text and Graphics 2016 meeting|TEI Conference and Members' Meeting in Vienna, Austria, September 26-30, 2016.]]
* [[SIG Text and Graphics 2018 meeting|TEI Conference and Members Meeting in Tokyo, Japan, September 9-13, 2018.]]
* [[SIG Text and Graphics 2019 meeting|TEI Conference and Members Meeting in Graz, Austria, September 16-20, 2019.]]
* [[SIG Text and Graphics 2023 meeting|Joint MEC and TEI Conference in Paderborn, Germany, September 4-8, 2023.]]

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

==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 ==

[[FacsimileMarkup|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.

[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX TEI Guidelines 11.1, Digital Facsimiles]: Description of Facsimile markup in TEI P5

== A Guide to Images in TEI ==
[[User_talk:Martin_de_la_Iglesia/A_Guide_to_Images_in_TEI|This page]] is a proposal for a specialized tutorial. Please contribute and discuss.

== Diagrams ==
Encoding of diagrams was discussed on TEI-L in May 2014: http://listserv.brown.edu/archives/cgi-bin/wa?A1=ind1405&L=TEI-L#9 --[[User:Martin de la Iglesia|Martin de la Iglesia]] 12:57, 8 May 2014 (CEST)

[[Category:SIG|Text]]

SIG Text and Graphics 2019 meeting

2019-10-17T10:41:05Z

Martin de la Iglesia: /* Summary */ added link to meeting report

at [https://graz-2019.tei-c.org/ TEI Conference and Members’ Meeting in Graz, Austria, September 16-20, 2019].

'''when''': Tuesday 17 September, 2:00pm - 3:30pm

'''where''': Seminar Room LS 15.02

==Summary==
This year's SIG meeting started with a presentation by Uwe Sikora (Göttingen State and University Library) of an application that is being developed to annotate nested <zone> elements. From there the discussion went on to general issues of positioning zones in non-TEI formats such as SVG and JSON. Whether and how to link this kind of coordinate data to TEI documents is still a matter of debate (cf. https://github.com/TEIC/TEI/issues/1508) that is becoming more and more relevant, particularly in the light of the increasing popularity of IIIF. --[[User:Martin de la Iglesia|Martin de la Iglesia]] ([[User talk:Martin de la Iglesia|talk]]) 11:52, 24 September 2019 (CEST)
:See also this blogpost: https://eos.hypotheses.org/272 --[[User:Martin de la Iglesia|Martin de la Iglesia]] ([[User talk:Martin de la Iglesia|talk]]) 12:41, 17 October 2019 (CEST)

SIG Text and Graphics 2019 meeting

2019-09-24T09:52:51Z

Martin de la Iglesia: /* Summary */

SIG Text and Graphics 2019 meeting

2019-09-24T08:49:14Z

Martin de la Iglesia: replaced Agenda with Summary

SIG Text and Graphics 2019 meeting

2019-09-02T12:04:56Z

Martin de la Iglesia: added sections "Participants" and "Agenda"

at [https://graz-2019.tei-c.org/ TEI Conference and Members’ Meeting in Graz, Austria, September 16-20, 2019].

'''when''': Tuesday 17 September, 2:00pm - 3:30pm

'''where''': Seminar Room LS 15.02

==Participants==
# [[User:Martin de la Iglesia|Martin de la Iglesia]] ([[User talk:Martin de la Iglesia|talk]]) 14:04, 2 September 2019 (CEST)
# ...

==Agenda (preliminary)==
* Annotation of nested <zone>s (U. S.)
* GitHub issues from previous SIG meetings
* Technical Metadata about Digital Images
* ...

SIG Text and Graphics 2019 meeting

2019-09-02T10:15:04Z

Martin de la Iglesia: created

at [https://graz-2019.tei-c.org/ TEI Conference and Members’ Meeting in Graz, Austria, September 16-20, 2019].

'''when''': Tuesday 17 September, 2:00pm - 3:30pm

'''where''': Seminar Room LS 15.02

SIG:Text&Graphic

2019-09-02T10:11:17Z

Martin de la Iglesia: /* Meetings */ +1

= 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, [mailto:iglesia@hab.de iglesia@hab.de]<br/>
John Walsh, [mailto:jawalsh@indiana.edu 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.
* [[SIG Text and Graphics 2013 meeting|TEI Members' Meeting in Rome, Italy, October 2-5, 2013.]]
* [[SIG Text and Graphics 2015 meeting|TEI Conference and Members' Meeting in Lyon, France, October 28-31, 2015.]]
* [[SIG Text and Graphics 2016 meeting|TEI Conference and Members' Meeting in Vienna, Austria, September 26-30, 2016.]]
* [[SIG Text and Graphics 2018 meeting|TEI Conference and Members Meeting in Tokyo, Japan, September 9-13, 2018.]]
* [[SIG Text and Graphics 2019 meeting|TEI Conference and Members Meeting in Graz, Austria, September 16-20, 2019.]]

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

==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 ==

[[FacsimileMarkup|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.

[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX TEI Guidelines 11.1, Digital Facsimiles]: Description of Facsimile markup in TEI P5

== A Guide to Images in TEI ==
[[User_talk:Martin_de_la_Iglesia/A_Guide_to_Images_in_TEI|This page]] is a proposal for a specialized tutorial. Please contribute and discuss.

== Diagrams ==
Encoding of diagrams was discussed on TEI-L in May 2014: http://listserv.brown.edu/archives/cgi-bin/wa?A1=ind1405&L=TEI-L#9 --[[User:Martin de la Iglesia|Martin de la Iglesia]] 12:57, 8 May 2014 (CEST)

[[Category:SIG|Text]]

SIG Text and Graphics 2018 meeting

2018-10-02T13:10:21Z

Martin de la Iglesia: minutes continued

at [https://tei2018.dhii.asia/ TEI Conference and Members Meeting in Tokyo, Japan, September 9-13, 2018].

'''when''': Tuesday 11 September, 10:45-12:15

'''where''': room B1

== Minutes ==

=== 2016 Meeting follow-up ===
* Update definition of <graphic>: GitHub ticket [https://github.com/TEIC/TEI/issues/1439#issuecomment-426220380 1439] expanded according to discussion.
* zone used with JSON, etc: GitHub ticket [https://github.com/TEIC/TEI/issues/1508#issuecomment-426225568 1508] expanded according to discussion.
* placement of nested <figure>s: GitHub ticket [https://github.com/TEIC/TEI/issues/1515#issuecomment-426227830 1515] expanded according to discussion.

=== Guidelines Release 3.4.0 ===
* new element <path>: GitHub ticket [https://github.com/TEIC/TEI/issues/1453#issuecomment-426230891 1453] expanded according to discussion.

=== TEI and IIIF ===
Recently there has been a lot of discussion about TEI and IIIF interoperability on TEI-L and elsewhere. Four main issues can be identified:
# convert TEI to IIIF manifest [https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;d8301523.1609]
# link from TEI to IIIF image [https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;a36dfd45.1706]
# link from TEI to IIIF manifest [https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;868063ae.1709]
# link from IIIF manifest to TEI-encoded transcription [https://hcmc.uvic.ca/tei2017/abstracts/t_125_viglianti_teiandiiif.html]
After some discussion, we decided not to actively pursue this huge and complex topic further as a group, at least not for the time being.

--[[User:Martin de la Iglesia|Martin de la Iglesia]] 13:10, 2 October 2018 (UTC)

SIG Text and Graphics 2018 meeting

2018-10-02T12:52:28Z

Martin de la Iglesia: minutes added

SIG Text and Graphics 2018 meeting

2018-08-23T11:20:46Z

Martin de la Iglesia: page created

at [https://tei2018.dhii.asia/ TEI Conference and Members Meeting in Tokyo, Japan, September 9-13, 2018].

'''when''': Tuesday 11 September, 10:45-12:15

'''where''': room B1

SIG:Text&Graphic

2018-08-23T11:17:44Z

Martin de la Iglesia: /* Meetings */ +1

= 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, [mailto:iglesia@hab.de iglesia@hab.de]<br/>
John Walsh, [mailto:jawalsh@indiana.edu 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.
* [[SIG Text and Graphics 2013 meeting|TEI Members' Meeting in Rome, Italy, October 2-5, 2013.]]
* [[SIG Text and Graphics 2015 meeting|TEI Conference and Members' Meeting in Lyon, France, October 28-31, 2015.]]
* [[SIG Text and Graphics 2016 meeting|TEI Conference and Members' Meeting in Vienna, Austria, September 26-30, 2016.]]
* [[SIG Text and Graphics 2018 meeting|TEI Conference and Members Meeting in Tokyo, Japan, September 9-13, 2018.]]

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

==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 ==

[[FacsimileMarkup|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.

[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX TEI Guidelines 11.1, Digital Facsimiles]: Description of Facsimile markup in TEI P5

== A Guide to Images in TEI ==
[[User_talk:Martin_de_la_Iglesia/A_Guide_to_Images_in_TEI|This page]] is a proposal for a specialized tutorial. Please contribute and discuss.

== Diagrams ==
Encoding of diagrams was discussed on TEI-L in May 2014: http://listserv.brown.edu/archives/cgi-bin/wa?A1=ind1405&L=TEI-L#9 --[[User:Martin de la Iglesia|Martin de la Iglesia]] 12:57, 8 May 2014 (CEST)

[[Category:SIG|Text]]

Talk:MilestoneXSLT

2018-04-19T09:22:18Z

Martin de la Iglesia: /* Script 2: suggestions for improvement */ code optimisation

== More comments, please ==
I found these pieces of code highly useful, but (despite having worked with XSLT before) it took me very long to understand how they actually work, i.e. what some of the expressions actually do. Maybe future readers would benefit from some comments added to the code.
--[[User:Martin de la Iglesia|Martin de la Iglesia]] 05:57, 6 August 2012 (EDT)

== Script 2: suggestions for improvement ==

regarding the 2nd of the XSLT 2.0 stylesheets:
#Just a minor point, but I think the line <code><xsl:variable name="cur-p" select="generate-id(.)"/></code> is unnecessary, because this variable isn't used anywhere. I assume it's a relict from the XSLT 1.0 version.
#The line <code><xsl:sequence select="current()/ancestor::p[1]/lb/@*"/></code> doesn't seem entirely correct; more precisely, it only works for the particular example input provided, but not when there are multiple lb elements, in which case only the attribute value of the last lb is applied to each lb element.
#Instead, in order to copy the attributes, I suggest to add <source lang="xml"><xsl:copy-of select="@*"/></source> after each of the tags inserted in step2 (p, lb, del), e.g. <source lang="xml"><p xmlns="http://www.tei-c.org/ns/1.0"><xsl:copy-of select="@*"/></source> etc. Note, however, that this might add unwanted default attributes to the output - see https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;42710be0.1404 for solutions to this problem.
--[[User:Martin de la Iglesia|Martin de la Iglesia]] 12:23, 18 April 2018 (CEST)

Talk:MilestoneXSLT

2018-04-18T10:23:07Z

Martin de la Iglesia: /* Script 2: suggestions for improvement */ new section

== More comments, please ==
I found these pieces of code highly useful, but (despite having worked with XSLT before) it took me very long to understand how they actually work, i.e. what some of the expressions actually do. Maybe future readers would benefit from some comments added to the code.
--[[User:Martin de la Iglesia|Martin de la Iglesia]] 05:57, 6 August 2012 (EDT)

== Script 2: suggestions for improvement ==

regarding the 2nd of the XSLT 2.0 stylesheets:
#Just a minor point, but I think the line <code><xsl:variable name="cur-p" select="generate-id(.)"/></code> is unnecessary, because this variable isn't used anywhere. I assume it's a relict from the XSLT 1.0 version.
#The line <code><xsl:sequence select="current()/ancestor::p[1]/lb/@*"/></code> doesn't seem entirely correct; more precisely, it only works for the particular example input provided, but not when there are multiple lb elements, in which case only the attribute value of the last lb is applied to each lb element.
#Instead, in order to copy the attributes, I suggest to add <source lang="xml"><xsl:for-each select="@*"><xsl:copy-of select="."/></xsl:for-each></source> after each of the tags inserted in step2 (p, lb, del), e.g. <source lang="xml"><p xmlns="http://www.tei-c.org/ns/1.0"><xsl:for-each select="@*"><xsl:copy-of select="."/></xsl:for-each></source> etc. Note, however, that this might add unwanted default attributes to the output - see https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;42710be0.1404 for solutions to this problem.
--[[User:Martin de la Iglesia|Martin de la Iglesia]] 12:23, 18 April 2018 (CEST)

SIG:Text&Graphic

2017-08-02T15:27:19Z

Martin de la Iglesia: /* Convenors */ e-mail address updated

= 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, [mailto:iglesia@hab.de iglesia@hab.de]<br/>
John Walsh, [mailto:jawalsh@indiana.edu 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.
* [[SIG Text and Graphics 2013 meeting|TEI Members' Meeting in Rome, Italy, October 2-5, 2013.]]
* [[SIG Text and Graphics 2015 meeting|TEI Conference and Members' Meeting in Lyon, France, October 28-31, 2015.]]
* [[SIG Text and Graphics 2016 meeting|TEI Conference and Members' Meeting in Vienna, Austria, September 26-30, 2016.]]

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

==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 ==

[[FacsimileMarkup|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.

[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX TEI Guidelines 11.1, Digital Facsimiles]: Description of Facsimile markup in TEI P5

== A Guide to Images in TEI ==
[[User_talk:Martin_de_la_Iglesia/A_Guide_to_Images_in_TEI|This page]] is a proposal for a specialized tutorial. Please contribute and discuss.

== Diagrams ==
Encoding of diagrams was discussed on TEI-L in May 2014: http://listserv.brown.edu/archives/cgi-bin/wa?A1=ind1405&L=TEI-L#9 --[[User:Martin de la Iglesia|Martin de la Iglesia]] 12:57, 8 May 2014 (CEST)

[[Category:SIG|Text]]

User:Martin de la Iglesia

2017-08-02T15:19:41Z

Martin de la Iglesia: updated

Herzog August Bibliothek Wolfenbüttel, Germany,<br/>
project "Annotated digital edition of Philipp Hainhofer’s (1578-1647) travel and collection accounts" - [http://www.hab.de/en/home/research/projects/annotated-digital-edition-of-philipp-hainhofers-1578-1647-travel-and-collection-accounts.html project description]

[[Category:Users|Iglesia]]

SIG Text and Graphics 2016 meeting

2016-10-06T09:33:26Z

Martin de la Iglesia: changed Agenda to Minutes

at TEI Conference and Members' Meeting in Vienna, Austria, September 26-30, 2016.

'''when''': Friday 30 September, 09.00-10.30

'''where''': Museumszimmer (Museum room)

== Minutes ==
# '''facsimile encoding with the recently updated <graphic> element''' (cf. [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1603&L=tei-l&D=0&P=60 TEI-L], [http://github.com/TEIC/TEI/issues/1439 GitHub #1439]): formerly limited to inline images, <graphic> can now (as of March 2016 / version 3.0.0) be also used to encode facsimiles. Several examples in the Guidelines already reflect this, but the Guidelines prose needs to be updated accordingly. At the least, cross-references between chapters 11 and 3.9 should be added. See [https://github.com/TEIC/TEI/issues/1427#issuecomment-250683529 GitHub #1427].
# '''linking to coordinate data in non-TEI formats''': in some project architectures, image coordinates are stored in external files, e.g. in JSON. Currently there is no encoding mechanism to explicitly link from a TEI <zone> to such a non-TEI file. See [https://github.com/TEIC/TEI/issues/1508 GitHub #1508].
# '''placement of nested <figure> elements''': <figure> may contain <figure> and there are examples in the Guidelines of such multi-part images. However, the Guidelines do not say how to indicate the exact position of the inner images. A possible solution might be to allow <zone> inside <figure> so that both the outer and the inner images can be wrapped in <zone> and then positioned using the TEI coordinate attributes. See [https://github.com/TEIC/TEI/issues/1515 GitHub #1515].

SIG Text and Graphics 2016 meeting

2016-07-25T13:43:45Z

Martin de la Iglesia: /* Agenda */ +1

at TEI Conference and Members' Meeting in Vienna, Austria, September 26-30, 2016.

'''when''': Friday 30 September, 09.00-10.30

'''where''': Museumszimmer (Museum room)

== Agenda ==
* Introductions, individual encoding issues (all)
* facsimile encoding with the recently updated <graphic> element; cf. [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1603&L=tei-l&D=0&P=60 TEI-L], [http://github.com/TEIC/TEI/issues/1439 GitHub] (Martin de la Iglesia)
* placement of nested <figure> elements (Martin de la Iglesia)

SIG Text and Graphics 2016 meeting

2016-07-07T12:31:19Z

Martin de la Iglesia: page created

SIG:Text&Graphic

2016-07-07T12:24:34Z

Martin de la Iglesia: /* Meetings */ Link to next meeting subpage added

= 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, [mailto:mdelaig@sub.uni-goettingen.de mdelaig@sub.uni-goettingen.de]<br/>
John Walsh, [mailto:jawalsh@indiana.edu 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.
* [[SIG Text and Graphics 2013 meeting|TEI Members' Meeting in Rome, Italy, October 2-5, 2013.]]
* [[SIG Text and Graphics 2015 meeting|TEI Conference and Members' Meeting in Lyon, France, October 28-31, 2015.]]
* [[SIG Text and Graphics 2016 meeting|TEI Conference and Members' Meeting in Vienna, Austria, September 26-30, 2016.]]

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

==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 ==

[[FacsimileMarkup|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.

[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX TEI Guidelines 11.1, Digital Facsimiles]: Description of Facsimile markup in TEI P5

== A Guide to Images in TEI ==
[[User_talk:Martin_de_la_Iglesia/A_Guide_to_Images_in_TEI|This page]] is a proposal for a specialized tutorial. Please contribute and discuss.

== Diagrams ==
Encoding of diagrams was discussed on TEI-L in May 2014: http://listserv.brown.edu/archives/cgi-bin/wa?A1=ind1405&L=TEI-L#9 --[[User:Martin de la Iglesia|Martin de la Iglesia]] 12:57, 8 May 2014 (CEST)

[[Category:SIG|Text]]

SIG Text and Graphics 2015 meeting

2015-11-05T10:31:51Z

Martin de la Iglesia: /* Agenda */ updated

at TEI Conference and Members' Meeting in Lyon, France, October 28-31, 2015

'''when''': Thursday 29 October, 16.30-18.00

'''where''': room AR51

== Agenda ==
# Introductions, individual encoding issues (all)
# Encoding non-rectangular writing surfaces with <surface @points> (Martin de la Iglesia)

SIG Text and Graphics 2015 meeting

2015-11-04T12:55:34Z

Martin de la Iglesia: update

at TEI Conference and Members' Meeting in Lyon, France, October 28-31, 2015

'''when''': Thursday 29 October, 16.30-18.00

'''where''': room AR51

== Agenda ==
# Encoding non-rectangular writing surfaces with <surface @points> (Martin de la Iglesia)
#
#

SIG Text and Graphics 2015 meeting

2015-10-27T11:29:21Z

Martin de la Iglesia: /* Agenda */ +1

at TEI Conference and Members' Meeting in Lyon, France, October 28-31, 2015

'''when''': Thursday 29 October, 16.30-18.00

'''where''': room tba

== Agenda ==
# Encoding non-rectangular writing surfaces with <surface @points> (Martin de la Iglesia)
#
#

SIG Text and Graphics 2015 meeting

2015-10-20T08:21:04Z

Martin de la Iglesia: created

at TEI Conference and Members' Meeting in Lyon, France, October 28-31, 2015

'''when''': Thursday 29 October, 16.30-18.00

'''where''': room tba

== Agenda ==
#
#
#

SIG:Text&Graphic

2015-10-07T08:55:39Z

Martin de la Iglesia: /* Meetings */ +1

= 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, [mailto:mdelaig@sub.uni-goettingen.de mdelaig@sub.uni-goettingen.de]<br/>
John Walsh, [mailto:jawalsh@indiana.edu 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.
* [[SIG Text and Graphics 2013 meeting|TEI Members' Meeting in Rome, Italy, October 2-5, 2013.]]
* [[SIG Text and Graphics 2015 meeting|TEI Conference and Members' Meeting in Lyon, France, October 28-31, 2015.]]

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

==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 ==

[[FacsimileMarkup|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.

[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX TEI Guidelines 11.1, Digital Facsimiles]: Description of Facsimile markup in TEI P5

== A Guide to Images in TEI ==
[[User_talk:Martin_de_la_Iglesia/A_Guide_to_Images_in_TEI|This page]] is a proposal for a specialized tutorial. Please contribute and discuss.

== Diagrams ==
Encoding of diagrams was discussed on TEI-L in May 2014: http://listserv.brown.edu/archives/cgi-bin/wa?A1=ind1405&L=TEI-L#9 --[[User:Martin de la Iglesia|Martin de la Iglesia]] 12:57, 8 May 2014 (CEST)

[[Category:SIG|Text]]

Crosswalks

2014-11-17T10:40:47Z

Martin de la Iglesia: /* From other formats to TEI */ +1

[[Category:SIG:Libraries]]

This page is a central location to gather ''schema crosswalks'' (''mappings'') from TEI headers to other data formats and from other data formats to TEI headers, and to mention tools that implement these mappings.

If you have a mapping that you'd like to share but don't have a place to put it, consider adding it directly to the wiki as its own page!

== From TEI to other formats ==

=== TEI to MARC ===

[http://www.tei-c.org/SIG/Libraries/teiinlibraries/main-driver.html#index.xml-body.1_div.4_div.1_div.6 Section 4.1.6] of [http://purl.oclc.org/NET/teiinlibraries <cite>Best Practices for TEI in Libraries</cite> (version 3.0)] provides a mapping.

=== TEI to MODS ===

?

=== TEI to Dublin Core ===

?

== From other formats to TEI ==

=== MARC to TEI ===

[http://www.tei-c.org/SIG/Libraries/teiinlibraries/main-driver.html#index.xml-body.1_div.4_div.1_div.6 Section 4.1.6] of [http://purl.oclc.org/NET/teiinlibraries <cite>Best Practices for TEI in Libraries</cite> (version 3.0)] provides a mapping. Conversion from MARCXML to TEI has been implemented in [[Thutmose_II]].

=== TextGrid to TEI ===

There is a "Copy TEI Header" button in the metadata forms in TextGridLab. Maybe this crosswalk is documented somewhere?

SIG:Text&Graphic

2014-05-08T10:57:01Z

Martin de la Iglesia: /* Text & Graphics Special Interest Group */ added section 'diagrams'

= 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, [mailto:mdelaig@sub.uni-goettingen.de mdelaig@sub.uni-goettingen.de]<br/>
John Walsh, [mailto:jawalsh@indiana.edu 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.
* [[SIG Text and Graphics 2013 meeting|TEI Members' Meeting in Rome, Italy, October 2-5, 2013.]]

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

==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 ==

[[FacsimileMarkup|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.

[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX TEI Guidelines 11.1, Digital Facsimiles]: Description of Facsimile markup in TEI P5

== A Guide to Images in TEI ==
[[User_talk:Martin_de_la_Iglesia/A_Guide_to_Images_in_TEI|This page]] is a proposal for a specialized tutorial. Please contribute and discuss.

== Diagrams ==
Encoding of diagrams was discussed on TEI-L in May 2014: http://listserv.brown.edu/archives/cgi-bin/wa?A1=ind1405&L=TEI-L#9 --[[User:Martin de la Iglesia|Martin de la Iglesia]] 12:57, 8 May 2014 (CEST)

[[Category:SIG|Text]]

User talk:Martin de la Iglesia

2014-03-07T08:42:50Z

Martin de la Iglesia: added two more images

'''Welcome to ''TEIWiki''!'''
We hope you will contribute much and well.
You will probably want to read the [[Help:Contents|help pages]].
Again, welcome and have fun! [[User:Piotr Banski|Piotr]] 05:15, 2 December 2011 (EST)

== mysterious quote signs ==

Example 1: [[File:Pv_nov_1862_detail.jpg]]

Example 2: [[File:Pv_1862_02_21_detail.jpg]]

Example 3:

[[File:Pv 1860 07 21 detail.jpg]]

Example 4:

[[File:Pv 1862 05 11.jpg]]

File:Pv 1862 05 11.jpg

2014-03-07T08:42:01Z

Martin de la Iglesia:

File:Pv 1860 07 21 detail.jpg

2014-03-07T08:39:36Z

Martin de la Iglesia:

User talk:Martin de la Iglesia

2014-03-05T10:19:11Z

Martin de la Iglesia: /* mysterious quote signs */ new section

File:Pv nov 1862 detail.jpg

2014-03-05T10:17:46Z

Martin de la Iglesia:

File:Pv 1862 02 21 detail.jpg

2014-03-05T10:15:48Z

Martin de la Iglesia:

Sandbox for Genetic Editing

2013-11-04T10:55:15Z

Martin de la Iglesia: added discussion of line children

The purpose of this page is to discuss any issues of the with chapter 11 of version 2 of TEI P5, especially the elements and attributes which have been newly introduced in this version in the wake of the draft proposal “An Encoding Model for Genetic Editions”:
*<line>
** Some elements from other modules are not allowed as child elements of <line>, e.g. <subst>, <rs>, <date>, or <stamp>. This can cause problems when one would like to encode the corresponding phenomena. Two types of workaround are possible:
*** substitute the problematic element for a legal one, e.g. use <mod type="subst"> instead of <subst>;
*** wrap the problematic element in <seg>, e.g. <seg><rs>...</rs></seg>. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 05:55, 4 November 2013 (EST)
*<listChange>
*<metamark>
*<mod>
*<redo>
*<retrace>
*<sourceDoc>
*<substJoin>
*<surfaceGrp>
*<transpose>
*<undo>
*@change
*@instant
The page is not confined to issues of ‘genetic’ editing. Any problems of ‘diplomatic’ or ‘documentary’ transcriptions of manuscripts, be they modern, medieval or ancient, may be addressed here.

Also, the well-established elements and attributes may need to be discussed as their use is in many ways affected by the new ones.

==Projects==
* '''[http://www.uni-goettingen.de/en/303691.html Genetic-critical and annotated hybrid-edition of Theodor Fontane’s notebooks based on a virtual research environment]''': our TEI code (not published yet) is based on a <sourceDoc>/<zone>/<line> structure. We're happy to discuss encoding issues here. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:49, 25 October 2013 (EDT)

==Bibliography==
Brüning, Gerrit, Katrin Henzel, and Dietmar Pravida. 2013. “Multiple Encoding in Genetic Editions: The Case of ‘Faust’.” In ''Journal of the Text Encoding Initiative [Online]'' 4. URL: http://jtei.revues.org/697; DOI: 10.4000/jtei.697.

Muñoz, Trevor, Raffaele Viglianti, Neil Fraistat. 2013. “Texts and Documents: new challenges for TEI interchange and the possibilities for participatory archives.” In ''The Linked TEI: Text Encoding in the Web. Abstracts of the TEI Conference and Members Meeting 2013: October 2–5, Rome'', edited by Fabio Ciotti and Arianna Ciula, 99–104. Rome: Digilab Sapienza University & TEI Consortium.

Robinson, Peter. 2013. “Towards a Theory of Digital Editions.” In ''Variants'' 10: 105–31.

Sandbox for Genetic Editing

2013-10-25T10:49:11Z

Martin de la Iglesia: /* Projects */ added Fontane's notebooks

The purpose of this page is to discuss any issues of the with chapter 11 of version 2 of TEI P5, especially the elements and attributes which have been newly introduced in this version in the wake of the draft proposal “An Encoding Model for Genetic Editions”:
*<line>
*<listChange>
*<metamark>
*<mod>
*<redo>
*<retrace>
*<sourceDoc>
*<substJoin>
*<surfaceGrp>
*<transpose>
*<undo>
*@change
*@instant
The page is not confined to issues of ‘genetic’ editing. Any problems of ‘diplomatic’ or ‘documentary’ transcriptions of manuscripts, be they modern, medieval or ancient, may be addressed here.

Also, the well-established elements and attributes may need to be discussed as their use is in many ways affected by the new ones.

==Projects==
* '''[http://www.uni-goettingen.de/en/303691.html Genetic-critical and annotated hybrid-edition of Theodor Fontane’s notebooks based on a virtual research environment]''': our TEI code (not published yet) is based on a <sourceDoc>/<zone>/<line> structure. We're happy to discuss encoding issues here. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:49, 25 October 2013 (EDT)

==Bibliography==
Brüning, Gerrit, Katrin Henzel, and Dietmar Pravida. 2013. “Multiple Encoding in Genetic Editions: The Case of ‘Faust’.” In ''Journal of the Text Encoding Initiative [Online]'' 4. URL: http://jtei.revues.org/697; DOI: 10.4000/jtei.697.

Muñoz, Trevor, Raffaele Viglianti, Neil Fraistat. 2013. “Texts and Documents: new challenges for TEI interchange and the possibilities for participatory archives.” In ''The Linked TEI: Text Encoding in the Web. Abstracts of the TEI Conference and Members Meeting 2013: October 2–5, Rome'', edited by Fabio Ciotti and Arianna Ciula, 99–104. Rome: Digilab Sapienza University & TEI Consortium.

Robinson, Peter. 2013. “Towards a Theory of Digital Editions.” In ''Variants'' 10: 105–31.

Future changes to Best Practices for TEI in Libraries

2013-10-18T12:53:55Z

Martin de la Iglesia: /* reconsider rend="keep-hyphen" */ aw

[[Category:Suggestions]]

This page describes changes to the [https://github.com/sydb/TEI-in-Libraries/issues Best Practices for TEI in Libraries] which will be made at some point but which did not delay release of version 3.0.

<strong>These items will be migrated into the [https://github.com/sydb/TEI-in-Libraries/issues GitHub issue tracker].</strong>

== milestone element ==

<code><milestone unit="typography" n="******"/></code> -- Is this TEI-conformant? Is there a better way to do this in any case?

: This is not TEI conformant, unless you think that "*****" is a valid way of naming something (here this particular milestone). I would suggest
: <code> <milestone type="separator" unit="nonstructural" rend="stars"/> </code>

: Or possibly
: <code><space dim="vertical" extent="[whatever]" rend="stars"/></code>

: Or you could use <ornament> if you have followed tite in adding it. [[User:LouBurnard|LouBurnard]]

:: I agree with Lou that “typography” is not really a unit, and stars are not really a label for the unit, whatever it is. I’m not fond of <tt><space></tt> for this purpose, but perhaps there are convincing arguments I haven’t considered. I quite like
:: <code><milestone type="separator" unit="nonstructural" rend="stars"/></code>
:: except that I think, in general, these units ''are'' structural. So I would prefer <tt>"undetermined"</tt> as the value of <tt>unit=</tt>. [[User:Syd| Syd Bauman ]]

::: Note that these values of @rend do not conform to our general recommendation to use CSS for values of @rend. ([[User:Kshawkin|Kshawkin]] 12:38, 13 November 2011 (EST))

==ref using a URN==

===deprecate key===

The section on "key and ref" needs to be revised so that the Shakespeare example points to a Linked Data URI for this authority record, which is now this would be done now that id.loc.gov is available. Furthermore, the use of <taxonomy> in this example is not even warranted in its current form in the BP, where we recommend it simply to gloss a string used as part of the value of @key even when not for a typology of any sort.

So once both of these things are fixed, the Shakespeare example no longer illustrates a magic token, so a new example should be created that uses a "tag" URI for the value of @target as implemented in P5 in [http://sourceforge.net/tracker/?func=detail&aid=3437509&group_id=106328&atid=644065 feature request 3437509]. Then we will really no longer be recommending use of @key, so the title of this section in the BP should be revised. ([[User:Kshawkin|Kshawkin]] 22:20, 17 June 2012 (EDT))

: An alternative approach would be to use [[Prefix Definition Proposal|a scheme for documenting private URI schemes and similar abbreviated pointing systems as proposed by Martin Holmes to the Technical Council]]. ([[User:Kshawkin|Kshawkin]] 23:05, 13 November 2012 (EST))

===alternative handling of ISBNs===

See outcome of http://purl.org/TEI/fr/3500566 . Solution (e) on this ticket seems especially good for machine processing, though we should probably use ref instead of ptr so that there is a way to represent the ISBN printed on an item (which might not be the real one). See AACR2 for how to represent the stated and known ISBNs.

==The TEI Header==

===breaking out components of MARC 1xx and 7xx subfields ===

Consider whether various MARC 1xx and 7xx subfields could be broken out into components of persName. If so, we'll change recommendations for persName@type.

Separately, we could also simply use <date> within <author> and <editor<. So

<code>
<author><persName>Shakespeare, William, 1564-1616</persName></author>
</code>

would become:

<code>
<author><persName>Shakespeare, William</persName>, <date notBefore="1564" notAfter="1616">1564-1616</date></author>
</code>

===list of elements deleted and changed by our ODDs===

Syd's list of elements is now on a [[List_of_elements_in_P5_header_module_modified_in_ODDs_for_Best_Practices_for_TEI_in_Libraries|different wiki page]] because this page is meant for things to be addressed once version 3.0 is complete. (Which is now entirely out of date. —[[User:Syd|Syd]])

===Identifiers for outside metadata?===

====Pending Issues Discussed====
Should we have a place in the header to indicate an identifier for an outside metadata record for the item? Examples:
* record number for the source document in the local catalog
* record number for the source document in WorldCat
* record number for this TEI document in the local catalog
* record number for this TEI document in WorldCat
Having such a link would allow a delivery system to provide an unambiguous link to this full metadata without relying on matching other information in the header like a title, ISBN, or call number.
([[User:Kshawkin|Kshawkin]])

Yes, I think we should. How about the spot where the TEI Guidelines recommend putting the code for the classification of the text (in some scheme), <tt><classCode></tt> inside <tt><classDec></tt>, or is that too much of a stretch? (—[[User:Syd|Syd]])

: During the call on 2009-02-10, Syd said he no longer thinks use of <tt>classCode</tt> (and a corresponding <tt>classDecl</tt>) is a good idea. Instead, he suggested we createa new element, <tt>otherDesc</tt>, to contain elements from outside the TEI namespace for metadata not covered by the TEI header. The BP could specify how this element is used. ([[User:Kshawkin|Kshawkin]])

NOTE: we talked about this during our conf call on 2009-02-10; we decided to have a sub-group conference call on 2009-02-17 to talk in more detail about this. [[User:Emcaulay|Emcaulay]]

: We didn't get to this on 2009-02-17, so we postponed to 2009-03-03. However, few people showed up, so we postponed again. As Syd put it, there are two issues to consider here:

: A. What mechanism should we use to we point from the TEI header to metadata located outside the TEI document? (For example, how do you identify a MARC, METS, or MODS record that provides additional metadata about the TEI document and/or the source document?)

: B. Should we provide a recommendation on storing non-TEI metadata within the TEI document (using a different element namespace)? For example, should we allow Dublin Core elements anywhere in the TEI header?

<hr />

Email discussions in late March 2009 and early April 2009 with Syd, Melanie, Kevin, Michelle and Glen did not reach a conclusion. Tentative plans for the future would do this sort of thing when an element has the @ref attribute:

<pre>
<author>
<persName xml:id="persName_1" ref="http://authorities.loc.gov/cgi-bin/Pwebrecon.cgi?AuthRecID=1563939&v1=1&HC=1&SEQ=20090404152214&PID=wRSbpUQ7Uptm_ypRikIdNPzF">Welles, Gideon, 1802-1878.</persName>
</author>
</pre>

except that in your example there's no @type or other method for describing the relationship between the content of <persName> and the value of @ref. P5 says that @ref "provides an explicit means of locating a full definition for the entity being named by means of one or more URIs", but we are looking for a typology of some sort for these links and need a place to indicate the type of link.

And we'd do this when there's no @ref:

<pre>
<sourceDesc id="sourceDesc_1">
[. . .]
</sourceDesc>
</pre>

for which you'd find elsewhere in the document:

<pre>
<link type="MARCsource" target="#sourceDesc_1 http://mirlyn.lib.umich.edu/F/?func=direct&doc_number=000601789&local_base=MIU01_PUB"/>
</pre>

link elements might be grouped together in one of these places:

* TEI/teiHeader/profileDesc/creation/ab/linkGrp
* 1st child of <text> last child of <text>
* TEI/text/back/div[@type='editorial']/linkGrp

<hr />

UPDATE: We'll probably use <idno> in various header elements: see https://sourceforge.net/tracker/index.php?func=detail&aid=2493417&group_id=106328&atid=644065 . In any case, we'll need to tell people how much metadata to include in TEI header if they will also have external, possibly canonical, metadata sources.

<hr />

While at the Swinburne conference with John I happen to look over his shoulder while he was encoding and I noticed his use of <tt><relatedItem></tt> in the <tt><biblStruct></tt>: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-relatedItem.html.
You may have come across this already in your break-out meetings, but at a quick glance, the application seems to fit our needs:
<tt><relatedItem></tt> contains or references some other bibliographic item which is related to the present one in some specified manner, for example as a constituent or alternative version of it. John was using it in conjunction with an embedded <tt><note></tt> to provide additional context. <tt><ptr></tt> and <tt><ref></tt> are also valid within <relatedItem>. (—[[User:Mdalmau|Mdalmau]])

: this element is designed to reference a bibliographic item, not another metadata record or a single piece of metadata. So I don't think it's quite right. ([[User:Kshawkin|Kshawkin]])

====Metadata Working Group====
Per discussion at the SIG on Libraries meeting in Ann Arbor (2009-11), Syd [https://list.indiana.edu/sympa/arc/teilib-l/2010-01/msg00000.html put out a call] for members of a working group to look at the relationship between the TEI header and other sources of metadata. This group will formulate recommendations for the TEI Council and/or for the text of the Best Practices. However, as decided a few times in the past, release of the Best Practices will not be held up for this group's work to finish because of the large scope of the work.

====Expressing RDF in TEI====

http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1106&L=TEI-L&T=0&F=&S=&P=15216 (which refers to https://sourceforge.net/tracker/index.php?func=detail&aid=3309894&group_id=106328&atid=644065 , where there is ongoing discussion)

====Use of mets:mdref====

Consider using <mets:mdref> to reference outside metadata.

====New container element?====

A new element might be added to the header to hold non-TEI metadata. See [https://sourceforge.net/p/tei/feature-requests/453/ feature request 453].

===extent element===

Instead of

<pre>
<extent>viii, [7]-215 p</extent>
<extent>20 cm.</extent>
</pre>

we might use elements from the msDescription module and do it this way:

<pre>
<extent>viii, [7]-215 p</extent>
<extent>
<height quantity="20" unit="cm"/>
</extent>
</pre>

Had a width been given for this item in the catalog record, in the header it would have been:

<pre>
<extent>viii, [7]-215 p</extent>
<extent>
<width quantity="30" unit="cm"/>
<height quantity="20" unit="cm"/>
</extent>
</pre>

=== appInfo and application ===

Consider inclusion of these elements in the header. Lou wrote, "There is at least one proposal forthcoming for further work on defining the scope and usage of these elements". Wait for these proposals to make their way into P5 before revisiting this question.

=== children of editorialDecl ===

Per [http://sourceforge.net/tracker/index.php?func=detail&aid=2878062&group_id=106328&atid=644062 a change in P5], editorialDecl can now have mixed content of <p>s and specialized elements like <hyphenation>. Revisit our decision to put all content into <p>s and come up with recommended uses for specialized elements.

=== respStmt within imprint ===

Per https://sourceforge.net/tracker/?func=detail&aid=3408897&group_id=106328&atid=644065, P5 will soon allow respStmt within imprint for printer, distributor, etc. Consider recommending this as well, which will require us to dissasiate the BP with version 1.9.1 of P5. Note will be difficult to map from MARC 260 $b.

==indicating interviewers and interviewees==

Section “Level 4 Oral History” currently recommends that the speaking participants in the interview be identified is as authors of the document, or in profileDesc/particDesc/list/item/name. In the example encoding of this interviewees and interviewers are differentiated as text inside the given <tt><item></tt>. This strikes me as sloppy. It may well be appropriate to '''permit''' this encoding, in case someone is digitizing hundreds of interviews and has OCRed metadata that lists the participants this way. But certainly a '''best''' practice would make use of <tt><listPerson></tt>, and explicitly indicate <tt>"interviewer"</tt>, <tt>"interviewee"</tt>, <tt>"thirdParty"</tt> (or whatever) on the <tt>role=</tt> of <tt><person></tt>, no? —[[User:Syd|Syd]]

== encoding <pb>s within <note>s ==

Give guidance on encoding of <pb/>s within <note>s. Should these be encoded or omitted, with the <note> element appearing in the XML "within" the page on which it began? (Note that the BP allows for local practice in gathering all notes for a given section to a div at the end of the section.)

If encoding such <pb/>s will be optional or required, there will generally be two instances of <pb n="X"/> every time a note crosses a page boundary. Should we recommend use of @sameAs or @corresp to indicate that you are encoding the same page break twice? See [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1011&L=TEI-L&T=0&F=&S=&P=9746 this thread on TEI-L].

== bibliographies and other lists of works cited ==

We give no guidance on encoding bibliographies, lists of works cited, lists of references, and other such things in documents. In TEI, you would use listBibl for this. We need to decide:

# Whether to include this in the BP and at which level
# Whether to use bibl, biblStruct, or biblFull inside the list. (I strongly argue for bibl for faithfully source documents.)
# Since listBibl can include a head, the listBibl element could be a sibling of a div in TEI. However, this would go against the BP, which says to use divs for everything. So should listBibl go inside a div? If so, should the head be a child of listBibl (as in TEI) or of the div (to be consistent with other parts of the BP)?

([[User:Kshawkin|Kshawkin]] 12:45, 14 July 2011 (EDT))

== providing stylesheets ==

MARCXML <--> teiHeader
: [http://www.blackmesatech.com/ Black Mesa Technologies] has undertaken this work for us (gratis)!

MODS <--> teiHeader

Tite --> Level 3.5 (Syd's recommendation)
: Syd said in Wuerzburg in October 2011 that he would do this. ([[User:Kshawkin|Kshawkin]] 15:08, 13 November 2011 (EST))

== providing tools ==

providing tools for workflows

== mention RDA ==

The section "Determining Data Values for the TEI Header" mentions AACR2 and ISBD(ER). Perhaps also mention RDA?

== how to record non-ASCII characters ==

People often want to know what to do with non-ASCII characters. There are generally four options:

* insert them as they are (and assume the files will be manipulated by Unicode-aware software and that people can distinguish these from similar characters)
* insert decimal entity references
* insert hexadecimal entity references
* insert mneumonic entity references (which need to be declared)

We should give advice on this.

== add <distinct> to Level 4 ==

Consider adding [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-distinct.html distinct] to Level 4.
[[Category:SIG:Libraries]]

== METS profile? ==

The section on linking between page images and the TEI document does not advise on use of any particular METS profile. Consider developing one, especially one that would work with [http://dfg-viewer.de/ DFG-Viewer] since this tool can be used to view any METS object regardless of where it's hosted. Torsten Schaßen developed a METS profile for manuscripts for the DFG-Viewer that uses the TEI header (as opposed to the regular book profile, which uses MODS).

== Guidance on encoding serials? ==

People often ask how to handle encoding of serials. Should you have a single TEI document for the whole journal run, for individual volumes, for individual issues, or for individual articles? How do you encode metadata about the serial as a whole, issues, and article?

== How to indicate conformance to the BP? ==

In TEI, you typically use editorialDecl to say things about your specific use of the TEI. We use @n to say which encoding level you follow. And we have various p elements to describe encoding practices. But we have no place to say that the @n refers to the BP or that you follow the BP at all. We really should have this.

: You could refer to a schema using http://www.w3.org/TR/xml-model/ . Still need a mechanism to point to the ODD and/or prose documentation. This is part of a larger problem in the TEI. ([[User:Kshawkin|Kshawkin]] 17:02, 7 November 2011 (EST))

== @rend vs. @html:style for CSS values ==

In TEI, the value of @rend is data.word+. James Cummings [http://lists.village.virginia.edu/pipermail/tei-council/2011/014431.html wrote in an email to tei-council], "While it is true that the order of data.word+ is significant and important they are meant to be individual tokens that do not necessarily have any relation to each other." (More [http://blogs.oucs.ox.ac.uk/jamesc/2011/12/01/rend-and-the-war-on-text-bearing-attributes/ on James's blog].) More specifically, there's nothing that says that data.word+ must be interpreted as discrete tokens with no relation to each other, but many programmers find it obvious that a set of token words will be an unordered set. This is problematic if you use give CSS property-value pairs in the value of @rend. So Sebastian suggested that in the BP we use @html:style instead. This way we could continue using non-CSS values of @rend for hyphenation without violating our own recommendation.

:I'm not sure if I get this right: do you mean, the problem is that the property and the value of a property-value pair are interpreted separately because of the whitespace between them? If so, why don't you simply omit this whitespace? Besides, @html:style seems to be something very different, semantically, than @rend, so I don't think this would be a suitable alternative. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:18, 10 January 2012 (EST)

:: CSS syntax, like XML syntax, disregards whitespace, so things like "font-align: right" and "font-align:right" are equivalent. Right now the BP is written to assume that any valid CSS could be put in @rend, so we'd have to change it to say something like "use any valid CSS but remove all whitespace". If we did this, it would basically fix the problem, as you say.

:: You're right that @rend and @html:style currently have different semantics since @rend allows any description of appearance whereas @html:style requires use of the CSS vocabulary and syntax. However, the BP essentially redefines use of @rend to make it semantically equivalent to @html:style, so it seems more transparent to simply use @html:style.

:: --[[User:Kshawkin|Kshawkin]] 20:55, 13 January 2012 (EST)
:::OK, but I think this problem doesn't really affect the examples over at [[User talk:Martin de la Iglesia/A Guide to Images in TEI|A Guide to Images in TEI]], which are more about the coordinate system used, rather then the attribute. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 03:59, 16 January 2012 (EST)

== Rework Level 1 and Level 2 structure? ==

Consider one of two ways to rework the encoding at Levels 1 and 2:

A) Kevin suggests removing the wrapper div1 and ab elements, leaving the OCR text in the body element. This would make it easier to upgrade documents to a higher level (because you wouldn't need to remove tags but could simply insert new ones.

B) Instead of putting the whole text in a single ab element, use one ab for each page, Lou suggests this:

<pre>
<div1>
<ab n="[pageno]" facs="00000001.tif">

</ab>
<ab n="[pageno]" facs="00000002.tif">

</ab>

</div1>
</pre>

Then you wouldn't even need the pb element. But upgrading such a document to Level 3 would require significant reworking.

== pb@xml:id and METS ==

The sentence:

Use the @xml:id attribute on each <pb> element and a METS document to provide correspondence between <pb> elements and one or more facsimile page images (e.g., master, web derivatives, etc.).

isn't very clear. Is the value of each pb@xml:id also included somewhere in the METS document? If so, where exactly?

== revised display examples for levels 3 and 4 ==

The display example for Level 3 has texts with lots of features not found in Level 3 and is of oral transcriptions, which don't have a clear source document. For clarity, I suggest we instead link to http://name.umdl.umich.edu/abu0246.0001.001 as a display example for Level 3 and http://webapp1.dlib.indiana.edu/vwwp/view?docId=VAB7020.xml for Level 4.

== reconsider rend="keep-hyphen" ==

The @rend value "keep-hyphen" was meant to mean "keep the hyphen when tokenizing", not "keep the hyphen when rendering" as it appears from a quick read. It's also misleading to use @tei:rend to distinguish soft and hard hyphens when these can't be distinguished by the appearance in the source document (as @tei:rend is meant for). Consider revising this attribute value.

: Conal Tuohy proposes encoding a "hard" hyphen (such as in "so-called") as an actual hyphen in the source text (without the need for any XML markup around it), and a "soft" hyphen as <code><lb rend="hyphen"/></code> (noting that a line-break was rendered in the source document).

: See http://purl.org/TEI/fr/3523225 .

::Just for the record: my current suggested solution for encoding "hard" hyphens is <code><lb break="keepHyphen"/></code>, because I think @break is where this information fits best, semantically. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 08:53, 18 October 2013 (EDT)

== new section on metadata for "analytic item" (articles within a volume of conference proceedings or within a journal issue) ==

People often ask on TEI-L how to encode metadata for parts of a larger TEI document, and these questions largely come from the library community. See, for example, [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1209&L=TEI-L&F=&S=&P=52762 this thread]. We should give guidance here.

SIG Text and Graphics 2013 meeting

2013-10-16T10:31:08Z

Martin de la Iglesia: added minutes

at TEI Members' Meeting in Rome, Italy, October 2-5, 2013

'''when''': Thursday 3 October, 14.30

'''where''': Room 117

== Agenda / Minutes ==
* introductions - areas of interest mentioned:
** graphic design (leaflets) - how to edit?
** (newspaper) websites - how to archive, including pictorial content?
** critical editions, particularly with regard to images - how to link different readings to images?
* TEI Boilerplate facsimile demo
** John Walsh demonstrated TEI Boilerplate; see http://teiboilerplate.org/ and also https://github.com/GrantLS/TEI-Boilerplate.
* 'A Guide to Images in TEI'
** Martin de la Iglesia explained difference between the comprehensive [[User_talk:Martin_de_la_Iglesia/A_Guide_to_Images_in_TEI|'Guide']] and a more concise proposed Images [[TEI_Cheatsheets|Cheatsheet]]; meeting participants expressed interest in seeing both resources developed.
* open discussion of the facsimile chapter/elements
** "tokenization in images": if one wants to link text tokens to the corresponding areas in the facsimile, how can one avoid drawing boxes manually?
** The @points attribute seems to be missing from the <surface> element, although it would make sense to have it there. A feature request will be considered.

SIG Text and Graphics 2013 meeting

2013-09-30T14:19:34Z

Martin de la Iglesia: /* Agenda */ formatting

at TEI Members' Meeting in Rome, Italy, October 2-5, 2013

'''when''': Thursday 3 October, 14.30

'''where''': Room 117

== Agenda ==
* introductions
* TEI Boilerplate facsimile demo
* 'A Guide to Images in TEI'
* open discussion of the facsimile chapter/elements
* ...

SIG Text and Graphics 2013 meeting

2013-09-30T14:05:06Z

Martin de la Iglesia: page created, agenda added

at TEI Members' Meeting in Rome, Italy, October 2-5, 2013

'''when''': Thursday 3 October, 14.30

'''where''': Room 117

== Agenda ==
* Introductions
* TEI Boilerplate facsimile demo
* 'A Guide to Images in TEI'
* open discussion of the facsimile chapter/elements
* ...

SIG:Text&Graphic

2013-09-30T13:52:41Z

Martin de la Iglesia: /* Meetings */ added link to 2013 meeting page

= 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, [mailto:mdelaig@sub.uni-goettingen.de mdelaig@sub.uni-goettingen.de]<br/>
John Walsh, [mailto:jawalsh@indiana.edu 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.
* [[SIG Text and Graphics 2013 meeting|TEI Members' Meeting in Rome, Italy, October 2-5, 2013.]]

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

==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 ==

[[FacsimileMarkup|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.

[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX TEI Guidelines 11.1, Digital Facsimiles]: Description of Facsimile markup in TEI P5

== A Guide to Images in TEI ==
[[User_talk:Martin_de_la_Iglesia/A_Guide_to_Images_in_TEI|This page]] is a proposal for a specialized tutorial. Please contribute and discuss.

[[Category:SIG|Text]]

User talk:Martin de la Iglesia/A Guide to Images in TEI

2013-09-19T10:23:58Z

Martin de la Iglesia: /* Image Metadata */ added link to current TEI-L discussion

==General==
===Suggested use of this page===
The idea is to start by filling in the different chapters in [[User_talk:Martin_de_la_Iglesia/A_Guide_to_Images_in_TEI#Outline|Outline]] below. In the beginning, I think it makes sense to do this in a Discussion page, in order to avoid switching back and forth between the Article and the Discussion page all the time. After some time we can move the text from the Discussion page to my namespace, then after some more consolidation to the main wiki. Finally, we could move it to an entirely different website if we found the TEI Wiki unsuitable. However, feel free to suggest other procedures, or maybe an entirely different environment for working on this resource altogether. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:47, 2 December 2011 (EST)
===Title===
The title of this page (currently: "A Guide to Images in TEI") is just a working title. Feel free to suggest alternative titles. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:47, 2 December 2011 (EST)
===Related resources===
We should think about how this resource relates to [[TEI to SVG]] (and maybe other relevant pages/resources), and whether and how this information should be integrated here. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:47, 2 December 2011 (EST)

Is there a need for a [[TEI Cheatsheets|TEI Cheatsheet]] for images? I imagine such a cheatsheet as a more concise and practical version of this Guide. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:59, 5 August 2013 (EDT)

==Outline==
===Aims and Scope===
We should have a text here which explains what this resource is for and how it differs from the TEI Guidelines. In the meantime, I paste my announcement e-mail to the SIG Text & Graphics mailing list from December 1, 2011:

:[...]
:I learned in Würzburg that some other SIGs are planning to create specialized tutorials that cover aspects relevant to the respective SIG's scope which are not already covered by general introductory TEI resources like TEI By Example. This sounds like a good idea for our SIG, too. I'm aware that, basically, the solutions are all in the TEI Guidelines somewhere, but as we all know, it can be quite tough to make encoding decisions by only consulting the Guidelines. This is especially true for the encoding of graphics-related information, which, as far as I have seen, is not well covered by TEI By Example.

:In addition to the examples given by John, I'd like this new FAQ/Tutorial to tackle basic questions such as
:- how to encode the position of images on a page
:- how to link images to text
:- how to align images with portions of text or vice versa
:- how to encode descriptions of images or other image metadata
:etc.
:So what I'm envisioning is a sort of beginner's guide to handling images in TEI, either as a FAQ (i.e. self-contained chapters) or a step-by-step Tutorial (i.e. "what to do when you encounter an image in your text"). As John already mentioned, integration into TEI By Example might also be a possibility (although I haven't discussed this idea with the TEI By Example people yet).
:[...]

--[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:11, 5 December 2011 (EST)

===Basic Integration of Images/Linking to Images===
John (Walsh) suggested covering the <figure> tag. Additionally, it might be useful to have a general discussion on image types (binary vs. SVG vs. characters (i.e. trying to find matching Unicode characters for special symbols instead of integrating them as images)) and the different encoding practices they imply. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:18, 5 December 2011 (EST)
====Examples====
Here's an example of different encodings for the same image. The image I'd like to represent is the wedge-shaped marking that indicates that the word "war" is to be inserted into the line below.

[[File:Fontane-30633-detail.jpg|200px]]
* binary: the marking is extracted from the scan and provided as a separate file which is pointed to in the TEI code and displayed at the appropriate position in the transcribed text.
[[File:Fontane-30633-detail2.png|75px]]<pre><nowiki>
<figure><graphic url="myfilename.png"/></figure>
</nowiki></pre>
'''pro:''' representing an image through a digital image results in probably the strongest resemblance to the original image. '''con:''' it is quite a lot of work to extract the image from the scan; the TEI code provides hardly any semantics or searchability (except for the filename, or additional information in <figure>); the image can be difficult to align and position, especially if other reference points than the upper left corner of the image are to be used (see according sections) - anchor points generated by e.g. the Text Image Link Editor in TextGrid might provide a workaround for this problem.

* SVG: an SVG drawing is designed that resembles the original image. Simplified measurements, obtained from measuring the image on the original page or its facsimile, are provided in the TEI code, from which the SVG is created by a transformation stylesheet.
<pre><nowiki>
<svg xmlns="http://www.w3.org/2000/svg" width="0.9cm" height="1em">
<line x1="0" y1="0" x2="0.3cm" y2="1em" style="stroke:black; stroke-width:2px;" />
<line x1="0.3cm" y1="1em" x2="0.9cm" y2="0" style="stroke:black; stroke-width:2px;" />
</svg>
</nowiki></pre>
<pre><nowiki>
<figure rend="marking_V(left:0.3cm;right:0.6cm)"/>
</nowiki></pre>
This TEI code indicates that it's a "V"-shaped marking, with a left side of 3 mm width and a right side of 6 mm width. (The height is fixed at 1 em.) From these measurements, the SVG code above is created during transformation.

--[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:27, 5 January 2012 (EST)

=====Examples of different methods for other images=====

* direct extraction from facsimile: this only works when writing and image are not as closely intertwined as in the example above. If coordinates are provided, the image can be extracted from the facsimile (the location of which is provided in <surface @facs>) on transformation and placed correctly in between the transcription of the surrounding writing.
<pre><nowiki>
<zone ulx="123" uly="234" lrx="345" lry="456">
<figure>...</figure>
</zone>
</nowiki></pre>
These coordinates represent pixels in the facsimile file. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 08:11, 5 August 2013 (EDT)

* simple line drawings: coordinates in <zone> provide information on the position, length and angle of lines such as horizontal rules that divide sections of text.

<pre><nowiki>
<zone ulx="1.2" uly="6.7" lrx="5.6" lry="6.9">
<figure type="line_drawing"/>
</zone>
</nowiki></pre>

These coordinates describe a horizontal line of about 4 1/2 centimetres length with a slight slope, which can be drawn e.g. in SVG on transformation. '''con:''' the difference between the @lry and @uly values is ambiguous, as it can be interpreted as either width or angle. The respective missing value should be provided as well, e.g. in <figure @rend> or <zone @rotate>. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 08:30, 5 August 2013 (EDT)

===Linking to Facsimile Page Images===
This is another topic suggested by John ("using <facsimile> and @facs to link to facsimile page images"). --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:23, 5 December 2011 (EST)

You might draw upon [http://www.tei-c.org/SIG/Libraries/teiinlibraries/main-driver.html#txtimglnk this section] of the [http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries]. ([[User:Kshawkin|Kshawkin]] 08:26, 2 December 2011 (EST))
:Thanks, Kevin. I wasn't aware of that section. There's one thing I don't understand about the third approach: in the sample METS document, which is the ID that is used in @xml:id in the TEI code? --[[User:Martin de la Iglesia|Martin de la Iglesia]] 05:35, 7 December 2011 (EST)

:: Hmm, I agree that the recommendation isn't at all clear, and I actually don't know METS very well. I've made a note to revisit this in a future revision to the Best Practices. In the meantime, if you know METS well, you might look at the sample METS document linked to from the Best Practices. If that doesn't clarify, I'd contact my coeditor Michelle Dalmau: I think she will know. --[[User:Kshawkin|Kshawkin]] 10:04, 12 December 2011 (EST)
:::Thanks again. Michelle explained it to me and now I see the usefulness of this method, at least in some projects. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 09:47, 21 December 2011 (EST)

===Positioning an Image===
What I'd like to see here is a discussion of the <surface>/<zone> coordinate positioning system vs. <ptr>-like positioning solutions, and maybe of other systems as well (e.g. lines and margin for y and x axis positioning). --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:28, 5 December 2011 (EST)
====Examples====
* metric margins in CSS style for x and y axis starting points, counting from leaf borders (height and width are determined by the figure itself): <pre><figure style="margin-left:1.2cm; margin-top:3.4cm">...</figure></pre>
* CSS style margins in percent: <pre><figure style="margin-left:12%; margin-top:34%">...</figure></pre>
* CSS style margins in lines for y axis (not valid CSS, but line alignment can be important in some cases): <pre><figure style="margin-left:1.2cm" rend="margin-top:7lines">...</figure></pre> (i.e. the image starts in line 8)
* added height and width:
<pre><nowiki>
<figure style="margin-left:1.2cm; margin-top:3.4cm">
<figDesc>
<dimensions>
<height quantity="123" unit="mm"/>
<width quantity="75" unit="mm"/>
</dimensions>
</figDesc>
</figure>
</nowiki></pre>
--[[User:Martin de la Iglesia|Martin de la Iglesia]] 05:21, 4 January 2012 (EST)

: On the use of CSS in @rend, see [[Future_changes_to_Best_Practices_for_TEI_in_Libraries#.40rend_vs._.40html:style_for_CSS_values|this discussion]]. ([[User:Kshawkin|Kshawkin]] 18:24, 6 January 2012 (EST))
::Thanks, Kevin, I wasn't aware of that. See my comment there. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:18, 10 January 2012 (EST)

::Alright, so we should add that there might be a problem with whitespaces in CSS style values, and that @html:style can be used as an alternative to @rend. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:03, 16 January 2012 (EST)
:::Substituted @rend with @style where applicable. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 05:19, 2 August 2013 (EDT)

* coordinates in <zone> (or <surface> where applicable); coordinate values follow the system employed in the TEI document (here: centimeters):
<pre><nowiki>
<zone ulx="1.2" uly="0.5" lrx="3.5" lry="7.1">
<figure>...</figure>
</zone>
</nowiki></pre>
--[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:39, 5 August 2013 (EDT)

===Image-Text Linking===
This section should cover the encoding of different kinds of image-text relationships (e.g. an image illustrating a text paragraph, or a text paragraph describing an image), other than merely topographical ones which are covered in the following section, Image-Text Alignment. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:40, 5 December 2011 (EST)

* using <zone> elements to associate text with images: as the example in the next section, this example refers to the image pictured in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html#FTNM] in the TEI Guidelines:

<pre><nowiki>
<zone>67. We now give some examples, from the works of the great masters, of some of the most frequently used bowings.</zone>
<zone>
<figure>...</figure>
<zone>Ex. 8. Andante con moto.</zone>
<zone>SCHUBERT : Symphony in B minor.</zone>
<zone>pp</zone>
<zone>fp</zone>
</zone>
</nowiki></pre>

In this case, the second <zone> element which contains both the <figure> element and other <zone> elements with text suggest that the text and the image belong together. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 08:58, 5 August 2013 (EDT)

===Image-Text Alignment===
How to position text relative to an image, or an image relative to text (including special cases such as an image pointing at a character, or an image pointing at two separate characters) should be covered here. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:43, 5 December 2011 (EST)
* Here's an example of the latter case: in the following part of a scan from a 19th century German manuscript, a line connects two separate paragraphs. I'd be happy to represent this in the transcript as a straight SVG line that goes roughly from the word "Nissen" to "wird", but how to encode (and XSL-transform) this?
[[File:Fontane-30621-detail.jpg|200px]]

--[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:33, 21 December 2011 (EST)

* line numbers for images - this is an issue in editions in general and not specific to TEI, but still: if there's an image spanning the whole width of a page, and which is preceded and followed by writing, how does it fit in an editorial line numbering system? Should the image have its own line number, or should the image be ignored when numbering the regular text lines? --[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:53, 5 August 2013 (EDT)

* This example of positioning transcribed writing within an image using coordinate attributes in <zone> refers to the image pictured in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html#FTNM] in the TEI Guidelines:

<pre><nowiki>
<zone ulx="18" uly="50" lrx="489" lry="118">
<figure>...</figure>
<zone ulx="29" uly="51">Ex. 8. Andante con moto.</zone>
<zone ulx="298" uly="50">SCHUBERT : Symphony in B minor.</zone>
<zone ulx="66" uly="106">pp</zone>
<zone ulx="341" uly="106">fp</zone>
</zone>
</nowiki></pre>

(coordinate values in pixels) --[[User:Martin de la Iglesia|Martin de la Iglesia]] 08:47, 5 August 2013 (EDT)

===Image Metadata===
I'm thinking primarily of content description texts, but we could embed this in a general discussion of how (or whether) to encode any "invisible" aspects of images. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:34, 5 December 2011 (EST)
* classification in @type:
<pre><nowiki>
<figure type="floor_plan">...</figure>
</nowiki></pre>
Are there any suitable vocabularies that could be used for this kind of indexing? --[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:47, 5 August 2013 (EDT)
* See also the TEI-L thread [http://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;16c70b50.1309|"Storing image metadata in TEI files"] starting from September 18, 2013, which discusses <facsimile> and <graphic> elements, XMP, EXIF and VRA.

SIG:Text&Graphic

2013-09-05T09:28:23Z

Martin de la Iglesia: changed structure, added section/link

= 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, [mailto:mdelaig@sub.uni-goettingen.de mdelaig@sub.uni-goettingen.de]<br/>
John Walsh, [mailto:jawalsh@indiana.edu 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<br/>
To post to list: [mailto:tei-graphics-sig@listserv.brown.edu tei-graphics-sig@listserv.brown.edu]<br/>
To send mail to list owners: [mailto:tei-graphics-sig-request@listserv.brown.edu tei-graphics-sig-request@listserv.brown.edu]<br/>

==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 ==

[[FacsimileMarkup|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.

[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX TEI Guidelines 11.1, Digital Facsimiles]: Description of Facsimile markup in TEI P5

== A Guide to Images in TEI ==
[[User_talk:Martin_de_la_Iglesia/A_Guide_to_Images_in_TEI|This page]] is a proposal for a specialized tutorial. Please contribute and discuss.

[[Category:SIG|Text]]

User talk:Martin de la Iglesia/A Guide to Images in TEI

2013-09-05T09:00:40Z

Martin de la Iglesia: /* Examples */ TEI code example updated

User talk:Martin de la Iglesia/A Guide to Images in TEI

2013-08-05T12:58:16Z

Martin de la Iglesia: /* Image-Text Linking */ added example

==General==
===Suggested use of this page===
The idea is to start by filling in the different chapters in [[User_talk:Martin_de_la_Iglesia/A_Guide_to_Images_in_TEI#Outline|Outline]] below. In the beginning, I think it makes sense to do this in a Discussion page, in order to avoid switching back and forth between the Article and the Discussion page all the time. After some time we can move the text from the Discussion page to my namespace, then after some more consolidation to the main wiki. Finally, we could move it to an entirely different website if we found the TEI Wiki unsuitable. However, feel free to suggest other procedures, or maybe an entirely different environment for working on this resource altogether. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:47, 2 December 2011 (EST)
===Title===
The title of this page (currently: "A Guide to Images in TEI") is just a working title. Feel free to suggest alternative titles. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:47, 2 December 2011 (EST)
===Related resources===
We should think about how this resource relates to [[TEI to SVG]] (and maybe other relevant pages/resources), and whether and how this information should be integrated here. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:47, 2 December 2011 (EST)

Is there a need for a [[TEI Cheatsheets|TEI Cheatsheet]] for images? I imagine such a cheatsheet as a more concise and practical version of this Guide. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:59, 5 August 2013 (EDT)

==Outline==
===Aims and Scope===
We should have a text here which explains what this resource is for and how it differs from the TEI Guidelines. In the meantime, I paste my announcement e-mail to the SIG Text & Graphics mailing list from December 1, 2011:

:[...]
:I learned in Würzburg that some other SIGs are planning to create specialized tutorials that cover aspects relevant to the respective SIG's scope which are not already covered by general introductory TEI resources like TEI By Example. This sounds like a good idea for our SIG, too. I'm aware that, basically, the solutions are all in the TEI Guidelines somewhere, but as we all know, it can be quite tough to make encoding decisions by only consulting the Guidelines. This is especially true for the encoding of graphics-related information, which, as far as I have seen, is not well covered by TEI By Example.

:In addition to the examples given by John, I'd like this new FAQ/Tutorial to tackle basic questions such as
:- how to encode the position of images on a page
:- how to link images to text
:- how to align images with portions of text or vice versa
:- how to encode descriptions of images or other image metadata
:etc.
:So what I'm envisioning is a sort of beginner's guide to handling images in TEI, either as a FAQ (i.e. self-contained chapters) or a step-by-step Tutorial (i.e. "what to do when you encounter an image in your text"). As John already mentioned, integration into TEI By Example might also be a possibility (although I haven't discussed this idea with the TEI By Example people yet).
:[...]

--[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:11, 5 December 2011 (EST)

===Basic Integration of Images/Linking to Images===
John (Walsh) suggested covering the <figure> tag. Additionally, it might be useful to have a general discussion on image types (binary vs. SVG vs. characters (i.e. trying to find matching Unicode characters for special symbols instead of integrating them as images)) and the different encoding practices they imply. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:18, 5 December 2011 (EST)
====Examples====
Here's an example of different encodings for the same image. The image I'd like to represent is the wedge-shaped marking that indicates that the word "war" is to be inserted into the line below.

[[File:Fontane-30633-detail.jpg|200px]]
* binary: the marking is extracted from the scan and provided as a separate file which is pointed to in the TEI code and displayed at the appropriate position in the transcribed text.
[[File:Fontane-30633-detail2.png|75px]]<pre><nowiki>
<figure><graphic url="myfilename.png"/></figure>
</nowiki></pre>
'''pro:''' representing an image through a digital image results in probably the strongest resemblance to the original image. '''con:''' it is quite a lot of work to extract the image from the scan; the TEI code provides hardly any semantics or searchability (except for the filename, or additional information in <figure>); the image can be difficult to align and position, especially if other reference points than the upper left corner of the image are to be used (see according sections) - anchor points generated by e.g. the Text Image Link Editor in TextGrid might provide a workaround for this problem.

* SVG: an SVG drawing is designed that resembles the original image. Simplified measurements, obtained from measuring the image on the original page or its facsimile, are provided in the TEI code, from which the SVG is created by a transformation stylesheet.
<pre><nowiki>
<svg xmlns="http://www.w3.org/2000/svg" width="0.9cm" height="1em">
<line x1="0" y1="0" x2="0.3cm" y2="1em" style="stroke:black; stroke-width:2px;" />
<line x1="0.3cm" y1="1em" x2="0.9cm" y2="0" style="stroke:black; stroke-width:2px;" />
</svg>
</nowiki></pre>
<pre><nowiki>
<figure rend="marking_V(left:0.3cm;right:0.6cm)"/>
</nowiki></pre>
This TEI code indicates that it's a "V"-shaped marking, with a left side of 3 mm width and a right side of 6 mm width. (The height is fixed at 1 em.) From these measurements, the SVG code above is created during transformation.

--[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:27, 5 January 2012 (EST)

=====Examples of different methods for other images=====

* direct extraction from facsimile: this only works when writing and image are not as closely intertwined as in the example above. If coordinates are provided, the image can be extracted from the facsimile (the location of which is provided in <surface @facs>) on transformation and placed correctly in between the transcription of the surrounding writing.
<pre><nowiki>
<zone ulx="123" uly="234" lrx="345" lry="456">
<figure>...</figure>
</zone>
</nowiki></pre>
These coordinates represent pixels in the facsimile file. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 08:11, 5 August 2013 (EDT)

* simple line drawings: coordinates in <zone> provide information on the position, length and angle of lines such as horizontal rules that divide sections of text.

<pre><nowiki>
<zone ulx="1.2" uly="6.7" lrx="5.6" lry="6.9">
<figure type="line_drawing"/>
</zone>
</nowiki></pre>

These coordinates describe a horizontal line of about 4 1/2 centimetres length with a slight slope, which can be drawn e.g. in SVG on transformation. '''con:''' the difference between the @lry and @uly values is ambiguous, as it can be interpreted as either width or angle. The respective missing value should be provided as well, e.g. in <figure @rend> or <zone @rotate>. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 08:30, 5 August 2013 (EDT)

===Linking to Facsimile Page Images===
This is another topic suggested by John ("using <facsimile> and @facs to link to facsimile page images"). --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:23, 5 December 2011 (EST)

You might draw upon [http://www.tei-c.org/SIG/Libraries/teiinlibraries/main-driver.html#txtimglnk this section] of the [http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries]. ([[User:Kshawkin|Kshawkin]] 08:26, 2 December 2011 (EST))
:Thanks, Kevin. I wasn't aware of that section. There's one thing I don't understand about the third approach: in the sample METS document, which is the ID that is used in @xml:id in the TEI code? --[[User:Martin de la Iglesia|Martin de la Iglesia]] 05:35, 7 December 2011 (EST)

:: Hmm, I agree that the recommendation isn't at all clear, and I actually don't know METS very well. I've made a note to revisit this in a future revision to the Best Practices. In the meantime, if you know METS well, you might look at the sample METS document linked to from the Best Practices. If that doesn't clarify, I'd contact my coeditor Michelle Dalmau: I think she will know. --[[User:Kshawkin|Kshawkin]] 10:04, 12 December 2011 (EST)
:::Thanks again. Michelle explained it to me and now I see the usefulness of this method, at least in some projects. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 09:47, 21 December 2011 (EST)

===Positioning an Image===
What I'd like to see here is a discussion of the <surface>/<zone> coordinate positioning system vs. <ptr>-like positioning solutions, and maybe of other systems as well (e.g. lines and margin for y and x axis positioning). --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:28, 5 December 2011 (EST)
====Examples====
* metric margins in CSS style for x and y axis starting points, counting from leaf borders (height and width are determined by the figure itself): <pre><figure style="margin-left:1.2cm; margin-top:3.4cm">...</figure></pre>
* CSS style margins in percent: <pre><figure style="margin-left:12%; margin-top:34%">...</figure></pre>
* CSS style margins in lines for y axis (not valid CSS, but line alignment can be important in some cases): <pre><figure style="margin-left:1.2cm" rend="margin-top:7lines">...</figure></pre> (i.e. the image starts in line 8)
* added height and width:
<pre><nowiki>
<figure style="margin-left:1.2cm; margin-top:3.4cm">
<figDesc>
<dimensions>
<height quantity="12.3" unit="cm"/>
<width quantity="7.5" unit="cm"/>
</dimensions>
</figDesc>
</figure>
</nowiki></pre>
--[[User:Martin de la Iglesia|Martin de la Iglesia]] 05:21, 4 January 2012 (EST)

: On the use of CSS in @rend, see [[Future_changes_to_Best_Practices_for_TEI_in_Libraries#.40rend_vs._.40html:style_for_CSS_values|this discussion]]. ([[User:Kshawkin|Kshawkin]] 18:24, 6 January 2012 (EST))
::Thanks, Kevin, I wasn't aware of that. See my comment there. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:18, 10 January 2012 (EST)

::Alright, so we should add that there might be a problem with whitespaces in CSS style values, and that @html:style can be used as an alternative to @rend. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:03, 16 January 2012 (EST)
:::Substituted @rend with @style where applicable. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 05:19, 2 August 2013 (EDT)

* coordinates in <zone> (or <surface> where applicable); coordinate values follow the system employed in the TEI document (here: centimeters):
<pre><nowiki>
<zone ulx="1.2" uly="0.5" lrx="3.5" lry="7.1">
<figure>...</figure>
</zone>
</nowiki></pre>
--[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:39, 5 August 2013 (EDT)

===Image-Text Linking===
This section should cover the encoding of different kinds of image-text relationships (e.g. an image illustrating a text paragraph, or a text paragraph describing an image), other than merely topographical ones which are covered in the following section, Image-Text Alignment. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:40, 5 December 2011 (EST)

* using <zone> elements to associate text with images: as the example in the next section, this example refers to the image pictured in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html#FTNM] in the TEI Guidelines:

<pre><nowiki>
<zone>67. We now give some examples, from the works of the great masters, of some of the most frequently used bowings.</zone>
<zone>
<figure>...</figure>
<zone>Ex. 8. Andante con moto.</zone>
<zone>SCHUBERT : Symphony in B minor.</zone>
<zone>pp</zone>
<zone>fp</zone>
</zone>
</nowiki></pre>

In this case, the second <zone> element which contains both the <figure> element and other <zone> elements with text suggest that the text and the image belong together. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 08:58, 5 August 2013 (EDT)

===Image-Text Alignment===
How to position text relative to an image, or an image relative to text (including special cases such as an image pointing at a character, or an image pointing at two separate characters) should be covered here. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:43, 5 December 2011 (EST)
* Here's an example of the latter case: in the following part of a scan from a 19th century German manuscript, a line connects two separate paragraphs. I'd be happy to represent this in the transcript as a straight SVG line that goes roughly from the word "Nissen" to "wird", but how to encode (and XSL-transform) this?
[[File:Fontane-30621-detail.jpg|200px]]

--[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:33, 21 December 2011 (EST)

* line numbers for images - this is an issue in editions in general and not specific to TEI, but still: if there's an image spanning the whole width of a page, and which is preceded and followed by writing, how does it fit in an editorial line numbering system? Should the image have its own line number, or should the image be ignored when numbering the regular text lines? --[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:53, 5 August 2013 (EDT)

* This example of positioning transcribed writing within an image using coordinate attributes in <zone> refers to the image pictured in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html#FTNM] in the TEI Guidelines:

<pre><nowiki>
<zone ulx="18" uly="50" lrx="489" lry="118">
<figure>...</figure>
<zone ulx="29" uly="51">Ex. 8. Andante con moto.</zone>
<zone ulx="298" uly="50">SCHUBERT : Symphony in B minor.</zone>
<zone ulx="66" uly="106">pp</zone>
<zone ulx="341" uly="106">fp</zone>
</zone>
</nowiki></pre>

(coordinate values in pixels) --[[User:Martin de la Iglesia|Martin de la Iglesia]] 08:47, 5 August 2013 (EDT)

===Image Metadata===
I'm thinking primarily of content description texts, but we could embed this in a general discussion of how (or whether) to encode any "invisible" aspects of images. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:34, 5 December 2011 (EST)
* classification in @type:
<pre><nowiki>
<figure type="floor_plan">...</figure>
</nowiki></pre>
Are there any suitable vocabularies that could be used for this kind of indexing? --[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:47, 5 August 2013 (EDT)

User talk:Martin de la Iglesia/A Guide to Images in TEI

2013-08-05T12:47:00Z

Martin de la Iglesia: /* Image-Text Alignment */ new section

==General==
===Suggested use of this page===
The idea is to start by filling in the different chapters in [[User_talk:Martin_de_la_Iglesia/A_Guide_to_Images_in_TEI#Outline|Outline]] below. In the beginning, I think it makes sense to do this in a Discussion page, in order to avoid switching back and forth between the Article and the Discussion page all the time. After some time we can move the text from the Discussion page to my namespace, then after some more consolidation to the main wiki. Finally, we could move it to an entirely different website if we found the TEI Wiki unsuitable. However, feel free to suggest other procedures, or maybe an entirely different environment for working on this resource altogether. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:47, 2 December 2011 (EST)
===Title===
The title of this page (currently: "A Guide to Images in TEI") is just a working title. Feel free to suggest alternative titles. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:47, 2 December 2011 (EST)
===Related resources===
We should think about how this resource relates to [[TEI to SVG]] (and maybe other relevant pages/resources), and whether and how this information should be integrated here. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:47, 2 December 2011 (EST)

Is there a need for a [[TEI Cheatsheets|TEI Cheatsheet]] for images? I imagine such a cheatsheet as a more concise and practical version of this Guide. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:59, 5 August 2013 (EDT)

==Outline==
===Aims and Scope===
We should have a text here which explains what this resource is for and how it differs from the TEI Guidelines. In the meantime, I paste my announcement e-mail to the SIG Text & Graphics mailing list from December 1, 2011:

:[...]
:I learned in Würzburg that some other SIGs are planning to create specialized tutorials that cover aspects relevant to the respective SIG's scope which are not already covered by general introductory TEI resources like TEI By Example. This sounds like a good idea for our SIG, too. I'm aware that, basically, the solutions are all in the TEI Guidelines somewhere, but as we all know, it can be quite tough to make encoding decisions by only consulting the Guidelines. This is especially true for the encoding of graphics-related information, which, as far as I have seen, is not well covered by TEI By Example.

:In addition to the examples given by John, I'd like this new FAQ/Tutorial to tackle basic questions such as
:- how to encode the position of images on a page
:- how to link images to text
:- how to align images with portions of text or vice versa
:- how to encode descriptions of images or other image metadata
:etc.
:So what I'm envisioning is a sort of beginner's guide to handling images in TEI, either as a FAQ (i.e. self-contained chapters) or a step-by-step Tutorial (i.e. "what to do when you encounter an image in your text"). As John already mentioned, integration into TEI By Example might also be a possibility (although I haven't discussed this idea with the TEI By Example people yet).
:[...]

--[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:11, 5 December 2011 (EST)

===Basic Integration of Images/Linking to Images===
John (Walsh) suggested covering the <figure> tag. Additionally, it might be useful to have a general discussion on image types (binary vs. SVG vs. characters (i.e. trying to find matching Unicode characters for special symbols instead of integrating them as images)) and the different encoding practices they imply. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:18, 5 December 2011 (EST)
====Examples====
Here's an example of different encodings for the same image. The image I'd like to represent is the wedge-shaped marking that indicates that the word "war" is to be inserted into the line below.

[[File:Fontane-30633-detail.jpg|200px]]
* binary: the marking is extracted from the scan and provided as a separate file which is pointed to in the TEI code and displayed at the appropriate position in the transcribed text.
[[File:Fontane-30633-detail2.png|75px]]<pre><nowiki>
<figure><graphic url="myfilename.png"/></figure>
</nowiki></pre>
'''pro:''' representing an image through a digital image results in probably the strongest resemblance to the original image. '''con:''' it is quite a lot of work to extract the image from the scan; the TEI code provides hardly any semantics or searchability (except for the filename, or additional information in <figure>); the image can be difficult to align and position, especially if other reference points than the upper left corner of the image are to be used (see according sections) - anchor points generated by e.g. the Text Image Link Editor in TextGrid might provide a workaround for this problem.

* SVG: an SVG drawing is designed that resembles the original image. Simplified measurements, obtained from measuring the image on the original page or its facsimile, are provided in the TEI code, from which the SVG is created by a transformation stylesheet.
<pre><nowiki>
<svg xmlns="http://www.w3.org/2000/svg" width="0.9cm" height="1em">
<line x1="0" y1="0" x2="0.3cm" y2="1em" style="stroke:black; stroke-width:2px;" />
<line x1="0.3cm" y1="1em" x2="0.9cm" y2="0" style="stroke:black; stroke-width:2px;" />
</svg>
</nowiki></pre>
<pre><nowiki>
<figure rend="marking_V(left:0.3cm;right:0.6cm)"/>
</nowiki></pre>
This TEI code indicates that it's a "V"-shaped marking, with a left side of 3 mm width and a right side of 6 mm width. (The height is fixed at 1 em.) From these measurements, the SVG code above is created during transformation.

--[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:27, 5 January 2012 (EST)

=====Examples of different methods for other images=====

* direct extraction from facsimile: this only works when writing and image are not as closely intertwined as in the example above. If coordinates are provided, the image can be extracted from the facsimile (the location of which is provided in <surface @facs>) on transformation and placed correctly in between the transcription of the surrounding writing.
<pre><nowiki>
<zone ulx="123" uly="234" lrx="345" lry="456">
<figure>...</figure>
</zone>
</nowiki></pre>
These coordinates represent pixels in the facsimile file. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 08:11, 5 August 2013 (EDT)

* simple line drawings: coordinates in <zone> provide information on the position, length and angle of lines such as horizontal rules that divide sections of text.

<pre><nowiki>
<zone ulx="1.2" uly="6.7" lrx="5.6" lry="6.9">
<figure type="line_drawing"/>
</zone>
</nowiki></pre>

These coordinates describe a horizontal line of about 4 1/2 centimetres length with a slight slope, which can be drawn e.g. in SVG on transformation. '''con:''' the difference between the @lry and @uly values is ambiguous, as it can be interpreted as either width or angle. The respective missing value should be provided as well, e.g. in <figure @rend> or <zone @rotate>. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 08:30, 5 August 2013 (EDT)

===Linking to Facsimile Page Images===
This is another topic suggested by John ("using <facsimile> and @facs to link to facsimile page images"). --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:23, 5 December 2011 (EST)

You might draw upon [http://www.tei-c.org/SIG/Libraries/teiinlibraries/main-driver.html#txtimglnk this section] of the [http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries]. ([[User:Kshawkin|Kshawkin]] 08:26, 2 December 2011 (EST))
:Thanks, Kevin. I wasn't aware of that section. There's one thing I don't understand about the third approach: in the sample METS document, which is the ID that is used in @xml:id in the TEI code? --[[User:Martin de la Iglesia|Martin de la Iglesia]] 05:35, 7 December 2011 (EST)

:: Hmm, I agree that the recommendation isn't at all clear, and I actually don't know METS very well. I've made a note to revisit this in a future revision to the Best Practices. In the meantime, if you know METS well, you might look at the sample METS document linked to from the Best Practices. If that doesn't clarify, I'd contact my coeditor Michelle Dalmau: I think she will know. --[[User:Kshawkin|Kshawkin]] 10:04, 12 December 2011 (EST)
:::Thanks again. Michelle explained it to me and now I see the usefulness of this method, at least in some projects. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 09:47, 21 December 2011 (EST)

===Positioning an Image===
What I'd like to see here is a discussion of the <surface>/<zone> coordinate positioning system vs. <ptr>-like positioning solutions, and maybe of other systems as well (e.g. lines and margin for y and x axis positioning). --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:28, 5 December 2011 (EST)
====Examples====
* metric margins in CSS style for x and y axis starting points, counting from leaf borders (height and width are determined by the figure itself): <pre><figure style="margin-left:1.2cm; margin-top:3.4cm">...</figure></pre>
* CSS style margins in percent: <pre><figure style="margin-left:12%; margin-top:34%">...</figure></pre>
* CSS style margins in lines for y axis (not valid CSS, but line alignment can be important in some cases): <pre><figure style="margin-left:1.2cm" rend="margin-top:7lines">...</figure></pre> (i.e. the image starts in line 8)
* added height and width:
<pre><nowiki>
<figure style="margin-left:1.2cm; margin-top:3.4cm">
<figDesc>
<dimensions>
<height quantity="12.3" unit="cm"/>
<width quantity="7.5" unit="cm"/>
</dimensions>
</figDesc>
</figure>
</nowiki></pre>
--[[User:Martin de la Iglesia|Martin de la Iglesia]] 05:21, 4 January 2012 (EST)

: On the use of CSS in @rend, see [[Future_changes_to_Best_Practices_for_TEI_in_Libraries#.40rend_vs._.40html:style_for_CSS_values|this discussion]]. ([[User:Kshawkin|Kshawkin]] 18:24, 6 January 2012 (EST))
::Thanks, Kevin, I wasn't aware of that. See my comment there. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:18, 10 January 2012 (EST)

::Alright, so we should add that there might be a problem with whitespaces in CSS style values, and that @html:style can be used as an alternative to @rend. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:03, 16 January 2012 (EST)
:::Substituted @rend with @style where applicable. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 05:19, 2 August 2013 (EDT)

* coordinates in <zone> (or <surface> where applicable); coordinate values follow the system employed in the TEI document (here: centimeters):
<pre><nowiki>
<zone ulx="1.2" uly="0.5" lrx="3.5" lry="7.1">
<figure>...</figure>
</zone>
</nowiki></pre>
--[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:39, 5 August 2013 (EDT)

===Image-Text Linking===
This section should cover the encoding of different kinds of image-text relationships (e.g. an image illustrating a text paragraph, or a text paragraph describing an image), other than merely topographical ones which are covered in the following section, Image-Text Alignment. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:40, 5 December 2011 (EST)

===Image-Text Alignment===
How to position text relative to an image, or an image relative to text (including special cases such as an image pointing at a character, or an image pointing at two separate characters) should be covered here. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:43, 5 December 2011 (EST)
* Here's an example of the latter case: in the following part of a scan from a 19th century German manuscript, a line connects two separate paragraphs. I'd be happy to represent this in the transcript as a straight SVG line that goes roughly from the word "Nissen" to "wird", but how to encode (and XSL-transform) this?
[[File:Fontane-30621-detail.jpg|200px]]

--[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:33, 21 December 2011 (EST)

* line numbers for images - this is an issue in editions in general and not specific to TEI, but still: if there's an image spanning the whole width of a page, and which is preceded and followed by writing, how does it fit in an editorial line numbering system? Should the image have its own line number, or should the image be ignored when numbering the regular text lines? --[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:53, 5 August 2013 (EDT)

* This example of positioning transcribed writing within an image using coordinate attributes in <zone> refers to the image pictured in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html#FTNM] in the TEI Guidelines:

<pre><nowiki>
<zone ulx="18" uly="50" lrx="489" lry="118">
<figure>...</figure>
<zone ulx="29" uly="51">Ex. 8. Andante con moto.</zone>
<zone ulx="298" uly="50">SCHUBERT : Symphony in B minor.</zone>
<zone ulx="66" uly="106">pp</zone>
<zone ulx="341" uly="106">fp</zone>
</zone>
</nowiki></pre>

(coordinate values in pixels) --[[User:Martin de la Iglesia|Martin de la Iglesia]] 08:47, 5 August 2013 (EDT)

===Image Metadata===
I'm thinking primarily of content description texts, but we could embed this in a general discussion of how (or whether) to encode any "invisible" aspects of images. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:34, 5 December 2011 (EST)
* classification in @type:
<pre><nowiki>
<figure type="floor_plan">...</figure>
</nowiki></pre>
Are there any suitable vocabularies that could be used for this kind of indexing? --[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:47, 5 August 2013 (EDT)

User talk:Martin de la Iglesia/A Guide to Images in TEI

2013-08-05T12:30:45Z

Martin de la Iglesia: /* Examples of different methods for other images */ new section: simple line drawings

==General==
===Suggested use of this page===
The idea is to start by filling in the different chapters in [[User_talk:Martin_de_la_Iglesia/A_Guide_to_Images_in_TEI#Outline|Outline]] below. In the beginning, I think it makes sense to do this in a Discussion page, in order to avoid switching back and forth between the Article and the Discussion page all the time. After some time we can move the text from the Discussion page to my namespace, then after some more consolidation to the main wiki. Finally, we could move it to an entirely different website if we found the TEI Wiki unsuitable. However, feel free to suggest other procedures, or maybe an entirely different environment for working on this resource altogether. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:47, 2 December 2011 (EST)
===Title===
The title of this page (currently: "A Guide to Images in TEI") is just a working title. Feel free to suggest alternative titles. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:47, 2 December 2011 (EST)
===Related resources===
We should think about how this resource relates to [[TEI to SVG]] (and maybe other relevant pages/resources), and whether and how this information should be integrated here. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:47, 2 December 2011 (EST)

Is there a need for a [[TEI Cheatsheets|TEI Cheatsheet]] for images? I imagine such a cheatsheet as a more concise and practical version of this Guide. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:59, 5 August 2013 (EDT)

==Outline==
===Aims and Scope===
We should have a text here which explains what this resource is for and how it differs from the TEI Guidelines. In the meantime, I paste my announcement e-mail to the SIG Text & Graphics mailing list from December 1, 2011:

:[...]
:I learned in Würzburg that some other SIGs are planning to create specialized tutorials that cover aspects relevant to the respective SIG's scope which are not already covered by general introductory TEI resources like TEI By Example. This sounds like a good idea for our SIG, too. I'm aware that, basically, the solutions are all in the TEI Guidelines somewhere, but as we all know, it can be quite tough to make encoding decisions by only consulting the Guidelines. This is especially true for the encoding of graphics-related information, which, as far as I have seen, is not well covered by TEI By Example.

:In addition to the examples given by John, I'd like this new FAQ/Tutorial to tackle basic questions such as
:- how to encode the position of images on a page
:- how to link images to text
:- how to align images with portions of text or vice versa
:- how to encode descriptions of images or other image metadata
:etc.
:So what I'm envisioning is a sort of beginner's guide to handling images in TEI, either as a FAQ (i.e. self-contained chapters) or a step-by-step Tutorial (i.e. "what to do when you encounter an image in your text"). As John already mentioned, integration into TEI By Example might also be a possibility (although I haven't discussed this idea with the TEI By Example people yet).
:[...]

--[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:11, 5 December 2011 (EST)

===Basic Integration of Images/Linking to Images===
John (Walsh) suggested covering the <figure> tag. Additionally, it might be useful to have a general discussion on image types (binary vs. SVG vs. characters (i.e. trying to find matching Unicode characters for special symbols instead of integrating them as images)) and the different encoding practices they imply. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:18, 5 December 2011 (EST)
====Examples====
Here's an example of different encodings for the same image. The image I'd like to represent is the wedge-shaped marking that indicates that the word "war" is to be inserted into the line below.

[[File:Fontane-30633-detail.jpg|200px]]
* binary: the marking is extracted from the scan and provided as a separate file which is pointed to in the TEI code and displayed at the appropriate position in the transcribed text.
[[File:Fontane-30633-detail2.png|75px]]<pre><nowiki>
<figure><graphic url="myfilename.png"/></figure>
</nowiki></pre>
'''pro:''' representing an image through a digital image results in probably the strongest resemblance to the original image. '''con:''' it is quite a lot of work to extract the image from the scan; the TEI code provides hardly any semantics or searchability (except for the filename, or additional information in <figure>); the image can be difficult to align and position, especially if other reference points than the upper left corner of the image are to be used (see according sections) - anchor points generated by e.g. the Text Image Link Editor in TextGrid might provide a workaround for this problem.

* SVG: an SVG drawing is designed that resembles the original image. Simplified measurements, obtained from measuring the image on the original page or its facsimile, are provided in the TEI code, from which the SVG is created by a transformation stylesheet.
<pre><nowiki>
<svg xmlns="http://www.w3.org/2000/svg" width="0.9cm" height="1em">
<line x1="0" y1="0" x2="0.3cm" y2="1em" style="stroke:black; stroke-width:2px;" />
<line x1="0.3cm" y1="1em" x2="0.9cm" y2="0" style="stroke:black; stroke-width:2px;" />
</svg>
</nowiki></pre>
<pre><nowiki>
<figure rend="marking_V(left:0.3cm;right:0.6cm)"/>
</nowiki></pre>
This TEI code indicates that it's a "V"-shaped marking, with a left side of 3 mm width and a right side of 6 mm width. (The height is fixed at 1 em.) From these measurements, the SVG code above is created during transformation.

--[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:27, 5 January 2012 (EST)

=====Examples of different methods for other images=====

* direct extraction from facsimile: this only works when writing and image are not as closely intertwined as in the example above. If coordinates are provided, the image can be extracted from the facsimile (the location of which is provided in <surface @facs>) on transformation and placed correctly in between the transcription of the surrounding writing.
<pre><nowiki>
<zone ulx="123" uly="234" lrx="345" lry="456">
<figure>...</figure>
</zone>
</nowiki></pre>
These coordinates represent pixels in the facsimile file. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 08:11, 5 August 2013 (EDT)

* simple line drawings: coordinates in <zone> provide information on the position, length and angle of lines such as horizontal rules that divide sections of text.

<pre><nowiki>
<zone ulx="1.2" uly="6.7" lrx="5.6" lry="6.9">
<figure type="line_drawing"/>
</zone>
</nowiki></pre>

These coordinates describe a horizontal line of about 4 1/2 centimetres length with a slight slope, which can be drawn e.g. in SVG on transformation. '''con:''' the difference between the @lry and @uly values is ambiguous, as it can be interpreted as either width or angle. The respective missing value should be provided as well, e.g. in <figure @rend> or <zone @rotate>. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 08:30, 5 August 2013 (EDT)

===Linking to Facsimile Page Images===
This is another topic suggested by John ("using <facsimile> and @facs to link to facsimile page images"). --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:23, 5 December 2011 (EST)

You might draw upon [http://www.tei-c.org/SIG/Libraries/teiinlibraries/main-driver.html#txtimglnk this section] of the [http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries]. ([[User:Kshawkin|Kshawkin]] 08:26, 2 December 2011 (EST))
:Thanks, Kevin. I wasn't aware of that section. There's one thing I don't understand about the third approach: in the sample METS document, which is the ID that is used in @xml:id in the TEI code? --[[User:Martin de la Iglesia|Martin de la Iglesia]] 05:35, 7 December 2011 (EST)

:: Hmm, I agree that the recommendation isn't at all clear, and I actually don't know METS very well. I've made a note to revisit this in a future revision to the Best Practices. In the meantime, if you know METS well, you might look at the sample METS document linked to from the Best Practices. If that doesn't clarify, I'd contact my coeditor Michelle Dalmau: I think she will know. --[[User:Kshawkin|Kshawkin]] 10:04, 12 December 2011 (EST)
:::Thanks again. Michelle explained it to me and now I see the usefulness of this method, at least in some projects. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 09:47, 21 December 2011 (EST)

===Positioning an Image===
What I'd like to see here is a discussion of the <surface>/<zone> coordinate positioning system vs. <ptr>-like positioning solutions, and maybe of other systems as well (e.g. lines and margin for y and x axis positioning). --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:28, 5 December 2011 (EST)
====Examples====
* metric margins in CSS style for x and y axis starting points, counting from leaf borders (height and width are determined by the figure itself): <pre><figure style="margin-left:1.2cm; margin-top:3.4cm">...</figure></pre>
* CSS style margins in percent: <pre><figure style="margin-left:12%; margin-top:34%">...</figure></pre>
* CSS style margins in lines for y axis (not valid CSS, but line alignment can be important in some cases): <pre><figure style="margin-left:1.2cm" rend="margin-top:7lines">...</figure></pre> (i.e. the image starts in line 8)
* added height and width:
<pre><nowiki>
<figure style="margin-left:1.2cm; margin-top:3.4cm">
<figDesc>
<dimensions>
<height quantity="12.3" unit="cm"/>
<width quantity="7.5" unit="cm"/>
</dimensions>
</figDesc>
</figure>
</nowiki></pre>
--[[User:Martin de la Iglesia|Martin de la Iglesia]] 05:21, 4 January 2012 (EST)

: On the use of CSS in @rend, see [[Future_changes_to_Best_Practices_for_TEI_in_Libraries#.40rend_vs._.40html:style_for_CSS_values|this discussion]]. ([[User:Kshawkin|Kshawkin]] 18:24, 6 January 2012 (EST))
::Thanks, Kevin, I wasn't aware of that. See my comment there. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:18, 10 January 2012 (EST)

::Alright, so we should add that there might be a problem with whitespaces in CSS style values, and that @html:style can be used as an alternative to @rend. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:03, 16 January 2012 (EST)
:::Substituted @rend with @style where applicable. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 05:19, 2 August 2013 (EDT)

* coordinates in <zone> (or <surface> where applicable); coordinate values follow the system employed in the TEI document (here: centimeters):
<pre><nowiki>
<zone ulx="1.2" uly="0.5" lrx="3.5" lry="7.1">
<figure>...</figure>
</zone>
</nowiki></pre>
--[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:39, 5 August 2013 (EDT)

===Image-Text Linking===
This section should cover the encoding of different kinds of image-text relationships (e.g. an image illustrating a text paragraph, or a text paragraph describing an image), other than merely topographical ones which are covered in the following section, Image-Text Alignment. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:40, 5 December 2011 (EST)

===Image-Text Alignment===
How to position text relative to an image, or an image relative to text (including special cases such as an image pointing at a character, or an image pointing at two separate characters) should be covered here. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:43, 5 December 2011 (EST)
* Here's an example of the latter case: in the following part of a scan from a 19th century German manuscript, a line connects two separate paragraphs. I'd be happy to represent this in the transcript as a straight SVG line that goes roughly from the word "Nissen" to "wird", but how to encode (and XSL-transform) this?
[[File:Fontane-30621-detail.jpg|200px]]

--[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:33, 21 December 2011 (EST)

* line numbers for images - this is an issue in editions in general and not specific to TEI, but still: if there's an image spanning the whole width of a page, and which is preceded and followed by writing, how does it fit in an editorial line numbering system? Should the image have its own line number, or should the image be ignored when numbering the regular text lines? --[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:53, 5 August 2013 (EDT)

===Image Metadata===
I'm thinking primarily of content description texts, but we could embed this in a general discussion of how (or whether) to encode any "invisible" aspects of images. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:34, 5 December 2011 (EST)
* classification in @type:
<pre><nowiki>
<figure type="floor_plan">...</figure>
</nowiki></pre>
Are there any suitable vocabularies that could be used for this kind of indexing? --[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:47, 5 August 2013 (EDT)

User talk:Martin de la Iglesia/A Guide to Images in TEI

2013-08-05T12:15:42Z

Martin de la Iglesia: /* Examples */ structure correction

==General==
===Suggested use of this page===
The idea is to start by filling in the different chapters in [[User_talk:Martin_de_la_Iglesia/A_Guide_to_Images_in_TEI#Outline|Outline]] below. In the beginning, I think it makes sense to do this in a Discussion page, in order to avoid switching back and forth between the Article and the Discussion page all the time. After some time we can move the text from the Discussion page to my namespace, then after some more consolidation to the main wiki. Finally, we could move it to an entirely different website if we found the TEI Wiki unsuitable. However, feel free to suggest other procedures, or maybe an entirely different environment for working on this resource altogether. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:47, 2 December 2011 (EST)
===Title===
The title of this page (currently: "A Guide to Images in TEI") is just a working title. Feel free to suggest alternative titles. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:47, 2 December 2011 (EST)
===Related resources===
We should think about how this resource relates to [[TEI to SVG]] (and maybe other relevant pages/resources), and whether and how this information should be integrated here. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:47, 2 December 2011 (EST)

Is there a need for a [[TEI Cheatsheets|TEI Cheatsheet]] for images? I imagine such a cheatsheet as a more concise and practical version of this Guide. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:59, 5 August 2013 (EDT)

==Outline==
===Aims and Scope===
We should have a text here which explains what this resource is for and how it differs from the TEI Guidelines. In the meantime, I paste my announcement e-mail to the SIG Text & Graphics mailing list from December 1, 2011:

:[...]
:I learned in Würzburg that some other SIGs are planning to create specialized tutorials that cover aspects relevant to the respective SIG's scope which are not already covered by general introductory TEI resources like TEI By Example. This sounds like a good idea for our SIG, too. I'm aware that, basically, the solutions are all in the TEI Guidelines somewhere, but as we all know, it can be quite tough to make encoding decisions by only consulting the Guidelines. This is especially true for the encoding of graphics-related information, which, as far as I have seen, is not well covered by TEI By Example.

:In addition to the examples given by John, I'd like this new FAQ/Tutorial to tackle basic questions such as
:- how to encode the position of images on a page
:- how to link images to text
:- how to align images with portions of text or vice versa
:- how to encode descriptions of images or other image metadata
:etc.
:So what I'm envisioning is a sort of beginner's guide to handling images in TEI, either as a FAQ (i.e. self-contained chapters) or a step-by-step Tutorial (i.e. "what to do when you encounter an image in your text"). As John already mentioned, integration into TEI By Example might also be a possibility (although I haven't discussed this idea with the TEI By Example people yet).
:[...]

--[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:11, 5 December 2011 (EST)

===Basic Integration of Images/Linking to Images===
John (Walsh) suggested covering the <figure> tag. Additionally, it might be useful to have a general discussion on image types (binary vs. SVG vs. characters (i.e. trying to find matching Unicode characters for special symbols instead of integrating them as images)) and the different encoding practices they imply. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:18, 5 December 2011 (EST)
====Examples====
Here's an example of different encodings for the same image. The image I'd like to represent is the wedge-shaped marking that indicates that the word "war" is to be inserted into the line below.

[[File:Fontane-30633-detail.jpg|200px]]
* binary: the marking is extracted from the scan and provided as a separate file which is pointed to in the TEI code and displayed at the appropriate position in the transcribed text.
[[File:Fontane-30633-detail2.png|75px]]<pre><nowiki>
<figure><graphic url="myfilename.png"/></figure>
</nowiki></pre>
'''pro:''' representing an image through a digital image results in probably the strongest resemblance to the original image. '''con:''' it is quite a lot of work to extract the image from the scan; the TEI code provides hardly any semantics or searchability (except for the filename, or additional information in <figure>); the image can be difficult to align and position, especially if other reference points than the upper left corner of the image are to be used (see according sections) - anchor points generated by e.g. the Text Image Link Editor in TextGrid might provide a workaround for this problem.

* SVG: an SVG drawing is designed that resembles the original image. Simplified measurements, obtained from measuring the image on the original page or its facsimile, are provided in the TEI code, from which the SVG is created by a transformation stylesheet.
<pre><nowiki>
<svg xmlns="http://www.w3.org/2000/svg" width="0.9cm" height="1em">
<line x1="0" y1="0" x2="0.3cm" y2="1em" style="stroke:black; stroke-width:2px;" />
<line x1="0.3cm" y1="1em" x2="0.9cm" y2="0" style="stroke:black; stroke-width:2px;" />
</svg>
</nowiki></pre>
<pre><nowiki>
<figure rend="marking_V(left:0.3cm;right:0.6cm)"/>
</nowiki></pre>
This TEI code indicates that it's a "V"-shaped marking, with a left side of 3 mm width and a right side of 6 mm width. (The height is fixed at 1 em.) From these measurements, the SVG code above is created during transformation.

--[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:27, 5 January 2012 (EST)

=====Examples of different methods for other images=====

* direct extraction from facsimile: this only works when writing and image are not as closely intertwined as in the example above. If coordinates are provided, the image can be extracted from the facsimile (the location of which is provided in <surface @facs>) on transformation and placed correctly in between the transcription of the surrounding writing.
<pre><nowiki>
<zone ulx="123" uly="234" lrx="345" lry="456">
<figure>...</figure>
</zone>
</nowiki></pre>
These coordinates represent pixels in the facsimile file. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 08:11, 5 August 2013 (EDT)

===Linking to Facsimile Page Images===
This is another topic suggested by John ("using <facsimile> and @facs to link to facsimile page images"). --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:23, 5 December 2011 (EST)

You might draw upon [http://www.tei-c.org/SIG/Libraries/teiinlibraries/main-driver.html#txtimglnk this section] of the [http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries]. ([[User:Kshawkin|Kshawkin]] 08:26, 2 December 2011 (EST))
:Thanks, Kevin. I wasn't aware of that section. There's one thing I don't understand about the third approach: in the sample METS document, which is the ID that is used in @xml:id in the TEI code? --[[User:Martin de la Iglesia|Martin de la Iglesia]] 05:35, 7 December 2011 (EST)

:: Hmm, I agree that the recommendation isn't at all clear, and I actually don't know METS very well. I've made a note to revisit this in a future revision to the Best Practices. In the meantime, if you know METS well, you might look at the sample METS document linked to from the Best Practices. If that doesn't clarify, I'd contact my coeditor Michelle Dalmau: I think she will know. --[[User:Kshawkin|Kshawkin]] 10:04, 12 December 2011 (EST)
:::Thanks again. Michelle explained it to me and now I see the usefulness of this method, at least in some projects. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 09:47, 21 December 2011 (EST)

===Positioning an Image===
What I'd like to see here is a discussion of the <surface>/<zone> coordinate positioning system vs. <ptr>-like positioning solutions, and maybe of other systems as well (e.g. lines and margin for y and x axis positioning). --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:28, 5 December 2011 (EST)
====Examples====
* metric margins in CSS style for x and y axis starting points, counting from leaf borders (height and width are determined by the figure itself): <pre><figure style="margin-left:1.2cm; margin-top:3.4cm">...</figure></pre>
* CSS style margins in percent: <pre><figure style="margin-left:12%; margin-top:34%">...</figure></pre>
* CSS style margins in lines for y axis (not valid CSS, but line alignment can be important in some cases): <pre><figure style="margin-left:1.2cm" rend="margin-top:7lines">...</figure></pre> (i.e. the image starts in line 8)
* added height and width:
<pre><nowiki>
<figure style="margin-left:1.2cm; margin-top:3.4cm">
<figDesc>
<dimensions>
<height quantity="12.3" unit="cm"/>
<width quantity="7.5" unit="cm"/>
</dimensions>
</figDesc>
</figure>
</nowiki></pre>
--[[User:Martin de la Iglesia|Martin de la Iglesia]] 05:21, 4 January 2012 (EST)

: On the use of CSS in @rend, see [[Future_changes_to_Best_Practices_for_TEI_in_Libraries#.40rend_vs._.40html:style_for_CSS_values|this discussion]]. ([[User:Kshawkin|Kshawkin]] 18:24, 6 January 2012 (EST))
::Thanks, Kevin, I wasn't aware of that. See my comment there. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:18, 10 January 2012 (EST)

::Alright, so we should add that there might be a problem with whitespaces in CSS style values, and that @html:style can be used as an alternative to @rend. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:03, 16 January 2012 (EST)
:::Substituted @rend with @style where applicable. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 05:19, 2 August 2013 (EDT)

* coordinates in <zone> (or <surface> where applicable); coordinate values follow the system employed in the TEI document (here: centimeters):
<pre><nowiki>
<zone ulx="1.2" uly="0.5" lrx="3.5" lry="7.1">
<figure>...</figure>
</zone>
</nowiki></pre>
--[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:39, 5 August 2013 (EDT)

===Image-Text Linking===
This section should cover the encoding of different kinds of image-text relationships (e.g. an image illustrating a text paragraph, or a text paragraph describing an image), other than merely topographical ones which are covered in the following section, Image-Text Alignment. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:40, 5 December 2011 (EST)

===Image-Text Alignment===
How to position text relative to an image, or an image relative to text (including special cases such as an image pointing at a character, or an image pointing at two separate characters) should be covered here. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:43, 5 December 2011 (EST)
* Here's an example of the latter case: in the following part of a scan from a 19th century German manuscript, a line connects two separate paragraphs. I'd be happy to represent this in the transcript as a straight SVG line that goes roughly from the word "Nissen" to "wird", but how to encode (and XSL-transform) this?
[[File:Fontane-30621-detail.jpg|200px]]

--[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:33, 21 December 2011 (EST)

* line numbers for images - this is an issue in editions in general and not specific to TEI, but still: if there's an image spanning the whole width of a page, and which is preceded and followed by writing, how does it fit in an editorial line numbering system? Should the image have its own line number, or should the image be ignored when numbering the regular text lines? --[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:53, 5 August 2013 (EDT)

===Image Metadata===
I'm thinking primarily of content description texts, but we could embed this in a general discussion of how (or whether) to encode any "invisible" aspects of images. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:34, 5 December 2011 (EST)
* classification in @type:
<pre><nowiki>
<figure type="floor_plan">...</figure>
</nowiki></pre>
Are there any suitable vocabularies that could be used for this kind of indexing? --[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:47, 5 August 2013 (EDT)

User talk:Martin de la Iglesia/A Guide to Images in TEI

2013-08-05T12:11:33Z

Martin de la Iglesia: /* Examples */ new section: direct extraction from facsimile

==General==
===Suggested use of this page===
The idea is to start by filling in the different chapters in [[User_talk:Martin_de_la_Iglesia/A_Guide_to_Images_in_TEI#Outline|Outline]] below. In the beginning, I think it makes sense to do this in a Discussion page, in order to avoid switching back and forth between the Article and the Discussion page all the time. After some time we can move the text from the Discussion page to my namespace, then after some more consolidation to the main wiki. Finally, we could move it to an entirely different website if we found the TEI Wiki unsuitable. However, feel free to suggest other procedures, or maybe an entirely different environment for working on this resource altogether. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:47, 2 December 2011 (EST)
===Title===
The title of this page (currently: "A Guide to Images in TEI") is just a working title. Feel free to suggest alternative titles. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:47, 2 December 2011 (EST)
===Related resources===
We should think about how this resource relates to [[TEI to SVG]] (and maybe other relevant pages/resources), and whether and how this information should be integrated here. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:47, 2 December 2011 (EST)

Is there a need for a [[TEI Cheatsheets|TEI Cheatsheet]] for images? I imagine such a cheatsheet as a more concise and practical version of this Guide. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:59, 5 August 2013 (EDT)

==Outline==
===Aims and Scope===
We should have a text here which explains what this resource is for and how it differs from the TEI Guidelines. In the meantime, I paste my announcement e-mail to the SIG Text & Graphics mailing list from December 1, 2011:

:[...]
:I learned in Würzburg that some other SIGs are planning to create specialized tutorials that cover aspects relevant to the respective SIG's scope which are not already covered by general introductory TEI resources like TEI By Example. This sounds like a good idea for our SIG, too. I'm aware that, basically, the solutions are all in the TEI Guidelines somewhere, but as we all know, it can be quite tough to make encoding decisions by only consulting the Guidelines. This is especially true for the encoding of graphics-related information, which, as far as I have seen, is not well covered by TEI By Example.

:In addition to the examples given by John, I'd like this new FAQ/Tutorial to tackle basic questions such as
:- how to encode the position of images on a page
:- how to link images to text
:- how to align images with portions of text or vice versa
:- how to encode descriptions of images or other image metadata
:etc.
:So what I'm envisioning is a sort of beginner's guide to handling images in TEI, either as a FAQ (i.e. self-contained chapters) or a step-by-step Tutorial (i.e. "what to do when you encounter an image in your text"). As John already mentioned, integration into TEI By Example might also be a possibility (although I haven't discussed this idea with the TEI By Example people yet).
:[...]

--[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:11, 5 December 2011 (EST)

===Basic Integration of Images/Linking to Images===
John (Walsh) suggested covering the <figure> tag. Additionally, it might be useful to have a general discussion on image types (binary vs. SVG vs. characters (i.e. trying to find matching Unicode characters for special symbols instead of integrating them as images)) and the different encoding practices they imply. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:18, 5 December 2011 (EST)
====Examples====
Here's an example of different encodings for the same image. The image I'd like to represent is the wedge-shaped marking that indicates that the word "war" is to be inserted into the line below.

[[File:Fontane-30633-detail.jpg|200px]]
* binary: the marking is extracted from the scan and provided as a separate file which is pointed to in the TEI code and displayed at the appropriate position in the transcribed text.
[[File:Fontane-30633-detail2.png|75px]]<pre><nowiki>
<figure><graphic url="myfilename.png"/></figure>
</nowiki></pre>
'''pro:''' representing an image through a digital image results in probably the strongest resemblance to the original image. '''con:''' it is quite a lot of work to extract the image from the scan; the TEI code provides hardly any semantics or searchability (except for the filename, or additional information in <figure>); the image can be difficult to align and position, especially if other reference points than the upper left corner of the image are to be used (see according sections) - anchor points generated by e.g. the Text Image Link Editor in TextGrid might provide a workaround for this problem.
* direct extraction from facsimile: this only works when writing and image are not as closely intertwined as in the example above. If coordinates are provided, the image can be extracted from the facsimile (the location of which is provided in <surface @facs>) on transformation and placed correctly in between the transcription of the surrounding writing.
<pre><nowiki>
<zone ulx="123" uly="234" lrx="345" lry="456">
<figure>...</figure>
</zone>
</nowiki></pre>
These coordinates represent pixels in the facsimile file. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 08:11, 5 August 2013 (EDT)

* SVG: an SVG drawing is designed that resembles the original image. Simplified measurements, obtained from measuring the image on the original page or its facsimile, are provided in the TEI code, from which the SVG is created by a transformation stylesheet.
<pre><nowiki>
<svg xmlns="http://www.w3.org/2000/svg" width="0.9cm" height="1em">
<line x1="0" y1="0" x2="0.3cm" y2="1em" style="stroke:black; stroke-width:2px;" />
<line x1="0.3cm" y1="1em" x2="0.9cm" y2="0" style="stroke:black; stroke-width:2px;" />
</svg>
</nowiki></pre>
<pre><nowiki>
<figure rend="marking_V(left:0.3cm;right:0.6cm)"/>
</nowiki></pre>
This TEI code indicates that it's a "V"-shaped marking, with a left side of 3 mm width and a right side of 6 mm width. (The height is fixed at 1 em.) From these measurements, the SVG code above is created during transformation.

--[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:27, 5 January 2012 (EST)

===Linking to Facsimile Page Images===
This is another topic suggested by John ("using <facsimile> and @facs to link to facsimile page images"). --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:23, 5 December 2011 (EST)

You might draw upon [http://www.tei-c.org/SIG/Libraries/teiinlibraries/main-driver.html#txtimglnk this section] of the [http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries]. ([[User:Kshawkin|Kshawkin]] 08:26, 2 December 2011 (EST))
:Thanks, Kevin. I wasn't aware of that section. There's one thing I don't understand about the third approach: in the sample METS document, which is the ID that is used in @xml:id in the TEI code? --[[User:Martin de la Iglesia|Martin de la Iglesia]] 05:35, 7 December 2011 (EST)

:: Hmm, I agree that the recommendation isn't at all clear, and I actually don't know METS very well. I've made a note to revisit this in a future revision to the Best Practices. In the meantime, if you know METS well, you might look at the sample METS document linked to from the Best Practices. If that doesn't clarify, I'd contact my coeditor Michelle Dalmau: I think she will know. --[[User:Kshawkin|Kshawkin]] 10:04, 12 December 2011 (EST)
:::Thanks again. Michelle explained it to me and now I see the usefulness of this method, at least in some projects. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 09:47, 21 December 2011 (EST)

===Positioning an Image===
What I'd like to see here is a discussion of the <surface>/<zone> coordinate positioning system vs. <ptr>-like positioning solutions, and maybe of other systems as well (e.g. lines and margin for y and x axis positioning). --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:28, 5 December 2011 (EST)
====Examples====
* metric margins in CSS style for x and y axis starting points, counting from leaf borders (height and width are determined by the figure itself): <pre><figure style="margin-left:1.2cm; margin-top:3.4cm">...</figure></pre>
* CSS style margins in percent: <pre><figure style="margin-left:12%; margin-top:34%">...</figure></pre>
* CSS style margins in lines for y axis (not valid CSS, but line alignment can be important in some cases): <pre><figure style="margin-left:1.2cm" rend="margin-top:7lines">...</figure></pre> (i.e. the image starts in line 8)
* added height and width:
<pre><nowiki>
<figure style="margin-left:1.2cm; margin-top:3.4cm">
<figDesc>
<dimensions>
<height quantity="12.3" unit="cm"/>
<width quantity="7.5" unit="cm"/>
</dimensions>
</figDesc>
</figure>
</nowiki></pre>
--[[User:Martin de la Iglesia|Martin de la Iglesia]] 05:21, 4 January 2012 (EST)

: On the use of CSS in @rend, see [[Future_changes_to_Best_Practices_for_TEI_in_Libraries#.40rend_vs._.40html:style_for_CSS_values|this discussion]]. ([[User:Kshawkin|Kshawkin]] 18:24, 6 January 2012 (EST))
::Thanks, Kevin, I wasn't aware of that. See my comment there. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:18, 10 January 2012 (EST)

::Alright, so we should add that there might be a problem with whitespaces in CSS style values, and that @html:style can be used as an alternative to @rend. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:03, 16 January 2012 (EST)
:::Substituted @rend with @style where applicable. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 05:19, 2 August 2013 (EDT)

* coordinates in <zone> (or <surface> where applicable); coordinate values follow the system employed in the TEI document (here: centimeters):
<pre><nowiki>
<zone ulx="1.2" uly="0.5" lrx="3.5" lry="7.1">
<figure>...</figure>
</zone>
</nowiki></pre>
--[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:39, 5 August 2013 (EDT)

===Image-Text Linking===
This section should cover the encoding of different kinds of image-text relationships (e.g. an image illustrating a text paragraph, or a text paragraph describing an image), other than merely topographical ones which are covered in the following section, Image-Text Alignment. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:40, 5 December 2011 (EST)

===Image-Text Alignment===
How to position text relative to an image, or an image relative to text (including special cases such as an image pointing at a character, or an image pointing at two separate characters) should be covered here. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:43, 5 December 2011 (EST)
* Here's an example of the latter case: in the following part of a scan from a 19th century German manuscript, a line connects two separate paragraphs. I'd be happy to represent this in the transcript as a straight SVG line that goes roughly from the word "Nissen" to "wird", but how to encode (and XSL-transform) this?
[[File:Fontane-30621-detail.jpg|200px]]

--[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:33, 21 December 2011 (EST)

* line numbers for images - this is an issue in editions in general and not specific to TEI, but still: if there's an image spanning the whole width of a page, and which is preceded and followed by writing, how does it fit in an editorial line numbering system? Should the image have its own line number, or should the image be ignored when numbering the regular text lines? --[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:53, 5 August 2013 (EDT)

===Image Metadata===
I'm thinking primarily of content description texts, but we could embed this in a general discussion of how (or whether) to encode any "invisible" aspects of images. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:34, 5 December 2011 (EST)
* classification in @type:
<pre><nowiki>
<figure type="floor_plan">...</figure>
</nowiki></pre>
Are there any suitable vocabularies that could be used for this kind of indexing? --[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:47, 5 August 2013 (EDT)

User talk:Martin de la Iglesia/A Guide to Images in TEI

2013-08-05T11:59:45Z

Martin de la Iglesia: /* Related resources */ new section

==General==
===Suggested use of this page===
The idea is to start by filling in the different chapters in [[User_talk:Martin_de_la_Iglesia/A_Guide_to_Images_in_TEI#Outline|Outline]] below. In the beginning, I think it makes sense to do this in a Discussion page, in order to avoid switching back and forth between the Article and the Discussion page all the time. After some time we can move the text from the Discussion page to my namespace, then after some more consolidation to the main wiki. Finally, we could move it to an entirely different website if we found the TEI Wiki unsuitable. However, feel free to suggest other procedures, or maybe an entirely different environment for working on this resource altogether. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:47, 2 December 2011 (EST)
===Title===
The title of this page (currently: "A Guide to Images in TEI") is just a working title. Feel free to suggest alternative titles. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:47, 2 December 2011 (EST)
===Related resources===
We should think about how this resource relates to [[TEI to SVG]] (and maybe other relevant pages/resources), and whether and how this information should be integrated here. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:47, 2 December 2011 (EST)

Is there a need for a [[TEI Cheatsheets|TEI Cheatsheet]] for images? I imagine such a cheatsheet as a more concise and practical version of this Guide. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:59, 5 August 2013 (EDT)

==Outline==
===Aims and Scope===
We should have a text here which explains what this resource is for and how it differs from the TEI Guidelines. In the meantime, I paste my announcement e-mail to the SIG Text & Graphics mailing list from December 1, 2011:

:[...]
:I learned in Würzburg that some other SIGs are planning to create specialized tutorials that cover aspects relevant to the respective SIG's scope which are not already covered by general introductory TEI resources like TEI By Example. This sounds like a good idea for our SIG, too. I'm aware that, basically, the solutions are all in the TEI Guidelines somewhere, but as we all know, it can be quite tough to make encoding decisions by only consulting the Guidelines. This is especially true for the encoding of graphics-related information, which, as far as I have seen, is not well covered by TEI By Example.

:In addition to the examples given by John, I'd like this new FAQ/Tutorial to tackle basic questions such as
:- how to encode the position of images on a page
:- how to link images to text
:- how to align images with portions of text or vice versa
:- how to encode descriptions of images or other image metadata
:etc.
:So what I'm envisioning is a sort of beginner's guide to handling images in TEI, either as a FAQ (i.e. self-contained chapters) or a step-by-step Tutorial (i.e. "what to do when you encounter an image in your text"). As John already mentioned, integration into TEI By Example might also be a possibility (although I haven't discussed this idea with the TEI By Example people yet).
:[...]

--[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:11, 5 December 2011 (EST)

===Basic Integration of Images/Linking to Images===
John (Walsh) suggested covering the <figure> tag. Additionally, it might be useful to have a general discussion on image types (binary vs. SVG vs. characters (i.e. trying to find matching Unicode characters for special symbols instead of integrating them as images)) and the different encoding practices they imply. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:18, 5 December 2011 (EST)
====Examples====
Here's an example of different encodings for the same image. The image I'd like to represent is the wedge-shaped marking that indicates that the word "war" is to be inserted into the line below.

[[File:Fontane-30633-detail.jpg|200px]]
* binary: the marking is extracted from the scan and provided as a separate file which is pointed to in the TEI code and displayed at the appropriate position in the transcribed text.
[[File:Fontane-30633-detail2.png|75px]]<pre><nowiki>
<figure><graphic url="myfilename.png"/></figure>
</nowiki></pre>
'''pro:''' representing an image through a digital image results in probably the strongest resemblance to the original image. '''con:''' it is quite a lot of work to extract the image from the scan; the TEI code provides hardly any semantics or searchability (except for the filename, or additional information in <figure>); the image can be difficult to align and position, especially if other reference points than the upper left corner of the image are to be used (see according sections) - anchor points generated by e.g. the Text Image Link Editor in TextGrid might provide a workaround for this problem.
* SVG: an SVG drawing is designed that resembles the original image. Simplified measurements, obtained from measuring the image on the original page or its facsimile, are provided in the TEI code, from which the SVG is created by a transformation stylesheet.
<pre><nowiki>
<svg xmlns="http://www.w3.org/2000/svg" width="0.9cm" height="1em">
<line x1="0" y1="0" x2="0.3cm" y2="1em" style="stroke:black; stroke-width:2px;" />
<line x1="0.3cm" y1="1em" x2="0.9cm" y2="0" style="stroke:black; stroke-width:2px;" />
</svg>
</nowiki></pre>
<pre><nowiki>
<figure rend="marking_V(left:0.3cm;right:0.6cm)"/>
</nowiki></pre>
This TEI code indicates that it's a "V"-shaped marking, with a left side of 3 mm width and a right side of 6 mm width. (The height is fixed at 1 em.) From these measurements, the SVG code above is created during transformation.

--[[User:Martin de la Iglesia|Martin de la Iglesia]] 06:27, 5 January 2012 (EST)

===Linking to Facsimile Page Images===
This is another topic suggested by John ("using <facsimile> and @facs to link to facsimile page images"). --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:23, 5 December 2011 (EST)

You might draw upon [http://www.tei-c.org/SIG/Libraries/teiinlibraries/main-driver.html#txtimglnk this section] of the [http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries]. ([[User:Kshawkin|Kshawkin]] 08:26, 2 December 2011 (EST))
:Thanks, Kevin. I wasn't aware of that section. There's one thing I don't understand about the third approach: in the sample METS document, which is the ID that is used in @xml:id in the TEI code? --[[User:Martin de la Iglesia|Martin de la Iglesia]] 05:35, 7 December 2011 (EST)

:: Hmm, I agree that the recommendation isn't at all clear, and I actually don't know METS very well. I've made a note to revisit this in a future revision to the Best Practices. In the meantime, if you know METS well, you might look at the sample METS document linked to from the Best Practices. If that doesn't clarify, I'd contact my coeditor Michelle Dalmau: I think she will know. --[[User:Kshawkin|Kshawkin]] 10:04, 12 December 2011 (EST)
:::Thanks again. Michelle explained it to me and now I see the usefulness of this method, at least in some projects. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 09:47, 21 December 2011 (EST)

===Positioning an Image===
What I'd like to see here is a discussion of the <surface>/<zone> coordinate positioning system vs. <ptr>-like positioning solutions, and maybe of other systems as well (e.g. lines and margin for y and x axis positioning). --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:28, 5 December 2011 (EST)
====Examples====
* metric margins in CSS style for x and y axis starting points, counting from leaf borders (height and width are determined by the figure itself): <pre><figure style="margin-left:1.2cm; margin-top:3.4cm">...</figure></pre>
* CSS style margins in percent: <pre><figure style="margin-left:12%; margin-top:34%">...</figure></pre>
* CSS style margins in lines for y axis (not valid CSS, but line alignment can be important in some cases): <pre><figure style="margin-left:1.2cm" rend="margin-top:7lines">...</figure></pre> (i.e. the image starts in line 8)
* added height and width:
<pre><nowiki>
<figure style="margin-left:1.2cm; margin-top:3.4cm">
<figDesc>
<dimensions>
<height quantity="12.3" unit="cm"/>
<width quantity="7.5" unit="cm"/>
</dimensions>
</figDesc>
</figure>
</nowiki></pre>
--[[User:Martin de la Iglesia|Martin de la Iglesia]] 05:21, 4 January 2012 (EST)

: On the use of CSS in @rend, see [[Future_changes_to_Best_Practices_for_TEI_in_Libraries#.40rend_vs._.40html:style_for_CSS_values|this discussion]]. ([[User:Kshawkin|Kshawkin]] 18:24, 6 January 2012 (EST))
::Thanks, Kevin, I wasn't aware of that. See my comment there. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:18, 10 January 2012 (EST)

::Alright, so we should add that there might be a problem with whitespaces in CSS style values, and that @html:style can be used as an alternative to @rend. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:03, 16 January 2012 (EST)
:::Substituted @rend with @style where applicable. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 05:19, 2 August 2013 (EDT)

* coordinates in <zone> (or <surface> where applicable); coordinate values follow the system employed in the TEI document (here: centimeters):
<pre><nowiki>
<zone ulx="1.2" uly="0.5" lrx="3.5" lry="7.1">
<figure>...</figure>
</zone>
</nowiki></pre>
--[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:39, 5 August 2013 (EDT)

===Image-Text Linking===
This section should cover the encoding of different kinds of image-text relationships (e.g. an image illustrating a text paragraph, or a text paragraph describing an image), other than merely topographical ones which are covered in the following section, Image-Text Alignment. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:40, 5 December 2011 (EST)

===Image-Text Alignment===
How to position text relative to an image, or an image relative to text (including special cases such as an image pointing at a character, or an image pointing at two separate characters) should be covered here. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:43, 5 December 2011 (EST)
* Here's an example of the latter case: in the following part of a scan from a 19th century German manuscript, a line connects two separate paragraphs. I'd be happy to represent this in the transcript as a straight SVG line that goes roughly from the word "Nissen" to "wird", but how to encode (and XSL-transform) this?
[[File:Fontane-30621-detail.jpg|200px]]

--[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:33, 21 December 2011 (EST)

* line numbers for images - this is an issue in editions in general and not specific to TEI, but still: if there's an image spanning the whole width of a page, and which is preceded and followed by writing, how does it fit in an editorial line numbering system? Should the image have its own line number, or should the image be ignored when numbering the regular text lines? --[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:53, 5 August 2013 (EDT)

===Image Metadata===
I'm thinking primarily of content description texts, but we could embed this in a general discussion of how (or whether) to encode any "invisible" aspects of images. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 04:34, 5 December 2011 (EST)
* classification in @type:
<pre><nowiki>
<figure type="floor_plan">...</figure>
</nowiki></pre>
Are there any suitable vocabularies that could be used for this kind of indexing? --[[User:Martin de la Iglesia|Martin de la Iglesia]] 07:47, 5 August 2013 (EDT)