[tei-council] Dates and calendars

[Martin Holmes]

On 12-08-13 04:38 AM, Lou Burnard wrote:
> I am an eejut.  Gabby is of course completely right. (I knew I
> disapproved of something, but I misremembered what)
>
> I wonder though whether this specific example (where @calendar is
> supplied but there is no content) shouldn't therefore trigger a
> schematron error. It doesn't make a lot of sense to say "there's a date
> in this calendar here but I'm not telling you what it is" surely?

I claim eejut status too. Of course I should be using @when-custom. And 
I'm glad it's there, because what I really want to do is to be able to 
calculate the equivalent gregorian date automatically from a julian 
date, so I need a formal attribute (which I can constrain with 
schematron) for encoding the julian date. So I disapprove of your 
disapproval of att.datable.custom.

This does seem to be a good candidate for a schematron rule, so I'll do 
that, assuming Gabby agrees, and I'll also use it as the basis for the 
little guide to writing constraints that I've been supposed to be 
creating for ages.

Cheers,
Martin

> On 13/08/12 11:16, Gabriel Bodard wrote:
>> The @calendar attribute on datable elements is defined as "indicat[ing]
>> the system or calendar to which the date represented by the _content of
>> this element_ belongs"; in other words the markup:
>>
>> <date when="1424-02" calendar="#julian"/>
>>
>> Means: "A date in the Julian calendar which corresponds to February 1424
>> CE in the proleptic Gregorian calendar." If you want to encode a
>> normalized version of the Julian date, the only legal way to do so is to
>> use @when-custom and @datingMethod.
>>
>> (This is exactly the use-case for which we introduced the whole
>> http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html
>> class, of which Lou so disapproves. ;-) )
>>
>>
>

-- 
Martin Holmes
University of Victoria Humanities Computing and Media Centre
(mholmes at uvic.ca)