[tei-council] Making absolutely bare a little more bare

[David Sewell]

I am not a metadata guru so I won't comment on which TEI header elements
can be eliminated, but certainly <postscript> can be eliminated,
especially as <opener> and <closer> are unavailable.

On the other hand, I wonder why <table> was omitted from TEI Bare. It
is a fairly basic structural component of texts and has a simple content
model. Would it make sense to add it? I suppose it depends on how one
interprets "a TEI schema with the bare minimum of tags to make a
recognizable document", as the ODD documentation for TEI Bare says.

David

On Thu, 4 Dec 2008, Laurent Romary wrote:

> I did. And doing so discovered a few other candidates for deletion. So
> the victims so far are:
> <editionStmt>, <extent>, <seriesStmt>, <postcript>, <biblFull>,
> <notesStmt>, <typeNote>, <postcript>
>
> I am still wondering why we managed to keep all these...
>
> Le 4 déc. 08 à 14:26, Sebastian Rahtz a écrit :
>
> > Looks fine by me. Have you tested whether it works
> > without them? possibly some hard-wired dependency
> > which is why we left them in? (if so, we should track those
> > down)
> >
> > --
> > Sebastian Rahtz      Information Manager, Oxford University
> > Computing Services
> > 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>

-- 
David Sewell, Editorial and Technical Manager
ROTUNDA, The University of Virginia Press
PO Box 801079, Charlottesville, VA 22904-4318 USA
Courier: 310 Old Ivy Way, Suite 302, Charlottesville VA 22903
Email: dsewell at virginia.edu   Tel: +1 434 924 9973
Web: http://rotunda.upress.virginia.edu/