#346 make attributes from and to (as pointers) part of a class

GREEN
closed
None
5
2013-01-15
2012-03-03
Laurent Romary
No

In the course of working on bibliographical ranges, where a proposal is made to create a class for @from and @to (see http://www.tei-c.org/Activities/Council/Working/tcw23.xml\), Keven, Martin and I identified the need to rationalized the other usages of these attribute when they are actually defined as data.pointer, namely in app, arc, locus and span.

Discussion

1 2 > >> (Page 1 of 2)
  • Lou Burnard
    Lou Burnard
    2012-03-15

    • milestone: --> 871209
     
  • BODARD Gabriel
    BODARD Gabriel
    2012-03-20

    Is there a proposal for the handling of @from and @to (when pointers) on other elements? Could they all, for example, be part of the same class (perhaps not named att.biblRange in this case)?

     
  • Lou Burnard
    Lou Burnard
    2012-04-17

    The semantics of @from and @to on arc and on biblScope differ greatly from the other two cases. The interpretation of @from (without @to) on span is quite different and probably not applicable to @from on app.
    We conclude there is no good reason to make a class here. We also note that the meaning of "the passage" in the spec for @from on span could be more clearly expressed, distinguishing the cases where it points to an empty element, an element, or a string-range or xpath.

     
  • Lou Burnard
    Lou Burnard
    2012-04-17

    • assigned_to: nobody --> kshawkin
     
  • Lou Burnard
    Lou Burnard
    2012-04-17

    Council agrees that we will review the text for clarificaqtion.

     
  • James Cummings
    James Cummings
    2012-09-19

    Lou to come up with a new proposal of wording. (council face 2 face 2012-09)

     
  • James Cummings
    James Cummings
    2012-09-19

    • milestone: 871209 --> GREEN
    • assigned_to: kshawkin --> louburnard
     
  • Lou Burnard
    Lou Burnard
    2013-01-04

    With the addition of @target to <span>, it seems plausible that we may eventually deprecate use of @from and @to on this element. This introduction has also necessitated some revision of the text explaining the significance of these three attributes. Council needs to review the text at AISP to see if this is now clearer.

     
  • Kevin Hawkins
    Kevin Hawkins
    2013-01-10

    In Ann Arbor (corresponding to the 2012-04-17 comment) we agreed that RW would clarify the defintion of <span> using wording from section 17.3 (#AISP). (See tips in the 2012-04-17 comment.)

    And then in Oxford we noted that this was still not done and agreed that KH and RW would do this together.

    Furthermore, in Oxford we also agreed that Lou would clarify the wording in the Guidelines (see the comment from 2012-09-19). I don't remember what exactly he was going to clarify, and he indicates in the comment at 2013-01-04 that he revised the text at #AISP, which correspond to the section 17.3 that KH and RW are supposed to pull text from. However, I don't see any recent revisions to AI-AnalyticMechanisms.xml. Perhaps he hasn't checked them in yet?

     
1 2 > >> (Page 1 of 2)