I've just realised you could also do all this -- with no need for
customization -- by using the <label> element, which is already
available within <edition>, as a sibling of <date>.
<date>23 jun 09</date>
So no need for a new attribute. If we do go for a new attribute, we need
to remember that it would apply to the status of the document whose
edition is being specified -- so for example, @docStatus on an <edition>
inside a <sourceDesc> would refer to the status of the source document,
not that of its digital version.
Martin Holmes wrote:
> Here are some possibilities:
> galley (for proofing)
> Sebastian Rahtz wrote:
>> Martin Holmes wrote:
>>> I'm convinced too -- edition/@docStatus sounds perfect. Do you agree
>>> that it should be an open string value in the regular schema, but with
>>> lots of useful suggestions in the Guidelines?
>> yes indeed. its a perfect example for an open string
>> and a local customization
>>> Should we start gathering
>> my current list includes "draft" and "frozen", but
>> I'm in the middle of a debate at work about suitable names...