From 6270dac60640e1f738d1df39165d107a67efe78a Mon Sep 17 00:00:00 2001 From: ebeshero Date: Mon, 13 Nov 2023 20:38:13 -0500 Subject: [PATCH 01/28] started draft of 4.7 release notes --- P5/ReleaseNotes/readme-4.7.0.xml | 177 +++++++++++++++++++++++++++++++ 1 file changed, 177 insertions(+) create mode 100644 P5/ReleaseNotes/readme-4.7.0.xml diff --git a/P5/ReleaseNotes/readme-4.7.0.xml b/P5/ReleaseNotes/readme-4.7.0.xml new file mode 100644 index 0000000000..6637ced1b1 --- /dev/null +++ b/P5/ReleaseNotes/readme-4.7.0.xml @@ -0,0 +1,177 @@ + + + + + + + + + TEI P5 version 4.7.0 and Stylesheets version 7.56.0 release notes + + + + Thursday, 16 November 2023 + + + + The Text Encoding Initiative + + +

Created retrospectively from ChangeLog and GitHub trackers

+ + + + + +

Release 4.7.0 is codenamed ????.

+

This release introduces new features and resolves a number of issues raised by the TEI + community. As always, the majority of these changes and corrections are a consequence of + feature requests or bugs reported by the TEI community using the GitHub tracking system. A + full list of the issues resolved in the course of this release cycle may be found under the + 4.7.0 milestone.

+ +

The following changes are particularly worth highlighting in this release: + + New encoding features + New with this release is the eventName element, which may be used anywhere as a member of att.global to encode a name for an event. + The new eventName element also has membership in several attribute classes associated with named entities, including att.datable to supply a date range for the use of an event's name, and att.typed, allowing it type and subtype attributes. It has also been added to att.editLike, permitting its application in contexts of describing events in an editing process (#2382). + The content model of event has been modified to contain eventName elements without invalidate older ways of labeling events. + The first child of an event element may still be an idno a head element, but modelling of events may now begin instead with eventName or with members of model.pLike (ab or p) or model.labelLike (desc or label). See PR #2483. + + + + + + + + Changes to content models + + + + + + Changes to classes + + + +

+

With these release notes we are beginning a practice of documenting changes to content models that could invalidate ODD customizations in TEI projects + if they are working with the current release of these TEI Guidelines. Those maintaining ODD customizations of the TEI may want to be aware of the following changes and + adapt your ODD files accordingly. + + ODD-breaking changes + + +

+

+ + + Improvements of prose and examples + + + + + + + + + Housekeeping + + + + + +

+ +

In addition, many improvements have been made to the XSLT stylesheets (which provide + processing of TEI ODD files for Roma and + TEIGarage as well as other TEI + conversions). The Stylesheets are maintained separately from the Guidelines at https://github.com/TEIC/Stylesheets. A + full list of the issues resolved in the course of this release cycle may be found under the + 7.56.0 milestone.

+ +

Highlights of this release include: + + + + + + +

+ + + From c348b1d6831ee6524a89c0e0c31684dfe1410b88 Mon Sep 17 00:00:00 2001 From: ebeshero Date: Mon, 13 Nov 2023 21:05:41 -0500 Subject: [PATCH 02/28] more content for readme draft --- P5/ReleaseNotes/readme-4.7.0.xml | 61 ++++---------------------------- 1 file changed, 6 insertions(+), 55 deletions(-) diff --git a/P5/ReleaseNotes/readme-4.7.0.xml b/P5/ReleaseNotes/readme-4.7.0.xml index 6637ced1b1..6bbe749282 100644 --- a/P5/ReleaseNotes/readme-4.7.0.xml +++ b/P5/ReleaseNotes/readme-4.7.0.xml @@ -40,8 +40,10 @@ See the file COPYING.txt for details New with this release is the eventName element, which may be used anywhere as a member of att.global to encode a name for an event. The new eventName element also has membership in several attribute classes associated with named entities, including att.datable to supply a date range for the use of an event's name, and att.typed, allowing it type and subtype attributes. It has also been added to att.editLike, permitting its application in contexts of describing events in an editing process (#2382). The content model of event has been modified to contain eventName elements without invalidate older ways of labeling events. - The first child of an event element may still be an idno a head element, but modelling of events may now begin instead with eventName or with members of model.pLike (ab or p) or model.labelLike (desc or label). See PR #2483. + The first child of an event element may still be an idno a head element, but modelling of events may now begin instead with eventName or with members of model.pLike (ab or p) or model.labelLike (desc or label). See PR #2483. + A Schematron constraint has been added to the specification for dataSpec in order to prevent the possibility of elements being included in the specification for an attribute’s datatype (PR #2443 and #2426). + @@ -49,7 +51,7 @@ See the file COPYING.txt for details Changes to content models - + A scheme attribute is now usually optional on constraintSpec, except for the case of a constraintSpec with mode = "add" or mode = "replace" (PR #2453 and #2261). + +

From 11ba3dcd2cc32f08cd5fb08c0ad3c88965ba8e59 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Mon, 13 Nov 2023 21:20:53 -0500 Subject: [PATCH 03/28] wording adjustments to readme --- P5/ReleaseNotes/readme-4.7.0.xml | 27 +++++++++++++-------------- 1 file changed, 13 insertions(+), 14 deletions(-) diff --git a/P5/ReleaseNotes/readme-4.7.0.xml b/P5/ReleaseNotes/readme-4.7.0.xml index 6637ced1b1..ef66a2b74d 100644 --- a/P5/ReleaseNotes/readme-4.7.0.xml +++ b/P5/ReleaseNotes/readme-4.7.0.xml @@ -33,21 +33,20 @@ See the file COPYING.txt for details feature requests or bugs reported by the TEI community using the GitHub tracking system. A full list of the issues resolved in the course of this release cycle may be found under the 4.7.0 milestone.

- -

The following changes are particularly worth highlighting in this release: - - New encoding features - New with this release is the eventName element, which may be used anywhere as a member of att.global to encode a name for an event. - The new eventName element also has membership in several attribute classes associated with named entities, including att.datable to supply a date range for the use of an event's name, and att.typed, allowing it type and subtype attributes. It has also been added to att.editLike, permitting its application in contexts of describing events in an editing process (#2382). - The content model of event has been modified to contain eventName elements without invalidate older ways of labeling events. - The first child of an event element may still be an idno a head element, but modelling of events may now begin instead with eventName or with members of model.pLike (ab or p) or model.labelLike (desc or label). See PR #2483. +

