diff --git a/P5/Source/Guidelines/en/AI-AnalyticMechanisms.xml b/P5/Source/Guidelines/en/AI-AnalyticMechanisms.xml
index 65ea77daed..04a1a60032 100644
--- a/P5/Source/Guidelines/en/AI-AnalyticMechanisms.xml
+++ b/P5/Source/Guidelines/en/AI-AnalyticMechanisms.xml
@@ -1225,9 +1225,11 @@ see chapter .
The selection and combination of modules to form a TEI schema is
described in .
-
-
-
+
+
+
+
+
The term language corpus is used to mean a number of
rather different things. It may refer simply to any collection of
linguistic data (for example, written, spoken, signed, or multimodal), although
@@ -305,19 +305,25 @@ corpora.
When the module defined in this chapter is included in a schema, a
number of additional elements become available within the
profileDesc element of the TEI header (discussed in section
-). These
-elements, members of the model.profileDescPart, are discussed in the
+).
+
+
+
+
+
+These elements, members of the model.profileDescPart, are discussed in the
remainder of the chapter.
-
-
-
-
+
+
+
-
-
-
-
+
+
+
+
+
The Text Description
The textDesc element provides a full description of the
@@ -964,4 +970,4 @@ elements, or silently omitted, as appropriate.
Encoders of text often find it useful to indicate that some aspects
of the encoded text are problematic or uncertain, and to indicate who is
responsible for various aspects of the markup of the electronic text.
@@ -448,10 +448,13 @@ in a given situation, encoders should provide their own controlled
vocabulary and document it in the encodingDesc or
tagUsage elements of the TEI header.
-->
-
-
+
+
-
+
+
+
+
@@ -607,4 +610,4 @@ The selection and combination of modules to form a TEI schema is described in
.
-
\ No newline at end of file
+
diff --git a/P5/Source/Guidelines/en/CO-CoreElements.xml b/P5/Source/Guidelines/en/CO-CoreElements.xml
index b8885c7395..c64cb2406f 100644
--- a/P5/Source/Guidelines/en/CO-CoreElements.xml
+++ b/P5/Source/Guidelines/en/CO-CoreElements.xml
@@ -5988,23 +5988,25 @@ were dialogue in a play. The following example is taken from a 19th century
The selection and combination of modules to form a TEI schema is
described in .
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/P5/Source/Guidelines/en/DEPRECATIONS.xml b/P5/Source/Guidelines/en/DEPRECATIONS.xml
index 7f444112d0..542ead3737 100644
--- a/P5/Source/Guidelines/en/DEPRECATIONS.xml
+++ b/P5/Source/Guidelines/en/DEPRECATIONS.xml
@@ -9,5 +9,17 @@
attributes, attribute values, datatypes etc.) which are deprecated
in this revision of the TEI Guidelines (revision of TEI P5 ).
+
+
+ Members of model.oddDecl are currently permitted in many
+ places. After 2026-09-03 this feature
+ (which some would call a bug) will be altered so that most such
+ elements will need to occur within a specGrp or
+ schemaSpec (or egXML) element. The affected
+ elements are: classSpec, constraintSpec,
+ dataSpec, elementSpec, macroSpec,
+ outputRendition, and specGrpRef.
+
+
-
\ No newline at end of file
+
diff --git a/P5/Source/Guidelines/en/DI-PrintDictionaries.xml b/P5/Source/Guidelines/en/DI-PrintDictionaries.xml
index a672f5fe98..6fa4edfbce 100644
--- a/P5/Source/Guidelines/en/DI-PrintDictionaries.xml
+++ b/P5/Source/Guidelines/en/DI-PrintDictionaries.xml
@@ -1,7 +1,7 @@
-
+
Dictionaries
This chapter defines a module for encoding lexical resources of all
@@ -284,24 +284,22 @@ derived headwords.
diff --git a/P5/Source/Guidelines/en/DR-PerformanceTexts.xml b/P5/Source/Guidelines/en/DR-PerformanceTexts.xml
index 5b0422ce56..2af52c6a3f 100644
--- a/P5/Source/Guidelines/en/DR-PerformanceTexts.xml
+++ b/P5/Source/Guidelines/en/DR-PerformanceTexts.xml
@@ -33,10 +33,11 @@ of performance texts. The model.stageLike
class supplies a set of elements for stage directions and similar
items such as camera movements, which can occur between or within
speeches.
-
-
-
-
+
+
+
+
+
Front and Back Matter
@@ -1404,4 +1405,4 @@ within a speech or between speeches.
The selection and combination of modules to form a TEI schema is described in
.
-
\ No newline at end of file
+
diff --git a/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml b/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml
index 9b607a61ec..c8e5a3f5af 100644
--- a/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml
+++ b/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml
@@ -1801,13 +1801,15 @@ monsters, Reader, with thy quill.
Estrutura do texto por defeitoテキスト構造モジュール
-
-
-
-
-
-
+
+
+
+
+
+
+
+
The selection and combination of modules to form a TEI schema is
described in .
-
\ No newline at end of file
+
diff --git a/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml b/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml
index f3280c6f14..da6285e9bd 100644
--- a/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml
+++ b/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml
@@ -1095,10 +1095,12 @@ discussion at .
The selection and combination of modules to form a TEI
schema is described in .
-
-
-
-
+
+
+
+
+
+
-
\ No newline at end of file
+
diff --git a/P5/Source/Guidelines/en/GD-GraphsNetworksTrees.xml b/P5/Source/Guidelines/en/GD-GraphsNetworksTrees.xml
index eddf6facde..ba8fbd997a 100644
--- a/P5/Source/Guidelines/en/GD-GraphsNetworksTrees.xml
+++ b/P5/Source/Guidelines/en/GD-GraphsNetworksTrees.xml
@@ -1316,9 +1316,11 @@ representing such information: see in particular chapters , <
The selection and combination of modules to form a TEI schema is
described in .
-
-
-
+
+
+
+
+
-
\ No newline at end of file
+
diff --git a/P5/Source/Guidelines/en/HD-Header.xml b/P5/Source/Guidelines/en/HD-Header.xml
index 2600ad7e26..364424bf55 100644
--- a/P5/Source/Guidelines/en/HD-Header.xml
+++ b/P5/Source/Guidelines/en/HD-Header.xml
@@ -1778,7 +1778,9 @@ more than one language, as in the following example:
longitude according to the 1984 World Geodetic System (WGS84).
-
+
+
+
The Unit Declaration
When documents feature units of measurement that are not listed in the International System of Units, the unitDecl element may be used in the encoding description to provide definitions and information about their origins and equivalents.
diff --git a/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml b/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml
index c3005758f6..ce56c9a89b 100644
--- a/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml
+++ b/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml
@@ -397,8 +397,8 @@ the preceding example thus:
-
-
+
+
@@ -740,7 +740,7 @@ kinds of object:
A node is an instance of one of the node kinds defined in
the XQuery and XPath Data Model 3.1. It represents
-a single item in the XML information set for a document. For pointing
+a single item in the XML information set for a document. For pointing
purposes, the only nodes that are of interest are Text Nodes,
Element Nodes, and Attribute Nodes.
@@ -1590,9 +1590,9 @@ Enter a Ship-master, and a Boteswaine.
See further and .
-
-
-
+
+
+
@@ -2895,7 +2895,7 @@ combination of exclusive and inclusive alt elements, as follows.
Stand-off Markup
- Introduction
+ Introduction
Most of the mechanisms defined in this chapter rely to a
greater or lesser extent on the fact that tags in a marked-up
@@ -2909,78 +2909,78 @@ combination of exclusive and inclusive alt elements, as follows.
XInclude mechanism defined by the W3C; another is to use pointers
as demonstrated elsewhere in this chapter.
-
There are many reasons for using stand-off markup: the source
- text might be read-only so that additional markup cannot be added,
+
There are many reasons for using stand-off markup: the source
+ text might be read-only so that additional markup cannot be added,
or a single text may need to be marked up
according to several hierarchically incompatible schemes, or a single
scheme may need to accommodate multiple hierarchical ambiguities, so that
a single markup tree is not the most faithful representation of the
source material.
-
This section describes a generic mechanism for expressing
- all kinds of markup externally as stand-off tags,
- for use whenever it is appropriate; and a place in the TEI
- structure (standOff) to contain certain common kinds
- of stand-off markup.
-
-
Throughout this section the following terms will be systematically used in
- specific senses.
-
-
- a document to which the stand-off markup refers (a source document can be either XML or
- plain text); there may be more than one source document.
-
- markup that is already present in an XML source document
-
- markup that is either outside of the source document
- and points in to it to the data it describes, or is pointed
- at by the data that refers to it; or alternatively is in
- another part of the source document and points elsewhere
- within the document to the data it describes, or is pointed
- at by data elsewhere that refers to it.
-
- a document that contains stand-off markup that points to a different, source document
-
- the action of creating a new XML document with external markup and data integrated with the
- source document data, and possibly some source document markup as well
-
- a process applied to markup from a pre-existing XML
- document, which splits it into two documents, an XML
- (external) document containing some of the markup of the
- original document, and another (source) XML document
- containing whatever text content and markup has not been
- extracted into the stand-off document; if all markup has been
- externalized from a document, the new source may be a plain
- text document
-
-
-
The three major requirements satisfied by this scheme for stand-off markup are:
-
- any valid TEI markup can be either internal or
- external,
- external markup can be internalized by
- applying it to the document content by either
- substituting the existing markup or adding to it,
- to form a valid TEI document, and
- the external markup itself specifies whether
- an internalized document is to be created by substituting
- the existing internal markup or by adding to
- it.
-
-
-
-
+
This section describes a generic mechanism for expressing
+ all kinds of markup externally as stand-off tags,
+ for use whenever it is appropriate; and a place in the TEI
+ structure (standOff) to contain certain common kinds
+ of stand-off markup.
+
+
Throughout this section the following terms will be systematically used in
+ specific senses.
+
+
+ a document to which the stand-off markup refers (a source document can be either XML or
+ plain text); there may be more than one source document.
+
+ markup that is already present in an XML source document
+
+ markup that is either outside of the source document
+ and points in to it to the data it describes, or is pointed
+ at by the data that refers to it; or alternatively is in
+ another part of the source document and points elsewhere
+ within the document to the data it describes, or is pointed
+ at by data elsewhere that refers to it.
+
+ a document that contains stand-off markup that points to a different, source document
+
+ the action of creating a new XML document with external markup and data integrated with the
+ source document data, and possibly some source document markup as well
+
+ a process applied to markup from a pre-existing XML
+ document, which splits it into two documents, an XML
+ (external) document containing some of the markup of the
+ original document, and another (source) XML document
+ containing whatever text content and markup has not been
+ extracted into the stand-off document; if all markup has been
+ externalized from a document, the new source may be a plain
+ text document
+
+
+
The three major requirements satisfied by this scheme for stand-off markup are:
+
+ any valid TEI markup can be either internal or
+ external,
+ external markup can be internalized by
+ applying it to the document content by either
+ substituting the existing markup or adding to it,
+ to form a valid TEI document, and
+ the external markup itself specifies whether
+ an internalized document is to be created by substituting
+ the existing internal markup or by adding to
+ it.
+
+
+
+
@@ -3001,31 +3001,31 @@ combination of exclusive and inclusive alt elements, as follows.
scheme of XPointer, these Guidelines permit the use of any of the
pointing schemes discussed in section .
-
XInclude is a W3C recommendation which specifies a syntax for the
- inclusion within an XML document of data fragments placed in
- different resources. Included resources can be either plain
- text or XML. XInclude instructions within an XML document
- are meant to be replaced by a resource targetted by a
- URI, possibly augmented by an XPointer that identifies the
- exact subresource to be included.
+
XInclude is a W3C recommendation which specifies a syntax for the
+ inclusion within an XML document of data fragments placed in
+ different resources. Included resources can be either plain
+ text or XML. XInclude instructions within an XML document
+ are meant to be replaced by a resource targetted by a
+ URI, possibly augmented by an XPointer that identifies the
+ exact subresource to be included.
-
The xi:include element uses the href attribute to specify the location of
- the resource to be included; its value is an URI containing,
- if necessary, an XPointer. Additionally, it uses the parse attribute (whose only valid values
- are text and xml) to specify whether
- the included content is plain text or an XML fragment, and
- the encoding attribute to provide a hint, when
- the included fragment is text, of the character encoding of
- the fragment. An optional xi:fallback element is
- also permitted within an xi:include; it specifies
- alternative content to be used when the external resource
- cannot be fetched for some reason. Its use is not however
- recommended for stand-off markup.
+
The xi:include element uses the href attribute to specify the location of
+ the resource to be included; its value is an URI containing,
+ if necessary, an XPointer. Additionally, it uses the parse attribute (whose only valid values
+ are text and xml) to specify whether
+ the included content is plain text or an XML fragment, and
+ the encoding attribute to provide a hint, when
+ the included fragment is text, of the character encoding of
+ the fragment. An optional xi:fallback element is
+ also permitted within an xi:include; it specifies
+ alternative content to be used when the external resource
+ cannot be fetched for some reason. Its use is not however
+ recommended for stand-off markup.
- Stand-off Markup in TEI
+ Stand-off Markup in TEI
The operations of internalizing and externalizing markup are
very useful and practically important. XInclude processing as
@@ -3083,7 +3083,7 @@ xpointer="range(xpath(id('par1')//emph),xpath(id('par2')//emph))"/>
The semantics of XInclude require the creation of well-formed XML results even though
the pointing mechanisms it uses do not necessarily
respect the hierarchical structure of XML documents, as in
- this case. While
+ this case. While
this is a good way to ensure that internalization is always
possible, it has implications for the use of XInclude as a
notation for the description of overlapping
@@ -3111,7 +3111,7 @@ The semantics of XInclude require the creation of well-formed XML results even t
links and facilitating adjustments to the source document
without breaking external documents that reference it.
-
+
Any tag can be externalized by
@@ -3129,20 +3129,20 @@ The semantics of XInclude require the creation of well-formed XML results even t
If bees are few.