diff --git a/P5/Source/Guidelines/en/HD-Header.xml b/P5/Source/Guidelines/en/HD-Header.xml
index b03c51e5d7..0757439b01 100644
--- a/P5/Source/Guidelines/en/HD-Header.xml
+++ b/P5/Source/Guidelines/en/HD-Header.xml
@@ -1779,7 +1779,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 3d8e462b99..2b320119de 100644
--- a/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml
+++ b/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml
@@ -398,8 +398,8 @@ the preceding example thus:
-
-
+
+
@@ -741,7 +741,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.
@@ -1592,9 +1592,9 @@ Enter a Ship-master, and a Boteswaine.
See further and .
-
-
-
+
+
+
@@ -2897,7 +2897,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
@@ -2911,78 +2911,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.
+
+
+
+
@@ -3003,31 +3003,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
@@ -3085,7 +3085,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
@@ -3113,14 +3113,14 @@ 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
- removing its content and replacing it with an
- xi:include element that contains an XPointer
- pointing to the desired content.
-
For instance the following portion of a TEI document:
+ removing its content and replacing it with an
+ xi:include element that contains an XPointer
+ pointing to the desired content.
+
For instance the following portion of a TEI document:
1755
@@ -3131,20 +3131,20 @@ The semantics of XInclude require the creation of well-formed XML results even t
If bees are few.
- can be externalized by placing the actual text in a separate
- document, and providing exactly the same markup with the
- xi:include elements:
-
-
- To make a prairie it takes a clover and one bee,\n
+ can be externalized by placing the actual text in a separate
+ document, and providing exactly the same markup with the
+ xi:include elements:
+
+
+ To make a prairie it takes a clover and one bee,\n
One clover, and a bee,\n
And revery.\n
The revery alone will do,\n
If bees are few.\n
]]>
-
-
-
+
+
+
1755
@@ -3172,50 +3172,50 @@ If bees are few.\n
-
Please note that this specification requires that the
- XInclude namespace declaration is present in all cases. The
- xi:fallback element contains text or XML fragments to
- be placed in the document if the inclusion fails for any
- reason (for instance due to inaccessibility of an external
- resource). The xi:fallback element is optional; if it
- is not present an XInclude processor must signal a fatal error
- when a resource is not found. This is the preferred behaviour
- for use with stand-off markup. These Guidelines recommend
- against the use of xi:fallback for stand-off
- markup.
+
Please note that this specification requires that the
+ XInclude namespace declaration is present in all cases. The
+ xi:fallback element contains text or XML fragments to
+ be placed in the document if the inclusion fails for any
+ reason (for instance due to inaccessibility of an external
+ resource). The xi:fallback element is optional; if it
+ is not present an XInclude processor must signal a fatal error
+ when a resource is not found. This is the preferred behaviour
+ for use with stand-off markup. These Guidelines recommend
+ against the use of xi:fallback for stand-off
+ markup.
- Well-formedness and Validity of Stand-off Markup
-
The whole source fragment
- identified by an XInclude element, as well as any markup
- therein contained is inserted in the position specified, and
- an XInclude processor is required to ensure that the resulting
- internalized document is
- well-formed. This has obvious implications when the external
- document contains XML markup. A plain text source document
- will always create a well-formed
- internalized document.
-
While a TEI customization may permit
+
Well-formedness and Validity of Stand-off Markup
+
The whole source fragment
+ identified by an XInclude element, as well as any markup
+ therein contained is inserted in the position specified, and
+ an XInclude processor is required to ensure that the resulting
+ internalized document is
+ well-formed. This has obvious implications when the external
+ document contains XML markup. A plain text source document
+ will always create a well-formed
+ internalized document.
+
While a TEI customization may permit
xi:include elements in various places in a TEI document
instance, in general these Guidelines suggest that validity be
verified after the resolution of all the xi:include
elements.
- Including Text or XML Fragments
-
When the source text is plain text the overall form of the
- XPointer pointing to it is of minimal importance. The form
- of the XPointer matters considerably, on the other hand,
- when the source document is XML.
-
In this case, it is rather important to distinguish whether
- we intend to substitute the source XML with the new one, or
- just to add new markup to it. The XPointers used in the
- references can express both cases.
-
A simple way is to make sure to select only textual data in
- the XPointer. For instance, given the following
- document:
-
-
+
Including Text or XML Fragments
+
When the source text is plain text the overall form of the
+ XPointer pointing to it is of minimal importance. The form
+ of the XPointer matters considerably, on the other hand,
+ when the source document is XML.
+
In this case, it is rather important to distinguish whether
+ we intend to substitute the source XML with the new one, or
+ just to add new markup to it. The XPointers used in the
+ references can express both cases.
+
A simple way is to make sure to select only textual data in
+ the XPointer. For instance, given the following
+ document:
+
+
@@ -3228,7 +3228,7 @@ If bees are few.\n
If bees are few.
-
+
the expression
range(element(/1/2/1.0),element(/1/2/11.1)) will select
the whole poem, text content anddiv elements
@@ -3238,11 +3238,11 @@ nodes count).
xpointer(//text()/range-to(.)) and
xpointer(string-range(//text(),"To")/range-to(//text(),"few.")
will only select the text of the poem, with no markup inside.
-
Thus, the following could be a valid stand-off document for
- the
Source.xhtml document:
-
-
-
+
Thus, the following could be a valid stand-off document for
+ the
Source.xhtml document:
+
+
+
1755
@@ -3455,10 +3455,11 @@ will only select the text of the poem, with no markup inside.
-
-
-
-
+
+
+
+
+
diff --git a/P5/Source/Guidelines/en/ST-Infrastructure.xml b/P5/Source/Guidelines/en/ST-Infrastructure.xml
index b141ec6789..9cc7c93991 100644
--- a/P5/Source/Guidelines/en/ST-Infrastructure.xml
+++ b/P5/Source/Guidelines/en/ST-Infrastructure.xml
@@ -1048,124 +1048,126 @@ one, or vice versa, should be done with care.
these Guidelines are classified in this way, and future editions of these recommendations
will extend and develop this classification scheme.
A complete alphabetical list of all model classes is provided in .
diff --git a/P5/Source/Guidelines/en/TD-DocumentationElements.xml b/P5/Source/Guidelines/en/TD-DocumentationElements.xml
index d5acac80bc..64a3133522 100644
--- a/P5/Source/Guidelines/en/TD-DocumentationElements.xml
+++ b/P5/Source/Guidelines/en/TD-DocumentationElements.xml
@@ -385,7 +385,9 @@ element -->
xml:lang and a versionDate attribute to
indicate the language used and the date on which the
translated text was last checked against its source.
-
+
+
+
The equiv element is used to document equivalencies between the concept represented by this
object and the same concept as described in other schemes or ontologies. The uri attribute
is used to supply a pointer to some location where such external concepts are defined. For example, to
@@ -1880,9 +1882,11 @@ xmlns="http://www.tei-c.org/ns/Examples">
The validUntil attribute may be used to signal an intent to remove a construct
from future versions of the schema being specified.
-
-
-
+
+
+
+
+
The elementSpec, attDef and schemaSpec specification elements also have an
attribute which determines which namespace to which the object being created will belong. In the case of
schemaSpec, this namespace is inherited by all the elements created in the schema, unless
@@ -1890,7 +1894,9 @@ xmlns="http://www.tei-c.org/ns/Examples">
-
+
+
+
These attributes are used by an ODD processor to determine how declarations are to be combined to form
a schema or DTD, as further discussed in this section.
diff --git a/P5/Source/Specs/model.oddDecl.xml b/P5/Source/Specs/model.oddDecl.xml
index 4cfcea94d9..3da41811f4 100644
--- a/P5/Source/Specs/model.oddDecl.xml
+++ b/P5/Source/Specs/model.oddDecl.xml
@@ -6,14 +6,7 @@
ODD 문서에서 마크업 언어로 선언을 생성하는 요소를 모아 놓는다.匯集的元素使ODD文件內某些標記語言中產生宣告。ODD文書で使用される要素の宣言を生成する要素をまとめる。
- regroupe les éléments qui, dans des documents ODD,
- génèrent des déclarations dans un langage d'encodage.
- agrupa elementos que generan declaraciones en un lenguaje
- de codificación dado en documentos aislados
- raggruppa elementi che generano dichiarazioni in un dato
- linguaggio di codifica in documenti isolati
-
-
-
-
-
\ No newline at end of file
+ regroupe les éléments qui, dans des documents ODD, génèrent des déclarations dans un langage d'encodage.
+ agrupa elementos que generan declaraciones en un lenguaje de codificación dado en documentos aislados
+ raggruppa elementi che generano dichiarazioni in un dato linguaggio di codifica in documenti isolati
+
diff --git a/P5/Source/Specs/moduleSpec.xml b/P5/Source/Specs/moduleSpec.xml
index 49f5e2123d..36e926a03e 100644
--- a/P5/Source/Specs/moduleSpec.xml
+++ b/P5/Source/Specs/moduleSpec.xml
@@ -7,33 +7,29 @@
especificación de módulospécification de modulespecifica del modulo
- documents the structure, content, and purpose of a single
-module, i.e. a named and externally visible group of declarations.
+ documents the structure, content, and purpose of a single module, i.e. a named and externally visible group of declarations.하나의 모듈에 대한 구조, 내용 및 목적을 기록한다. 즉, 선언의 이름과 외부적으로 가시적인 그룹記錄單一模組的結構、內容、以及用途,例如:一個已命名且外部明確的宣告組。
- いちモジュールの構造、内容、目的を記録する。例えば、外部から名前で参
- 照可能な宣言集合などである。
- documente la structure, le contenu et les
- fonctions d'un module, i.e. d'un groupe de déclarations nommé et
- visible extérieurement.
+ いちモジュールの構造、内容、目的を記録する。例えば、外部から名前で参 照可能な宣言集合などである。
+ documente la structure, le contenu et les fonctions d'un module, i.e. d'un groupe de déclarations nommé et visible extérieurement.documenta la estructura, el contenido y la finalidad de un único módulo, es decir, un grupo de declaraciones específicamente indicado y visible externamente.documenta struttura, contenuto e scopo di un unico modulo, cioè un gruppo di dichiarazioni specificamente indicato ed esternamente visibile
-
+
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
diff --git a/P5/Source/Specs/specGrp.xml b/P5/Source/Specs/specGrp.xml
index 3759c4c82b..b86b1c3079 100644
--- a/P5/Source/Specs/specGrp.xml
+++ b/P5/Source/Specs/specGrp.xml
@@ -8,18 +8,16 @@
groupe de spécificationsgrupo de instruccionesgruppo di istruzioni
- contains any convenient grouping of specifications for use within
- the current module.
+ contains any convenient grouping of specifications for use within the current module.현 모듈 내에서 사용에 대한 명시를 다양한 방법의 그룹화를 포함한다.包含在現有模組中的細節使用說明群組。当該モジュール中にある規定をまとめる。
- contient tout regroupement approprié de
- spécifications pour une utilisation dans le module en question.
+ contient tout regroupement approprié de spécifications pour une utilisation dans le module en question.contiene cualquier agrupación funcional de instrucciones para el uso al interno del módulo corrientecontiene un qualsiasi raggruppamento funzionale di istruzioni per l'uso all'interno del modulo corrente
-
+
@@ -109,4 +107,4 @@ contains specifications for the elements
-
\ No newline at end of file
+
diff --git a/P5/Source/Specs/specGrpRef.xml b/P5/Source/Specs/specGrpRef.xml
index 3362ea72d9..c6fcd66b86 100644
--- a/P5/Source/Specs/specGrpRef.xml
+++ b/P5/Source/Specs/specGrpRef.xml
@@ -8,20 +8,17 @@
référence à un groupe de spécificationsreferencia a un grupo de instruccionesriferimento a gruppo di istruzioni
- indicates that the declarations contained by the specGrp referenced should be
- inserted at this point.
+ indicates that the declarations contained by the specGrp referenced should be inserted at this point.참조된 specGrp에 의해 포함된 선언은 이 지점에서 삽입되어야함을 나타낸다.指出被參照的元素specGrp中的宣告應在此插入。要素specGrpにより含まれる宣言が、この場所に挿入されるべきこ とを示す。
- indique que les déclarations contenues dans l'élément
- specGrpréférencé doivent être insérées à cet endroit.
- indica el punto en el que deben inserirse las
- declaraciones contenidas en el specGrp indicado.
- indica il punto in cui devono essere inserite le
- dichiarazioni contenute nello specGrp indicato
+ indique que les déclarations contenues dans l'élément specGrpréférencé doivent être insérées à cet endroit.
+ indica el punto en el que deben inserirse las declaraciones contenidas en el specGrp indicado.
+ indica il punto in cui devono essere inserite le dichiarazioni contenute nello specGrp indicato
-
+
+
@@ -30,12 +27,9 @@
여기에 국부적으로 소속된 명시 그룹을 가리킨다.指向照理屬於此位置的說明群組。論理的にはこの場素にある規定グループを参照する。
- pointe vers l'élément specGrp qui doit
- logiquement être référencé à cet endroit.
- indica el grupo de instrucciones que por lógica
- corresponde a ese punto en cuestión.
- indica il gruppo di istruzioni che per logica
- corrisponde al punto in questione
+ pointe vers l'élément specGrp qui doit logiquement être référencé à cet endroit.
+ indica el grupo de instrucciones que por lógica corresponde a ese punto en cuestión.
+ indica il gruppo di istruzioni che per logica corrisponde al punto in questione
@@ -123,4 +117,4 @@
-
\ No newline at end of file
+
From 437c554d11c7eed853eb82c564770c9437aa2b5f Mon Sep 17 00:00:00 2001
From: Syd Bauman
Date: Sat, 3 Jan 2026 20:47:10 -0500
Subject: [PATCH 2/4] First stage in addressing issue #2306. Still have to
write tests.
---
.../Guidelines/en/AI-AnalyticMechanisms.xml | 8 +-
.../Guidelines/en/CC-LanguageCorpora.xml | 30 ++-
.../en/CE-CertaintyResponsibility.xml | 13 +-
P5/Source/Guidelines/en/CO-CoreElements.xml | 38 +--
.../Guidelines/en/DR-PerformanceTexts.xml | 11 +-
.../Guidelines/en/DS-DefaultTextStructure.xml | 16 +-
.../en/FT-TablesFormulaeGraphics.xml | 12 +-
.../Guidelines/en/GD-GraphsNetworksTrees.xml | 10 +-
P5/Source/Guidelines/en/ST-Infrastructure.xml | 240 +++++++++---------
P5/Source/Specs/classSpec.xml | 68 ++---
P5/Source/Specs/constraintSpec.xml | 7 +
P5/Source/Specs/dataSpec.xml | 7 +
P5/Source/Specs/elementSpec.xml | 7 +
P5/Source/Specs/macroSpec.xml | 9 +-
P5/Source/Specs/model.oddDecl.xml | 37 ++-
P5/Source/Specs/outputRendition.xml | 9 +-
P5/Source/Specs/specGrpRef.xml | 9 +-
17 files changed, 303 insertions(+), 228 deletions(-)
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 .
-
-
-
+
+
+
+
+
diff --git a/P5/Source/Guidelines/en/CC-LanguageCorpora.xml b/P5/Source/Guidelines/en/CC-LanguageCorpora.xml
index 6b8be10742..97428c62d9 100644
--- a/P5/Source/Guidelines/en/CC-LanguageCorpora.xml
+++ b/P5/Source/Guidelines/en/CC-LanguageCorpora.xml
@@ -1,7 +1,7 @@
-
Language Corpora
+
Language Corpora
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/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/ST-Infrastructure.xml b/P5/Source/Guidelines/en/ST-Infrastructure.xml
index f745f121a9..55360eedba 100644
--- a/P5/Source/Guidelines/en/ST-Infrastructure.xml
+++ b/P5/Source/Guidelines/en/ST-Infrastructure.xml
@@ -1071,125 +1071,127 @@ one, or vice versa, should be done with care.
these Guidelines are classified in this way, and future editions of these recommendations
will extend and develop this classification scheme.
A complete alphabetical list of all model classes is provided in .
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/P5/Source/Specs/classSpec.xml b/P5/Source/Specs/classSpec.xml
index 28b2299bd7..5a70c3b739 100644
--- a/P5/Source/Specs/classSpec.xml
+++ b/P5/Source/Specs/classSpec.xml
@@ -1,7 +1,7 @@
-
+class specification부류 명시
@@ -9,17 +9,11 @@
spécification de classeindicazione di classeクラス仕様
- contains reference information for a TEI element class;
-that is a group of
- elements which appear together in content models, or
- which share some common attribute, or both.
+ contains reference information for a TEI element class; that is a group of elements which appear together in content models, or which share some common attribute, or both.TEI 요소 부류에 대한 참조 정보를 포함한다; 이것은 내용 모델에서 함께 나타나거나, 공통 속성을 공유하거나, 이 둘을 포괄하는 요소들의 그룹이다.包含一個TEI元素集的參照資訊;元素集是一群在內容模組中同時出現、或共用某些屬性、或兩者皆包括的元素。
- TEI要素クラスにおける参照情報を示す。内容モデルに出現する要素のまと
- まり、共通する属性のまとまり、またはその両方。
- contient des informations de référence pour une
- classe d'éléments TEI, c'est-à-dire un groupe d'éléments qui figurent ensemble
- dans des modèles de contenu ou qui partagent un attribut commun, ou qui ont l'un et l'autre.
+ TEI要素クラスにおける参照情報を示す。内容モデルに出現する要素のまと まり、共通する属性のまとまり、またはその両方。
+ contient des informations de référence pour une classe d'éléments TEI, c'est-à-dire un groupe d'éléments qui figurent ensemble dans des modèles de contenu ou qui partagent un attribut commun, ou qui ont l'un et l'autre.contiene informaciones relativas a una clase de elementos TEI, es decir, a un grupo de elementos que aparecen juntos en modelos de contenido, o que tienen algunos atributos en común, o ambas cosas.contiene informazioni relative a una classe di elementi TEI, cioè un gruppo di elementi che compaiono insieme in modelli di contenuto, oppure che hanno alcuni attributi in comune, o entrambe le cose
@@ -42,13 +36,20 @@ that is a group of
+
+
+
+
+
+
+ indicates whether this is a model class or an attribute class모델 부류 또는 속성 부류 여부를 나타낸다.指出這是結構元素集或是屬性元素集。当該クラスがモデルクラスか属性クラスかを示す。
- indique si c'est une classe de modèles ou une classe d'attributs.
+ indique si c'est une classe de modèles ou une classe d'attributsindica si se trata de una clase de modelos o de atributos.indica se si tratta di una classe di modelli o di attributi
@@ -64,8 +65,7 @@ that is a group of
이 부류의 원소는 동일 내용 모델에서 나타난다.該元素集的元素出現在相同的內容模組中内容モデルクラス。
- les membres de cette classe
- figurent dans les mêmes modèles de contenu
+ les membres de cette classe figurent dans les mêmes modèles de contenulos miembros de esta clase aparecen en los mismos modelos de contenido.i membri di questa classe compaiono negli stessi modelli di contenuto
@@ -80,24 +80,18 @@ that is a group of
이 부류의 원소는 공통 속성을 공유한다.該元素集的元素有共用的屬性属性クラス。
- les membres de cette classe
- partagent des attributs communs
+ les membres de cette classe partagent des attributs communslos miembros de esta clase tienen algunos atributos comunes.i membri di questa classe hanno alcuni attributi in comune
- indicates which alternation and sequence instantiations
- of a model class may be referenced. By default, all variations
- are permitted.
+ indicates which alternation and sequence instantiations of a model class may be referenced. By default, all variations are permitted.모델 부류의 교체 및 일련의 인스턴스 생성이 참조될 수 있음을 나타낸다. 기본적으로 모든 변이형이 허용된다.說明應該建立結構元素集的哪些替換及順序作業實例。在預設的情形下,會提供所有的變數。
- モデルクラスのインスタンスとしてある選択肢を示す。デフォルトでは、
- あらゆるものが可能である。
- donne les règles régissant dans une
- instance TEI l'ordre et l'alternance des éléments définis par la classe. Par
- défaut, toutes les variations sont données.
+ モデルクラスのインスタンスとしてある選択肢を示す。デフォルトでは、 あらゆるものが可能である。
+ donne les règles régissant dans une instance TEI l'ordre et l'alternance des éléments définis par la classe. Par défaut, toutes les variations sont données.indica que alternancia y que tipos de secuencia se establecen para una clase de modelos; por defecto se indican todas las variaciones.indica quale alternanza e quali tipi di sequenza stabilire per una classe di modelli; di norma sono indicate tutte le variazioni
@@ -107,8 +101,7 @@ that is a group of
부류의 원소들은 선택가능 항목이다.該元素集的元素是替換元素当該クラスの構成要素は、選択的である。
- les membres de la classe
- constituent des alternatives
+ les membres de la classe constituent des alternativeslos miembros de las clase estan en relación de alternancia.i membri della classe sono in relatione di alternanza
@@ -117,31 +110,26 @@ that is a group of
부류의 원소는 차례대로 제시된다.該元素集的元素會依序呈現当該クラスの構成要素は、リストとしてある。
- les membres de la classe doivent
- tous être donnés dans l'ordre indiqué
+ les membres de la classe doivent tous être donnés dans l'ordre indiquélos miembros de las clase se indican en secuencia.i membri della classe devono essere indicati in sequenzamembers of the class may be provided, in sequence,
- but are optional
+ but are optional
부류의 원소는 차례대로 제시될 수 있지만 수의적이다.該元素集的元素可依序呈現,但非必須当該クラスの構成要素は、リストから選択される。
- les membres de la classe peuvent
- être donnés, dans l'ordre indiqué, mais sont facultatifs
+ les membres de la classe peuvent être donnés, dans l'ordre indiqué, mais sont facultatifslos miembros de la clase pueden proporcionarse en modo de secuencia pero son opcionales.i membri della classe possono essere indicati in sequenza ma sono facoltativi
- members of the class may be provided one or more
- times, in sequence, but are optional.
+ members of the class may be provided one or more times, in sequence, but are optional.부류의 원소들은 한 번 이상 그리고 차례대로 제시될 수 있지만 수의적이다.該元素集的元素可一次或多次依序呈現,但非必須当該クラスの構成要素は、リストから1つ以上が選択される。
- les membres de la classe peuvent
- être donnés une ou plusieurs fois, dans l'ordre indiqué, mais sont
- facultatifs
+ les membres de la classe peuvent être donnés une ou plusieurs fois, dans l'ordre indiqué, mais sont facultatifslos miembros de la clase pueden indicarse una o más ocasiones en secuencia, pero son opcionales.i membri della classe possono essere indicati una o più volte in sequenza ma sono facoltativi
@@ -150,8 +138,7 @@ that is a group of
부류의 원소들은 차례대로 한 번 이상 제시될 수 있다.該元素集的元素可一次或多次依序呈現当該クラスの構成要素は、リストから1つ以上が選択される。
- les membres de la classe doivent
- être donnés au moins une fois, dans l'ordre indiqué.
+ les membres de la classe doivent être donnés au moins une fois, dans l'ordre indiqué.miembros de la clase pueden ser indicados una o más veces en secuencia.i membri della classe possono essere indicati una o più volte in sequenza
@@ -167,9 +154,10 @@ that is a group of
The principles on which segmentation is carried out, and
-any special codes or attribute values used, should be defined explicitly
-in the segmentation element of the encodingDesc within
-the associated TEI header.
+ any special codes or attribute values used, should be
+ defined explicitly in the segmentation element of
+ the encodingDesc within the associated TEI
+ header.
diff --git a/P5/Source/Specs/constraintSpec.xml b/P5/Source/Specs/constraintSpec.xml
index 265108e4fb..c0ed874093 100644
--- a/P5/Source/Specs/constraintSpec.xml
+++ b/P5/Source/Specs/constraintSpec.xml
@@ -21,6 +21,13 @@
+
+
+
+
+
+
+
-
+macro specification매크로 명시
@@ -36,6 +36,13 @@
+
+
+
+
+
+
+
diff --git a/P5/Source/Specs/model.oddDecl.xml b/P5/Source/Specs/model.oddDecl.xml
index 41a3a42f2f..b466d5f773 100644
--- a/P5/Source/Specs/model.oddDecl.xml
+++ b/P5/Source/Specs/model.oddDecl.xml
@@ -1,18 +1,41 @@
-
+groups elements which generate declarations in some markup language in ODD documents.ODD 문서에서 마크업 언어로 선언을 생성하는 요소를 모아 놓는다.匯集的元素使ODD文件內某些標記語言中產生宣告。ODD文書で使用される要素の宣言を生成する要素をまとめる。
- regroupe les éléments qui, dans des documents ODD,
- génèrent des déclarations dans un langage d'encodage.
- agrupa elementos que generan declaraciones en un lenguaje
- de codificación dado en documentos aislados
- raggruppa elementi che generano dichiarazioni in un dato
- linguaggio di codifica in documenti isolati
+ regroupe les éléments qui, dans des documents ODD, génèrent des déclarations dans un langage d'encodage.
+ agrupa elementos que generan declaraciones en un lenguaje de codificación dado en documentos aislados
+ raggruppa elementi che generano dichiarazioni in un dato linguaggio di codifica in documenti isolati
+
+
+
+
+
+
+
+ DEPRECATION WARNING: Sometime after 2026-09-03 the <>
+ element will no longer be allowed as a child of <>;
+ it will need to be a descendant of either a <specGrp> or a <schemaSpec>.
+
+
+
+
+
diff --git a/P5/Source/Specs/outputRendition.xml b/P5/Source/Specs/outputRendition.xml
index 457b5d862a..fd1d0b4667 100644
--- a/P5/Source/Specs/outputRendition.xml
+++ b/P5/Source/Specs/outputRendition.xml
@@ -1,7 +1,7 @@
-
+
describes the rendering or
appearance intended for all occurrences of an element in a specified
@@ -13,6 +13,13 @@
+
+
+
+
+
+
+ provides a way of defining
diff --git a/P5/Source/Specs/specGrpRef.xml b/P5/Source/Specs/specGrpRef.xml
index da68e6d9ad..274539156f 100644
--- a/P5/Source/Specs/specGrpRef.xml
+++ b/P5/Source/Specs/specGrpRef.xml
@@ -1,7 +1,7 @@
-
+reference to a specification group명시 그룹에 대한 참조參照到一個說明群組
@@ -21,6 +21,13 @@
+
+
+
+
+
+
+ points at the specification group which logically belongs here.
From ac2b2a77efc0eb2537400406c0b5092ce91de08d Mon Sep 17 00:00:00 2001
From: Syd Bauman
Date: Sat, 3 Jan 2026 21:02:51 -0500
Subject: [PATCH 3/4] Added a single test to detest for
elementSpec-should-not-be-in-head.
---
P5/Test/detest.odd | 5 +-
.../detest_odd_schematron.svrl | 409 ++++++++----------
2 files changed, 189 insertions(+), 225 deletions(-)
diff --git a/P5/Test/detest.odd b/P5/Test/detest.odd
index 72effe8d3a..8bba949e6e 100644
--- a/P5/Test/detest.odd
+++ b/P5/Test/detest.odd
@@ -61,7 +61,10 @@
- A Test Schema
+ A Test should be flagged as an error: elementSpec
+ should not be in head; also this desc does not have @xml:lang
+ nor @versionDate.Schema
+
+ 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.
+
+