[tei-council] draft: email to TEI-L for proofing TEI P5
James Cummings
James.Cummings at it.ox.ac.uk
Mon Jan 13 12:39:17 EST 2014
Dear TEI Council,
Any reason why I shouldn't send this to TEI-L in the next hour or
two? Suggested changes?
-James
====
Dear TEI-L,
The TEI Technical Council is planning to make a release of the
TEI P5 Guidelines (version 2.6.0) on 20 January 2014 (if
everything goes to plan). This release is currently available on
our continuous integration server (Jenkins) as 2.6.0beta for
proofreading by the Technical Council and the TEI community at
large. As part of getting the community even more involved with
the process of making release of the TEI Guidelines, we would be
interested in getting any reports (feel free to send to me
personally) of small typos or bugs relating to this release in
particular. If they are major schema-changing bugs or new feature
requests then they may have to wait until the next release and in
that case submitting them at SourceForge: http://tei.sf.net/ is a
better idea.
Please submit any TEI P5 Version 2.6.0beta bugs/typos by 5pm
(GMT) on Friday 17 January 2014.
The draft release notes:
http://tei.it.ox.ac.uk/jenkins/job/TEIP5/lastSuccessfulBuild/artifact/release/doc/tei-p5-doc/readme-2.6.0.html
The draft 2.6.0 release (in its English version):
http://tei.it.ox.ac.uk/jenkins/job/TEIP5/lastSuccessfulBuild/artifact/release/doc/tei-p5-doc/en/html/index.html
The draft release notes are appended below. Some users may notice
their <publicationStmt> elements not validating because of
greater enforcement of the existing rules using schematron. For
more information about this change in particular, please see
http://wiki.tei-c.org/index.php/PublicationStmt-Changes (or ask
here on TEI-L)
Many thanks for any improvements.
-James Cummings
TEI Technical Council Chair
===
TEI P5 version 2.6.0beta release notes
This version of the TEI Guidelines 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 SourceForge tracking system. If you find
something you think needs to change in the TEI Guidelines,
schemas, tools, or website, please submit a feature request or
bug ticket at http://tei.sf.net/for consideration. Lists ofclosed
bugs
<http://sourceforge.net/p/tei/bugs/search/?q=status%3Aclosed-wont-fix+or+status%3Aclosed-rejected+or+status%3Aclosed-out-of-date+or+status%3Aclosed-accepted+or+status%3Aclosed-works-for-me+or+status%3Aclosed+or+status%3Aclosed-duplicate+or+status%3Aclosed-invalid+or+status%3Aclosed-fixed>andclosed
feature requests
<http://sourceforge.net/p/tei/feature-requests/search/?q=status%3Aclosed-wont-fix+or+status%3Aclosed-later+or+status%3Aclosed-rejected+or+status%3Aclosed-out-of-date+or+status%3Aclosed-accepted+or+status%3Aclosed-remind+or+status%3Aclosed+or+status%3Aclosed-duplicate+or+status%3Aclosed-invalid+or+status%3Aclosed-fixed>are
available on the site.
Some of the more noticeable changes inthis release
<http://tei.it.ox.ac.uk/jenkins/job/TEIP5/lastSuccessfulBuild/artifact/release/doc/tei-p5-doc/en/html/index.html>include:
* Footnotes in the Guidelines now appear in a popup box when
you click on them, rather than causing a jump to the bottom
of the page. (This function depends on JavaScript; if you
have JS turned off, the old behaviour will still work.)
* The prose restriction that
the<pubPlace>,<address>,<idno>,<availability>,
and<date>children of<publicationStmt>occur in that order has
been removed.
* The content model of<publicationStmt>has been updated to
reflect the restrictions detailed in the prose of
section2.2.4 Publication, Distribution, Licensing, etc.
<http://tei.it.ox.ac.uk/jenkins/job/TEIP5/lastSuccessfulBuild/artifact/release/doc/tei-p5-doc/en/html/HD.html#HD24>.
* <stage>now claims membership of att.placement (and thus gets
the at placeattribute) as
perhttps://sourceforge.net/p/tei/feature-requests/476/.
* <docDate>is now available as a child
of<dateLine>(https://sourceforge.net/p/tei/feature-requests/472/),
and the content models of<signed>and<salute>have been
loosened
(https://sourceforge.net/p/tei/feature-requests/433/;https://sourceforge.net/p/tei/feature-requests/478/)
to allow more flexibility in the‘top’‘tail’of sections
(prompted by experience in EEBO TCP)
* Poetry (<l>) is now allowed in the<trailer>
* Usage of at corresphas been clarified
(https://sourceforge.net/p/tei/bugs/506/).
* The value of the at matchPatternattribute is now defined as W3C
XPath syntax rather than W3C XML Schema Language
(https://sourceforge.net/p/tei/feature-requests/432/). This
allows for more powerful regular expressions.
* @perfon<tech>now has the datatype 1+ data.pointer, instead of
data.enumerated (http://sourceforge.net/p/tei/bugs/524/).
* Support for ‘pure ODD’: it is now possible to define content
models using TEI XML constructs only, as an alternative to
the use of RELAX NG. This change is discussed further in a
paper by Burnard and Rahtz presented at2013's ACM Document
Engineering conference <http://www.doceng2013.org/programme>.
Support for the new syntax in ODD processing scripts is
incomplete, however, and not yet fully tested.
* Use of the element<valDesc>throughout the TEI specifications
code was rationalised: mostly this involved removal of
redundant commentary, but in some cases element or attribute
descriptions have been extended or modified.
* A new<abstract>element has been added to support descriptive
metadata about a “born-digital” item (such as a journal
article in a review) to be stored in the TEI Header
perhttps://sourceforge.net/p/tei/bugs/506/
* @namehas been made optional (previously required)
on<relation>as
perhttps://sourceforge.net/p/tei/feature-requests/467/since a
Schematron test is in place to check whether one
of at name, at ref, or at keyis available.
* <forest>and<forestGrp>,<colloc>and others are examples of
elements which used to have locally-declared at typeattributes
which benefit from the ability to now modify class-provided
attributes locally to the element. They now claim membership
of att.typed (and thus get at typeand@subtypeattributes).
Similarly<desc>also is now also a member of att.typed as
perhttps://sourceforge.net/p/tei/feature-requests/473/.
* The<s>element has been modified to not allow it to self-nest
as perhttps://sourceforge.net/p/tei/bugs/578
There are also some changes to the way the Council is managing
the Guidelines:
* Pre-release versions of the TEI P5 development tree are now
tagged as “alpha” and “beta” in their version information.
* In preparation for a program to get translations of reference
documentation up to date, all<desc>and<gloss>elements have
been dated. This allows us to easily generate lists of
translated blocks which are need revising.
* More examples were added or corrected in this release and
improvements to the overall way examples are maintained is
under consideration by the TEI Technical Council.
In addition, the XSL stylesheets which provide processing of TEI
ODD files for Roma and OxGarage have been updated, notably
providing better support for multi-namespace ODD. The Stylesheets
are being maintained separately from the Guidelines and are
athttps://github.com/TEIC/Stylesheets.
--
Dr James Cummings, James.Cummings at it.ox.ac.uk
Academic IT Services, University of Oxford
More information about the tei-council
mailing list