I've also used @precision on <date>. I'd also use @confidence if its
definition wasn't so closely tied to @min and @max; it would be nice to
be able to use the combination of @confidence, @notBefore and @notAfter
to specify a date range with less than 100% confidence.
On 2017-12-05 08:17 AM, John T Young wrote:
> On the Casebooks Project we use @precision loads on <time> and less
> often but still often enough on <date>. It seems (to me) a succinct way
> of saying 'this must have happened at around this time but not
> necessarily at exactly this time'. What should we use instead - @cert?
> That seems less satisfactory to me, because we aren't trying to say we
> aren't sure that it was around that time, just that we aren't sure
> exactly what 'around' means (which rules out @notBefore and @notAfter).
> On 05/12/2017 14:29, Syd Bauman wrote:
>> The TEI Technical Council plans to remove the elements listed below
>> from the att.dimensions class. This means that these elements would
>> lose the following attributes:
>> atLeast=, atMost=, confidence=, extent=, max=, min=, precision=,
>> quantity=, scope=, and unit=
>> These attributes (which are used for expressing a measurement or
>> statistical information about a set) should never have been on these
>> elements in the first place. Thus their presence is considered a
>> corrigible error, and their removal is scheduled to take place at the
>> next release (likely in Jan or Feb 2018) without a 2-year
>> "deprecation" period, during which use of these attributes on these
>> elements would cause a warning to occur.
>> The elements that will lose these attributes are:
>> <affiliation>, <am>, <birth>, <climate>, <corr>, <date>, <death>,
>> <education>, <event>, <expan>, <faith>, <floruit>, <geogName>,
>> <langKnowledge>, <langKnown>, <location>, <name>, <nationality>,
>> <occupation>, <org>, <orgName>, <origDate>, <origPlace>, <origin>,
>> <persName>, <person>, <persona>, <place>, <placeName>, <reg>,
>> <relation>, <residence>, <sex>, <socecStatus>, <terrain>, and
>> If anyone is actually using one of these attributes on one of these
>> elements, and its removal in future releases might be a hardship,
>> please let us know by posting here or to the issue
>> Thank you.
>>  The <persona> element was not actually discussed in detail on the
>> issue 299 discussion board, but its removal from the
>> att.dimensions class seems entirely uncontroversial.
>>  While time is something measurable and quantifiable, the
>> attributes in att.dimension and att.ranging are not appropriate
>> for the <time> element because measurements of temporal
>> dimensions are typically more complex than a simple quantity and
>> unit pairing, and are thus handled by att.duration; furthermore a
>> set of temporal measurements would not be reported in a single
>> <time> element, but rather in a set of them.