[tei-council] dating attributes

[Sebastian Rahtz]

>
> NOW BE IT HEREBY PROPOSED:
>
> 1. all elements the content of which describes either a point or a 
> span in time should carry the same set of attributes, and constitute 
> members of the att.datable class
pretty easy to agree with
> 2, the members of the att.datable class shall be @notBefore, 
> @notAfter, @normw3c @norm, and @exact
@to and @after have no new existence?
> 3. @notBefore and @notAfter have the same significance as at present. 
> Their datatype is data.temporal.user (see below)
sadly, there is no "below" to see.

so notBefore and notAfter cannot be checked?
> 4. @normw3c contains a normalized representation of a nodern calendar 
> date in W3C format, like the current @value. Its datatype is 
> data.temporal.w3c
> 5. @norm contains a normalized representation of a date in any 
> user-chosen calendar according to a defined format. Its datatype is 
> data.temporal.user, and the calendar is specified somewhere (not sure 
> where) in the header.
evil names! "norm" is a particularly infelicitous contraction. why not 
@w3cValue and @userValue?

-- 
Sebastian Rahtz      

Information Manager, Oxford University Computing Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431

OSS Watch: JISC Open Source Advisory Service
http://www.oss-watch.ac.uk