Re: [libdb-develop] [feature] Date Ranges and Database Manipulations

[Bruce D'A. <bd...@fa...>]

On Nov 29, 2004, at 6:21 PM, Morbus Iff wrote:

> Instead of simply an "annotation" column, however, there'd be three 
> content columns: date_start (YYYY-MM-DD), date_end (YYYY-MM-DD) and 
> date_raw (a string).

I was just reminded of something I've seen in LoC schema that may be of 
relevance:

       <temporal encoding="w3cdtf" qualifier="approximate" 
point="start">1919</temporal>

So a range is indicated by this I guess:

       <temporal encoding="w3cdtf" qualifier="approximate" 
point="start">1919</temporal>
       <temporal encoding="w3cdtf" qualifier="approximate" 
point="end">1923</temporal>

That would seem to fit within your thinking.  I still wonder if it 
would better to add a third option for the point that would allow 
indication of "March 12, 14, 19".

Of course, we still get back to the fact that database dates are poor 
representations of bibliographic dates.  It's a *very* small minority 
of books, movies, records, magazines, etc., etc. that ever have a date 
like YYYY-MM-DD associated with it.

Bruce