on <dateRange>y things (was "Re: [tei-council] adding (non-)Struct elements to <date> & <time>")

Syd Bauman Syd_Bauman at Brown.edu
Wed May 24 11:46:03 EDT 2006

> >> the personography proposal wants to add @from and @to to
> >> att.datable. is this relevant?

Very. We (I forget exactly who -- Syd, James, Matthew D.?) discussed
this quite a bit over breakfast one day. Whole things needs to be
rationalized, and can be with only a few shortcomings (e.g., those
based on James's observation below), methinks.

> Am I remembering it correctly that the ISO:8601 handles
> duration/periods/intervals absolutely fine, but that it is the W3C
> datatype which doesn't?
> I think ISO 8601 allows:
>    1. Start and end, such as 2006-05-01T13:00:00Z/2006-05-11T15:30:00Z
>    2. Start and duration, such as 2006-03-01T13:00:00Z/P1Y2M10DT2H30M
>    3. Duration and end, such as P1Y2M10DT2H30M/2006-05-11T15:30:00Z
>    4. Duration only, such as P1Y2M10DT2H30M
> But that these aren't catered for in the W3C datatype. (Which is a
> shame.)

Yup. 'Tis a shame, esp. since XSD datatype processors already need to
know how to do all the pieces. But because they're not assembled,
we'd have to use separate attributes to permit this flexibility.

1. <dateRange start="2006-05-01T13:00:00Z" end="2006-05-11T15:30:00Z"/>
2. <dateRange start="2006-03-01T13:00:00Z" dur="P1Y2M10DT2H30M"/>
3. <dateRange dur="P1Y2M10DT2H30M" end="2006-05-11T15:30:00Z"/>
4. <dateRange dur="P1Y2M10DT2H30M"/>

More information about the tei-council mailing list