From a perspective of those interested in the history of the TEI Guidelines as a developing entity it might be important to highlight that in addition to http://www.tei-c.org/Vault/P5/current/ that http://www.tei-c.org/Vault/P5/ now has all the earlier releases as well in a stable location. This means, for example, that in an academic article you could cite the reference page of a particular version of a particular element and/or compare it with another. Or indeed, one could also compare the underlying XML element specifications http://www.tei-c.org/Vault/P5/1.3.0/xml/tei/odd/Source/Specs/w.xml or, perhaps more importantly, potentially use the new ODD elements Sebastian mentioned to pull in an older version of a TEI element to your ODD. Of course one could do most of this already with the sourceforge SVN site, but this organises it nicely on a release-by-release basis and includes the rendered versions.
Just thought I'd mention that in case it escaped anyone's notice that might be interested.
From: TEI (Text Encoding Initiative) public discussion list [[log in to unmask]] On Behalf Of Sebastian Rahtz [[log in to unmask]]
Sent: 07 July 2010 23:07
To: [log in to unmask]
Subject: TEI P5 release 1.7.0
The new release of the TEI Guidelines is now in all the usual places:
* as file releases on Sourceforge at https://sourceforge.net/projects/tei/files/
* live at http://www.tei-c.org/Vault/P5/current/ and points south (not quite yet
at http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index.html, but soon)
* as Debian packags at http://tei.oucs.ox.ac.uk/teideb/
the release notes below cover most of the changes, but are not
This release introduces significant additional features to the way
in which the ODD system for TEI customization may be expressed. The
new features introduced allow a customization to be expressed by
inclusion (specifying only the elements it requires) rather than by
exclusion (specifying the elements which it does not require). They
also permit specification of a particular version of the Guidelines as
source for a schema.
Support for this entailed a number of changes, including definition
of new attributes for <moduleRef>, and new elements
<elementRef>, <macroref> and <classRef> as well
as revision to the prose of the relevant Guidelines
chapters. Some clarification of the way the odd-to-odd transformation
process works, for example when generating pattern prefixes for
RelaxNG, was also necessary. The new features greatly simplify the
process of generating user specific customisations, while retaining
all the existing behaviours. In addition, the test suite has been
revised and extended to check that the new facilities worked as
intended. Expanded tutorial material for the revised system will be
the subject of a Workshop to be taught at the 2010 General Meeting.
As usual, several minor clarifications and corrections were made to
the wording of the Guidelines in response to Sourceforge tickets (e.g.
3025031 3025032 3025017 3010481 2989088 2982439 2942469 2965680
2981703 2982056) and discussion on Council and TEI-L mailing
The work of the AFNOR group providing and correcting French
translations and examples also continued; in particular during May and June
substantial work on a new suite of French language examples was undertaken.
Other specific changes are listed below in reverse date order:
* 2010-07-02 : add constraint to prevent <relatedItem> supplying both a @target and some content (2728061)
* 2010-05-08 : add new source attribute and revise datatype of
existing version attributes for consistency
* 2010-05-06 : add new att.docStatus attribute class (2812634)
* 2010-05-06 : add <material> to att.canonical class