[tei-council] EDW90 proposals (1 of several)

Syd Bauman Syd_Bauman at Brown.edu
Sun Jul 31 10:16:47 EDT 2005


> <revisionDesc> applies to the document, not the header, surely?

I have often entered <change> elements in a <revisionDesc> that
describe a change to the <teiHeader>. I think of <revisionDesc> as a
revision description of the entire file (<TEI.2>, <teiCorpus2>,
whatever). 


> @creator is the metadata stiuff only. you might argue that
> <teiHeader> should be allowed a child <respStmt> of its own.

Might, but I wouldn't.


> @status seems too limited to be of serious use.

Remember that it (currently) has dateCreated= and dateUpdated= to go
with it. But nonetheless, I agree completely. Even all combined, they
are not really useful, and probably should be dropped.

We might create a mechanism for stating that a particular <change> in
the <revisionDesc> applies to only the <teiHeader>, not the <text>.
(E.g., attribute scope { ( "header" | "text" | "both" ) } or
something like that), but since we're not planning on using
independent headers anymore, I'm not sure there's a significant
advantage to such a scheme.


LB> 3. Drop <xxxSpan> elements in favour of HORSE-style attributes (i.e.
LB> something like the spanTo attribute added to <index>)

LB> I am basically in favour of this proposal, but it needs more careful
LB> and detailed articulation

I agree. If members of Council are interested, you can glean a little
bit more information about HORSE from the slides to my talk at ACH,
which are at
  http://www.tei-c.org/Talks/2005/ACH-ALLC/Bauman.tgz
particularly slides 6, 7, and 8. (There is currently no pointer from
any index page to those slides, as the other talks from that session
are not available yet due to licensing issues I just haven't gotten
around to dealing with.)


> why on earth would they care either way? if you let them have a
> private recondite name for an ID attribute, everyone else will want
> one too.

Really good point. The problem is that "they", the folks who use
<witness>, already have sigil= in P4. So it's not a question of
letting "them" have a special name, it will be viewed more as taking
away the special name currently available.




More information about the tei-council mailing list