Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#506 Meaning of @corresp rather in dispute

GREEN
closed-fixed
Martin Holmes
5(default)
2013-12-23
2013-01-22
Martin Holmes
No

Recent discussions on Council and TEI-L suggest that there are two distinct views on how @corresp should be used.

Lou's strong view is that @corresp "really is meant only for cases where the target and the source are interchangeable, as for example where one translates the other. I also think it is meant to be bidirectional -- that is, if corresp(a.b), then corresp(b,a)."

The other view (held by me, and I think also by James) is that it's a general-purpose attribute for linking between two things that have virtually any relationship the encoder wishes to capture. The definition of the attribute would seem to support this lax view: "points to elements that correspond to the current element in some way".

I think we definitely need to clarify this, since the lax use of @corresp is widespread. If indeed Lou is right, and @corresp is a specialist attribute, then I think there is a clear and desperate need for a general-purpose global linking attribute -- @link, perhaps. There are many use-cases, but here is one:

In a personography representing the characters appearing in a Shakespeare play, an individual character may have different names in different versions. I need to specify, for each <persName> element inside <person>, which versions of the work it is used in. So using @corresp, I would do this:

<person xml:id="Polonius">
<persName corresp="ver:F1 ver:FM ver:Q2 ver:Q2M ver:EM">Polonius</persName>
<persName corresp="ver:Q1 ver:Q1M">Corambis</persName>
</person>

Other characters may only appear in some versions of the work, so the same attribute needs to be available on <person>.

Discussion

  • Lou Burnard
    Lou Burnard
    2013-03-31

    • milestone: --> AMBER
     
  • Lou Burnard
    Lou Burnard
    2013-03-31

    Agree that we need to clarify this question. Interesting use case too!

     
  • Lou Burnard
    Lou Burnard
    2013-06-18

    Looking at this use case again, wouldn't @source be more appropriate?

     
  • Martin Holmes
    Martin Holmes
    2013-06-18

    I think you're right about this use-case, now I look at it again. But I still think the confusion needs to be clarified.

     
  • James Cummings
    James Cummings
    2013-11-19

    • assigned_to: Martin Holmes
    • Group: AMBER --> GREEN
    • Priority: 5 --> 1(low)
     
  • James Cummings
    James Cummings
    2013-11-19

    At Oxford 2013-11 face-to-face: MH to create an example and run it by tei-council before adding to the Guideliness

     
  • Martin Holmes
    Martin Holmes
    2013-12-20

    Suggested the following example to Council 2013-12-20:

    <text> <!-- ... -->
    <body>
    <!-- ... -->
      <p>It remained to the glorious
        <persName id="a001" corresp="#n001"">Cromwell</persName>
        to tame this tiger...</p>
    <!-- ... -->
    </body>
    <!-- ... -->
    <back>
      <note id="n001" target="#a001">
        <p>
          The famed <persName>Oliver
          Cromwell</persName>, Lord Protector...
        </p>
      </note>
    </back> 
    </text>
    

    Awaiting feedback.

     
    Last edit: Martin Holmes 2013-12-20
  • Martin Holmes
    Martin Holmes
    2013-12-23

    Following some more suggestions and discussion, a new example was submitted to Council and there were no objections. This was added in rev 12720. If everything builds and looks OK, this ticket will be closed.

     
  • Martin Holmes
    Martin Holmes
    2013-12-23

    Final fix in rev 12721. Closing the ticket.

     
  • Martin Holmes
    Martin Holmes
    2013-12-23

    • status: open --> closed-fixed
    • Priority: 1(low) --> 5(default)