Module 4: Poetry

5. Metaphorical Language

Just like any other aspect of the transcription and encoding process, analysing metaphorical language involves interpretation. Unlike the expression of this interpretation in structural markup, the analysis of metaphorical language addresses logical structures that probably will cross structural boundaries. Due to the primary focus of the TEI encoding scheme on representing structural characteristics of texts, and the syntactic requirement that all XML structures should nest properly, this kind of logical analysis will need a kind of workaround. One such workaround defines different analytic categories separately and links them to the relevant passages in the poems. A first requirement is that the smallest addressable structures be identified with an @xml:id attribute:
<lg xml:id="p001" type="poem">
<lg xml:id="s001" type="stanza">
<l xml:id="l001">Poppadom</l>
<l xml:id="l002">Oatmeal</l>
<l xml:id="l003">Bubble gum</l>
<l xml:id="l004">Cut of veal</l>
</lg>
<lg xml:id="s002" type="stanza">
<l xml:id="l005">Mince for pie</l>
<l xml:id="l006">Frozen peas</l>
<l xml:id="l007">Video for Guy</l>
<l xml:id="l008">Selection of teas</l>
</lg>
<lg xml:id="s003" type="stanza">
<l xml:id="l009">Paper towels/garbage bags</l>
<l xml:id="l010">Pasta sauce and Parmesan</l>
<l xml:id="l011">Pumpkin seed and olive oil</l>
</lg>
<lg xml:id="s004" type="stanza">
<l xml:id="l012">Cheesy crisps and favourite mags</l>
<l xml:id="l013">Kidney beans (1 large can)</l>
<l xml:id="l014">Cling film and kitchen foil</l>
</lg>
</lg>

Note:

@xml:id provides a unique identifier for the element bearing the attribute. Its value must start with a letter, or '_' and may be followed by one or more Named Characters (letter, digit, '.' , '-' , '_', Unicode Combining Character, or Extender). See the XML Specification for more guidance on the use of @xml:id.
These @xml:id values can later be used to identify spans of interpretive categories. Such interpretive spans are encoded as <span>, identifying the structural scope of this interpretation with the @to attribute marking its beginning and the @from attribute marking its end. Their values are values for an @xml:id attribute elsewhere in the document. Preferably, the @resp attribute is used to identify who is responsible for the interpretation. Related <span> elements can be grouped in a <spanGrp> element. A @type attribute can characterise the kind of analysis. In our poem, one way of identifying all images concerned with food and non-food could be:
<lg xml:id="p001" type="poem">
<lg xml:id="s001" type="stanza">
<l xml:id="l001">Poppadom</l>
<l xml:id="l002">Oatmeal</l>
<l xml:id="l003">Bubble gum</l>
<l xml:id="l004">Cut of veal</l>
</lg>
<lg xml:id="s002" type="stanza">
<l xml:id="l005">Mince for pie</l>
<l xml:id="l006">Frozen peas</l>
<l xml:id="l007">Video for Guy</l>
<l xml:id="l008">Selection of teas</l>
</lg>
<lg xml:id="s003" type="stanza">
<l xml:id="l009">Paper towels/garbage bags</l>
<l xml:id="l010">Pasta sauce and Parmesan</l>
<l xml:id="l011">Pumpkin seed and olive oil</l>
</lg>
<lg xml:id="s004" type="stanza">
<l xml:id="l012">Cheesy crisps and favourite mags</l>
<l xml:id="l013">Kidney beans (1 large can)</l>
<l xml:id="l014">Cling film and kitchen foil</l>
</lg>
</lg>
<spanGrp resp="RvdB" type="imagery">
<span from="#l001" to="#l006">food</span>
<span from="#l007">non-food</span>
<span from="#l008">food</span>
<span from="#l009">non-food</span>
<span from="#l010" to="#l013">food</span>
<span from="#l014">non-food</span>
</spanGrp>
Note that the @from attribute is mandatory. The @to attribute is optional; when it is missing, the entire structure identified by the @from attribute will be taken as the context for the interpretation.

Note:

The value of the @resp must be a pointer to an element in the document header that is associated with a person asserted as responsible for some aspect of the text's creation, transcription, editing, or encoding. See P5 14 Certainty and Responsibility.
As will be clear from this example, this system of linking analyses to textual structures is not very economic when discontinuous structures share the same analysis. Another approach for logical analysis works from the opposite angle by hooking text structures to specific interpretations. In order to do so, interpretive categories should be formally defined somewhere else, be it in the same document or externally. This is done inside the <interp> element, bearing a unique @xml:id attribute. Related interpretive categories can be grouped inside an <interpGrp> element. Following example could identify the same semantic categories from the previous example:
<interpGrp resp="RvdB" type="imagery">
<interp xml:id="food">food</interp>
<interp xml:id="non-food">non-food</interp>
</interpGrp>
Inside the transcription of the poem, reference can be made to these interpretations with the @ana attribute. Its value should always point to an identifier, either locally or externally. Suppose these interpretive categories are stored in a separate document named "analysis.xml". Then the poem could be analysed as follows:
<lg type="poem">
<lg ana="analysis.xml#food" type="stanza">
<l>Poppadom</l>
<l>Oatmeal</l>
<l>Bubble gum</l>
<l>Cut of veal</l>
</lg>
<lg xml:id="s002" type="stanza">
<l ana="analysis.xml#food">Mince for pie</l>
<l ana="analysis.xml#food">Frozen peas</l>
<l ana="analysis.xml#non-food">Video for Guy</l>
<l ana="analysis.xml#food">Selection of teas</l>
</lg>
<lg xml:id="s003" type="stanza">
<l ana="analysis.xml#non-food">Paper towels/garbage bags</l>
<l ana="analysis.xml#food">Pasta sauce and Parmesan</l>
<l ana="analysis.xml#food">Pumpkin seed and olive oil</l>
</lg>
<lg xml:id="s004" type="stanza">
<l ana="analysis.xml#food">Cheesy crisps and favourite mags</l>
<l ana="analysis.xml#food">Kidney beans (1 large can)</l>
<l ana="analysis.xml#non-food">Cling film and kitchen foil</l>
</lg>
</lg>

Note:

Of course, analyses can be much more complex. The TEI provides a generic mechanism for expressing complex hierarchies of interpretive relationships, called "Feature Structures". See P5 12 "Feature Structures" for a detailed treatment.

Summary

For the study of metaphorical language in poetry, logical structures should be identified and grouped into interpretive categories which can be related to other such categories. These interpretive categories with their logical relationships can be stored inside out outside the XML document. Reference from within the poem can be made to these internally or externally documented analysis.