So, where I used to use something like this:

<date notBefore="1598" notAfter="1615" precision="low"></date>

meaning "we're just taking a guess really, but our best guess would be 
that it's between 1598 and 1615", how would I express that with the 
current attributes?

You're of course welcome to say that such a formulation is so vague as 
to be ridiculous and not worth encoding, but it's the sort of thing I 
often get from content experts, and I think it's better than nothing; 
and it's certainly different from

<date notBefore="1598" notAfter="1615"></date>

i.e. without the @precision attribute. Would @cert do the job here? I 
guess this is, really, more of a matter of certainty than it is of 
precision, strictly speaking.


Lou's Laptop wrote:
> I think the point is that the W3C or ISO datatypes come with a defined
> precision which is explicit eg in the number  of digits you supply, and
> that there is no need therefore to add an extra attribute.
> Note that (as James, I think, pointed out first) "precision" is not the
> same as "reliability".
>  Martin Holmes wrote:
>> Hi there,
>> Garces, Juan wrote:
>>> Please forgive should I not see the obvious, but how do @notBefore/@notAfter and @from/@to express precision or lack thereof?
>> Having looked at the references and the discussion, I'm also puzzled by
>> this. It seems to me that the job done by @precision is no longer done
>> by any other attribute or combination of attributes. @cert perhaps comes
>> close:
>> cert  (certainty) signifies the degree of certainty associated with the
>> intervention or interpretation.
>> but I'm not sure "intervention or interpretation" extends to assigning a
>> date, does it?
>> Cheers,
>> Martin

Martin Holmes
University of Victoria Humanities Computing and Media Centre
([log in to unmask])
Half-Baked Software, Inc.
([log in to unmask])
[log in to unmask]