Revision 7f804df2f1b5855f6827fb611e57d5663a5980e5 authored by lb42 on 04 October 2015, 21:29:34 UTC, committed by lb42 on 04 October 2015, 21:29:34 UTC
readme-1.9.xml
<?xml version="1.0"?>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
<fileDesc>
<titleStmt>
<title>P5 version 1.9 release notes</title>
</titleStmt>
<editionStmt>
<edition>
<date when="2011-02">February 2010</date>
</edition>
</editionStmt>
<publicationStmt>
<authority>The Text Encoding Initiative</authority>
</publicationStmt>
<sourceDesc>
<p>created retrospectively from svn ChangeLog</p>
</sourceDesc>
</fileDesc>
</teiHeader>
<text>
<body>
<p>This release has the usual set of typo fixes to the reference
part of the Guidelines, some changes to the specs, many changes
to build tools, and associated updates to the processing
stylesheets. Notable changes (in decreasing order of visibility
to the end user) are:
<list type="ordered">
<item>The <gi>egXML</gi> element has been given an attribute
<att>valid</att> which can have the values true, false and
feasible. This indicates whether the example is supposed to be valid or
not. If it is marked feasible, this means it could be transformed into
a valid document by inserting any number of valid attributes and child
elements anywhere within it; it is valid against a version of the
schema concerned in which every data, list, element, or attribute
element has been made optional. The web version of the Guidelines will
distinguish these cases by use of different background colours. This
allows us to show examples which are only skeleton TEI documents, rather
than self-contained valid fragments.</item>
<item>All elements now have at least one example, and all the examples
have been checked for validity or feasibility again (a previous error
in the process had allowed some invalid ones through).</item>
<item>All elements have been changed to make them explicit members of
the <ident>att.global</ident> attribute class, rather than having this
done by special-case processing during the build
procedure. This means that any ODD which defines elements in
the TEI namespace will have to explicitly add
<ident>att.global</ident> to them.</item>
<item>The Guidelines are now available in ePub and Kindle formats.</item>
</list>
</p>
<p>
<p>The table below lists other changes which affect generated schemas.</p>
<table rend="rules">
<row role="label">
<cell>Date</cell>
<cell>Change</cell>
<cell>Sourceforge ticket</cell>
</row>
<row>
<cell>2011-02</cell>
<cell>Add @valid to egXML</cell>
<cell><ptr
target="https://sourceforge.net/tracker/?func=detail&aid=3156049&group_id=106328&atid=644065"/>
</cell>
</row>
<row>
<cell>2011-02</cell>
<cell>Make all elements explicit members of
att.global</cell>
<cell><ptr
target="https://sourceforge.net/tracker/?func=detail&aid=2994685&group_id=106328&atid=644065"/>
</cell>
</row>
<row>
<cell>2011-02</cell>
<cell>make <gi>collection</gi> typeable</cell>
<cell><ptt
target="https://sourceforge.net/tracker/?func=detail&atid=644065&aid=3114917&group_id=106328"/></cell>
</row>
<row>
<cell>2011-02</cell>
<cell>allow <gi>date</gi> as child of <gi>analytic</gi></cell>
<cell><ptt
target="http://sourceforge.net/tracker/?func=detail&aid=3168838&group_id=106328&atid=644065"/></cell>
</row>
</table>
</p>
</body>
</text>
</TEI>
Computing file changes ...
