#110 Review usage and precision of @extent

AMBER
closed
Lou Burnard
None
7
2008-09-10
2008-03-25
Lou Burnard
No

See debate on TEI-L 20-22 feb 08

Discussion

  • BODARD Gabriel
    BODARD Gabriel
    2008-04-24

    • labels: --> 666891
    • assigned_to: nobody --> jcummings
     
  • BODARD Gabriel
    BODARD Gabriel
    2008-04-24

    Logged In: YES
    user_id=597407
    Originator: NO

    (1) @extent and @unit on gap are to be suppressed, and instead gap will be made a member of att.dimensions, which gives it @quantity and @unit.

    (2) att.dimensions is to be extended by the addition of attributes: @from and @to (to indicate ranges of quantities); @atLeast and @atMost (for uncertain/imprecise quantities).

    (Anything more complicated than this we should recommend using the new <precision> element rather than trying to express it with the att.dimensions attributes.)

     
  • James Cummings
    James Cummings
    2008-04-24

    • assigned_to: jcummings --> louburnard
    • labels: 666891 -->
     
  • Lou Burnard
    Lou Burnard
    2008-06-21

    Logged In: YES
    user_id=1021146
    Originator: YES

    The trouble with this is that we also decided to add @precision to both att.dimensions and att.editLike.
    Adding <gap> (which is a member of att.editLike) to att.dimensions would thus give it the same attribute twice.

     
  • Lou Burnard
    Lou Burnard
    2008-08-17

    • milestone: --> AMBER
     
  • BODARD Gabriel
    BODARD Gabriel
    2008-08-17

    Logged In: YES
    user_id=597407
    Originator: NO

    I'm not sure why att.editLike is getting the @precision attribute then. I should argue that 'gap' should take quantity and precision in the same way as 'space' (and date, measure, num, etc.). So the essential question is, how do we add the @precision and related attributes to 'gap', 'space', 'date', 'measure', 'num', and various dimensions elements? (What others need @precision?) Surely any element in att.editLike that needs @precision also needs the other att.dimensions attributes--since precision only has any meaning if applied unambiguously to a quantity--so @precision shouldn't be in att.editLike in the first place. (If for some reason you want to apply precision to 'supplied', for example, you should use the new 'precision' element to do so.)

     
  • James Cummings
    James Cummings
    2008-08-18

    Logged In: YES
    user_id=612078
    Originator: NO

    I agree with Gabby that @precision only has meaning when there is a quantity -- otherwise we're talking about @cert which is different. I've upped the priority on this because although it may be 'Amber' in that it still needs some sorting out, I think it is something we should definitely try to do for the next release.

     
  • James Cummings
    James Cummings
    2008-08-18

    • priority: 5 --> 7
     
  • BODARD Gabriel
    BODARD Gabriel
    2008-08-27

    Logged In: YES
    user_id=597407
    Originator: NO

    After discussions of ticket #1933198 (on new <precision> element), I think that:

    (1) we need to define the four new attributes proposed below (@min, @max, @atLeast, @atMost) in a new attribute class, perhaps att.ranging or similar. (<precision> will then be a member of att.ranging but not att.dimensions.)

    (2) @precision should be defined within att.dimensions __but **not** att.editLike or att.ranging__.

     
  • Lou Burnard
    Lou Burnard
    2008-09-10

    At rev 4787, I added @min, @max, @atLeast, @atMost, @extent to att.dimensions; removed local definitions for @extent on <gap> and in att.damaged; removed @precision from att.editLike; made att.damaged and att.editLike subclasses of the new att.dimensions. Quite a bit of wording in the text still to be revised, but this seems to address most of what's required here.

     
  • Lou Burnard
    Lou Burnard
    2008-09-10

    • status: open --> closed