origDate to allow child certainty/precision

[raffazizzi]

I'd like to suggest that the origDate element be extended to allow a child element certainty or precision. As recently defined, it's now very convenient to use @match='..' on these elements to refer to the status of some aspect of their parent element, and origDate is certainly an element that it is often necessary to qualify what one says about a particular aspect of (which end of a data-span is precise and which approximate, for example).

Example of usage:

<origDate notBefore="0212" notAfter="0300"> Probably third century, and certainly after the Citizenship Edict of Caracalla. <precision match="../notBefore" degree="1"/> <precision match="../notAfter" degree="0.25"/> </origDate>

Original comment by: gabrielbodard

[raffazizzi]

In fact, I think I suggested in TEI-L that <precision/> should be allowed inside any element that allow multiple numerican attributes, i.e. anything in att.datable or att.ranging. Any objections?

Original comment by: gabrielbodard

[raffazizzi]

<precision> is a member of model.global so it ought to be available "globally". The problem is that <origDate> has a very restrictive model. It ought to be the same as that of <date>, I suppose. (cf discussion about <origPlace> which probably ought to have same content as <placeName>)

Original comment by: lb42

[raffazizzi]

This ticket now superseded by broader ticket #3054295 (content model of origDate and origPlace).

Original comment by: gabrielbodard

[raffazizzi]

• status: open --> closed-duplicate

Original comment by: gabrielbodard