[tei-council] P5 work process

[Sebastian Rahtz]

As another contribution to the debate, I have written 
http://www.tei-c.org/Drafts/edw87.xml, which attempts
to set some rules by which the TEI class system could be revised, and 
provides some data on
the subject.

My view is that the most effective way to proceed is to agree these 
rules (or amend them),
and then for one person to go off and prepare a complete worked-through
proposal for all the new names and memberships. Hopefully, this would be 95%
non-controversial, and the council would argue about the edge cases.

I would very much like to see _more_ rules about how to construct names 
of things!

If you haven't thought about TEI classes and their naming before,
this is probably dry stuff. But this stuff is going to become more and 
more visible,
and it behooves us to get it looking right.

Note that this work  would be

 * low-impact from the point of view of existing documents;
 * low-impact for authors and editors
 * (very very) high-impact for people who edit schemas or DTDs by hand
 * moderately high impact for people who write ODDs (ie one could write 
a converter)

-- 
Sebastian Rahtz      
Information Manager, Oxford University Computing Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431

OSS Watch: JISC Open Source Advisory Service
http://www.oss-watch.ac.uk