Possibly this is an argument for a new optional attribute on
<revisionDesc>, say @docStatus. (Named as such to indicate that it
represents that status of the document; "@status" might suggest it
applied to the status of the <revisionDesc> element itself.)
It would be hard to come up with a controlled vocabulary or even a list
of suggested values that would apply to all possible projects, as the
terminology used for workflow status is very project-specific.
But that last clause is also an argument for using a custom attribute in
a local namespace with a controlled vocabulary.
On Thu, 25 Jun 2009, Sebastian Rahtz wrote:
> Martin Holmes wrote:
> > I agree. For journal articles, I have to record at least two stages,
> > "proofing" and "published". In the past, I've resorted to the @rend
> > attribute on the root TEI or TEI.2 element
> hmm, thats not actually a bad solution, I had not considered it.
> > Does this kind of thing belong in the <revisionDesc>, perhaps?
> I wondered. you pick up the status from the last <change>. but thats a horrid
> and my authors would not do it...
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: [log in to unmask] Tel: +1 434 924 9973