#60 precision attribute on date/datestruct/daterange

CO
closed
Syd Bauman
None
7
2007-02-21
2005-04-28
James Cummings
No

Reminder:

date/@certainty should become date/@precision
dateRange/@exact should become dateRange/@precision
dateStruct/@exact should become dateRange/@precision

all possibly should also have a @cert attribute which
indicates certainty as opposed to the precision.

-James

Discussion

  • Lou Burnard
    Lou Burnard
    2005-08-06

    Logged In: YES
    user_id=1021146

    There is probably a need to distinguish the precision of a
    dating from the certainty with which the dating is made (one
    might be quite sure that a date was imprecise for example),
    but more is needed than these suggestions. Also
    dateRange@exact does something rather different from
    dateStruct@exact -- it says which of the other (to and from)
    attributes have high precision, with values both, to, from
    or neither.

    cert now has values high/medium/low

    would those also be sufficient for precision?

     
  • Syd Bauman
    Syd Bauman
    2006-09-25

    • priority: 5 --> 7
    • assigned_to: nobody --> sbauman
     
  • Syd Bauman
    Syd Bauman
    2007-02-02

    • milestone: --> CO
     
  • Syd Bauman
    Syd Bauman
    2007-02-21

    • status: open --> closed
     
  • Syd Bauman
    Syd Bauman
    2007-02-21

    Logged In: YES
    user_id=686243
    Originator: NO

    The date/@certainty was, in fact, changed to date/@precision on 2005-08-06. At the same time, <date> was given a new @cert attribute for indicating certainty as opposed to precision.
    However, because the precision of a date or time is generally indicated in the normalized value in the value= attribute, Council has recently decided to drop the @precision attribute entirely.
    The <dateStruct> and <dateRange> elements no longer exist.