The following changes are particularly worth highlighting in this release: + + New encoding features + New with this release is the eventName element, + which may be used to encode names of events either in + general transcribed text, or particularly in the + event element. (#2382). + The content model of event has been modified to + allow eventName (but it still allows older ways of + labeling events). See PR #2483. - - - - - - + + Changes to content models + The datatype of the class attribute on attRef has been changed from teidata.word to teidata.name (#2276). @@ -80,6 +83,7 @@ See the file COPYING.txt for details Improvements of prose and examples + Several Japanese translations have been added to element, attribute, and class specifications (PRs #2448, #2449, and #2461). From a4cb894b59b3bda01ac800d161d5df76417f2316 Mon Sep 17 00:00:00 2001 From: ebeshero Date: Mon, 13 Nov 2023 22:03:54 -0500 Subject: [PATCH 05/28] modified feature on eventName in release notes --- P5/ReleaseNotes/readme-4.7.0.xml | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/P5/ReleaseNotes/readme-4.7.0.xml b/P5/ReleaseNotes/readme-4.7.0.xml index 5f7a29804e..d323e4a595 100644 --- a/P5/ReleaseNotes/readme-4.7.0.xml +++ b/P5/ReleaseNotes/readme-4.7.0.xml @@ -36,13 +36,17 @@ See the file COPYING.txt for details

The following changes are particularly worth highlighting in this release: New encoding features New with this release is the eventName element, which may be used to encode - names of events either in general transcribed text, or particularly in the - event element. (event element. The new eventName element also has membership in several attribute classes associated with named entities, including att.datable to supply a date range for the use of an event's name, and att.typed, allowing it type and subtype attributes. It has also been added to att.editLike, permitting its application in contexts of describing events in an editing process (#2382). + The content model of event has been modified to contain eventName elements without invalidating older ways of labeling events. The first child of an event element may still be an idno a head element, but modelling of events may now begin instead with eventName or with members of model.pLike (ab or p) or model.labelLike (desc or label). See PR #2483. + + + The content model of event has been modified to allow eventName (but it still allows older ways of labeling events). See PR #2483. - + From 5f0ea86c5d83abcd7c5e2c4ec14da5ca64d39707 Mon Sep 17 00:00:00 2001 From: ebeshero Date: Mon, 13 Nov 2023 22:06:04 -0500 Subject: [PATCH 06/28] trimmed a bit release notes --- P5/ReleaseNotes/readme-4.7.0.xml | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/P5/ReleaseNotes/readme-4.7.0.xml b/P5/ReleaseNotes/readme-4.7.0.xml index d323e4a595..e6c446d727 100644 --- a/P5/ReleaseNotes/readme-4.7.0.xml +++ b/P5/ReleaseNotes/readme-4.7.0.xml @@ -39,14 +39,8 @@ See the file COPYING.txt for details names of events in general transcribed text, or in the event element. The new eventName element also has membership in several attribute classes associated with named entities, including att.datable to supply a date range for the use of an event's name, and att.typed, allowing it type and subtype attributes. It has also been added to att.editLike, permitting its application in contexts of describing events in an editing process (#2382). - The content model of event has been modified to contain eventName elements without invalidating older ways of labeling events. The first child of an event element may still be an idno a head element, but modelling of events may now begin instead with eventName or with members of model.pLike (ab or p) or model.labelLike (desc or label). See PR #2483. - - + The content model of event has been modified to contain eventName elements, but still allows older ways of labeling events. See PR #2483. - The content model of event has been modified to allow eventName - (but it still allows older ways of labeling events). See PR #2483. - From 5b03f67f68b32d5e2c5166b89422eef6286a6354 Mon Sep 17 00:00:00 2001 From: ebeshero Date: Mon, 13 Nov 2023 22:20:01 -0500 Subject: [PATCH 07/28] modified comments on eventName --- P5/ReleaseNotes/readme-4.7.0.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/P5/ReleaseNotes/readme-4.7.0.xml b/P5/ReleaseNotes/readme-4.7.0.xml index e6c446d727..950b9de583 100644 --- a/P5/ReleaseNotes/readme-4.7.0.xml +++ b/P5/ReleaseNotes/readme-4.7.0.xml @@ -37,7 +37,7 @@ See the file COPYING.txt for details New encoding features New with this release is the eventName element, which may be used to encode names of events in general transcribed text, or in the - event element. The new eventName element also has membership in several attribute classes associated with named entities, including att.datable to supply a date range for the use of an event's name, and att.typed, allowing it type and subtype attributes. It has also been added to att.editLike, permitting its application in contexts of describing events in an editing process (event element. The new eventName element also has membership in several attribute classes associated with named entities, including att.datable to supply a date range for the use of an event's name, and att.typed, allowing it type and subtype attributes. It has also been added to att.editLike, giving it the evidence attribute (#2382). The content model of event has been modified to contain eventName elements, but still allows older ways of labeling events. See PR #2483. From b1da8c7bb33c6b17f4f174dd65bafd84a71a15d4 Mon Sep 17 00:00:00 2001 From: ebeshero Date: Wed, 15 Nov 2023 01:58:18 -0500 Subject: [PATCH 08/28] complete draft of 4.7.0 release notes --- P5/ReleaseNotes/readme-4.7.0.xml | 116 ++++++++++++++++++++++--------- 1 file changed, 84 insertions(+), 32 deletions(-) diff --git a/P5/ReleaseNotes/readme-4.7.0.xml b/P5/ReleaseNotes/readme-4.7.0.xml index 950b9de583..363f2b85f4 100644 --- a/P5/ReleaseNotes/readme-4.7.0.xml +++ b/P5/ReleaseNotes/readme-4.7.0.xml @@ -36,22 +36,26 @@ See the file COPYING.txt for details

The following changes are particularly worth highlighting in this release: New encoding features New with this release is the eventName element, which may be used to encode - names of events in general transcribed text, or in the - event element. The new eventName element also has membership in several attribute classes associated with named entities, including att.datable to supply a date range for the use of an event's name, and att.typed, allowing it type and subtype attributes. It has also been added to att.editLike, giving it the evidence attribute (#2382). - The content model of event has been modified to contain eventName elements, but still allows older ways of labeling events. See PR #2483. - - - - - Deprecations - The re element in the dictionaries module is now deprecated, since its - model and use are identical to entry with type = "related" #2456. + names of events in general transcribed text, or in the event element. The new + eventName element also has membership in several attribute classes associated + with named entities, including att.datable to supply a date + range for the use of an event's name, and att.typed, allowing + it type and subtype attributes. It has also been added to att.editLike, giving it the evidence attribute (#2382). + The content model of event has been modified to contain eventName + elements, but still allows older ways of labeling events. See PR #2483. + The taxonomy and category elements are now added to att.datacat (#2419). Changes to content models + The content model of content has been changed to permit only one child + element from model.contentPart (#2381). At the request of the Manuscript SIG, the content model of additional is now more flexible, permitting any alternation of model.pLike (p or ab) with zero or more of adminInfo, @@ -63,40 +67,62 @@ See the file COPYING.txt for details order to prevent the possibility of elements being included in the specification for an attribute’s datatype (PR #2443 and #2426). - + A scheme attribute is now usually optional on constraintSpec, except for the case of a constraintSpec with mode = "add" or mode = "replace" (PR #2453 and #2261). + + #2426. The datatype of the class attribute on attRef has been changed from teidata.word to teidata.name (#2276). - + - + + -->

With these release notes we are beginning a practice of documenting changes to content models that could invalidate ODD customizations in TEI projects if they are working with the current release of these TEI Guidelines. Those maintaining ODD customizations of the TEI may want to be aware of the following changes and adapt your ODD files accordingly. - ODD-breaking changes - + ODD-breaking changes and deprecation + The calendar attribute has been removed from att.datable because it is supposed to designate information about a date + represented in an element’s contents and not be applied to elements that do not contain + dates. To clarify its intended usage, calendar has been moved to a new class, + att.calendarSystem, and its use is now deprecated on many + elements. The calendar attribute is now properly applied only to + date, time, origDate, and docDate. See #2045.

Improvements of prose and examples - + The title of the Guidelines section 2.2.8 has been changed to more accurately + reflect its content (2415). + Several revisions were applied to the explanation of TEI XPointer Schemas in the + Guidelines section 16.2.4 (#2083). + A new example was added for langKnown (2139). + The examples for use of the key attribute are updated and a source + attribution corrected (#2144). Several Japanese translations have been added to element, attribute, and class specifications (PRs #2448, #2449, and #2461). - + Inconsistencies have been corrected in initial capitalization and initial spacing of + the French descriptions in element specifications (#2486) + Descriptions of the ident and usage attributes on the + language element have been improved (#2447). Housekeeping - + Bugs have been corrected in the processing of Guidelines release notes to HTML in + building the TEI Guidelines (#2070). + The version P5 is now properly represented in footers and headings of the + published TEI Guidelines on the web (#2413). + Bookmark links on examples in the Guidelines now feature mouseover text (#2137). -

@@ -133,9 +158,36 @@ See the file COPYING.txt for details

Highlights of this release include: - + Attributes shown on the Guidelines element specification pages are now formatted as + a vertical nested list to improve their legibility (Stylesheets #592). + A bug in Stylesheets ODD processing that had produced output files with multiple + superfluous filename extensions has now been corrected (Stylehsheets 543 and + #2489). + A serious problem in the processing of ns attributes in ODD + customizations has been fixed (Stylesheets #424). + The Guidelines now output the sch: prefix consistently when representing elements in + the Schematron namespace (Stylesheets #529) + A bug has been fixed in the ODD processing of more than one anyElement in a + content model so that it no longer generates an invalid Relax NG output (Stylesheets + #631). + The xml:id on list elements is now properly being translated to + an HTML id attribute in HTML list container elements (Stylesheets #616 and PR #617). + The teitohtml stylesheet now properly highlights val and tag + elements in HTML output (#567). + Improvements and bug corrections have been applied to the docx to tei conversion + (Stylesheets #524, #610, and PR #634).

From e21ff17ec199fe1e976a39f86b7ae217d8419f7f Mon Sep 17 00:00:00 2001 From: martinascholger Date: Wed, 15 Nov 2023 11:57:37 +0100 Subject: [PATCH 09/28] members updated --- P5/Source/Guidelines/en/FM1-IntroductoryNote.xml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/P5/Source/Guidelines/en/FM1-IntroductoryNote.xml b/P5/Source/Guidelines/en/FM1-IntroductoryNote.xml index f07b2a8fb9..07464a05bb 100644 --- a/P5/Source/Guidelines/en/FM1-IntroductoryNote.xml +++ b/P5/Source/Guidelines/en/FM1-IntroductoryNote.xml @@ -42,7 +42,7 @@ $Id$ 2012–2015: Elena Pierazzo (King's College London / Université Stendhal-Grenoble 3) 2016–2017: Michelle Dalmau (Indiana University) 2018–2021: Kathryn Tomasek (Wheaton College) - 2022: Diane K. Jakacki (Bucknell University) + 2022-2023: Diane K. Jakacki (Bucknell University) @@ -53,6 +53,7 @@ $Id$ 2012–2014: James Cummings (University of Oxford) 2015–2017: Hugh Cayless (Duke University) 2018–2022: Martina Scholger (University of Graz) + 2023: Elisa Beshero-Bondar (Penn State Erie, The Behrend College) @@ -72,7 +73,7 @@ $Id$ 2011–2012: Piotr Bański (University of Warsaw) 2010–2013: Brett Barney (University of Nebraska) 2013–2023: Syd Bauman (Brown University / Northeastern University) - 2021–2022: Helena Bermúdez Sabel (Université de Neuchâtel) + 2021–2025: Helena Bermúdez Sabel (Université de Neuchâtel / JinnTec) 2016–2024: Elisa Beshero-Bondar (University of Pittsburgh at Greensburg / Penn State Erie, The Behrend College) 2022: Elli Bleeker (Huygens Institute for the History of the Netherlands) 2019–2020: Vanessa Bigot Juloux (Ecole Pratique des Hautes Etudes / Paris Sciences et Lettres / Andrews University, Michigan) @@ -102,6 +103,7 @@ $Id$ 2002: Martin Mueller (Northwestern University) 2013–2014, 2016–2019: Elli Mylonas (Brown University) 2010–2011: Julianne Nyhan (University of Trier / University College London) + 2023-2025: Patricia O Connor (Independent Researcher) 2008–2011: Elena Pierazzo (King's College London) 2006–2007, 2009–2010: Dot Porter (University of Kentucky / Digital Humanities Observatory / Indiana University) 2002–2003: Merillee Proffitt (Research Libraries Group) @@ -117,6 +119,7 @@ $Id$ 2004–2005: Natasha Smith (University of North Carolina at Chapel Hill) 2014–2022: Peter Stadler (Carl-Maria-von-Weber-Gesamtausgabe / University of Paderborn) 2017–2019: Sarah Stanley (Florida State University) + 2023: Joey Takeda (Digital Humanities Innovation Lab, Simon Fraser University) 2008–2009: Manfred Thaller (University of Cologne) 2006–2007: Conal Tuohy (Victoria University of Wellington) 2016–2024: Magdalena Turska (eXist Solutions / University of Oxford) @@ -167,6 +170,9 @@ these meetings were generously hosted by the following institutions: Short virtual meeting (May 2021) Short virtual meeting (October 2021) Short virtual (April 2022) + Newcastle University (September 2022) + University of Guelph (May 2023) + Paderborn University (September 2023)

During the production of TEI P5, the Council chartered a number From 99935d48607ec2f499b462c19fe6393b987ed91b Mon Sep 17 00:00:00 2001 From: ebeshero Date: Wed, 15 Nov 2023 22:30:20 -0500 Subject: [PATCH 10/28] spot correction to 4.7 readme --- P5/ReleaseNotes/readme-4.7.0.xml | 1 - 1 file changed, 1 deletion(-) diff --git a/P5/ReleaseNotes/readme-4.7.0.xml b/P5/ReleaseNotes/readme-4.7.0.xml index 363f2b85f4..f19c3881ba 100644 --- a/P5/ReleaseNotes/readme-4.7.0.xml +++ b/P5/ReleaseNotes/readme-4.7.0.xml @@ -73,7 +73,6 @@ See the file COPYING.txt for details mode = "replace" (PR #2453 and #2261). - #2426. The datatype of the class attribute on attRef has been changed from teidata.word to teidata.name (#2276). From a324e9f51ea63934aac3fc307ae6a50d3ad117e7 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Thu, 16 Nov 2023 00:03:49 -0500 Subject: [PATCH 11/28] tweaks to README --- P5/ReleaseNotes/readme-4.7.0.xml | 54 +++++++++++++++----------------- 1 file changed, 25 insertions(+), 29 deletions(-) diff --git a/P5/ReleaseNotes/readme-4.7.0.xml b/P5/ReleaseNotes/readme-4.7.0.xml index f19c3881ba..53dddf4140 100644 --- a/P5/ReleaseNotes/readme-4.7.0.xml +++ b/P5/ReleaseNotes/readme-4.7.0.xml @@ -33,14 +33,16 @@ See the file COPYING.txt for details feature requests or bugs reported by the TEI community using the GitHub tracking system. A full list of the issues resolved in the course of this release cycle may be found under the 4.7.0 milestone.

-

The following changes are particularly worth highlighting in this release: +

The following changes are particularly worth highlighting in this release: + + New encoding features New with this release is the eventName element, which may be used to encode names of events in general transcribed text, or in the event element. The new eventName element also has membership in several attribute classes associated with named entities, including att.datable to supply a date range for the use of an event's name, and att.typed, allowing - it type and subtype attributes. It has also been added to type and subtype attributes. It is also a memeber of att.editLike, giving it the evidence attribute (#2382). The content model of event has been modified to contain eventName @@ -49,8 +51,8 @@ See the file COPYING.txt for details The taxonomy and category elements are now added to att.datacat (#2419). - + Changes to content models The content model of content has been changed to permit only one child @@ -58,7 +60,7 @@ See the file COPYING.txt for details target="https://github.com/TEIC/TEI/issues/2381">#2381). At the request of the Manuscript SIG, the content model of additional is now more flexible, permitting any alternation of model.pLike - (p or ab) with zero or more of adminInfo, + (p or ab) instead of zero or one each of adminInfo, surrogates, or listBibl (#2195). The content model of revisionDesc now permits multiple listChange @@ -67,12 +69,11 @@ See the file COPYING.txt for details order to prevent the possibility of elements being included in the specification for an attribute’s datatype (PR #2443 and #2426). - - A scheme attribute is now usually optional on constraintSpec, - except for the case of a constraintSpec with mode = "add" or - mode = "replace" (PR + A scheme attribute is now optional on a constraintSpec + with a mode of either change or + delete (it is still required when mode + is add, replace, or unspecified — see PR #2453 and #2261). - The datatype of the class attribute on attRef has been changed from teidata.word to teidata.name (#2276). @@ -83,17 +84,17 @@ See the file COPYING.txt for details -->

-

With these release notes we are beginning a practice of documenting changes to content - models that could invalidate ODD customizations in TEI projects if they are working with the +

With these release notes we are beginning a practice of documenting changes that could + invalidate ODD customizations in TEI projects if they are working with the current release of these TEI Guidelines. Those maintaining ODD customizations of the TEI may want to be aware of the following changes and adapt your ODD files accordingly. ODD-breaking changes and deprecation The calendar attribute has been removed from att.datable because it is supposed to designate information about a date - represented in an element’s contents and not be applied to elements that do not contain + represented in an element’s contents, and thus should not be applied to elements that do not contain dates. To clarify its intended usage, calendar has been moved to a new class, att.calendarSystem, and its use is now deprecated on many - elements. The calendar attribute is now properly applied only to + elements. The calendar attribute is now properly available only on date, time, origDate, and docDate. See #2045. @@ -103,12 +104,12 @@ See the file COPYING.txt for details Improvements of prose and examples The title of the Guidelines section 2.2.8 has been changed to more accurately reflect its content (2415). + >#2415). Several revisions were applied to the explanation of TEI XPointer Schemas in the Guidelines section 16.2.4 (#2083). A new example was added for langKnown (2139). + target="https://github.com/TEIC/TEI/issues/2139">#2139). The examples for use of the key attribute are updated and a source attribution corrected (#2144). @@ -132,17 +133,13 @@ See the file COPYING.txt for details --> Housekeeping - Bugs have been corrected in the processing of Guidelines release notes to HTML in - building the TEI Guidelines (#2070). + Bugs have been corrected in the processing of Guidelines release notes to HTML + (#2070). The version P5 is now properly represented in footers and headings of the published TEI Guidelines on the web (#2413). Bookmark links on examples in the Guidelines now feature mouseover text (#2137). - - -

@@ -157,15 +154,15 @@ See the file COPYING.txt for details

Highlights of this release include: - Attributes shown on the Guidelines element specification pages are now formatted as - a vertical nested list to improve their legibility (Stylesheets #592). + Attributes shown on element and class specification pages are now formatted as + a vertical nested list to improve legibility + (PR + #619 and + #2489). A bug in Stylesheets ODD processing that had produced output files with multiple superfluous filename extensions has now been corrected (Stylehsheets 543 and - #2489). - - + target="https://github.com/TEIC/Stylesheets/issues/543">Stylehsheets 543). A serious problem in the processing of ns attributes in ODD customizations has been fixed (Stylesheets #424). @@ -187,7 +184,6 @@ See the file COPYING.txt for details (Stylesheets #524, #610, and PR #634). -

From 486847356cb23ecf9f970f2c5d654faaf2cbb6d4 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Thu, 16 Nov 2023 06:55:46 -0500 Subject: [PATCH 12/28] fix an erroneous comment (#2505) --- P5/Source/Specs/constraintSpec.xml | 37 +++++++++++++++--------------- 1 file changed, 19 insertions(+), 18 deletions(-) diff --git a/P5/Source/Specs/constraintSpec.xml b/P5/Source/Specs/constraintSpec.xml index 5acc1a8cbf..ca2aad8f6f 100644 --- a/P5/Source/Specs/constraintSpec.xml +++ b/P5/Source/Specs/constraintSpec.xml @@ -9,8 +9,7 @@ $Id$ constraint on schema - contains a formal constraint, typically expressed in a rule-based schema language, to which a construct must conform in order to be considered valid + contains a formal constraint, typically expressed in a rule-based schema language, to which a construct must conform in order to be considered valid @@ -58,7 +57,7 @@ $Id$ Relationship between scheme attribute and contents: ISO Schematron - Rules + Rules in the ISO Schematron language must be inside a constraintSpec with the value 'schematron' on the scheme attribute @@ -85,19 +84,21 @@ $Id$ supplies the name of the language in which the constraints are defined - - - The @scheme attribute of <constraintSpec> is required when the @mode is . - - + + + The @scheme attribute of <constraintSpec> is required when the @mode is . + + @@ -110,13 +111,13 @@ $Id$ within constraintSpec. Thus the value schematron is used to indicate that ISO Schematron is used within the constraintSpec.

-

The scheme attribute is required when the value - of mode is add or - replace. The scheme attribute is - permitted when the value of mode is - delete, but these Guidelines make no reccomendation - for what a processor should do if its value does not match - that of the constraintSpec being deleted.

+

The scheme attribute is required when the value + of mode is add or + replace. The scheme attribute is + permitted when the value of mode is + delete, but these Guidelines make no reccomendation + for what a processor should do if its value does not match + that of the constraintSpec being deleted.

 From cdeeedfed9ff1ee4b424f40335d1e648e7856faa Mon Sep 17 00:00:00 2001 From: Joey Takeda Date: Thu, 16 Nov 2023 05:23:08 -0800 Subject: [PATCH 13/28] Resolves #2465 (#2467) * Deletes deprecated .travis.yml file * Removes the Slack notifier action from the test action --- .github/workflows/test.yml | 11 +---------- .travis.yml | 24 ------------------------ 2 files changed, 1 insertion(+), 34 deletions(-) delete mode 100644 .travis.yml diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml index b7583a5eda..0cbd6e1456 100644 --- a/.github/workflows/test.yml +++ b/.github/workflows/test.yml @@ -34,13 +34,4 @@ jobs: - name: Run tests from the Test directory run: | cd P5 - make clean validate test XSL=${GITHUB_WORKSPACE}/Stylesheets - - - name: Slack Notification - if: always() - continue-on-error: true - uses: rtCamp/action-slack-notify@v2 - env: - SLACK_WEBHOOK: ${{ secrets.SLACK_WEBHOOK }} - SLACK_COLOR: ${{ job.status }} - MSG_MINIMAL: commit,actions url + make clean validate test XSL=${GITHUB_WORKSPACE}/Stylesheets \ No newline at end of file diff --git a/.travis.yml b/.travis.yml deleted file mode 100644 index 7ed4394c10..0000000000 --- a/.travis.yml +++ /dev/null @@ -1,24 +0,0 @@ -sudo: required - -language: java - -services: - - docker - -# before we can run the docker image for the tests, we need to -# * pull the docker image -# * get the current VERSION file of the stylesheets from the artifacts server -# * get the latest stylesheets zip file from the artifacts server -# * install the stylesheets within our working dir in a dedicated sub dir -before_install: - - docker pull teic/jenkins:dev - - curl https://jenkins.tei-c.org/view/TEI%20dev/job/Stylesheets-dev/lastSuccessfulBuild/artifact/dist/doc/tei-xsl/VERSION -o XSLVERSION - - curl https://jenkins.tei-c.org/view/TEI%20dev/job/Stylesheets-dev/lastStableBuild/artifact/tei-xsl-`head -1 XSLVERSION`.zip -o stylesheets.zip - - mkdir stylesheets - - unzip stylesheets.zip -d stylesheets - -script: - - docker run --rm -w /var/tei/P5 -it -v `pwd`:/var/tei -v $TRAVIS_BUILD_DIR/stylesheets/xml/tei/stylesheet:/usr/share/xml/tei/stylesheet -u $UID --entrypoint "make" teic/jenkins:dev clean validate test - -notifications: - slack: tei-c:3IFCBSmTvNx3j1GUMDWS9Dom \ No newline at end of file From 36d4d622b1e6845ba72e8c44fffe8a0ab789bd40 Mon Sep 17 00:00:00 2001 From: raffazizzi Date: Thu, 16 Nov 2023 09:32:10 -0500 Subject: [PATCH 14/28] confirmed version number --- P5/VERSION | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/P5/VERSION b/P5/VERSION index 81107396d2..f6cdf40983 100644 --- a/P5/VERSION +++ b/P5/VERSION @@ -1 +1 @@ -4.7.0a +4.7.0 From 8beda2ec5a96a1b29f7767c9d66f175c7db35f83 Mon Sep 17 00:00:00 2001 From: raffazizzi Date: Thu, 16 Nov 2023 10:43:02 -0500 Subject: [PATCH 15/28] fixed typos --- P5/ReleaseNotes/readme-4.7.0.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/P5/ReleaseNotes/readme-4.7.0.xml b/P5/ReleaseNotes/readme-4.7.0.xml index 53dddf4140..4695bc7bbb 100644 --- a/P5/ReleaseNotes/readme-4.7.0.xml +++ b/P5/ReleaseNotes/readme-4.7.0.xml @@ -41,8 +41,8 @@ See the file COPYING.txt for details names of events in general transcribed text, or in the event element. The new eventName element also has membership in several attribute classes associated with named entities, including att.datable to supply a date - range for the use of an event's name, and att.typed, allowing - it type and subtype attributes. It is also a memeber of att.typed, allowing + it type and subtype attributes. It is also a member of att.editLike, giving it the evidence attribute (#2382). The content model of event has been modified to contain eventName From 9cbcf5740c27744992db83569e146ff98ba2f888 Mon Sep 17 00:00:00 2001 From: "Hugh A. Cayless" Date: Thu, 16 Nov 2023 10:45:21 -0500 Subject: [PATCH 16/28] Add codename. --- P5/ReleaseNotes/readme-4.7.0.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/P5/ReleaseNotes/readme-4.7.0.xml b/P5/ReleaseNotes/readme-4.7.0.xml index 53dddf4140..701e5778eb 100644 --- a/P5/ReleaseNotes/readme-4.7.0.xml +++ b/P5/ReleaseNotes/readme-4.7.0.xml @@ -27,7 +27,7 @@ See the file COPYING.txt for details -

Release 4.7.0 is codenamed ????.

+

Release 4.7.0 is codenamed in nova fert animus.

This release introduces new features and resolves a number of issues raised by the TEI community. As always, the majority of these changes and corrections are a consequence of feature requests or bugs reported by the TEI community using the GitHub tracking system. A From d522c67af3852a87cfa5b688d1326abc0fc91b49 Mon Sep 17 00:00:00 2001 From: raffazizzi Date: Thu, 16 Nov 2023 16:29:06 -0500 Subject: [PATCH 17/28] upped version --- P5/VERSION | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/P5/VERSION b/P5/VERSION index f6cdf40983..90a8eb5ce3 100644 --- a/P5/VERSION +++ b/P5/VERSION @@ -1 +1 @@ -4.7.0 +4.8.0a From ed73010714e3b0981d9bd85b346dce97c5b5cd38 Mon Sep 17 00:00:00 2001 From: raffazizzi Date: Fri, 17 Nov 2023 13:45:46 -0500 Subject: [PATCH 18/28] fixed broken links in 4.7.0 release notes --- P5/ReleaseNotes/readme-4.7.0.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/P5/ReleaseNotes/readme-4.7.0.xml b/P5/ReleaseNotes/readme-4.7.0.xml index 7e4e7d717a..bbbefa8104 100644 --- a/P5/ReleaseNotes/readme-4.7.0.xml +++ b/P5/ReleaseNotes/readme-4.7.0.xml @@ -32,7 +32,7 @@ See the file COPYING.txt for details community. As always, the majority of these changes and corrections are a consequence of feature requests or bugs reported by the TEI community using the GitHub tracking system. A full list of the issues resolved in the course of this release cycle may be found under the - 4.7.0 milestone.

+ 4.7.0 milestone.

The following changes are particularly worth highlighting in this release: @@ -49,7 +49,7 @@ See the file COPYING.txt for details elements, but still allows older ways of labeling events. See PR #2483. The taxonomy and category elements are now added to att.datacat (att.datcat (#2419). @@ -149,7 +149,7 @@ See the file COPYING.txt for details conversions). The Stylesheets are maintained separately from the Guidelines at https://github.com/TEIC/Stylesheets. A full list of the issues resolved in the course of this release cycle may be found under the - 7.56.0 + 7.56.0 milestone.

Highlights of this release include: From 15e10e0275273d0b1bc6a36d58d34891da2826d5 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Sun, 26 Nov 2023 08:28:39 -0500 Subject: [PATCH 19/28] add a missing Oxford comma --- P5/Source/Guidelines/en/TS-TranscriptionsofSpeech.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/P5/Source/Guidelines/en/TS-TranscriptionsofSpeech.xml b/P5/Source/Guidelines/en/TS-TranscriptionsofSpeech.xml index 4126156226..c6385f2a2e 100644 --- a/P5/Source/Guidelines/en/TS-TranscriptionsofSpeech.xml +++ b/P5/Source/Guidelines/en/TS-TranscriptionsofSpeech.xml @@ -500,7 +500,7 @@ section .

An utterance may contain either running text, or text within which other basic structural elements are nested. Where such nesting occurs, the who attribute is considered to be inherited for the -elements pause, vocal, shift and +elements pause, vocal, shift, and kinesic; that is, a pause or shift (etc.) within an utterance is regarded as being produced by that speaker only, while a pause between utterances applies to all speakers. @@ -1472,4 +1472,4 @@ to divide a transcribed text up into meaningful analytic sections. - \ No newline at end of file + From a1ed62ac03a681adc6971810cf5e89f8d05f712b Mon Sep 17 00:00:00 2001 From: sabine seifert Date: Wed, 29 Nov 2023 15:49:47 +0100 Subject: [PATCH 20/28] Update definition, closes #2476 --- P5/Source/Specs/surface.xml | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/P5/Source/Specs/surface.xml b/P5/Source/Specs/surface.xml index d07cce59b3..70ee7aa2f3 100644 --- a/P5/Source/Specs/surface.xml +++ b/P5/Source/Specs/surface.xml @@ -10,8 +10,7 @@ $Id$ defines a written surface as a two-dimensional coordinate space, optionally grouping one or more graphic representations of -that space, zones of interest within that space, and transcriptions of the - writing within them. +that space, zones of interest within that space, and, when using an embedded transcription approach, transcriptions of the writing within them. 직사각형의 좌표 공간과 그 내부에서 기록 표면부를 정의한다. 수의적으로 그 공간의 하나 이상의 그림 표상과 관심 있는 직사각형 공간을 모아놓는다. define una superficie escrita en coordinadas rectangulares, agrupando opcionalmente una o más representaciones gráficas de ese espacio, y las zonas rectangulares de interés dentro de él. 矩形の座標により、書記の表面を定義する。選択的に、空間や矩形範囲中のひ From 2abbebcf679166bdaac0d696822a9a38571067e0 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Wed, 6 Dec 2023 19:27:36 -0500 Subject: [PATCH 21/28] Fix #2512 --- P5/Source/Specs/att.calendarSystem.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/P5/Source/Specs/att.calendarSystem.xml b/P5/Source/Specs/att.calendarSystem.xml index 36f102e80c..c34014f4d0 100644 --- a/P5/Source/Specs/att.calendarSystem.xml +++ b/P5/Source/Specs/att.calendarSystem.xml @@ -26,7 +26,7 @@ $Id$ - + @calendar indicates one or more From 06ed939a5bfc8fab8e36413497921d7ce1830fe1 Mon Sep 17 00:00:00 2001 From: lb42 Date: Wed, 20 Dec 2023 13:03:31 +0100 Subject: [PATCH 22/28] tweak fr --- Documents/pureODD/howtoChain-fr.xml | 27 ++++++++++++++++----------- 1 file changed, 16 insertions(+), 11 deletions(-) diff --git a/Documents/pureODD/howtoChain-fr.xml b/Documents/pureODD/howtoChain-fr.xml index a202110427..ee985255b2 100644 --- a/Documents/pureODD/howtoChain-fr.xml +++ b/Documents/pureODD/howtoChain-fr.xml @@ -9,7 +9,7 @@ Lou Burnard -

Unpublished draft

+

Published at lb42.github.io

authored from scratch

@@ -40,15 +40,20 @@ Traitement d’un ODD

Regardons d’un peu plus près la manière dont la TEI définit un schéma très léger appelé TEI Bare. Son élément de spécification de schéma commence comme suit : - + xml:lang="en"> + + + + + + + + + + + + +

Aucune attribut source n’est spécifié, ainsi la les déclarations des éléments demandés seront prises dans le fichier courant p5subset.xml.

Notez que cet ODD contient à la fois des références et des spécifications : il continet des références à des modèles (qui peuvent être conçues comme des raccourcis pour des références à des éléments ou des classes, dès lors qu’un module n’est rien d’autre qu’une collection de spécifications d’éléments et de classes) et des spécifications pour deux classes (classSpec), plutôt que des références (classRef). La référence au module tei contenue dans cette spécification icnlue la plupart des classes de la TEI, y compris ces deux classes-là. Un processeur ODD devra alors résoudre les spécifications de classe dupliquées pour les classes att.global et att.fragmentable. La solution requise est indiquée par la valeur de l’attribut mode : si celle-ci est delete alors les deux déclarations seront ignorées, et la classe est supprimée ; si sa valeur est change alors les deux déclarations seront mélangées de sorte que les parties spécification présentes dans la seconde spécification écrasent les premières. Dans ce cas, l’effet sera de supprimer les trois attributs mentionnés.

@@ -135,4 +140,4 @@ - \ No newline at end of file + From 7fbd0db5efdbb0c6ee5e6a055af31337c8c0981e Mon Sep 17 00:00:00 2001 From: lb42 Date: Wed, 20 Dec 2023 13:08:31 +0100 Subject: [PATCH 23/28] fr doc tweak --- Documents/pureODD/howtoChain-fr.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documents/pureODD/howtoChain-fr.xml b/Documents/pureODD/howtoChain-fr.xml index ee985255b2..86df88b3ee 100644 --- a/Documents/pureODD/howtoChain-fr.xml +++ b/Documents/pureODD/howtoChain-fr.xml @@ -6,7 +6,7 @@ Chaînage ODD pour les débutants - Lou Burnard + Lou Burnard et Emmanuel Chateau-Dutier

Published at lb42.github.io

From 1275cdfc90843930abeb78986c928f5128fa07a9 Mon Sep 17 00:00:00 2001 From: Lou Date: Wed, 20 Dec 2023 13:18:12 +0100 Subject: [PATCH 24/28] Update howtoChain-fr.xml --- Documents/pureODD/howtoChain-fr.xml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/Documents/pureODD/howtoChain-fr.xml b/Documents/pureODD/howtoChain-fr.xml index a202110427..5f7e57ff9e 100644 --- a/Documents/pureODD/howtoChain-fr.xml +++ b/Documents/pureODD/howtoChain-fr.xml @@ -6,10 +6,11 @@ Chaînage ODD pour les débutants - Lou Burnard + Lou Burnard et Emmanuel Château-Dutier + -

Unpublished draft

+

Published at lb42.github.io

authored from scratch

@@ -135,4 +136,4 @@ - \ No newline at end of file + From 0bb1c9ee14c8e296747a9b4bc3376dec61d3657a Mon Sep 17 00:00:00 2001 From: Lou Date: Wed, 20 Dec 2023 13:22:06 +0100 Subject: [PATCH 25/28] Update howtoChain-fr.xml --- Documents/pureODD/howtoChain-fr.xml | 26 ++++++++++++++++---------- 1 file changed, 16 insertions(+), 10 deletions(-) diff --git a/Documents/pureODD/howtoChain-fr.xml b/Documents/pureODD/howtoChain-fr.xml index 5f7e57ff9e..4b73552fd1 100644 --- a/Documents/pureODD/howtoChain-fr.xml +++ b/Documents/pureODD/howtoChain-fr.xml @@ -39,17 +39,23 @@
Traitement d’un ODD -

Regardons d’un peu plus près la manière dont la TEI définit un schéma très léger appelé TEI Bare. Son élément de spécification de schéma commence comme suit : Regardons d’un peu plus près la manière dont la TEI définit un schéma très léger appelé TEI Bare. + Son élément de spécification de schéma commence comme suit : - + xml:lang="en"> + + + + + + + + + + + + +

Aucune attribut source n’est spécifié, ainsi la les déclarations des éléments demandés seront prises dans le fichier courant p5subset.xml.

Notez que cet ODD contient à la fois des références et des spécifications : il continet des références à des modèles (qui peuvent être conçues comme des raccourcis pour des références à des éléments ou des classes, dès lors qu’un module n’est rien d’autre qu’une collection de spécifications d’éléments et de classes) et des spécifications pour deux classes (classSpec), plutôt que des références (classRef). La référence au module tei contenue dans cette spécification icnlue la plupart des classes de la TEI, y compris ces deux classes-là. Un processeur ODD devra alors résoudre les spécifications de classe dupliquées pour les classes att.global et att.fragmentable. La solution requise est indiquée par la valeur de l’attribut mode : si celle-ci est delete alors les deux déclarations seront ignorées, et la classe est supprimée ; si sa valeur est change alors les deux déclarations seront mélangées de sorte que les parties spécification présentes dans la seconde spécification écrasent les premières. Dans ce cas, l’effet sera de supprimer les trois attributs mentionnés.

From 465a7779b47e6f88b0e1077a1a454669480ffd0b Mon Sep 17 00:00:00 2001 From: Lou Date: Wed, 20 Dec 2023 16:48:56 +0000 Subject: [PATCH 26/28] Update howtoChain.xml --- Documents/pureODD/howtoChain.xml | 37 ++++++++++++++++---------------- 1 file changed, 19 insertions(+), 18 deletions(-) diff --git a/Documents/pureODD/howtoChain.xml b/Documents/pureODD/howtoChain.xml index 9e384e5a7d..c4f2bb0423 100644 --- a/Documents/pureODD/howtoChain.xml +++ b/Documents/pureODD/howtoChain.xml @@ -9,13 +9,14 @@ Lou Burnard -

Discussion draft

+

As published on lb42.github.io

authored from scratch

 + Minor changes for publication on lb42.github.io Expanded and announced on TEI-L Uploaded for Council review Drafted first part on train from Paris to La Souterraine; then lost @@ -73,22 +74,21 @@

Let's look more closely at the way the TEI defines a very light weight schema called TEI Bare. Its schema specification element begins like this: - - - - - - - - - - - - - - - + + + + + + + + + + + + + +

No source is specified, so declarations for the elements requested here will be taken from the current p5subset.xml.

@@ -251,7 +251,8 @@ the value for the source attribute on the schemaSpec defining our ODD. We could do the same thing (though I don't recommend it) even at the level of individual elements, by specifying a different version as source for an - elementSpec.

And just to make life a little simpler, there is an + elementSpec.

+

And just to make life a little simpler, there is an officially recognized short cut built into the current ODD processing stylesheets: instead of the lengthy URL above, we could simply say tei:3.0.0. For example, supposing that for some strange reason we don't want to add the current From 6b749a2bb6ed22b5e6a921d475040307a463ded8 Mon Sep 17 00:00:00 2001 From: Lou Date: Wed, 20 Dec 2023 17:14:22 +0000 Subject: [PATCH 27/28] Update howtoChain.xml --- Documents/pureODD/howtoChain.xml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Documents/pureODD/howtoChain.xml b/Documents/pureODD/howtoChain.xml index c4f2bb0423..fb81c2c5f4 100644 --- a/Documents/pureODD/howtoChain.xml +++ b/Documents/pureODD/howtoChain.xml @@ -59,14 +59,14 @@ in the current source tree. And one with the value http://example.com/superODDs/anotherSubset.xml will go looking for it at the URL indicated.

-

It's important to understand that the resource indicated by the sources +

It's important to understand that the resource indicated by the source attribute must contain complete and explicit specification elements: elementSpec rather than elementRef, classSpec rather than classRef and so on. It may of course contain other TEI elements, but these will be ignored entirely in the construction of a schema. A file called p5subset.xml, provided as part of every TEI release, is an example of such a resource: it contains specifications for every - single TEI element, class, macro, and datatype, but nothing else much. If the - source parameter is not supplied, the most recently available version of this + single TEI element, class, macro, and datatype, but nothing else much. If a value for the + source attribute is not specified, the most recently available version of this file is what will be used during the processing of an ODD.

@@ -98,8 +98,8 @@ specifications for two classes (classSpec), rather than references (classRef). The reference to the module tei brings with it specifications for most TEI classes, including these two. An ODD processor will therefore - have to resolve duplicate class specifications for the classes att.global - and att.fragmentable. The required resolution is indicated by the value of + have to deal with duplicate class specifications for the classes att.global + and att.fragmentable. The resolution method required is indicated by the value of the mode attribute: if this is delete then both declarations are to be ignored, and the class is therefore suppressed; if it is change then the two declarations are to be merged, with any part of it present in the second specification @@ -107,7 +107,7 @@ attributes mentioned.

If you'd like to check that this ODD does what you expect, and you have oXygen installed with a recent version of the TEI Frameworks, just download the file - tei_bare.odd, and tell oXygen to apply the predefined transformation + tei_bare.odd (you can get it from the TEI github repo), and tell oXygen to apply the predefined transformation TEI ODD to HTML to it. This will produce a mini-manual for the TEI Bare customization in HTML format, near the beginning of which you should see a list of the elements the schema contains. From f4ba6a006e8ae969101cf3f6f02d7bf8c1d96ae3 Mon Sep 17 00:00:00 2001 From: lou burnard Date: Wed, 20 Dec 2023 18:14:57 +0000 Subject: [PATCH 28/28] add section missing from fr tuto --- Documents/pureODD/howtoChain-fr.xml | 157 +++++++++++++++------------- 1 file changed, 84 insertions(+), 73 deletions(-) diff --git a/Documents/pureODD/howtoChain-fr.xml b/Documents/pureODD/howtoChain-fr.xml index 0e8bf85eea..84352cf56d 100644 --- a/Documents/pureODD/howtoChain-fr.xml +++ b/Documents/pureODD/howtoChain-fr.xml @@ -6,7 +6,6 @@ Chaînage ODD pour les débutants - Lou Burnard et Emmanuel Chateau-Dutier @@ -18,6 +17,7 @@ + Added last section missing from earlier translation French translation by Emmanuel Château Uploaded for Council review Drafted first part on train from Paris to La Souterraine;l then lost half of it by shutting lid in a hurry without saving first : doh. @@ -28,10 +28,10 @@

À quoi ça sert ?

Ce court guide est destiné à expliquer le mécanisme du ODD chaining. Un fichier ODD spécifie une utilisation de la TEI en sélectionnant des éléments ou des attributs particuliers, etc. dans l’ensemble de la TEI. Mais il est également possible de rafiner encore plus cette spécification en faisant dériver votre ODD les uns des autres. En principe, vous pouvez chaîner des ODDs ensemble de cette manière autant que vous le souhaitez. Vous pouvez employer cette fonctionnalité de différentes manières : - vous pouvez ajouter des restrictions additionnelles à un ODD existant, par exemple pour modifier la liste des valeurs possibles d’un attribut - vous pouvez réduire le sous-ensemble d’éléments produits par un ODD existant - vous pouvez ajouter de nouveaux éléments ou des modules à un ODD existant -

+vous pouvez ajouter des restrictions additionnelles à un ODD existant, par exemple pour modifier la liste des valeurs possibles d’un attribut +vous pouvez réduire le sous-ensemble d’éléments produits par un ODD existant +vous pouvez ajouter de nouveaux éléments ou des modules à un ODD existant +

Comment ça marche ? @@ -40,27 +40,26 @@
Traitement d’un ODD -

Regardons d’un peu plus près la manière dont la TEI définit un schéma très léger appelé TEI Bare. - Son élément de spécification de schéma commence comme suit : - - - - - - - - - - - - - -

+

Regardons d’un peu plus près la manière dont la TEI définit un schéma très léger appelé TEI Bare. + Son élément de spécification de schéma commence comme suit : + + + + + + + + + + + + + +

Aucune attribut source n’est spécifié, ainsi la les déclarations des éléments demandés seront prises dans le fichier courant p5subset.xml.

-

Notez que cet ODD contient à la fois des références et des spécifications : il continet des références à des modèles (qui peuvent être conçues comme des raccourcis pour des références à des éléments ou des classes, dès lors qu’un module n’est rien d’autre qu’une collection de spécifications d’éléments et de classes) et des spécifications pour deux classes (classSpec), plutôt que des références (classRef). La référence au module tei contenue dans cette spécification icnlue la plupart des classes de la TEI, y compris ces deux classes-là. Un processeur ODD devra alors résoudre les spécifications de classe dupliquées pour les classes att.global et att.fragmentable. La solution requise est indiquée par la valeur de l’attribut mode : si celle-ci est delete alors les deux déclarations seront ignorées, et la classe est supprimée ; si sa valeur est change alors les deux déclarations seront mélangées de sorte que les parties spécification présentes dans la seconde spécification écrasent les premières. Dans ce cas, l’effet sera de supprimer les trois attributs mentionnés.

-

Vous pouvez vérifier que cet ODD fait bien ce que vous attendez, si vous avez une d’oXygen installée avec une version récente du TEI Frameworks, téléchargez simplement le fichier tei_bare.odd, et demandez à oXygen de lui appliquer la transformation prédéfinie TEI ODD to HTML. Cela va produire un mini-manuel pour la personnalisation TEI Bare au format HTML au début de laquelle vous pourrez consulter la liste des éléments que le schéma contient.

Vous pouvez alors vérifier que les modifications de la classe d’attribut att.global indiquées ci-dessus ont bien été exécutées en consultant cette documentation.

@@ -72,70 +71,82 @@ Chaînage : sous-ensemble

Supposez maintenant que nous avons une version compilée de TEI_bare dans un fichier nommé TEI_bare.compiled.xml. Le traitement de la spécification de schéma suivante produirait alors exactement le même résultat que nous aurions obtenu d’une version non compilée.

- - - - - - + + + + + +

Cela fonctionne car chaqu’une des éléments moduleRef ici réfèrent au module (i.e. ensemble d’éléments, etc.) disponible dans l’ODD compilé plutôt qu’aux modules définis dans l’ensemble de la TEI. Notez aussi que seulement fournir l’ODD compilé comme source d’un schema n’est pas suffisant : nous devons aussi spécifier laquelle des déclarations elle contient nous voulons utiliser : nihil ex nihilo fit...!

Cependant, la raison pour laquelle nous nous sommes engagés sur cette voie n’était pas de pouvoir faire d’une autre manière ce que nous pouvions déjà faire autrement. Produisons maintenant une version réduite de TEI Bare dans laquelle l’élément head serait manquant.

- - - - - - + + + + + +

Et juste pour la complétude, voici une autre manière d’arriver au même effet :

- - - - - - - -

Notez qu’on ne peut supprimer ou modifier que les choses qui sont déjà présentes dans l’ODD compilé spécifié par l’attribut source. Cette approche du chaînage est bien adaptée dans une situation où nous définissons d’æbrod un DODD qui combine tous les éléments (etc.) que nous envisageons d’utiliser et que nous dérivons ensuite un sous-ensemble particulier à partir d’eux. Par exemple, un pour les manuscrits, un pour les imprimés de la Renaissance, un pour les imprimés contemporains, etc. (Cette approche a, par exemple, été adoptée par la Deutsches Text Archive.)

Chaînage : super-ensemble -

Mais le chaînage ODD n’est pas restreint à la définition de sous-ensembles. Supposez que nous voulions prendre le schéma existant TEI Bare et ajouter des déclarations d’autres modules. Nous pourrions bien sûr laborieusement copier toutes les déclarations dont nous avons besoin dans notre schemaSpec, mais cela serait bien plus élégant d’avoir de ne pas avoir à faire ça. Supposez, par exemple, que nous voulions ajouter tout ce qui est founi par le module gaiji. Ce module n’était pas inclus lorsque nous avons défini notre version compilée de TEI Bare, toutefois il est évidemment disponible dans l’ensemble de la TEI. Voici une manière de faire :

+

Mais le chaînage ODD n’est pas restreint à la définition de sous-ensembles. Supposez que nous voulions prendre le schéma existant TEI Bare et ajouter des déclarations d’autres modules. Nous pourrions bien sûr laborieusement copier toutes les déclarations dont nous avons besoin dans notre schemaSpec, mais cela serait bien plus élégant d’avoir de ne pas avoir à faire ça. Supposez, par exemple, que nous voulions ajouter tout ce qui est fourni par le module gaiji. Ce module n’était pas inclus lorsque nous avons défini notre version compilée de TEI Bare, bien qu'il est évidemment disponible dans l’ensemble de la TEI. Voici une manière de faire :

- - - - - - -

Le moduleRef qui va cherche le module gaiji utilise son propre attribut source pour spécifier où aller cherche les déclarations de ce module. Cele ne ferait pas sens d’aller les chercher dans tei_bare.compiled.odd : ils n’y sont pas. Au lieu de cela, ici celles-ci sont collectées depuis une copie en ligne d’un ODD compilé qui fournit l’ensemble des Guidelines TEI. Bien sûr, nous aurions aussi pu également réaliser la définition d’un sous-ensemble. Par exemple :

+ + + + + + +

Le moduleRef qui va rechercher le module gaiji utilise son propre attribut source pour spécifier où trouver les déclarations de ce module. Cela ne ferait pas sens d’aller les chercher dans tei_bare.compiled.odd : elle n’y sont pas. Au lieu de cela, on va les retrouvées depuis une copie en ligne d’un ODD compilé qui fournit l’ensemble des Guidelines TEI. Bien sûr, nous aurions aussi pu en meme temps réaliser la définition d’un sous-ensemble. Par exemple :

- - - - - - + + + + + +

Cet ODD nous donnera tout ce qui est disponible dans tei_bare avec les g, char, et glyph tirés par défaut du module gaiji. Nous pourrions parvenir au même effet en nommant explicitement les élements dont nous avions besoin, de nouveau en spécifiant où ceux-ci devraient être trouvés :

- - - - - - - - + + + + + + + +

On peut employer cette technique pour ramener un élément qui a été effacé du schéma compilé. Par exemple, l’élément q n’est pas disponible avec TEI Bare, mais il peut facilement être rétabli. Nous pouvons même spécifier quelle version de l’élément q est souhaitée : dans ce cas, nous irons chercher la version définie dans la distribution 3.0.0 de la TEI P5 :

- - - - - - + + + + + + +

Il existe un tableau utile répertoriant les dates et les numéros de version de toutes les versions de TEI P5 au TEI website. +

Un cas d'usage +

Supposons que vous mettiez en place une application de crowdsourcing pour la transcription de documents d'archives de quelque nature que ce soit. Une fois les documents capturés et légèrement étiquetés, vous envisagez d'enrichir les archives avec des métadonnées détaillées décrivant les personnes et les lieux qui y sont mentionnés. Vous prévoyez donc d'avoir besoin de deux schémas : un (très simple et contraint) pour valider les fichiers de transcription, et un autre (également très contraint, mais différemment) pour valider les métadonnées. Mais bien sûr, vous devrez également valider les documents complétés, combinant les deux types de données. Et il y a certaines fonctionnalités (paragraphes, titres, etc.) communes aux deux, ce qui suggère que vous aurez également besoin d'un troisième schéma... Le chaînage ODD est la réponse !

+ (Avant de poursuivre votre lecture, je vous suggère de télécharger notre petit ensemble de fichiers d'exemple et de lancer votre processeur XML préféré. Veuillez noter que ces fichiers d'exemple sont simplement destinés à démontrer l'effet du chaînage : dans une application réelle, on personnalise son schéma beaucoup plus précisément, par exemple en supprimant les attributs inutiles, en simplifiant les modèles de contenu, en ajoutant différents exemples, etc.)

+ Il nous faudra définir le troisième schéma, qui contient tout ce qui est susceptible d'être utile à l'un ou l'autre des deux autres, plus tout ce qui est commun aux deux. Appelons celui-ci notre mère ODD. Ouvrez le fichier motherODD.xml et vous verrez un ODD typique, avec l'élément racine TEI, défini en référence aux directives TEI complètes. En plus du module d'infrastructure tei, il contient des éléments tels que pb, p, hi, div, et name du module core, ainsi que l'ensemble de métadonnées que nous prévoyons d'utiliser pour chaque document TEI valide, qui prend ses composants des modules header, namesdates, et corpus.

+ Nous définirons nos deux schémas plus spécialisés en référence à celui-ci. Nous devons donc compiler le motherODD, le transformant effectivement en une collection ou une bibliothèque de spécifications TEI complètes. Nous faisons cela en exécutant la transformation odd2odd mentionnée ci-dessus : les résultats de notre fichier exemple se trouvent dans le fichier motherODD.compiled. + Jetez maintenant un œil aux deux sous-ensembles ODD différents dans notre exemple : un (justTranscripts.xml) pour les transcriptions et un (justMetadata.xml) pour les métadonnées. Notez que chacun de ces fichiers ODD fait référence à motherODD.compiled au moyen de son attribut source. Notez également que chacun d'eux spécifie un élément racine différent : ceci afin que l'on puisse utiliser les schémas résultants pour valider une transcription sans en-tête, ou un en-tête sans transcription.

+ Essayez de traiter chacun de ces fichiers ODD pour générer de la documentation et un schéma, de la manière habituelle. Comparez ensuite les résultats. Nous avons inclus quelques exemples de fichiers de données pour vous permettre de vérifier que la validation fonctionne comme elle le devrait : le fichier transcription.xml doit être valide par rapport au schéma généré à partir de l'ODD justTranscription.xml et le fichier metadata.xml doit être valide par rapport au schéma généré à partir de l'ODD justMetadata.xml. Notre exemple suppose un flux de travail particulier dans lequel, par exemple, l'attribut ref est utilisé pour associer des éléments name a un élément person ou place dans l'en-tête ; votre kilométrage peut bien sûr varier. +

Enfin, jetez un œil au fichier driver.tei : il utilise xInclude pour combiner les deux fichiers en un document TEI complet, qui devrait être valide par rapport au schéma généré à partir du motherODD. Encore une fois, n'hésitez pas à modifier si nécessaire en fonction de vos propres pratiques de travail ! +

+ +