`<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: |
`type` | indicates whether the notation conveys the abstract metrical form, its actual prosodic realization, or the rhyme scheme, or some combination thereof.
| Datatype: NAMES
| Values: One or more of the three attribute names `met` , `real` , or `rhyme` .
| 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 ).
| Default: #IMPLIED
| Example:
     <metDecl pattern= '( (1|0)+  \|? /? )* ' >
     <metDecl pattern= '((+-|-+)-+-+-+-+/)'
Note |

Example

       <metDecl id=ip pattern= '((+-|-+)-+-+-+-+/)'
            <symbol value='+'>stressed syllable
            <symbol value='-'>unstressed syllable
            <symbol value='/'>metrical line boundary
       </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.

Tagset base tag set for TEI headers
Class declarable
Filename `teihdr2`
Content: 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.
Parents encodingDesc
Children TEI...end ab bibl biblFull biblStruct camera caption castList cit eTree entry entryFree event graph kinesic l label lg lg1 list listBibl move note p pause q quote shift sound sp stage superentry symbol tech termEntry tree u view vocal witDetail witList writing
Declaration

    <!ELEMENT metDecl       - O  ((%component.seq) | (symbol+))     >
    <!ATTLIST metDecl            %a.global
                                 %a.declarable
              type               NAMES               "MET REAL"
              pattern            CDATA               #IMPLIED       >

See 5.3.8 ; 9.4

Back to index