ISO Schematron rules
The @when attribute cannot be used with any other att.datable.w3c attributes.
The @from and @notBefore attributes cannot be used together.
The @to and @notAfter attributes cannot be used together.
@calendar indicates the system or calendar to which the date represented by the content of this element
belongs, but this element has no textual content.
The element should not be categorized in detail with @subtype unless also categorized in general with @type
@schemeVersion can only be used if @scheme is specified.
Abstract model violation: Paragraphs may not occur inside other paragraphs or ab elements.
Abstract model violation: Lines may not contain higher-level structural elements such as div, p, or ab.
Only one of the
attributes @target and @cRef may be supplied on .
Only one of the
attributes @target' and @cRef' may be supplied on
The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element
The @level attribute
should not be specified on a <title> within the
<titleStmt>.
When a child of
<seriesStmt>, the level of a title should be
specified as 's'.
When inside the
series-level portion of a structured bibliographic
citation, the level of a title should be specified
as 's'.
When a child of
<analytic>, the level of a title should be
specified as 'a'.
When a child of
<monogr>, the level of a title should not be
specified as 'a'.
Inside the title statment the
@type of a <title> should be specified
Inside a structured
bibliographic citation of a mongraphic-level item,
@type of a <title> should be specified
Inside the analytic portion
of a structured bibliographic citation, @type of a
<title> should be specified
Use of
specialized child elements of the publication
statement (rather than paragraphs) is recommended
whenever possible
Dates inside the
publication statement should have @when
(and should not have content)
Dates
inside the publication statement should
not have content (and should have
@when)
On , either the @marks attribute should be used, or a paragraph of description provided
A single TEI in Libraries document should not mix numbered and unnumbered divisions.
The use of divisions (i.e., whether numbered or
unnumbered divisions are used) should be
documented in a <tagUsage> element by "Unnumbered divs used." or "Numbered divs used." The <tagUsage> element must be the child of
a <namespace name="http://www.tei-c.org/ns/1.0"> element.
The fact that logical divisions are not encoded (and thus neither numbered nor unnumbered divisions are used) should be
documented in a <tagUsage> element by "Logical divisions not encoded." The <tagUsage> element must be the child of
a <namespace name="http://www.tei-c.org/ns/1.0"> element.
A document that uses un-numbered divisions
should specify so by using <tagUsage
gi="div">Unnumbered divs
used.</tagUsage>; a document that uses
numbered divisions should specify so by using
<tagUsage gi="div1">Numbered divs
used.</tagUsage>; a document that uses
neither should specify so by using <tagUsage
gi="sourceDoc">Logical divisions not
encoded.</tagUsage>.
The <extent> element
should not be used as a direct child of
<fileDesc>, but rather only as a descendant of a
bibliographic citation (e.g., of the source).
When inside an <imprint>, a <date>
element should have a machine-readable version
of the date specified either on the @when
attribute, or, in the case of not knowing the
precise date, on the @notBefore and @notAfter
attributes.
The
use of the = attribute (found here on the
<>
element) is not recommended by the Best Practices
for TEI in Libraries