[tei-council] datatype issues (part 1)

Julia Flanders Julia_Flanders at Brown.edu
Tue Sep 20 14:15:23 EDT 2005

It certainly seems to me that the TEI community is likely to need a 
representation of time that doesn't require misleading levels of 
precision. If I'm transcribing a journal whose entries include the 
time of day, I don't want to be forced to represent those times as 
accurate to the second. Am I right in guessing that this is an 

The option of an extended tei.data.temporal might be a good way to do this.

>Thanks for the clarification, and apologies for my careless usage. 
>Let's see if I;ve understood the position correctly.
>(1) ISO 8601 defines a large  number of different formats for 
>representing temporal expressions
>(2) W3C has defined a subset of these for which named w3c datatypes exist
>(3) the edw90 proposal for tei.data.temporal is to allow a 
>combination of (some of or all?) the w3c datatypes plus a couple of 
>others which Syd proposes we should allow for as well by means of a 
>If that's correct, the only issue we have to argue about is whether 
>or not the 'extras' are desirable enough to outweigh the possible 
>inconvenience of supporting formats which off-the-shelf w3c-focussed 
>implementations may not recognise.
>I don't have a strong view on this: we could maybe distinguish 
>tei.data.temporal and tei.data.temporal.extended if others do -- the 
>distinction being that the former keeps to our original goal of 
>mapping cleanly to w3c datatypes.
>tei-council mailing list
>tei-council at lists.village.Virginia.EDU

More information about the tei-council mailing list