Dear list members.
I've to pose two questions. The first regards the <att>met</> and
<att>real</> attributes. We are tagging some poems by G. Pascoli,
recording some metrical information with these attributes. In some
cases we have to distinguish between emistichi, using the <seg> tag,
and we should provide metrical information about that segment.
We try to use the met and real attributes with the <seg> tag, but the
parser (sp 1.2.1, of course) refuses this, saying that "there is no
real attribute" for seg element. To note that even psgml doesn't list
those attributes as available for <seg> (nor <div>, <body> etc. tags).
Our DTD subsection is like this
<!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN" [
<!ENTITY % TEI.verse 'INCLUDE' >
<!ENTITY % TEI.linking 'INCLUDE' >
<!ENTITY % ISOpub PUBLIC "ISO 8879-1986//ENTITIES Publishing//EN">
<!ENTITY % ISOnum PUBLIC "ISO 8879-1986//ENTITIES Numeric and Special
<!ENTITY % ISOLat1 PUBLIC "ISO 8879-1986//ENTITIES Added Latin 1//EN"
<!ENTITY % ISOLat2 PUBLIC "ISO 8879-1986//ENTITIES Added Latin 2//EN"
Given a look at the dtd, I've seen that a.metrical parameter entity
isn't included in the declarations of the attributes of general
structure elements, nor in the one of <seg> element. However, P3 at
the chapter 9.4 says:
These attributes may be attached to the <lg> element, to any of its
numbered equivalents <lg1>, <lg2>, etc., to the higher-level
text-division elements <div>, <div1>, etc., or to the <body> element
itself if the whole of a text is in verse. 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 <l> and <seg> elements, but the
default notation for the rhyme attribute has no defined meaning when
specified on <l> or <seg>. The value for these attributes may take any
form desired by the encoder; the nature of the notation used will
determine how well the attribute values can be processed by automatic
To me this is an inconsistency between the Guidelines and the DTD. Am
The second question is about <fw>. Reading the Green Book, it seems like
it has the same role of milestone tags (included in m.globincl class).
Instead it is declared as an element of m.phrase class. This makes
difficult to use it to encode some aspects of the physical page of a
source. Is this an inconsistency of the Green book, as well, or am I
misunderstanding the Guidelines?
Thanks in advance for any advice and comment!
Centro Ricerche Informatica e Letteratura (CRILet)
Dipartimento di Studi Linguistici e Letterari
Facolta' di Lettere e Filosofia - Universita' di Roma "La Sapienza"
Piazza Aldo Moro, 5 - 00185 Roma Italia
Tel. +39 (6) 4991.3183
Fax. +39 (6) 4991.3575
E-mail: [log in to unmask]