<metDecl>

| ## Text Encoding Initiative
### The XML Version of the TEI Guidelines # <metDecl>

`<metDecl>` | 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>`).
Attributes | (In addition to global attributes and those inherited from declarable)
`type` | indicates whether the notation conveys the abstract metrical form, its actual prosodic realization, or the rhyme scheme, or some combination thereof.
| Datatype: CDATA
| Values: One or more of the three attribute names `met`, `real`, or `rhyme`, separated by whitespace.
| Default: met real
| Example:
Note | By default, the `<metDecl>` element documents the notation used for metrical pattern and realization. It may also be used to document the notation used for rhyme scheme information; if not otherwise documented, the rhyme scheme notation defaults to the traditional ‘abab’ notation.
`pattern` | specifies a regular expression defining any value that is legal for this notation.
| Datatype: CDATA
| Values: the value must be a valid expression for the `PATTERN` keyword as defined in the TEI extended pointer notation (see section 14.2.2.14 The PATTERN Keyword).
| Default: #IMPLIED
| Example:
    <metDecl pattern="( (1|0)+  \|? /? )* "/>
    <metDecl pattern="((+-|-+)-+-+-+-+/)"/>

Example

    <metDecl id="ip" pattern="((+-|-+)-+-+-+-+/)">
       <symbol value="+">stressed syllable</symbol>
       <symbol value="-">unstressed syllable</symbol>
       <symbol value="/">metrical line boundary</symbol>
    </metDecl>

This example is intended for the far more restricted case typified by the Shakespearean iambic pentameter. Only metrical patterns containing exactly ten syllables, alternately stressed and unstressed, (except for the first two which may be in either order) to each metrical line can be expressed using this notation.

Note

The encoder may choose whether to define the notation formally or informally. However, the two methods may not be mixed.

Only usable within the header if the verse base is enabled.

Module Declared in file teihdr2; Core tag sets: enabled when any TEI base is enabled
Class declarable
Data Description contains either a sequence of `<symbol>` elements or paragraphs. If one `<symbol>` is defined, then all the codes appearing within the `pattern` attribute should be documented, if the latter is specified.
May contain ab addSpan alt altGrp anchor bibl biblFull biblStruct camera caption castList cb certainty cit delSpan eTree entry entryFree event fLib fs fsLib fvLib gap graph index interp interpGrp join joinGrp kinesic l label lb lg lg1 lg2 lg3 lg4 lg5 link linkGrp list listBibl milestone move note p pause pb q quote respons shift sound sp span spanGrp stage superEntry symbol tech termEntry timeline tree u view vocal witDetail witList writing
May occur within encodingDesc
Declaration

    <!ELEMENT metDecl %om.RO;  ((%component.seq;) | (symbol+))>
    <!ATTLIST metDecl
          %a.global;
          %a.declarable;
          type CDATA "met real"
          pattern CDATA #IMPLIED>

See further 5.3.8 The Metrical Declaration Element; 9.4 Rhyme and Metrical Analysis

Up: 35 Elements