On Thu, 2008-01-31 at 10:58 +0900, Tim Finney wrote:
> Hi Martin,
> Yes, using the approach I am advocating for uncertain quantities means
> that @cert would specify confidence that the actual value lies within
> the specified range. It would not specify your confidence in the @when
> value. Thus <date @when="115" @notBefore="100" @notAfter="155"
> @cert="high"/> would be translated as "I am certain beyond reasonable
> doubt that the actual date of this thing lies between 100 and 155 CE.
> FWIW, I think that its most probable date is 115."
> This approach will work in many cases but certainly not all. As Gabby's
> examples show, each of @when, @notBefore and @notAfter can be uncertain.
> A general solution needs to be able to treat each of these things as an
> uncertain quantity. We can't have attributes on attributes so it would
> seem that stand-off markup is required for difficult cases.
It might be considered practicable to encode these complex dates as
multiple <date> elements (one for each distinct level of certainty, each
bearing only the date values which correspond to that level of
uncertainty). These distinct <date> elements could then be united using
@sameAs (or @synch?), or perhaps their unity could be expressed by
nesting them within an outer <date>.
<date when="1640" cert="low"/>
<date notBefore="1620" cert="medium"/>
<date notAfter="1660" cert="high"/>
<date xml:id="possibly-1640" when="1640" cert="low"/>
<date sameAs="#possibly-1640" notBefore="1620" cert="medium"/>
<date sameAs="#possibly-1640" notAfter="1660" cert="high"/>
New Zealand Electronic Text Centre