https://github.com/TEIC/TEI
Tip revision: 347c64fac3fa1a64ade0d8d1842813d4b8f7acec authored by Hugh Cayless on 12 May 2017, 16:57:59 UTC
Updates.
Updates.
Tip revision: 347c64f
VE.html
<!DOCTYPE html
SYSTEM "about:legacy-compat">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><!--THIS FILE IS GENERATED FROM AN XML MASTER. DO NOT EDIT (4)--><title>6 Verse - The TEI Guidelines</title><meta property="Language" content="en" /><meta property="DC.Title" content="6 Verse - The TEI Guidelines" /><meta property="DC.Language" content="SCHEME=iso639 en" /><meta property="DC.Creator.Address" content="tei@oucs.ox.ac.uk" /><meta charset="utf-8" /><link href="guidelines.css" rel="stylesheet" type="text/css" /><link href="odd.css" rel="stylesheet" type="text/css" /><link rel="stylesheet" media="print" type="text/css" href="guidelines-print.css" /><script type="text/javascript" src="jquery-1.2.6.min.js"></script><script type="text/javascript" src="columnlist.js"></script><script type="text/javascript" src="popupFootnotes.js"></script><script type="text/javascript">
$(function() {
$('ul.attrefs-class').columnizeList({cols:3,width:30,unit:'%'});
$('ul.attrefs-element').columnizeList({cols:3,width:30,unit:'%'});
$(".displayRelaxButton").click(function() {
$(this).parent().find('.RNG_XML').toggle();
$(this).parent().find('.RNG_Compact').toggle();
});
$(".tocTree .showhide").click(function() {
$(this).find(".tocShow,.tocHide").toggle();
$(this).parent().find("ul.continuedtoc").toggle();
});
})
</script><script type="text/javascript"><!--
var displayXML=0;
states=new Array()
states[0]="element-a"
states[1]="element-b"
states[2]="element-c"
states[3]="element-d"
states[4]="element-e"
states[5]="element-f"
states[6]="element-g"
states[7]="element-h"
states[8]="element-i"
states[9]="element-j"
states[10]="element-k"
states[11]="element-l"
states[12]="element-m"
states[13]="element-n"
states[14]="element-o"
states[15]="element-p"
states[16]="element-q"
states[17]="element-r"
states[18]="element-s"
states[19]="element-t"
states[20]="element-u"
states[21]="element-v"
states[22]="element-w"
states[23]="element-x"
states[24]="element-y"
states[25]="element-z"
function startUp() {
}
function hideallExcept(elm) {
for (var i = 0; i < states.length; i++) {
var layer;
if (layer = document.getElementById(states[i]) ) {
if (states[i] != elm) {
layer.style.display = "none";
}
else {
layer.style.display = "block";
}
}
}
var mod;
if ( mod = document.getElementById('byMod') ) {
mod.style.display = "none";
}
}
function showall() {
for (var i = 0; i < states.length; i++) {
var layer;
if (layer = document.getElementById(states[i]) ) {
layer.style.display = "block";
}
}
}
function showByMod() {
hideallExcept('');
var mod;
if (mod = document.getElementById('byMod') ) {
mod.style.display = "block";
}
}
--></script></head><body><div id="container"><div id="banner"><img src="Images/banner.jpg" alt="Text Encoding Initiative logo and banner" /></div></div><div class="mainhead"><h1>P5:
Guidelines for Electronic Text Encoding and Interchange</h1><p>Version 3.1.1a. Last updated on
10th May 2017, revision bd8dda3</p></div><div id="onecol" class="main-content"><h2><span class="headingNumber">6 </span>Verse</h2><div class="div1" id="VE"><div class="miniTOC miniTOC_left"><p><span class="subtochead">Table of contents</span></p><div class="subtoc"><ul class="subtoc"><li class="subtoc"><a class="subtoc" href="VE.html#VEST" title="Structural Divisions of Verse Texts">6.1 Structural Divisions of Verse Texts</a></li><li class="subtoc"><a class="subtoc" href="VE.html#VESE" title="Components of the Verse Line">6.2 Components of the Verse Line</a></li><li class="subtoc"><a class="subtoc" href="VE.html#VESA" title="Encoding Textual Structures Across Verses">6.3 Encoding Textual Structures Across Verses</a></li><li class="subtoc"><a class="subtoc" href="VE.html#VEME" title="Rhyme and Metrical Analysis">6.4 Rhyme and Metrical Analysis</a></li><li class="subtoc"><a class="subtoc" href="VE.html#VERH" title="Rhyme">6.5 Rhyme</a></li><li class="subtoc"><a class="subtoc" href="VE.html#HDMN" title="Metrical Notation Declaration">6.6 Metrical Notation Declaration</a></li><li class="subtoc"><a class="subtoc" href="VE.html#VEETC" title="Encoding Procedures for Other Verse Features">6.7 Encoding Procedures for Other Verse Features</a></li><li class="subtoc"><a class="subtoc" href="VE.html#VESTR" title="Module for Verse">6.8 Module for Verse</a></li></ul></div><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="WD.html"><span class="headingNumber">5 </span>Characters, Glyphs, and Writing Modes</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="DR.html"><span class="headingNumber">7 </span>Performance Texts</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><p>This module is intended for use when encoding texts which are entirely or predominantly in verse, and for which the elements for encoding verse structure already provided by the core module are inadequate.</p><p>The tags described in section <a class="link_ptr" href="CO.html#COVE" title="Core Tags for Verse"><span class="headingNumber">3.12.1 </span>Core Tags for Verse</a> include elements for the encoding of verse lines and line groups such as stanzas: these are available for any TEI document, irrespective of the module it uses. Like the modules for prose and for drama, the module for verse additionally makes use of the module defined in chapter <a class="link_ptr" href="DS.html" title="7"><span class="headingNumber">4 </span>Default Text Structure</a> to define the basic formal structure of a text, in terms of <a class="gi" title="(front matter) contains any prefatory matter (headers, abstracts, title page, prefaces, dedications, etc.) found at the start of a document, before the main body." href="ref-front.html">front</a>, <a class="gi" title="(text body) contains the whole body of a single unitary text, excluding any front or back matter." href="ref-body.html">body</a> and <a class="gi" title="(back matter) contains any appendixes, etc. following the main part of a text." href="ref-back.html">back</a> elements and the text-division elements into which these may be subdivided.</p><p>The module for verse extends the facilities provided by these modules in the following ways: </p><ul class="bulleted"><li class="item">a special purpose <a class="gi" title="marks the point at which a metrical line may be divided." href="ref-caesura.html">caesura</a> element is provided, to allow for segmentation of the verse line (see section <a class="link_ptr" href="VE.html#VESE" title="Components of the Verse Line"><span class="headingNumber">6.2 </span>Components of the Verse Line</a>)</li><li class="item">a set of attributes is provided for the encoding of rhyme scheme and metrical information (see sections <a class="link_ptr" href="VE.html#VEME" title="Rhyme and Metrical Analysis"><span class="headingNumber">6.4 </span>Rhyme and Metrical Analysis</a> and <a class="link_ptr" href="VE.html#VERH" title="Rhyme"><span class="headingNumber">6.5 </span>Rhyme</a>)</li><li class="item">a special purpose <a class="gi" title="marks the rhyming part of a metrical line." href="ref-rhyme.html">rhyme</a> element is provided to support simple analysis of rhyming words (see section <a class="link_ptr" href="VE.html#VERH" title="Rhyme"><span class="headingNumber">6.5 </span>Rhyme</a>)</li></ul><div class="div2" id="VEST"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="VE.html#VESE"><span class="headingNumber">6.2 </span>Components of the Verse Line</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#VEST" title="link to this section "><span class="invisible">TEI: Structural Divisions of Verse Texts</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">6.1 </span><span class="head">Structural Divisions of Verse Texts</span></h3><p>Like other kinds of text, texts written in verse may be of widely differing lengths and structures. A complete poem, no matter how short, may be treated as a free-standing text, and encoded in the same way as a distinct prose text. A group of poems functioning as a single unit may be encoded either as a <a class="gi" title="contains the body of a composite text, grouping together a sequence of distinct texts (or groups of such texts) which are regarded as a unit for some purpose, for example the collected works of an author, a sequence of prose essays, etc." href="ref-group.html">group</a> or as a <a class="gi" title="contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample." href="ref-text.html">text</a>, depending on the encoder's view of the text. For further discussion, including an example encoding for a verse anthology, see chapter <a class="link_ptr" href="DS.html" title="7"><span class="headingNumber">4 </span>Default Text Structure</a>.</p><div class="p">Many poems consist only of ungrouped lines. This short poem by Emily Dickinson is a simple case: <div id="index-egXML-d52e60035" class="pre egXML_valid"><span class="element"><text></span><br /> <span class="element"><front></span><br /> <span class="element"><head></span>1755<span class="element"></head></span><br /> <span class="element"></front></span><br /> <span class="element"><body></span><br /> <span class="element"><l></span>To make a prairie it takes a clover and one bee,<span class="element"></l></span><br /> <span class="element"><l></span>One clover, and a bee,<span class="element"></l></span><br /> <span class="element"><l></span>And revery.<span class="element"></l></span><br /> <span class="element"><l></span>The revery alone will do,<span class="element"></l></span><br /> <span class="element"><l></span>If bees are few.<span class="element"></l></span><br /> <span class="element"></body></span><br /><span class="element"></text></span><div style="float: right;"><a href="BIB.html#VEST-eg-1">bibliography</a> </div></div> </div><div class="p">Often, however, lines are grouped, formally or informally, into stanzas, verse paragraphs, etc. The <a class="gi" title="(line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc." href="ref-lg.html">lg</a> element defined in the core tag set (in section <a class="link_ptr" href="CO.html#COVE" title="Core Tags for Verse"><span class="headingNumber">3.12.1 </span>Core Tags for Verse</a>) may be used for all such groupings. It may thus serve for informal groupings of lines such as those of the following example from Allen Ginsberg: <div id="index-egXML-d52e60065" class="pre egXML_valid"><span class="element"><text></span><br /> <span class="element"><body></span><br /> <span class="element"><head></span>My Alba<span class="element"></head></span><br /> <span class="element"><lg></span><br /> <span class="element"><l></span>Now that I've wasted<span class="element"></l></span><br /> <span class="element"><l></span>five years in Manhattan<span class="element"></l></span><br /> <span class="element"><l></span>life decaying<span class="element"></l></span><br /> <span class="element"><l></span>talent a blank<span class="element"></l></span><br /> <span class="element"></lg></span><br /> <span class="element"><lg></span><br /> <span class="element"><l></span>talking disconnected<span class="element"></l></span><br /> <span class="element"><l></span>patient and mental<span class="element"></l></span><br /> <span class="element"><l></span>sliderule and number<span class="element"></l></span><br /> <span class="element"><l></span>machine on a desk<span class="element"></l></span><br /> <span class="element"></lg></span><br /> <span class="element"></body></span><br /><span class="element"></text></span><div style="float: right;"><a href="BIB.html#VEST-eg-2">bibliography</a> </div></div> </div><div class="p">It may also be used to mark the verse paragraphs into which longer poems are often divided, as in the following example from Samuel Taylor Coleridge's <span class="titlem">Frost at Midnight</span>: <div id="index-egXML-d52e60100" class="pre egXML_valid"><span class="element"><lg></span><br /> <span class="element"><l></span>The Frost performs its secret ministry,<span class="element"></l></span><br /> <span class="element"><l></span>Unhelped by any wind. ...<span class="element"></l></span><br /> <span class="element"><l></span>Whose puny flaps and freaks the idling Spirit<span class="element"></l></span><br /> <span class="element"><l></span>By its own moods interprets, every where<span class="element"></l></span><br /> <span class="element"><l></span>Echo or mirror seeking of itself,<span class="element"></l></span><br /> <span class="element"><l <span class="attribute">part</span>="<span class="attributevalue">I</span>"></span>And makes a toy of Thought.<span class="element"></l></span><br /><span class="element"></lg></span><br /><span class="element"><lg></span><br /> <span class="element"><l <span class="attribute">part</span>="<span class="attributevalue">F</span>"></span>But O! how oft,<span class="element"></l></span><br /> <span class="element"><l></span>How oft, at school, with most believing mind<span class="element"></l></span><br /> <span class="element"><l></span>Presageful, have I gazed upon the bars,<span class="element"></l></span><br /> <span class="element"><l></span>To watch that fluttering <span class="element"><hi></span>stranger<span class="element"></hi></span>! ... <span class="element"></l></span><br /><span class="element"></lg></span><br /><span class="element"><lg></span><br /> <span class="element"><l></span>Dear Babe, that sleepest cradled by my side,<span class="element"></l></span><br /><span class="element"></lg></span><div style="float: right;"><a href="BIB.html#VEST-eg-3">bibliography</a> </div></div> Note, in the above example, the use of the <span class="att">part</span> attribute on the <a class="gi" title="(verse line) contains a single, possibly incomplete, line of verse." href="ref-l.html">l</a> element, where a verse line is broken between two line groups, as discussed in section <a class="link_ptr" href="CO.html#COVE" title="Core Tags for Verse"><span class="headingNumber">3.12.1 </span>Core Tags for Verse</a>.</div><div class="p">Most typically, however, the <a class="gi" title="(line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc." href="ref-lg.html">lg</a> element is used to mark the highly regular line groups which characterize stanzaic and similar verse forms, as in the following example from Chaucer: <div id="index-egXML-d52e60146" class="pre egXML_valid"><span class="element"><lg></span><br /> <span class="element"><l></span>Sire Thopas was a doghty swayn;<span class="element"></l></span><br /> <span class="element"><l></span>White was his face as payndemayn,<span class="element"></l></span><br /> <span class="element"><l></span>His lippes rede as rose;<span class="element"></l></span><br /> <span class="element"><l></span>His rode is lyk scarlet in grayn,<span class="element"></l></span><br /> <span class="element"><l></span>And I yow telle in good certayn,<span class="element"></l></span><br /> <span class="element"><l></span>He hadde a semely nose.<span class="element"></l></span><br /><span class="element"></lg></span><br /><span class="element"><lg></span><br /> <span class="element"><l></span>His heer, his ber was lyk saffroun,<span class="element"></l></span><br /> <span class="element"><l></span>That to his girdel raughte adoun;<span class="element"></l></span><br /><span class="element"></lg></span><div style="float: right;"><a href="BIB.html#VEST-eg-4">bibliography</a> </div></div> </div><div class="p">Like other text-division elements, <a class="gi" title="(line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc." href="ref-lg.html">lg</a> elements may be nested hierarchically. For example, one particularly common English stanzaic form consists of a quatrain or sestet followed by a couplet. The <a class="gi" title="(line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc." href="ref-lg.html">lg</a> element may be used to encode both the stanza and its components, as in the following example from Byron: <div id="index-egXML-d52e60176" class="pre egXML_valid"><span class="element"><lg <span class="attribute">type</span>="<span class="attributevalue">stanza</span>"></span><br /> <span class="element"><lg <span class="attribute">type</span>="<span class="attributevalue">sestet</span>"></span><br /> <span class="element"><l></span>In the first year of Freedom's second dawn<span class="element"></l></span><br /> <span class="element"><l></span>Died George the Third; although no tyrant, one<span class="element"></l></span><br /> <span class="element"><l></span>Who shielded tyrants, till each sense withdrawn<span class="element"></l></span><br /> <span class="element"><l></span>Left him nor mental nor external sun:<span class="element"></l></span><br /> <span class="element"><l></span>A better farmer ne'er brushed dew from lawn,<span class="element"></l></span><br /> <span class="element"><l></span>A worse king never left a realm undone!<span class="element"></l></span><br /> <span class="element"></lg></span><br /> <span class="element"><lg <span class="attribute">type</span>="<span class="attributevalue">couplet</span>"></span><br /> <span class="element"><l></span>He died — but left his subjects still behind,<span class="element"></l></span><br /> <span class="element"><l></span>One half as mad — and t'other no less blind.<span class="element"></l></span><br /> <span class="element"></lg></span><br /><span class="element"></lg></span><div style="float: right;"><a href="BIB.html#VEST-eg-5">bibliography</a> </div></div> </div><p>Note the use of the <span class="att">type</span> attribute to name the type of unit encoded by the <a class="gi" title="(line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc." href="ref-lg.html">lg</a> element; this attribute is common to all members of the <a class="link_odd" title="provides attributes common to all elements which behave in the same way as divisions." href="ref-att.divLike.html">att.divLike</a> class (see section <a class="link_ptr" href="DS.html#DSDIV1" title="Unnumbered Divisions"><span class="headingNumber">4.1.1 </span>Un-numbered Divisions</a>).<span id="Note67_return"><a class="notelink" title="For discussion of other attributes of this class, see ." href="#Note67"><sup>30</sup></a></span> When used on <a class="gi" title="(line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc." href="ref-lg.html">lg</a>, the <span class="att">type</span> attribute is intended solely for conventional names of different classes of text block. For systematic analysis of metrical and rhyme schemes, use the <span class="att">met</span> and <span class="att">rhyme</span> attributes, for which see below, section <a class="link_ptr" href="VE.html#VEME" title="Rhyme and Metrical Analysis"><span class="headingNumber">6.4 </span>Rhyme and Metrical Analysis</a>.</p><div class="p">As a further example, consider the Shakespearean sonnet. This may be divided into two parts: a concluding couplet, and a body of twelve lines, itself subdivided into three quatrains: <div id="index-egXML-d52e60242" class="pre egXML_valid"><span class="element"><text></span><br /> <span class="element"><body></span><br /> <span class="element"><lg></span><br /> <span class="element"><lg <span class="attribute">type</span>="<span class="attributevalue">quatrain</span>"></span><br /> <span class="element"><l></span>My Mistres eyes are nothing like the Sunne,<span class="element"></l></span><br /> <span class="element"><l></span>Currall is farre more red, then her lips red<span class="element"></l></span><br /> <span class="element"><l></span>If snow be white, why then her brests are dun:<span class="element"></l></span><br /> <span class="element"><l></span>If haires be wiers, black wiers grown on her head:<span class="element"></l></span><br /> <span class="element"></lg></span><br /> <span class="element"><lg <span class="attribute">type</span>="<span class="attributevalue">quatrain</span>"></span><br /> <span class="element"><l></span>I have seene Roses damaskt, red and white,<span class="element"></l></span><br /> <span class="element"><l></span>But no such Roses see I in her cheekes,<span class="element"></l></span><br /> <span class="element"><l></span>And in some perfumes is there more delight,<span class="element"></l></span><br /> <span class="element"><l></span>Then in the breath that from my Mistres reekes.<span class="element"></l></span><br /> <span class="element"></lg></span><br /> <span class="element"><lg <span class="attribute">type</span>="<span class="attributevalue">quatrain</span>"></span><br /> <span class="element"><l></span>I love to heare her speake, yet well I know,<span class="element"></l></span><br /> <span class="element"><l></span>That Musicke hath a farre more pleasing sound:<span class="element"></l></span><br /> <span class="element"><l></span>I graunt I never saw a goddesse goe,<span class="element"></l></span><br /> <span class="element"><l></span>My Mistres when shee walkes treads on the ground.<span class="element"></l></span><br /> <span class="element"></lg></span><br /> <span class="element"></lg></span><br /> <span class="element"><lg <span class="attribute">type</span>="<span class="attributevalue">couplet</span>"></span><br /> <span class="element"><l></span>And yet by heaven I think my love as rare,<span class="element"></l></span><br /> <span class="element"><l></span>As any she beli'd with false compare.<span class="element"></l></span><br /> <span class="element"></lg></span><br /> <span class="element"></body></span><br /><span class="element"></text></span><div style="float: right;"><a href="BIB.html#VEST-eg-6">bibliography</a> </div></div> </div><p>Particularly lengthy poetic texts are often subdivided into units larger than stanzas or paragraphs, which may themselves be subdivided. Spenser's <span class="titlem">Faery Queene</span>, for example, consists of twelve ‘books’ each of which contains a prologue followed by twelve ‘cantos’. Each prologue and each canto consists of nine-line ‘stanzas’, each of which follows the same regular pattern. Other examples in the same tradition are easy to find.</p><div class="p">Large structures of this kind are most conveniently represented by <a class="gi" title="(text division) contains a subdivision of the front, body, or back of a text." href="ref-div.html">div</a> or <a class="gi" title="(level-1 text division) contains a first-level subdivision of the front, body, or back of a text." href="ref-div1.html">div1</a> elements, as described in section <a class="link_ptr" href="DS.html#DSDIV" title="Divisions of the Body"><span class="headingNumber">4.1 </span>Divisions of the Body</a>. Thus the start of the <span class="titlem">Faerie Queene</span> might be encoded as follows: <div id="index-egXML-d52e60308" class="pre egXML_valid"><span class="element"><body></span><br /> <span class="element"><div <span class="attribute">n</span>="<span class="attributevalue">I</span>" <span class="attribute">type</span>="<span class="attributevalue">book</span>"></span><br /> <span class="element"><div <span class="attribute">n</span>="<span class="attributevalue">1</span>" <span class="attribute">type</span>="<span class="attributevalue">canto</span>"></span><br /> <span class="element"><lg <span class="attribute">n</span>="<span class="attributevalue">I.1.1</span>" <span class="attribute">type</span>="<span class="attributevalue">stanza</span>"></span><br /> <span class="element"><l></span>A Gentle Knight was pricking on the plain<span class="element"></l></span><br /> <span class="element"><l></span>Y cladd in mightie armes and silver shielde,<span class="element"></l></span><br /> <span class="element"></lg></span><br /> <span class="element"></div></span><br /> <span class="element"></div></span><br /><span class="element"></body></span><div style="float: right;"><a href="BIB.html#VE-eg-01">bibliography</a> </div></div> The encoder must choose at which point in the hierarchy of structural units to introduce <a class="gi" title="(line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc." href="ref-lg.html">lg</a> elements rather than a yet smaller <a class="gi" title="(text division) contains a subdivision of the front, body, or back of a text." href="ref-div.html">div</a> element: it would (for example) also be possible to encode the above example as follows:<div id="index-egXML-d52e60325" class="pre egXML_valid"><span class="element"><body></span><br /> <span class="element"><div <span class="attribute">n</span>="<span class="attributevalue">I</span>" <span class="attribute">type</span>="<span class="attributevalue">book</span>"></span><br /> <span class="element"><div <span class="attribute">n</span>="<span class="attributevalue">I.1</span>" <span class="attribute">type</span>="<span class="attributevalue">canto</span>"></span><br /> <span class="element"><div <span class="attribute">n</span>="<span class="attributevalue">I.1.1</span>" <span class="attribute">type</span>="<span class="attributevalue">stanza</span>"></span><br /> <span class="element"><l></span>A gentle knight was pricking on the plain<span class="element"></l></span><br /> <span class="element"><l></span>Ycladd in mightie armes and silver shielde,<span class="element"></l></span><br /> <span class="element"></div></span><br /> <span class="element"></div></span><br /> <span class="element"></div></span><br /><span class="element"></body></span><div style="float: right;"><a href="BIB.html#VE-eg-01">bibliography</a> </div></div></div><p>One reason for using <a class="gi" title="(text division) contains a subdivision of the front, body, or back of a text." href="ref-div.html">div</a> rather than <a class="gi" title="(line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc." href="ref-lg.html">lg</a> elements is that the former may contain non-metrical elements, such as epigraphs or dedications and other members of the <a class="link_odd" title="groups elements appearing at the beginning of a text division." href="ref-model.divTop.html">model.divTop</a> class, whereas <a class="gi" title="(line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc." href="ref-lg.html">lg</a> elements may contain only headings or metrical lines.</p></div><div class="div2" id="VESE"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="VE.html#VEST"><span class="headingNumber">6.1 </span>Structural Divisions of Verse Texts</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="VE.html#VESA"><span class="headingNumber">6.3 </span>Encoding Textual Structures Across Verses</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#VESE" title="link to this section "><span class="invisible">TEI: Components of the Verse Line</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">6.2 </span><span class="head">Components of the Verse Line</span></h3><p>It is often convenient for various kinds of analysis to encode subdivisions of verse lines. The general purpose <a class="gi" title="(arbitrary segment) represents any segmentation of text below the ‘chunk’ level." href="ref-seg.html">seg</a> element defined in the tag set for segmentation and alignment (section <a class="link_ptr" href="SA.html#SASE" title="Blocks Segments and Anchors"><span class="headingNumber">16.3 </span>Blocks, Segments, and Anchors</a>) is provided for this purpose: </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-seg.html">seg</a></span> (arbitrary segment) represents any segmentation of text below the ‘chunk’ level.</li></ul><p>To use this element together with the module for verse, the module for segmentation and alignment must also be enabled as further described in section <a class="link_ptr" href="ST.html#STIN" title="Defining a TEI Schema"><span class="headingNumber">1.2 </span>Defining a TEI Schema</a>.</p><div class="p">In Old and Middle English alliterative verse, individual verse lines are typically split into half lines. The <a class="gi" title="(arbitrary segment) represents any segmentation of text below the ‘chunk’ level." href="ref-seg.html">seg</a> element may be used to mark these explicitly, as in the following example from Langland's <span class="titlem">Piers Plowman</span>: <div id="index-egXML-d52e60373" class="pre egXML_valid"><span class="element"><l></span><br /> <span class="element"><seg></span>In a somer<br /> seson,<span class="element"></seg></span><br /> <span class="element"><seg></span>whan softe was the sonne,<span class="element"></seg></span><br /><span class="element"></l></span><br /><span class="element"><l></span><br /> <span class="element"><seg></span>I shoop me into shroudes<span class="element"></seg></span><br /> <span class="element"><seg></span>as I a sheep were,<span class="element"></seg></span><br /><span class="element"></l></span><br /><span class="element"><l></span><br /> <span class="element"><seg></span>In habite as an heremite <span class="element"></seg></span><br /> <span class="element"><seg></span>unholy of werkes,<span class="element"></seg></span><br /><span class="element"></l></span><br /><span class="element"><l></span><br /> <span class="element"><seg></span>Went wide in this world <span class="element"></seg></span><br /> <span class="element"><seg></span>wondres to here.<span class="element"></seg></span><br /><span class="element"></l></span><div style="float: right;"><a href="BIB.html#VESE-eg-9">bibliography</a> </div></div> </div><div class="p">The <a class="gi" title="(arbitrary segment) represents any segmentation of text below the ‘chunk’ level." href="ref-seg.html">seg</a> element can be nested hierarchically, in the same way as the <a class="gi" title="(line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc." href="ref-lg.html">lg</a> element, down to whatever level of detailed structure is required. In the following example, the line has been divided into <span class="term">feet</span>, each of which has been further subdivided into syllables.<span id="Note68_return"><a class="notelink" title="As elsewhere in these Guidelines, this example has been formatted for clarity of exposition rather than correct display. Note in particular that wheth…" href="#Note68"><sup>31</sup></a></span> <div id="index-egXML-d52e60425" class="pre egXML_valid"><span class="element"><l></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">foot</span>"></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>Ar<span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>ma <span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>vi<span class="element"></seg></span><br /> <span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">foot</span>"></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>rum<span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>que <span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>ca<span class="element"></seg></span><br /> <span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">foot</span>"></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>no <span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>Tro<span class="element"></seg></span><br /> <span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">foot</span>"></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>iae <span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>qui <span class="element"></seg></span><br /> <span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">foot</span>"></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>pri<span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>mus <span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>ab <span class="element"></seg></span><br /> <span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">foot</span>"></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>or<span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>is <span class="element"></seg></span><br /> <span class="element"></seg></span><br /><span class="element"></l></span><div style="float: right;"><a href="BIB.html#VE-eg-02">bibliography</a> </div></div></div><p>The <a class="gi" title="(arbitrary segment) represents any segmentation of text below the ‘chunk’ level." href="ref-seg.html">seg</a> element may be used to identify any subcomponent of a line which has content; its type attribute may characterize such units in any way appropriate to the needs of the encoder. For the specific case of labeling each foot with its formal type (<span class="q">‘dactyl’</span>, <span class="q">‘spondee’</span>, etc.), and each syllable with its metrical or prosodic status (syllables bearing primary or secondary stress, long syllables, short syllables), however, the specialized attributes <span class="att">met</span> and <span class="att">real</span> are defined, which provide a more systematic framework than the <span class="att">type</span> attribute; see section <a class="link_ptr" href="VE.html#VEME" title="Rhyme and Metrical Analysis"><span class="headingNumber">6.4 </span>Rhyme and Metrical Analysis</a> below.</p><div class="p">In classical verse, a hexameter like that above may also be formally divided into two <span class="term">cola</span> or ‘hemistiches’. This example provides a typical case, in that the boundary of the first colon falls in the middle of one of the feet (between the syllables <span class="q">‘no’</span> and <span class="q">‘Tro’</span>). If both kinds of segmentation are required, the <span class="att">part</span> attribute might be used to mark the overlapping structure as follows. <div id="index-egXML-d52e60504" class="pre egXML_valid"><span class="element"><l></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">hemistich</span>"></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">foot</span>"></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>Ar<span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>ma <span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>vi<span class="element"></seg></span><br /> <span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">foot</span>"></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>rum<span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>que <span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>ca<span class="element"></seg></span><br /> <span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">foot</span>" <span class="attribute">part</span>="<span class="attributevalue">I</span>"></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>no <span class="element"></seg></span><br /> <span class="element"></seg></span><br /> <span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">hemistich</span>"></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">foot</span>" <span class="attribute">part</span>="<span class="attributevalue">F</span>"></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>Tro<span class="element"></seg></span><br /> <span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">foot</span>"></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>iae <span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">syll</span>"></span>qui <span class="element"></seg></span><br /> <span class="element"></seg></span><br /> <span class="element"></seg></span><br /><span class="element"></l></span><div style="float: right;"><a href="BIB.html#VE-eg-02">bibliography</a> </div></div></div><p>Instead of using the <span class="att">part</span> attribute on the <a class="gi" title="(arbitrary segment) represents any segmentation of text below the ‘chunk’ level." href="ref-seg.html">seg</a> element, it might be simpler just to mark the point at which the caesura occurs. An additional element is provided for analyses of this kind, in which what is to be marked are points <span class="q">‘between the words’</span>, which have some significance within a verse line: </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-caesura.html">caesura</a></span> marks the point at which a metrical line may be divided.</li></ul><p> In classical prosody, the <span class="term">caesura</span>, which occurs within a foot, is distinguished from a <span class="term">diaeresis</span>, which occurs on a foot boundary (not to be confused with the division of a diphthong into two syllables, or the diacritic symbol used to indicate such division, each of which is also termed <span class="term">diaeresis</span>). This distinction is rarely made nowadays, the term <span class="mentioned">caesura</span> being used for any division irrespective of foot boundaries. No special-purpose <span class="gi"><diaeresis></span> element is therefore provided.</p><div class="p">As an example of the <a class="gi" title="marks the point at which a metrical line may be divided." href="ref-caesura.html">caesura</a> element, we refer again to the example from Langland. An encoder might choose simply to record the location of the caesura within each line, rather than encoding each half-line as a segment in its own right, as follows: <div id="index-egXML-d52e60569" class="pre egXML_valid"><span class="element"><l></span>In a somer seson,<br /> <span class="element"><caesura/></span> whan softe was the sonne, <span class="element"></l></span><br /><span class="element"><l></span>I shoop me into shroudes <span class="element"><caesura/></span> as I a sheep were, <span class="element"></l></span><br /><span class="element"><l></span>In habite as an heremite <span class="element"><caesura/></span> unholy of werkes, <span class="element"></l></span><br /><span class="element"><l></span>Went wide in this world <span class="element"><caesura/></span> wondres to here. <span class="element"></l></span><div style="float: right;"><a href="BIB.html#VESE-eg-9">bibliography</a> </div></div> </div><div class="p">Logically, the opposite of caesura might be considered to be <span class="term">enjambement</span>. When the <span class="ident-module">verse</span> module is included in a schema, an additional class called <a class="link_odd" title="(enjambement) provides an attribute which may be used to indicate enjambement of the parent element." href="ref-att.enjamb.html">att.enjamb</a> is defined as follows: <ul class="specList"><li><span class="specList-classSpec"><a href="ref-att.enjamb.html">att.enjamb</a></span> (enjambement) provides an attribute which may be used to indicate enjambement of the parent element.<table class="specDesc"><tr><td class="Attribute"><span class="att">enjamb</span></td><td>(enjambement) indicates that the end of a verse line is marked by enjambement.
Sample values include: 1] no; 2] yes; 3] weak; 4] strong</td></tr></table></li></ul> The following lines demonstrate the use of the <span class="att">enjamb</span> attribute to mark places where there is a discrepancy between the boundaries of the <a class="gi" title="(verse line) contains a single, possibly incomplete, line of verse." href="ref-l.html">l</a> elements and the syntactic structure of the verse (a discrepancy of some significance in some schools of verse): <div id="index-egXML-d52e60609" class="pre egXML_valid"><span class="element"><l <span class="attribute">enjamb</span>="<span class="attributevalue">y</span>"></span>Un astrologue, un jour, se laissa choir<span class="element"></l></span><br /><span class="element"><l></span>Au fond d'un puits.<span class="element"></l></span><div style="float: right;"><a href="BIB.html#VESE-eg-13">bibliography</a> </div></div> </div></div><div class="div2" id="VESA"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="VE.html#VESE"><span class="headingNumber">6.2 </span>Components of the Verse Line</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="VE.html#VEME"><span class="headingNumber">6.4 </span>Rhyme and Metrical Analysis</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#VESA" title="link to this section "><span class="invisible">TEI: Encoding Textual Structures Across Verses</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">6.3 </span><span class="head">Encoding Textual Structures Across Verses</span></h3><p>It is possible that certain textual structures may span multiple lines of verse, either by incorporating more than one, or by crossing line hierarchy. This is common, for example, when lines contain reported thought or speech (i.e. <a class="gi" title="(speech or thought) indicates passages thought or spoken aloud, whether explicitly indicated in the source or not, whether directly or indirectly reported, whether by real people or fictional characters." href="ref-said.html">said</a>), or other forms of quotation (i.e. <a class="gi" title="(quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used." href="ref-q.html">q</a>). For these cases, it is recommended practice to fragment and reconstruct the elements representing the textual structures.</p><div class="p">The following example from Margaret Cavendish's <span class="titlem">Nature's Pictures</span> shows speech encoded across two lines reconstructed by chaining elements with <span class="att">prev</span> and <span class="att">next</span> attributes: <div id="index-egXML-d52e60648" class="pre egXML_valid"><span class="element"><lg <span class="attribute">type</span>="<span class="attributevalue">couplet</span>"></span><br /> <span class="element"><l></span><br /> <span class="element"><said <span class="attribute">xml:id</span>="<span class="attributevalue">eg1-said1</span>"<br /> <span class="attribute">next</span>="<span class="attributevalue">#eg1-said2</span>"></span>Our lives<span class="element"></said></span>, ſaid he,<br /> <span class="element"><said <span class="attribute">xml:id</span>="<span class="attributevalue">eg1-said2</span>"<br /> <span class="attribute">next</span>="<span class="attributevalue">#eg1-said3</span>" <span class="attribute">prev</span>="<span class="attributevalue">#eg1-said1</span>"></span>wee'll give before we yield<span class="element"></said></span>,<br /> <span class="element"></l></span><br /> <span class="element"><l></span><br /> <span class="element"><said <span class="attribute">xml:id</span>="<span class="attributevalue">eg1-said3</span>"<br /> <span class="attribute">prev</span>="<span class="attributevalue">#eg1-said2</span>"></span>Wee'll win your battles, or dye in the field<span class="element"></said></span>.<br /> <span class="element"></l></span><br /><span class="element"></lg></span><div style="float: right;"><a href="BIB.html#VESA-eg-1">bibliography</a> </div></div></div><div class="p">Alternatively, the elements may be reconstructed with stand-off markup using the element <a class="gi" title="identifies a possibly fragmented segment of text, by pointing at the possibly discontiguous elements which compose it." href="ref-join.html">join</a>: <div id="index-egXML-d52e60667" class="pre egXML_valid"><span class="element"><lg <span class="attribute">type</span>="<span class="attributevalue">couplet</span>"></span><br /> <span class="element"><l></span><br /> <span class="element"><seg <span class="attribute">xml:id</span>="<span class="attributevalue">eg2-said1</span>"></span>Our lives<span class="element"></seg></span>, ſaid he,<br /> <span class="element"><seg <span class="attribute">xml:id</span>="<span class="attributevalue">eg2-said2</span>"></span>wee'll give before we yield<span class="element"></seg></span>,<br /> <span class="element"></l></span><br /> <span class="element"><l></span><br /> <span class="element"><seg <span class="attribute">xml:id</span>="<span class="attributevalue">eg2-said3</span>"></span>Wee'll win your battles, or dye in the field<span class="element"></seg></span>.<br /> <span class="element"></l></span><br /><span class="element"></lg></span><br /><span class="comment"><!-- Elsewhere in the document --></span><br /><span class="element"><p></span><br /> <span class="element"><join <span class="attribute">result</span>="<span class="attributevalue">said</span>" <span class="attribute">scope</span>="<span class="attributevalue">root</span>"<br /> <span class="attribute">target</span>="<span class="attributevalue">#eg2-said1 #eg2-said2 #eg2-said3</span>"/></span><br /><span class="element"></p></span><div style="float: right;"><a href="BIB.html#VESA-eg-1">bibliography</a> </div></div></div><p>A more general discussion of these and other strategies to deal with fragmentation and reconstruction appears in section <a class="link_ptr" href="NH.html#NHVE" title="Fragmentation and Reconstitution of Virtual Elements"><span class="headingNumber">20.3 </span>Fragmentation and Reconstitution of Virtual Elements</a>.</p></div><div class="div2" id="VEME"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="VE.html#VESA"><span class="headingNumber">6.3 </span>Encoding Textual Structures Across Verses</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="VE.html#VERH"><span class="headingNumber">6.5 </span>Rhyme</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#VEME" title="link to this section "><span class="invisible">TEI: Rhyme and Metrical Analysis</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">6.4 </span><span class="head">Rhyme and Metrical Analysis</span></h3><p>When the module for verse is in use, the following additional attributes are available to record information about rhyme and metrical form: </p><ul class="specList"><li><span class="specList-classSpec"><a href="ref-att.metrical.html">att.metrical</a></span> defines a set of attributes which certain elements may use to represent metrical information.<table class="specDesc"><tr><td class="Attribute"><span class="att">met</span></td><td>(metrical structure, conventional) contains a user-specified encoding for the conventional metrical structure of the element.</td></tr><tr><td class="Attribute"><span class="att">real</span></td><td>(metrical structure, realized) contains a user-specified encoding for the actual realization of the conventional metrical structure applicable to the element.</td></tr><tr><td class="Attribute"><span class="att">rhyme</span></td><td>(rhyme scheme) specifies the rhyme scheme applicable to a group of verse lines.</td></tr></table></li></ul><p>These attributes may be attached to the <a class="gi" title="(line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc." href="ref-lg.html">lg</a> element, or to the higher-level text-division elements <a class="gi" title="(text division) contains a subdivision of the front, body, or back of a text." href="ref-div.html">div</a>, <a class="gi" title="(level-1 text division) contains a first-level subdivision of the front, body, or back of a text." href="ref-div1.html">div1</a>, etc. In general, the attributes should be specified at the highest level possible; they may not however be specifiable at the highest level if some of the subdivisions of a text are in prose and others in verse. All these attributes may also be attached to the <a class="gi" title="(verse line) contains a single, possibly incomplete, line of verse." href="ref-l.html">l</a> and <a class="gi" title="(arbitrary segment) represents any segmentation of text below the ‘chunk’ level." href="ref-seg.html">seg</a> elements, but the default notation for the <span class="att">rhyme</span> attribute has no defined meaning when specified on <a class="gi" title="(verse line) contains a single, possibly incomplete, line of verse." href="ref-l.html">l</a> or <a class="gi" title="(arbitrary segment) represents any segmentation of text below the ‘chunk’ level." href="ref-seg.html">seg</a>. The value for these attributes may take any form desired by the encoder, but the nature of the notation used will determine how well the attribute values can be processed by automatic means.</p><p>The primary function of the metrical attributes is to encode the conventional metrical or rhyming structure within which the poet is working, rather than the actual prosodic realization of each line; the latter can be recorded using the <span class="att">real</span> attribute, as further discussed below. A simple mechanism is also provided for recording the actual realization of a rhyme pattern; see <a class="link_ptr" href="VE.html#VERH" title="Rhyme"><span class="headingNumber">6.5 </span>Rhyme</a>.</p><div class="div3" id="VEMEsamp"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="VE.html#VEMElevels"><span class="headingNumber">6.4.2 </span>Segment-Level versus Line-level Tagging</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#VEMEsamp" title="link to this section "><span class="invisible">TEI: Sample Metrical Analyses</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">6.4.1 </span><span class="head">Sample Metrical Analyses</span></h4><div class="p">As a simple example of the use of these attributes, consider the following lines from Pope's <q class="titlea">Essay on Criticism</q>: <div id="index-egXML-d52e60738" class="pre egXML_valid"><span class="element"><div <span class="attribute">type</span>="<span class="attributevalue">book</span>" <span class="attribute">n</span>="<span class="attributevalue">1</span>" <span class="attribute">met</span>="<span class="attributevalue">-+|-+|-+|-+|-+/</span>"<br /> <span class="attribute">rhyme</span>="<span class="attributevalue">aa</span>"></span><br /> <span class="element"><lg <span class="attribute">n</span>="<span class="attributevalue">1</span>" <span class="attribute">type</span>="<span class="attributevalue">paragraph</span>"></span><br /> <span class="element"><l></span>'Tis hard to say, if greater Want of Skill<span class="element"></l></span><br /> <span class="element"><l></span>Appear in <span class="element"><hi></span>Writing<span class="element"></hi></span> or in <span class="element"><hi></span>Judging<span class="element"></hi></span> ill;<span class="element"></l></span><br /> <span class="element"><l></span>But, of the two, less dang'rous is th'Offence,<span class="element"></l></span><br /> <span class="element"><l></span>To tire our <span class="element"><hi></span>Patience<span class="element"></hi></span>, than mis-lead our <span class="element"><hi></span>Sense<span class="element"></hi></span>:<span class="element"></l></span><br /> <span class="element"></lg></span><br /><span class="element"></div></span><div style="float: right;"><a href="BIB.html#VEMEsamp-eg-14">bibliography</a> </div></div> </div><p>This text is written entirely in <span class="term">heroic couplets</span>; each line is an iambic pentameter (which, using a common notation, can be described with the formula <span class="val">-+|-+|-+|-+|-+/</span>, each <span class="val">-</span> denoting a metrically unstressed syllable, each <span class="val">+</span> a metrically stressed one, each <span class="val">|</span> a foot boundary, and the <span class="val">/</span> a line-end), and the couplets rhyme (which can be represented with the conventional formula <span class="val">aa</span>).</p><p>Because both rhyme pattern and metrical form are consistent throughout the poem, they may be conveniently specified on the <a class="gi" title="(text division) contains a subdivision of the front, body, or back of a text." href="ref-div.html">div</a> element; the values given for the attributes will be inherited by any metrical unit contained within the <a class="gi" title="(text division) contains a subdivision of the front, body, or back of a text." href="ref-div.html">div</a> elements of this poem, and must be interpreted in the appropriate way.</p><p>Since the notation used in the <span class="att">met</span>, <span class="att">real</span>, and <span class="att">rhyme</span> attributes is user-defined, no binding description can be given of its details or of how its interpretation must proceed. (A default notation is provided for the <span class="att">rhyme</span> attribute, which however the encoder can replace with another; see section <a class="link_ptr" href="VE.html#VERH" title="Rhyme"><span class="headingNumber">6.5 </span>Rhyme</a>.) It is expected, however, that software should be able to support these attributes in useful ways; the more intelligent the software is, and the more knowledge of metrics is built into it, the better it will be able to support these attributes. In the extract given above, for example, the <span class="att">met</span> and <span class="att">rhyme</span> attribute values specified on the <a class="gi" title="(text division) contains a subdivision of the front, body, or back of a text." href="ref-div.html">div</a> element are inherited directly by the <a class="gi" title="(line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc." href="ref-lg.html">lg</a> elements nested within it. Since the <span class="att">met</span> value specifies the metrical form of a single verse line, the structure of the <a class="gi" title="(line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc." href="ref-lg.html">lg</a> as a whole is understood to involve as many repetitions of the pattern as there are lines in the verse paragraph. The same attribute value, when inherited in turn by the <a class="gi" title="(verse line) contains a single, possibly incomplete, line of verse." href="ref-l.html">l</a> element, must be understood <em>not</em> to repeat. With sufficiently sophisticated software, segments within the line might even be understood as inheriting precisely that portion of the formula which applies to the segment in question; this will, however, be easier to accomplish for some languages than for others.</p><p>The <span class="att">rhyme</span> attribute in this example uses the default notation to specify a rhyme scheme applicable only to pairs of lines. As elsewhere, the default notation for the <span class="att">rhyme</span> attribute has no meaning for metrical units at the line level or below. In verse forms where line-internal rhyme is structurally significant, e.g. in some skaldic poetry, the default notation is incapable of expressing the required information, since the rhyme pattern may need to be specified for units smaller than the line. In such cases, a user-specified rhyme notation must be substituted for the default notation, or else the rhyme pattern must be described using some alternative method (e.g. by using the <a class="gi" title="defines an association or hypertextual link among elements or passages, of some type not more precisely specifiable by other elements." href="ref-link.html">link</a> mechanism described below).</p><p>The precise semantics of the <span class="att">met</span> attribute and the inferences which software is expected or able to draw from it, are implementation-dependent; so are the semantics and processing of the <span class="att">rhyme</span> attribute, when user-specified notations are used.</p><p>A formal definition of the significance of each component of the pattern given as the value of the <span class="att">met</span> attribute may be provided in the <a class="gi" title="(metrical notation declaration) documents the notation employed to represent a metrical pattern when this is specified as the value of a @met, @real, or @rhyme attribute on any structural element of a metrical text (e.g. <lg>, <l>, or <seg>)." href="ref-metDecl.html">metDecl</a> element within the <a class="gi" title="(encoding description) documents the relationship between an electronic text and the source or sources from which it was derived." href="ref-encodingDesc.html">encodingDesc</a> element in the TEI header (see section <a class="link_ptr" href="VE.html#HDMN" title="Metrical Notation Declaration"><span class="headingNumber">6.6 </span>Metrical Notation Declaration</a>). The encoder is free to invent any notation appropriate to his or her analytic needs, provided that it is adequately documented in this element. The notation may define metrical components using invented or traditional names (such as <span class="q">‘iamb’</span> or <span class="q">‘hexameter’</span>) or in terms of basic units such as codes for stressed or unstressed syllables, or a combination of the two.</p><div class="p">The <span class="att">real</span> (for <span class="q">‘realization’</span>) attribute may optionally be specified to indicate any deviation from the pattern defined by the <span class="att">met</span> attribute which the encoder wishes to record. By default, the <span class="att">real</span> attribute has the same value as the <span class="att">met</span> attribute on the same element; it is only necessary to provide an explicit value when the realization differs in some way from the abstract metrical pattern. The tension between conventional metrical pattern and its realization may thus be recorded explicitly. For example, many readers of the above passage would stress the word <span class="q">‘But’</span> at the beginning of the third line rather than the word <span class="q">‘of’</span> following it, as the metrical pattern would normally require. This variation might be encoded as follows: <div id="index-egXML-d52e60901" class="pre egXML_valid"><span class="element"><l <span class="attribute">real</span>="<span class="attributevalue">+-|-+|-+|-+|-+</span>"></span>But, of the two, ...<span class="element"></l></span></div></div><p>Where the <span class="att">real</span> attribute is used to over-ride the default or conventional metrical pattern, it applies only to the element on which it is specified. The default pattern for any subsequent lines is unaffected.</p><div class="p">As it happens, this particular kind of variation is very common in the English iambic pentameter—it even has a name: <span class="term">trochaic substitution</span>—an encoder might therefore choose to regard this not as an instance of a variant realization, but as an instance of a variant metrical form: <div id="index-egXML-d52e60920" class="pre egXML_valid"><span class="element"><l <span class="attribute">met</span>="<span class="attributevalue">+-|-+|-+|-+|-+</span>"></span>But, of the two,<br /> ...<span class="element"></l></span></div> Alternatively, a different metrical notation might be defined, in which this kind of variation was permitted throughout the text.</div><div class="p">In choosing whether to over-ride a metrical specification in this way or by using the <span class="att">real</span> attribute, the encoder is required to determine whether the change is a systematic or conventional one (as in this example) or an occasional variation, perhaps for local effect. In the following example, from Goethe's <q class="titlea">Auf dem See</q>, the variation is a matter of local realization: <div id="index-egXML-d52e60937" class="pre egXML_valid"><span class="element"><lg <span class="attribute">type</span>="<span class="attributevalue">chevy-chase-stanza</span>"<br /> <span class="attribute">met</span>="<span class="attributevalue">-+-+-+-+/-+-+-+</span>" <span class="attribute">rhyme</span>="<span class="attributevalue">ababcdcd</span>"></span><br /> <span class="element"><l <span class="attribute">n</span>="<span class="attributevalue">1</span>"></span> Und frische Nahrung, neues Blut<span class="element"></l></span><br /> <span class="element"><l <span class="attribute">n</span>="<span class="attributevalue">2</span>" <span class="attribute">real</span>="<span class="attributevalue">+--+-+</span>"></span> Saug' ich aus freier Welt;<span class="element"></l></span><br /> <span class="element"><l <span class="attribute">n</span>="<span class="attributevalue">3</span>" <span class="attribute">real</span>="<span class="attributevalue">+--+-+-+</span>"></span> Wie ist Natur so hold und gut,<span class="element"></l></span><br /> <span class="element"><l <span class="attribute">n</span>="<span class="attributevalue">4</span>" <span class="attribute">real</span>="<span class="attributevalue">---+-+</span>"></span> Die mich am Busen hält!<span class="element"></l></span><br /> <span class="element"><l <span class="attribute">n</span>="<span class="attributevalue">5</span>"></span> Die Welle wieget unsern Kahn<span class="element"></l></span><br /> <span class="element"><l <span class="attribute">n</span>="<span class="attributevalue">6</span>"></span> Im Rudertakt hinauf,<span class="element"></l></span><br /> <span class="element"><l <span class="attribute">n</span>="<span class="attributevalue">7</span>"></span> Und Berge, wolkig himmelan,<span class="element"></l></span><br /> <span class="element"><l <span class="attribute">n</span>="<span class="attributevalue">8</span>"></span> Begegnen unserm Lauf.<span class="element"></l></span><br /><span class="element"></lg></span><div style="float: right;"><a href="BIB.html#VE-eg-03">bibliography</a> </div></div> On the other hand, the famous inserted alexandrine in Pope's <span class="q">‘Essay on Criticism’</span>, might be encoded as follows: <div id="index-egXML-d52e60960" class="pre egXML_valid"><span class="element"><l <span class="attribute">n</span>="<span class="attributevalue">356</span>"></span> A<br /> needless alexandrine ends the song, <span class="element"></l></span><br /><span class="element"><l <span class="attribute">n</span>="<span class="attributevalue">357</span>" <span class="attribute">met</span>="<span class="attributevalue">-+|-+|-+|-+|-+|-+</span>"<br /> <span class="attribute">real</span>="<span class="attributevalue">++|-+|-+|+-|++|-+</span>"></span> That, like a wounded<br /> snake, drags its slow length along. <span class="element"></l></span><div style="float: right;"><a href="BIB.html#VEMEsamp-eg-14">bibliography</a> </div></div> Here the <span class="att">met</span> attribute indicates that a different metrical convention (the alexandrine) is in force, while the <span class="att">real</span> attribute indicates that there is a variation from that convention. As with many other aspects of metrical analysis, however, this is of necessity an entirely interpretive judgment.</div></div><div class="div3" id="VEMElevels"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="VE.html#VEMEsamp"><span class="headingNumber">6.4.1 </span>Sample Metrical Analyses</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="VE.html#VEMEana"><span class="headingNumber">6.4.3 </span>Metrical Analysis of Stanzaic Verse</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#VEMElevels" title="link to this section "><span class="invisible">TEI: Segment-Level versus Line-level Tagging</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">6.4.2 </span><span class="head">Segment-Level versus Line-level Tagging</span></h4><div class="p">The examples given so far have encoded information about the realization of metrical conventions at the level of the whole verse-line. This has obvious advantages of simplicity, but the disadvantage that any deviation from metrical convention is not marked at its precise point of occurrence in the text. Greater precision may be achieved, but only at the cost of marking deviant metrical units explicitly. This may be done with the <a class="gi" title="(arbitrary segment) represents any segmentation of text below the ‘chunk’ level." href="ref-seg.html">seg</a> element, giving the variant realization as the value of the <span class="att">real</span> attribute on that element. Using this method, the example given immediately above might be encoded as follows: <div id="index-egXML-d52e60987" class="pre egXML_valid"><span class="element"><l <span class="attribute">n</span>="<span class="attributevalue">356</span>"></span> A need<span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">foot</span>" <span class="attribute">n</span>="<span class="attributevalue">2</span>" <span class="attribute">real</span>="<span class="attributevalue">--</span>"></span>less a<span class="element"></seg></span>lexandrine ends the song,<span class="element"></l></span><br /><span class="element"><l <span class="attribute">n</span>="<span class="attributevalue">357</span>" <span class="attribute">met</span>="<span class="attributevalue">-+|-+|-+|-+|-+|-+</span>"></span><br /> <span class="element"><seg <span class="attribute">n</span>="<span class="attributevalue">1</span>" <span class="attribute">real</span>="<span class="attributevalue">++</span>"></span> That, like <span class="element"></seg></span> a wounded snake, <span class="element"><seg <span class="attribute">n</span>="<span class="attributevalue">4</span>" <span class="attribute">real</span>="<span class="attributevalue">+-</span>"></span> drags its <span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">n</span>="<span class="attributevalue">5</span>" <span class="attribute">real</span>="<span class="attributevalue">++</span>"></span> slow length <span class="element"></seg></span> along. <span class="element"></l></span><div style="float: right;"><a href="BIB.html#VEMEsamp-eg-14">bibliography</a> </div></div> The marking of the foot boundaries with the symbol <span class="val">|</span> in the <span class="att">met</span> attribute value of the <a class="gi" title="(verse line) contains a single, possibly incomplete, line of verse." href="ref-l.html">l</a> element allows the human reader, or a sufficiently intelligent software program, to isolate the correct portion of that attribute value as the default value for the same attribute on the <a class="gi" title="(arbitrary segment) represents any segmentation of text below the ‘chunk’ level." href="ref-seg.html">seg</a> elements for feet, namely <span class="val">-+</span>. It is of course up to the encoder to decide whether or not to include the <span class="att">n</span> attribute of <a class="gi" title="(arbitrary segment) represents any segmentation of text below the ‘chunk’ level." href="ref-seg.html">seg</a> here, and whether or not also to tag the feet in the line in which there is no deviation from the metrical convention. The ability of software to infer which foot is being marked, if not all are tagged, will depend heavily on the language of the text and the knowledge of prosody built into the software; the fuller and more explicit the markup, the easier it will be for software to handle it. It may prove useful, however, to mark metrical deviations in the manner shown, even if the available software is not sufficiently intelligent to scan lines without aid from the markup. Human readers who are interested in prosody may well be able to exploit the markup in useful ways even with less sophisticated software.</div><div class="p">There are circumstances where it may also be useful to use the <span class="att">met</span> attribute of <a class="gi" title="(arbitrary segment) represents any segmentation of text below the ‘chunk’ level." href="ref-seg.html">seg</a>. If we wish to identify the exact location of the different types of foot in the first line of Virgil's <span class="titlem">Aeneid</span>, the text could be encoded as follows (for simplicity's sake the caesura has been omitted): <div id="index-egXML-d52e61036" class="pre egXML_valid"><span class="element"><l></span><br /> <span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">foot</span>" <span class="attribute">met</span>="<span class="attributevalue">+--</span>"></span>Arma vi<span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">met</span>="<span class="attributevalue">+--</span>"></span>rumque ca<span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">met</span>="<span class="attributevalue">++</span>"></span>no Tro<span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">met</span>="<span class="attributevalue">++</span>"></span>iae qui <span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">met</span>="<span class="attributevalue">+--</span>"></span>primus ab<span class="element"></seg></span><br /> <span class="element"><seg <span class="attribute">met</span>="<span class="attributevalue">++</span>"></span> oris<span class="element"></seg></span><br /><span class="element"></l></span><div style="float: right;"><a href="BIB.html#VE-eg-02">bibliography</a> </div></div> An appropriate value of the <span class="att">met</span> attribute might also be supplied on the enclosing <a class="gi" title="(text division) contains a subdivision of the front, body, or back of a text." href="ref-div.html">div</a> element, to indicate that each foot may be made up of a dactyl or a spondee, so that the values given here for <span class="att">met</span> at the level of the foot may be considered a series of local variations on this fundamental pattern; in cases like this, of course, the local variations may also be considered aspects of realization rather than of convention, in which case the <span class="att">real</span> attribute may be used instead of <span class="att">met</span>, if desired.</div></div><div class="div3" id="VEMEana"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="VE.html#VEMElevels"><span class="headingNumber">6.4.2 </span>Segment-Level versus Line-level Tagging</a></li><li class="subtoc"></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#VEMEana" title="link to this section "><span class="invisible">TEI: Metrical Analysis of Stanzaic Verse</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">6.4.3 </span><span class="head">Metrical Analysis of Stanzaic Verse</span></h4><div class="p">The method described above may be used to encode quite complex verse forms, for instance various kinds of fixed-form stanzas. Let us take one of Dante's canzoni, in which each stanza except the last has the same combination of eleven-syllable and seven-syllable lines, and the same rhyme scheme: <div id="index-egXML-d52e61072" class="pre egXML_valid"><span class="element"><div <span class="attribute">type</span>="<span class="attributevalue">canzone</span>"<br /> <span class="attribute">met</span>="<span class="attributevalue">E/E/S/E/S/E/E/S/E/S/E/S/S/E/S/E/E/S/S/E/E</span>" <span class="attribute">rhyme</span>="<span class="attributevalue">abbcdaccbdceeffghhhgg</span>"></span><br /> <span class="element"><lg <span class="attribute">n</span>="<span class="attributevalue">1</span>" <span class="attribute">type</span>="<span class="attributevalue">stanza</span>"></span><br /> <span class="element"><l <span class="attribute">n</span>="<span class="attributevalue">1</span>"></span>Doglia mi reca nello core ardire<span class="element"></l></span><br /> <span class="element"></lg></span><br /><span class="element"></div></span><div style="float: right;"><a href="BIB.html#VEMEana-eg-23">bibliography</a> </div></div> </div><p>Here the <span class="att">met</span> attribute specifies a metrical pattern for each of the twenty-one lines making up a stanza of the <span class="term">canzone</span>. Each stanza inherits this definition from the parent <a class="gi" title="(text division) contains a subdivision of the front, body, or back of a text." href="ref-div.html">div</a> element. The <span class="att">rhyme</span> attribute specifies a rhyme scheme for each stanza, in the same way.</p><div class="p">In the metrical notation used here, the letter <span class="val">E</span> represents a line containing nine syllables which may or may not be metrically prominent, a tenth which is prominent and an optional non-prominent eleventh syllable. The letter <span class="q">‘S’</span> is used to represent a line containing five syllables which may or may not be metrically prominent, a sixth which is prominent and an optional non-prominent seventh syllable. A suitable definition for this notation might be given by a <a class="gi" title="(metrical notation declaration) documents the notation employed to represent a metrical pattern when this is specified as the value of a @met, @real, or @rhyme attribute on any structural element of a metrical text (e.g. <lg>, <l>, or <seg>)." href="ref-metDecl.html">metDecl</a> element like the following: <div id="index-egXML-d52e61104" class="pre egXML_valid"><span class="element"><metDecl <span class="attribute">type</span>="<span class="attributevalue">met</span>" <span class="attribute">pattern</span>="<span class="attributevalue">((E|S)/)+)</span>"></span><br /> <span class="element"><metSym <span class="attribute">value</span>="<span class="attributevalue">E</span>" <span class="attribute">terminal</span>="<span class="attributevalue">false</span>"></span>xxxxxxxxx+o<span class="element"></metSym></span><br /> <span class="element"><metSym <span class="attribute">value</span>="<span class="attributevalue">S</span>" <span class="attribute">terminal</span>="<span class="attributevalue">false</span>"></span>xxxxx+o<span class="element"></metSym></span><br /> <span class="element"><metSym <span class="attribute">value</span>="<span class="attributevalue">x</span>"></span>metrically prominent or non-prominent<span class="element"></metSym></span><br /> <span class="element"><metSym <span class="attribute">value</span>="<span class="attributevalue">+</span>"></span>metrically prominent<span class="element"></metSym></span><br /> <span class="element"><metSym <span class="attribute">value</span>="<span class="attributevalue">o</span>"></span>optional non prominent<span class="element"></metSym></span><br /> <span class="element"><metSym <span class="attribute">value</span>="<span class="attributevalue">/</span>"></span>line division<span class="element"></metSym></span><br /><span class="element"></metDecl></span></div></div><div class="p">As noted above, the metrical pattern specified on the <a class="gi" title="(text division) contains a subdivision of the front, body, or back of a text." href="ref-div.html">div</a> applies to each <a class="gi" title="(line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc." href="ref-lg.html">lg</a> (stanza) element contained within the <a class="gi" title="(text division) contains a subdivision of the front, body, or back of a text." href="ref-div.html">div</a>. In fact however, after seven stanzas of this type, there is a final stanza, known as a <span class="term">commiato</span> or envoi, which follows a different metrical and rhyming scheme. The solution to this problem is simply to specify a new <span class="att">met</span> attribute on the eighth stanza itself, which will override the default value inherited from parent <a class="gi" title="(text division) contains a subdivision of the front, body, or back of a text." href="ref-div.html">div</a>, as follows: <div id="index-egXML-d52e61140" class="pre egXML_valid"><span class="element"><div <span class="attribute">met</span>="<span class="attributevalue">[...]</span>"></span><br /> <span class="element"><lg></span><br /> <span class="element"><l></span> ... <span class="element"></l></span><br /> <span class="element"></lg></span><br /> <span class="element"><lg <span class="attribute">type</span>="<span class="attributevalue">commiato</span>"<br /> <span class="attribute">met</span>="<span class="attributevalue">E/S/S/E/S/E/E/S/S/E/E</span>" <span class="attribute">rhyme</span>="<span class="attributevalue">abbccdeeedd</span>"></span><br /> <span class="element"><l <span class="attribute">n</span>="<span class="attributevalue">1</span>"></span>Canzone, presso di qui è une donna<span class="element"></l></span><br /> <span class="element"></lg></span><br /><span class="element"></div></span><div style="float: right;"><a href="BIB.html#VEMEana-eg-23">bibliography</a> </div></div></div><p>Note that, in the same way as for the <span class="att">real</span> attribute, over-riding of this kind does not affect subsequent elements at the same hierarchic level. Any <a class="gi" title="(line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc." href="ref-lg.html">lg</a> element following the <span class="term">commiato</span> above would be assumed to use the same metrical and rhyming scheme as the one preceding the <span class="term">commiato</span>. Moreover, although it is quite regular (in the sense that the last stanza of each <span class="term">canzone</span> is a <span class="term">commiato</span>), the over-riding must be specified for each case.</p></div></div><div class="div2" id="VERH"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="VE.html#VEME"><span class="headingNumber">6.4 </span>Rhyme and Metrical Analysis</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="VE.html#HDMN"><span class="headingNumber">6.6 </span>Metrical Notation Declaration</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#VERH" title="link to this section "><span class="invisible">TEI: Rhyme</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">6.5 </span><span class="head">Rhyme</span></h3><p>The <span class="att">rhyme</span> attribute is used to specify the rhyme pattern of a verse form. It should not be confused with the <a class="gi" title="marks the rhyming part of a metrical line." href="ref-rhyme.html">rhyme</a> element, which is used to mark the actual rhyming word or words: </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-rhyme.html">rhyme</a></span> marks the rhyming part of a metrical line.</li></ul><p>Like the <span class="att">met</span> attribute, the <span class="att">rhyme</span> attribute can be used with a user-specified notation documented by the <a class="gi" title="(metrical notation declaration) documents the notation employed to represent a metrical pattern when this is specified as the value of a @met, @real, or @rhyme attribute on any structural element of a metrical text (e.g. <lg>, <l>, or <seg>)." href="ref-metDecl.html">metDecl</a> element in the TEI header. Unlike <span class="att">met</span>, however, the <span class="att">rhyme</span> attribute has a default notation; if this default notation is used, no <a class="gi" title="(metrical notation declaration) documents the notation employed to represent a metrical pattern when this is specified as the value of a @met, @real, or @rhyme attribute on any structural element of a metrical text (e.g. <lg>, <l>, or <seg>)." href="ref-metDecl.html">metDecl</a> element need be given.</p><p>The default notation for rhyme offers the ability to record patterns of rhyming lines, using the traditional notation in which distinct letters stand for rhyming lines. For a work in rhyming couplets, like the Pope example above, the <span class="att">rhyme</span> attribute simply specifies <span class="val">aa</span>, indicating that pairs of adjacent lines rhyme with each other. For a slightly more complex scheme, applicable to groups of four lines, in which lines 1 and 3 rhyme, as do lines 2 and 4, this attribute would have the value <span class="val">abab</span>. The traditional Spenserian stanza has the pattern <span class="val">ababbcbcc</span>, indicating that within each nine line stanza, lines 1 and 3 rhyme with each other, as do lines 2, 4, 5 and 7, and lines 6, 8 and 9.</p><div class="p">Non-rhyming lines within such a group may be represented using a hyphen or an x, as in the following example: <div id="index-egXML-d52e61219" class="pre egXML_valid"><span class="element"><lg <span class="attribute">rhyme</span>="<span class="attributevalue">aa-a</span>"></span><br /> <span class="element"><l></span>Why, all the Saints and Sages who discuss'd<span class="element"></l></span><br /> <span class="element"><l></span>Of the Two Worlds so learnedly, are thrust<span class="element"></l></span><br /> <span class="element"><l></span>Like foolish Prophets forth; their Words to Scorn<span class="element"></l></span><br /> <span class="element"><l></span>Are scatter'd, and their Mouths are stopt with Dust. <span class="element"></l></span><br /><span class="element"></lg></span><div style="float: right;"><a href="BIB.html#fitrub">bibliography</a> </div></div></div><div class="p">The <a class="gi" title="marks the rhyming part of a metrical line." href="ref-rhyme.html">rhyme</a> element may be used to mark the words (or parts of words) which rhyme according to a predefined pattern: <div id="index-egXML-d52e61234" class="pre egXML_valid"><span class="element"><lg <span class="attribute">type</span>="<span class="attributevalue">couplet</span>" <span class="attribute">rhyme</span>="<span class="attributevalue">aa</span>"></span><br /> <span class="element"><l></span>Outside in the distance a wildcat did <span class="element"><rhyme></span>growl<span class="element"></rhyme></span><span class="element"></l></span><br /> <span class="element"><l></span>Two riders were approaching and the wind began to <span class="element"><rhyme></span>howl<span class="element"></rhyme></span><span class="element"></l></span><br /><span class="element"></lg></span><div style="float: right;"><a href="BIB.html#VERH-eg-25">bibliography</a> </div></div></div><div class="p">The <span class="att">label</span> attribute is used to specify which parts of a rhyme scheme a given set of rhyming words represent: <div id="index-egXML-d52e61251" class="pre egXML_valid"><span class="element"><lg <span class="attribute">type</span>="<span class="attributevalue">quatrain</span>" <span class="attribute">rhyme</span>="<span class="attributevalue">abab</span>"></span><br /> <span class="element"><l></span>I wander thro' each charter'd <span class="element"><rhyme <span class="attribute">label</span>="<span class="attributevalue">a</span>"></span>street<span class="element"></rhyme></span>,<span class="element"></l></span><br /> <span class="element"><l></span>Near where the charter'd Thames does <span class="element"><rhyme <span class="attribute">label</span>="<span class="attributevalue">b</span>"></span>flow<span class="element"></rhyme></span>,<span class="element"></l></span><br /> <span class="element"><l></span>And mark in every face I <span class="element"><rhyme <span class="attribute">label</span>="<span class="attributevalue">a</span>"></span>meet<span class="element"></rhyme></span><span class="element"></l></span><br /> <span class="element"><l></span>Marks of weakness, marks of <span class="element"><rhyme <span class="attribute">label</span>="<span class="attributevalue">b</span>"></span>woe<span class="element"></rhyme></span>.<span class="element"></l></span><br /><span class="element"></lg></span><br /><span class="element"><lg <span class="attribute">rhyme</span>="<span class="attributevalue">abab</span>"></span><br /> <span class="element"><l></span>In every cry of every <span class="element"><rhyme <span class="attribute">label</span>="<span class="attributevalue">a</span>"></span>Man<span class="element"></rhyme></span><span class="element"></l></span><br /> <span class="element"><l></span>In every Infant's cry of <span class="element"><rhyme <span class="attribute">label</span>="<span class="attributevalue">b</span>"></span>fear<span class="element"></rhyme></span>,<span class="element"></l></span><br /> <span class="element"><l></span>In every voice, in every <span class="element"><rhyme <span class="attribute">label</span>="<span class="attributevalue">a</span>"></span>ban<span class="element"></rhyme></span>,<span class="element"></l></span><br /> <span class="element"><l></span>The mind-forg'd manacles I <span class="element"><rhyme <span class="attribute">label</span>="<span class="attributevalue">b</span>"></span>hear<span class="element"></rhyme></span>.<span class="element"></l></span><br /><span class="element"></lg></span><div style="float: right;"><a href="BIB.html#VE-eg-04">bibliography</a> </div></div></div><p>Within a given scope, all <a class="gi" title="marks the rhyming part of a metrical line." href="ref-rhyme.html">rhyme</a> elements with the same value for their <span class="att">label</span> attribute are assumed to rhyme with each other: thus, in the above example, the two rhymes labelled <code>a</code> in the first stanza rhyme with each other, but not necessarily with those labelled <code>a</code> in the second stanza. The scope is defined by the nearest ancestor element for which the <span class="att">rhyme</span> attribute has been supplied.</p><div class="p">The <a class="gi" title="marks the rhyming part of a metrical line." href="ref-rhyme.html">rhyme</a> element can appear anywhere within a verse line, and not necessarily around a single word. It can thus be used to mark quite complex internal rhyming schemes, as in the following example: <div id="index-egXML-d52e61314" class="pre egXML_valid"><span class="element"><lg <span class="attribute">rhyme</span>="<span class="attributevalue">ABCCBBA</span>"></span><br /> <span class="element"><l></span>The sunlight on the <span class="element"><rhyme <span class="attribute">label</span>="<span class="attributevalue">A</span>"></span>garden<span class="element"></rhyme></span><span class="element"></l></span><br /> <span class="element"><l></span><br /> <span class="element"><rhyme <span class="attribute">label</span>="<span class="attributevalue">A</span>"></span>Harden<span class="element"></rhyme></span>s and grows <span class="element"><rhyme <span class="attribute">label</span>="<span class="attributevalue">B</span>"></span>cold<span class="element"></rhyme></span>,<span class="element"></l></span><br /> <span class="element"><l></span>We cannot cage the <span class="element"><rhyme <span class="attribute">label</span>="<span class="attributevalue">C</span>"></span>minute<span class="element"></rhyme></span><span class="element"></l></span><br /> <span class="element"><l></span>Wi<span class="element"><rhyme <span class="attribute">label</span>="<span class="attributevalue">C</span>"></span>thin it<span class="element"></rhyme></span>s nets of <span class="element"><rhyme <span class="attribute">label</span>="<span class="attributevalue">B</span>"></span>gold<span class="element"></rhyme></span><span class="element"></l></span><br /> <span class="element"><l></span>When all is <span class="element"><rhyme <span class="attribute">label</span>="<span class="attributevalue">B</span>"></span>told<span class="element"></rhyme></span><span class="element"></l></span><br /> <span class="element"><l></span>We cannot beg for <span class="element"><rhyme <span class="attribute">label</span>="<span class="attributevalue">A</span>"></span>pardon<span class="element"></rhyme></span>.<span class="element"></l></span><br /><span class="element"></lg></span><div style="float: right;"><a href="BIB.html#VERH-eg-27">bibliography</a> </div></div> </div><p>This mechanism, although reasonably simple for simple cases, may not be appropriate for more complex applications. In general, rhyme may be considered as a special form of ‘correspondence’, and hence encoded using the mechanisms defined for that purpose in section <a class="link_ptr" href="SA.html#SACS" title="Correspondence and Alignment"><span class="headingNumber">16.5 </span>Correspondence and Alignment</a>. Similar considerations apply to other metrical features such as alliteration or assonance.</p><div class="p">To use the correspondence mechanisms to represent the complex rhyming pattern of the above example, each <a class="gi" title="marks the rhyming part of a metrical line." href="ref-rhyme.html">rhyme</a> element must be given a unique identifier, as follows: <div id="index-egXML-d52e61362" class="pre egXML_valid"><span class="element"><lg <span class="attribute">rhyme</span>="<span class="attributevalue">AB-BBA</span>"></span><br /> <span class="element"><l></span>The sunlight on the <span class="element"><rhyme <span class="attribute">xml:id</span>="<span class="attributevalue">V-A1</span>"></span>garden<span class="element"></rhyme></span><span class="element"></l></span><br /> <span class="element"><l></span><br /> <span class="element"><rhyme <span class="attribute">xml:id</span>="<span class="attributevalue">V-A2</span>"></span>Harden<span class="element"></rhyme></span>s and grows <span class="element"><rhyme <span class="attribute">xml:id</span>="<span class="attributevalue">V-B1</span>"></span>cold,<span class="element"></rhyme></span><span class="element"></l></span><br /> <span class="element"><l></span>We cannot cage the <span class="element"><rhyme <span class="attribute">xml:id</span>="<span class="attributevalue">V-C1</span>"></span>minute<span class="element"></rhyme></span><span class="element"></l></span><br /> <span class="element"><l></span>Wi<span class="element"><rhyme <span class="attribute">xml:id</span>="<span class="attributevalue">V-C2</span>"></span>thin it<span class="element"></rhyme></span>s nets of <span class="element"><rhyme <span class="attribute">xml:id</span>="<span class="attributevalue">V-B2</span>"></span>gold<span class="element"></rhyme></span><span class="element"></l></span><br /> <span class="element"><l></span>When all is <span class="element"><rhyme <span class="attribute">xml:id</span>="<span class="attributevalue">V-B3</span>"></span>told<span class="element"></rhyme></span><span class="element"></l></span><br /> <span class="element"><l></span>We cannot beg for <span class="element"><rhyme <span class="attribute">xml:id</span>="<span class="attributevalue">V-A3</span>"></span>pardon<span class="element"></rhyme></span>.<span class="element"></l></span><br /><span class="element"></lg></span><div style="float: right;"><a href="BIB.html#VERH-eg-27">bibliography</a> </div></div> Now that each rhyming word, or part-word, has been tagged and allocated an arbitrary identifier, the general purpose <a class="gi" title="defines an association or hypertextual link among elements or passages, of some type not more precisely specifiable by other elements." href="ref-link.html">link</a> element may be used to indicate which of the <a class="gi" title="marks the rhyming part of a metrical line." href="ref-rhyme.html">rhyme</a> elements share the same rhyme, as follows: <div id="index-egXML-d52e61401" class="pre egXML_valid"><span class="element"><linkGrp <span class="attribute">type</span>="<span class="attributevalue">rhyme</span>"></span><br /> <span class="element"><link <span class="attribute">target</span>="<span class="attributevalue">#V-A1 #V-A2 #V-A3</span>"/></span><br /> <span class="element"><link <span class="attribute">target</span>="<span class="attributevalue">#V-B1 #V-B2 #V-B3</span>"/></span><br /> <span class="element"><link <span class="attribute">target</span>="<span class="attributevalue">#V-C1 #V-C2</span>"/></span><br /><span class="element"></linkGrp></span></div></div><p>For further discussion of the <a class="gi" title="defines an association or hypertextual link among elements or passages, of some type not more precisely specifiable by other elements." href="ref-link.html">link</a> and <a class="gi" title="(link group) defines a collection of associations or hypertextual links." href="ref-linkGrp.html">linkGrp</a> element, see section <a class="link_ptr" href="SA.html#SACS" title="Correspondence and Alignment"><span class="headingNumber">16.5 </span>Correspondence and Alignment</a>.</p><p>The <a class="gi" title="marks the rhyming part of a metrical line." href="ref-rhyme.html">rhyme</a> and <a class="gi" title="marks the point at which a metrical line may be divided." href="ref-caesura.html">caesura</a> phrase level elements are made available by the <a class="link_odd" title="groups phrase-level elements which may appear within verse only." href="ref-model.lPart.html">model.lPart</a> class when the module defined by this chapter is included in a schema.</p></div><div class="teidiv1" id="HDMN"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="VE.html#VERH"><span class="headingNumber">6.5 </span>Rhyme</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="VE.html#VEETC"><span class="headingNumber">6.7 </span>Encoding Procedures for Other Verse Features</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#HDMN" title="link to this section "><span class="invisible">TEI: Metrical Notation Declaration</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">6.6 </span><span class="head">Metrical Notation Declaration</span></h3><p>When the module defined in this chapter is included in a schema, a specialized element is optionally available in the <a class="gi" title="(encoding description) documents the relationship between an electronic text and the source or sources from which it was derived." href="ref-encodingDesc.html">encodingDesc</a> element of the TEI header to document the metrical notation used in marking up a text. </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-metDecl.html">metDecl</a></span> (metrical notation declaration) documents the notation employed to represent a metrical pattern when this is specified as the value of a <span class="att">met</span>, <span class="att">real</span>, or <span class="att">rhyme</span> attribute on any structural element of a metrical text (e.g. <a class="gi" title="(line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc." href="ref-lg.html">lg</a>, <a class="gi" title="(verse line) contains a single, possibly incomplete, line of verse." href="ref-l.html">l</a>, or <a class="gi" title="(arbitrary segment) represents any segmentation of text below the ‘chunk’ level." href="ref-seg.html">seg</a>).<table class="specDesc"><tr><td class="Attribute"><span class="att">pattern</span></td><td>(regular expression pattern) specifies a regular expression defining any value that is legal for this notation.</td></tr></table></li><li><span class="specList-elementSpec"><a href="ref-metSym.html">metSym</a></span> (metrical notation symbol) documents the intended significance of a particular character or character sequence within a metrical notation, either explicitly or in terms of other <a class="gi" title="(metrical notation symbol) documents the intended significance of a particular character or character sequence within a metrical notation, either explicitly or in terms of other <metSym> elements in the same <metDecl>." href="ref-metSym.html">metSym</a> elements in the same <a class="gi" title="(metrical notation declaration) documents the notation employed to represent a metrical pattern when this is specified as the value of a @met, @real, or @rhyme attribute on any structural element of a metrical text (e.g. <lg>, <l>, or <seg>)." href="ref-metDecl.html">metDecl</a>.<table class="specDesc"><tr><td class="Attribute"><span class="att">value</span></td><td>specifies the character or character sequence being documented.</td></tr><tr><td class="Attribute"><span class="att">terminal</span></td><td>specifies whether the symbol is defined in terms of other symbols (<span class="att">terminal</span> is set to <span class="val">false</span>) or in prose (<span class="att">terminal</span> is set to <span class="val">true</span>).</td></tr></table></li></ul><p>As with other components of the header, metrical notation may be specified either formally or informally. In a formal specification, every symbol used in the metrical notation must be documented by a corresponding <a class="gi" title="(metrical notation symbol) documents the intended significance of a particular character or character sequence within a metrical notation, either explicitly or in terms of other <metSym> elements in the same <metDecl>." href="ref-metSym.html">metSym</a> element; in an informal one, only a brief prose description of the way in which the notation is used need be given. In either case, the optional <span class="att">pattern</span> attribute may be used to supply a regular expression which a processor can use to validate expressions in the intended notation. The following constraints apply: </p><ul class="bulleted"><li class="item">if <span class="att">pattern</span> is supplied, any notation used which does not conform to it should be regarded as invalid</li><li class="item">if any <a class="gi" title="(metrical notation symbol) documents the intended significance of a particular character or character sequence within a metrical notation, either explicitly or in terms of other <metSym> elements in the same <metDecl>." href="ref-metSym.html">metSym</a> is defined, then any notation using undefined symbols should be regarded as invalid</li><li class="item">if both pattern and symbol are defined, then every symbol appearing explicitly within pattern must be defined</li><li class="item">symbols which are not matched by <span class="att">pattern</span> may be defined within a <a class="gi" title="(metrical notation declaration) documents the notation employed to represent a metrical pattern when this is specified as the value of a @met, @real, or @rhyme attribute on any structural element of a metrical text (e.g. <lg>, <l>, or <seg>)." href="ref-metDecl.html">metDecl</a> element</li></ul><div class="p">As a simple example, consider the case of the notation in which metrical prominence, metrical feet, and line boundaries are all to be encoded. Legal specifications in this notation may be written for any sequence of metrically prominent or non-prominent features, optionally separated by foot or metrical line boundaries at arbitrary points. Assuming that the symbol <span class="mentioned">1</span> is used for metrical prominence, <span class="mentioned">0</span> for non-prominence, <span class="mentioned">|</span> for foot boundary and <span class="mentioned">/</span> for line boundary, then the following declaration achieves this object: <div id="index-egXML-d52e61483" class="pre egXML_valid"><span class="element"><metDecl <span class="attribute">pattern</span>="<span class="attributevalue">((1|0)+\|?/?)*</span>"></span><br /> <span class="element"><metSym <span class="attribute">value</span>="<span class="attributevalue">1</span>"></span>metrical prominence<span class="element"></metSym></span><br /> <span class="element"><metSym <span class="attribute">value</span>="<span class="attributevalue">0</span>"></span>metrical non-prominence<span class="element"></metSym></span><br /> <span class="element"><metSym <span class="attribute">value</span>="<span class="attributevalue">|</span>"></span>foot boundary<span class="element"></metSym></span><br /> <span class="element"><metSym <span class="attribute">value</span>="<span class="attributevalue">/</span>"></span>metrical line boundary<span class="element"></metSym></span><br /><span class="element"></metDecl></span></div></div><div class="p">The same notation might also be specified less formally, as follows: <div id="index-egXML-d52e61495" class="pre egXML_valid"><span class="element"><metDecl></span><br /> <span class="element"><p></span>Metrically prominent syllables are marked '1' and other syllables '0'. Foot<br /> divisions are marked by a vertical bar, and line divisions with a solidus.<span class="element"></p></span><br /> <span class="element"><p></span>This notation may be applied to any metrical unit, of any size (including, for<br /> example, individual feet as well as groups of lines).<span class="element"></p></span><br /><span class="element"></metDecl></span></div> Note that in this case, because the <span class="att">pattern</span> attribute has not been supplied, no processor can validate <span class="att">met</span> attribute values within the text which use this metrical notation.</div><div class="p">For more complex cases, it will often be more convenient to define a notation incrementally. The <span class="att">terminal</span> attribute should be used to indicate for a given symbol whether or not it may be re-defined in terms of other symbols used within the same notation. For example, here is a notation for encoding classical metres, in which symbols are provided for the most common types of foot. These symbols are themselves documented within the same notation, in terms of more primitive long and short syllables: <div id="index-egXML-d52e61515" class="pre egXML_valid"><span class="element"><metDecl <span class="attribute">pattern</span>="<span class="attributevalue">[DTIS3A]+</span>"></span><br /> <span class="element"><metSym <span class="attribute">n</span>="<span class="attributevalue">dactyl</span>" <span class="attribute">value</span>="<span class="attributevalue">D</span>"<br /> <span class="attribute">terminal</span>="<span class="attributevalue">false</span>"></span>-oo<span class="element"></metSym></span><br /> <span class="element"><metSym <span class="attribute">n</span>="<span class="attributevalue">trochee</span>" <span class="attribute">value</span>="<span class="attributevalue">T</span>"<br /> <span class="attribute">terminal</span>="<span class="attributevalue">false</span>"></span>-o<span class="element"></metSym></span><br /> <span class="element"><metSym <span class="attribute">n</span>="<span class="attributevalue">iamb</span>" <span class="attribute">value</span>="<span class="attributevalue">I</span>" <span class="attribute">terminal</span>="<span class="attributevalue">false</span>"></span>o-<span class="element"></metSym></span><br /> <span class="element"><metSym <span class="attribute">n</span>="<span class="attributevalue">spondee</span>" <span class="attribute">value</span>="<span class="attributevalue">S</span>"<br /> <span class="attribute">terminal</span>="<span class="attributevalue">false</span>"></span>--<span class="element"></metSym></span><br /> <span class="element"><metSym <span class="attribute">n</span>="<span class="attributevalue">tribrach</span>" <span class="attribute">value</span>="<span class="attributevalue">3</span>"<br /> <span class="attribute">terminal</span>="<span class="attributevalue">false</span>"></span>ooo<span class="element"></metSym></span><br /> <span class="element"><metSym <span class="attribute">n</span>="<span class="attributevalue">anapaest</span>" <span class="attribute">value</span>="<span class="attributevalue">A</span>"<br /> <span class="attribute">terminal</span>="<span class="attributevalue">false</span>"></span>oo-<span class="element"></metSym></span><br /> <span class="element"><metSym <span class="attribute">value</span>="<span class="attributevalue">o</span>"></span>short syllable<span class="element"></metSym></span><br /> <span class="element"><metSym <span class="attribute">value</span>="<span class="attributevalue">-</span>"></span>long syllable<span class="element"></metSym></span><br /><span class="element"></metDecl></span></div> Note here the use of the global <span class="att">n</span> attribute to supply an additional name for the symbols being documented.</div><p>Where an encoder wishes to use more than one different pattern for metrical notation, multiple <a class="gi" title="(metrical notation declaration) documents the notation employed to represent a metrical pattern when this is specified as the value of a @met, @real, or @rhyme attribute on any structural element of a metrical text (e.g. <lg>, <l>, or <seg>)." href="ref-metDecl.html">metDecl</a> elements may be included in the <a class="gi" title="(encoding description) documents the relationship between an electronic text and the source or sources from which it was derived." href="ref-encodingDesc.html">encodingDesc</a>, each supplied with an <span class="att">xml:id</span>. The <span class="att">decls</span> attribute may be used in the text of the document to specify which <a class="gi" title="(metrical notation declaration) documents the notation employed to represent a metrical pattern when this is specified as the value of a @met, @real, or @rhyme attribute on any structural element of a metrical text (e.g. <lg>, <l>, or <seg>)." href="ref-metDecl.html">metDecl</a> is in force at a particular point in the text. In this example, two <a class="gi" title="(metrical notation declaration) documents the notation employed to represent a metrical pattern when this is specified as the value of a @met, @real, or @rhyme attribute on any structural element of a metrical text (e.g. <lg>, <l>, or <seg>)." href="ref-metDecl.html">metDecl</a>s are defined in the header, one with an English verse pattern and one with a French pattern. In the body of the document, there are two <a class="gi" title="(text division) contains a subdivision of the front, body, or back of a text." href="ref-div.html">div</a> elements, one declaring the English pattern and one the French:</p><div id="index-egXML-d52e61561" class="pre egXML_valid"><span class="element"><encodingDesc></span><br /><span class="comment"><!-- ... --></span><br /> <span class="element"><metDecl <span class="attribute">xml:id</span>="<span class="attributevalue">md_en</span>" <span class="attribute">type</span>="<span class="attributevalue">met</span>"<br /> <span class="attribute">pattern</span>="<span class="attributevalue">((SU|US)USUSUSUS/)</span>"></span><br /> <span class="element"><metSym <span class="attribute">value</span>="<span class="attributevalue">S</span>"></span>stressed syllable<span class="element"></metSym></span><br /> <span class="element"><metSym <span class="attribute">value</span>="<span class="attributevalue">U</span>"></span>unstressed syllable<span class="element"></metSym></span><br /> <span class="element"><metSym <span class="attribute">value</span>="<span class="attributevalue">/</span>"></span>metrical line boundary<span class="element"></metSym></span><br /> <span class="element"></metDecl></span><br /> <span class="element"><metDecl <span class="attribute">xml:id</span>="<span class="attributevalue">md_fr</span>" <span class="attribute">type</span>="<span class="attributevalue">met</span>"<br /> <span class="attribute">pattern</span>="<span class="attributevalue">(AAAAAT\|AAAAT(A)?)</span>"></span><br /> <span class="element"><metSym <span class="attribute">value</span>="<span class="attributevalue">T</span>"></span>syllabe tonique<span class="element"></metSym></span><br /> <span class="element"><metSym <span class="attribute">value</span>="<span class="attributevalue">A</span>"></span>syllabe atone<span class="element"></metSym></span><br /> <span class="element"><metSym <span class="attribute">value</span>="<span class="attributevalue">|</span>"></span>pause métrique<span class="element"></metSym></span><br /> <span class="element"></metDecl></span><br /><span class="comment"><!-- ... --></span><br /><span class="element"></encodingDesc></span><br /><span class="comment"><!-- ... --></span><br /><span class="element"><body></span><br /> <span class="element"><div <span class="attribute">decls</span>="<span class="attributevalue">#md_en</span>"></span><br /> <span class="element"><lg></span><br /> <span class="element"><l></span><br /><span class="comment"><!-- ... --></span><br /> <span class="element"></l></span><br /><span class="comment"><!-- ... --></span><br /> <span class="element"></lg></span><br /> <span class="element"></div></span><br /> <span class="element"><div <span class="attribute">decls</span>="<span class="attributevalue">#md_fr</span>"></span><br /> <span class="element"><lg></span><br /> <span class="element"><l></span><br /><span class="comment"><!-- ... --></span><br /> <span class="element"></l></span><br /><span class="comment"><!-- ... --></span><br /> <span class="element"></lg></span><br /> <span class="element"></div></span><br /><span class="element"></body></span></div></div><div class="div2" id="VEETC"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="VE.html#HDMN"><span class="headingNumber">6.6 </span>Metrical Notation Declaration</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="VE.html#VESTR"><span class="headingNumber">6.8 </span>Module for Verse</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#VEETC" title="link to this section "><span class="invisible">TEI: Encoding Procedures for Other Verse Features</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">6.7 </span><span class="head">Encoding Procedures for Other Verse Features</span></h3><p>A number of procedures that may be of particular concern to encoders of verse texts are dealt with elsewhere in these guidelines. Some aspects of layout and physical appearance, especially important in the case of free verse, are dealt with in chapter <a class="link_ptr" href="PH.html" title="18"><span class="headingNumber">11 </span>Representation of Primary Sources</a>. Some initial recommendations for the encoding of phonetic or prosodic transcripts, which may be helpful in the analysis of sound structures in poetry, are to be found in chapter <a class="link_ptr" href="TS.html" title="11"><span class="headingNumber">8 </span>Transcriptions of Speech</a>; it may also be found convenient to use standard entity names (those proposed for the International Phonetic Alphabet suggest themselves) to mark positions of suprasegmentals such as primary and secondary stress, or other aspects of accentual structure.</p><p>As already indicated, chapter <a class="link_ptr" href="SA.html" title="14"><span class="headingNumber">16 </span>Linking, Segmentation, and Alignment</a> contains much which will be found useful for the aligning of multiple levels of commentary and structure within verse analysis. Encoders of verse (as of other types of literary text) will frequently wish to attach identifying labels to portions of text that are not part of a system of hierarchical divisions, may overlap with one another, and/or may be discontinuous; for instance passages associated with particular characters, themes, images, allusions, topoi, styles, or modes of narration. Much of the computerized analysis of verse seems likely to require dividing texts up into blocks in this way. The <a class="gi" title="associates an interpretative annotation directly with a span of text." href="ref-span.html">span</a> element discussed in <a class="link_ptr" href="AI.html#AISP" title="Spans and Interpretations"><span class="headingNumber">17.3 </span>Spans and Interpretations</a> provides the means for doing this. Finally, the procedures for the tagging of feature structures, described in chapter <a class="link_ptr" href="FS.html" title="16"><span class="headingNumber">18 </span>Feature Structures</a>, provide a powerful means of encoding a wide variety of aspects of verse literature, including not only the metrical structures discussed above, but also such stylistic and rhetorical features as metaphor.</p><p>For other features it must for the time being be left to encoders to devise their own terminology. Elements such as <span class="tag"><metaphor tenor="..." vehicle="..."></span> ... <span class="tag"></metaphor></span> might well suggest themselves; but given the problems of definition involved, and the great richness of modern metaphor theory, it is clear that any such format, if predefined by these Guidelines, would have seemed objectionable to some and excessively restrictive to many. Leaving the choice of tagging terminology to individual encoders carries with it one vital corollary, however: the encoder must be utterly explicit, in the TEI header, about the methods of tagging used and the criteria and definitions on which they rest. Where no formal elements are currently proposed, such information may readily be given as simple prose description within the <a class="gi" title="(encoding description) documents the relationship between an electronic text and the source or sources from which it was derived." href="ref-encodingDesc.html">encodingDesc</a> element defined in section <a class="link_ptr" href="HD.html#HD5" title="The Encoding Description"><span class="headingNumber">2.3 </span>The Encoding Description</a>.</p></div><div class="div2" id="VESTR"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="VE.html#VEETC"><span class="headingNumber">6.7 </span>Encoding Procedures for Other Verse Features</a></li><li class="subtoc"></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#VESTR" title="link to this section "><span class="invisible">TEI: Module for Verse</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">6.8 </span><span class="head">Module for Verse</span></h3><p>The module described in this chapter makes available the following components: </p><dl class="moduleSpec"><dt class="moduleSpecHead"><span lang="en">Module</span> verse: Verse structures</dt><dd><ul><li><span lang="en">Elements defined</span>: <a class="link_odd" title="marks the point at which a metrical line may be divided." href="ref-caesura.html">caesura</a> <a class="link_odd" title="(metrical notation declaration) documents the notation employed to represent a metrical pattern when this is specified as the value of a @met, @real, or @rhyme attribute on any structural element of a metrical text (e.g. <lg>, <l>, or <seg>)." href="ref-metDecl.html">metDecl</a> <a class="link_odd" title="(metrical notation symbol) documents the intended significance of a particular character or character sequence within a metrical notation, either explicitly or in terms of other <metSym> elements in the same <metDecl>." href="ref-metSym.html">metSym</a> <a class="link_odd" title="marks the rhyming part of a metrical line." href="ref-rhyme.html">rhyme</a></li><li><span lang="en">Classes defined</span>: <a class="link_odd" title="(enjambement) provides an attribute which may be used to indicate enjambement of the parent element." href="ref-att.enjamb.html">att.enjamb</a> <a class="link_odd" title="defines a set of attributes which certain elements may use to represent metrical information." href="ref-att.metrical.html">att.metrical</a></li></ul></dd></dl><p> The selection and combination of modules to form a TEI schema is described in <a class="link_ptr" href="ST.html#STIN" title="Defining a TEI Schema"><span class="headingNumber">1.2 </span>Defining a TEI Schema</a>.</p></div></div><nav class="left"><span class="upLink"> ↑ </span><a class="navigation" href="index.html">TEI P5 Guidelines</a><span class="previousLink"> « </span><a class="navigation" href="WD.html"><span class="headingNumber">5 </span>Characters, Glyphs, and Writing Modes</a><span class="nextLink"> » </span><a class="navigation" href="DR.html"><span class="headingNumber">7 </span>Performance Texts</a></nav><!--Notes in [div]--><div class="notes"><div class="noteHeading">Notes</div><div class="note" id="Note67"><span class="noteLabel">30 </span><div class="noteBody">For discussion of other attributes of this class, see <a class="link_ptr" href="DS.html#DSDIV3X" title="Partial and Composite Divisions"><span class="headingNumber">4.1.4 </span>Partial and Composite Divisions</a>.</div> <a class="link_return" title="Go back to text" href="#Note67_return">↵</a></div><div class="note" id="Note68"><span class="noteLabel">31 </span><div class="noteBody">As elsewhere in these Guidelines, this example has been formatted for clarity of exposition rather than correct display. Note in particular that whether an XML processor retains whitespace within the <a class="gi" title="(arbitrary segment) represents any segmentation of text below the ‘chunk’ level." href="ref-seg.html">seg</a> element or not (this can be configured by means of the <span class="att">xml:space</span> attribute) this example will still require additional processing, since whitespace should be retained for the lower level <a class="gi" title="(arbitrary segment) represents any segmentation of text below the ‘chunk’ level." href="ref-seg.html">seg</a> elements (those of type <span class="val">syll</span>) but not for the higher level one (those of type <span class="val">foot</span>).</div> <a class="link_return" title="Go back to text" href="#Note68_return">↵</a></div></div><div class="stdfooter autogenerated"><p>
[<a href="../../en/html/VE.html">English</a>]
[<a href="../../de/html/VE.html">Deutsch</a>]
[<a href="../../es/html/VE.html">Español</a>]
[<a href="../../it/html/VE.html">Italiano</a>]
[<a href="../../fr/html/VE.html">Français</a>]
[<a href="../../ja/html/VE.html">日本語</a>]
[<a href="../../ko/html/VE.html">한국어</a>]
[<a href="../../zh-TW/html/VE.html">中文</a>]
</p><hr /><div class="footer"><a class="plain" href="http://www.tei-c.org/About/">TEI Consortium</a> | <a class="plain" href="http://www.tei-c.org/About/contact.xml">Feedback</a></div><hr /><address><br />TEI Guidelines <a class="link_ref" href="AB.html#ABTEI4">Version</a> <a class="link_ref" href="../../readme-3.1.1.html">3.1.1a</a>. Last updated on <span class="date">10th May 2017</span>, revision <a class="link_ref" href="https://github.com/TEIC/TEI/commit/bd8dda3">bd8dda3</a>. This page generated on 2017-05-12T12:30:09Z.</address></div></div></body></html>