[tei-council] Re: [Fwd: the easter egg has hatched]

Syd Bauman Syd_Bauman at Brown.edu
Wed Apr 25 11:27:55 EDT 2007


Dear Syd,

Thank you for forwarding this to the Council list.

Cheers,

David

---------------------------- Original Message ----------------------------
Subject: the easter egg has hatched
From:    djbpitt at pitt.edu
Date:    Wed, April 25, 2007 11:11 am
To:      "TEI Council" <tei-council at lists.village.virginia.edu>
--------------------------------------------------------------------------

Dear Council,

How does one find a trac ticket anyway? In any case, comments on my
assigned chapters and a few others are below.

Best,

David
________

passim: Can we add links for references to classes, e.g.:
measure.attributes =
   att.measurement.attributes,
   attribute type { data.enumerated }?
Here data.enumerated is a link but att.measurement.attributes isn't,
although it might be useful if it were. Note also that references to model
groups are links, but references to attribute groups are not; why should
these be rendered differently?
Need examples for all ref-*.html pages (some have them, e.g., <equiv>, and
some don't, e.g., <altIdent>)
Am I the last person on earth who cares about the distinguishing
restrictive and non-restrictive clauses?

guidelines.css: add "white-space: pre;" for all .pre elements
fix line spacing to avoid extra space above lines with footnote reference
numbers (ask me how if necessary)
bulleted list in fn 52 in CO is rendered with bullets and text overlapping
(indentation set incorrectly?)

AB (Preamble/preface): Pervasive references to SGML, DTDs, WSDs, etc. Also
references to transition from P3; should these be to P4?

SG (Gentle introduction): Needs a thorough rewrite; a discussion of
content models in RelaxNG compact syntax is needed because this syntax is
used in the documentation in the Guidelines, but DTD syntax doesn't fit.
typo: documwents
in "has the value draft", "draft" isn't typographicaly distinct (unlike
the attribute value "P1" in the same line); this problem recurs frequently
in other sections, including Documentation; is this a markup problem or a
problem with the stylesheet?
says that XML predefines &amp; and &lt;, but there are three others (&gt;,
&apos;, and &quot;)?
fix alignment in declaration of parameter entity a.global
there are lots of references, especially toward the end (entities, marked
sections), to "the TEI DTD"; since this suggests that TEI structure is
modeled directly with DTDs, should it be updated to refer instead to ODDs?
example of marked section for <eg> should be wrapped; otherwise pre
rendering extends beyond right margin
example including/ignoring stanzas/couplets is garbled
how comfortably do namespaces coexist with DTDs?
tei2.dtd? Did we change the filename, or just the name of the root element?

CH (Character Sets): "modeling the value of @xml:lang parallels the
modeling of the value of @xml:lang"??
do we want French "coeur" to match only the four-character string, and not
the five-? This isn't a TEI problem, but the guidelines seem to assert
that a user would not want to search for the five-character string I got
spanked (rhymes with but differs from "thanked" :-( ) for
proofreading last time there was a call for *only* content-related
feedback, but "are encoded in ISO-8859-n as a singlebyte with the same
value as the code-point" needs a space between "single" and "byte". If
this non-content-related observation is unwelcome, just ignore it, and I
apologize for wasting your time. :-(

ST (Infrastructure): missing word in "may be combined more less freely"
(see snarky note above about proofreading)
identifies three ways to specify (ODD, RelaxNG, DTD), but shouldn't we
specify only ODD (not only recommended, but we mention no other; the
others are possible, but neither recommended nor supported)?
should "for a text to combine different kinds of object" read "objects"?
two missing spaces in fn 34
Remove the sentence that reads "The values of xml:id attributes must be
legal names with respect to the SGML declaration in force." and adjust the
following one. That is, XML isn't an implementation of SGML as far as the
TEI is concerned, and as far as TEI users are concerned (although they
don't need to know that), there is only one SGML declaration in the world,
and that's the XML one.
what's the meaning of the SGML reference in "Declare TEI.XML marked
section to permit SGML support"?
The description of the order for DTD components lists user-defined element
declarations at the end, but don't they need to come early for DTD
purposes, since early definitions take precedence over later ones? do we
need separate data.TruthValue and data.xTruthValue classes? Isn't this
like specifying language where it has to be European, i.e., a formal
restriction where user error is unlikely?
Should att.declaring be broader? Why can't a <p> (for example) be
associated with a declaration in the header (especially because <u> can)?
line break missing in example of n.X notation
references to use "in SGML mode" at the end

CO (core):
where does apostrophe mark a plural in English?
"Parentheses and other marks of suspension" should omit "other"
Lose the last comma in "light, buttery, pastry"
"Element foreign" has some "include" notes
The example that purports to illustrate a <bo> element doesn't seem to do
so; no reference to <bo> and no uri, although the description above
promises one
"All members of this class carry the following optional attributes:" is
not followed by a list of attributes (grabbed the description instead of
the attributes/values?)
"reg" erroneously tagged as attribute instead of element in the source
underlying "This use should be distinguished from the use of a nested @reg
(regularization) element ..."
Stray leading backslash in "\list = element list { list.content,
list.attributes }"
In the discussion of indexing, the <index> element is inserted after the
string being indexed, and does not contain it. Is this post-posed
milestone strategy the best approach? Note that the use of <anchor> to
mark the endpoint of a large target range becomes peculiar because the
start point (the location of the <index> element begins only *after* the
beginning of the logical target.
The indexing term always comes from the <term> child, which is often
necessary, but excludes the potential economy of using real text from the
body when <term> is not specified.
Reference to SGML in 4.10.3 (also just above and in 4.13)
In structured bibliographies, are multiple authors/editors entered
together in a single <author>/<editor> element or separately? There are
examples of both, but no explicit statement about best practice (or about
the conditions under which one or the other might be preferred).
"include" notes at the end

TD (Documentation Elements): Garbling in "In the remainder of this chapter
we refer to software which provides such as a processing environment as an
ODD processor"
comma after "i.e." in "i.e. a named"
reference to "SGML dtds" (aside from the problem of the reference to
"SGML," should "dtds" be capitalized?)
The text says "<egXML> contains a single well-formed XML example
demonstrating the use of some XML element or attribute," but the first
example (and others?) has no root element, and therefore is not well
formed. If it is intended that <egXML> is itself the root, then it doesn't
*contain* well-formed XML.
The immediately following example with escaped XML has non-bold <term>
tags, but does not clearly illustrate how the markup differs (that is,
they are character-for-character identical).
erroneous angle brackets (instead of leading "@") in: either a @bar
attribute or a <baz> attribute
missing space in "value ofsequenceRepeatable"
some values in this section are not typographically distinct, while some
earlier are. Is there missing markup in the source? Also in other
chapters.
the class name in "the class model.hiLike" is bold, but other class names
are not typographically distinct. Missing markup in the source?
is the plural of "child element" "children elements" (as here), or "child
elements" (sounds better?)
if you specify "delete" mode and no declaration exists, how can you remove
the existing declaration (which doesn't exist), as the chart states?
"include" notes at end








More information about the tei-council mailing list