[tei-council] datatype issues (part 1)

[Christian Wittern]

Syd Bauman <Syd_Bauman at Brown.edu> writes:

>
>> 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.
>
> Since
>
> a) I've yet to see any example of software that does something
>    useful with "13:14:54" but barfs on "13:15", and
> b) users aren't *required* to be imprecise
>
> I think the extras are well worth it.

I second that.  The requirement to give the @CREATEDATE up to the
seconds in METS regularily drives me crazy (I wonder who manages to
create such a record in just one second anyway).  It would be good to
save TEI users that headache.

>
> A bit of a side-note: to me the proposed
>    xsd:date | xsd:time | ... | xsd:token { pattern = "[whatever]" }
> *is* mapping directly to W3C datatypes. (I had not contemplated this
> "cleanly" business before :-) That is, nothing more than an average
> RelaxNG validator that knows the W3C datatype library (e.g., jing,
> xmllint) is needed to validate it.

This looks useful:-)

Christian

-- 
 Christian Wittern 
 Institute for Research in Humanities, Kyoto University
 47 Higashiogura-cho, Kitashirakawa, Sakyo-ku, Kyoto 606-8265, JAPAN