#443 @resp should be a member of att.global

GREEN
closed-fixed
6
2014-12-10
2013-03-11
No

This suggestion was originally raised in 2005, and closed because the discussion stalled: http://purl.org/tei/fr/1173968. The idea came up again on the Council list here:

http://lists.village.virginia.edu/pipermail/tei-council/2013/017238.html

I think there are strong arguments for the use of @resp in a wide range of different contexts. As Gaby says, " I can't imagine any element that I would not want to be able to say either who is responsible for the decisions it represents, or from what publication the information so tagged comes."

Related

Feature Requests: #443
Feature Requests: #536

Discussion

<< < 1 2 3 4 5 > >> (Page 2 of 5)
  • Martin Holmes

    Martin Holmes - 2013-05-31
    • assigned_to: Martin Holmes
     
  • Martin Holmes

    Martin Holmes - 2013-05-31

    Jennifer Drouin has a case for <castList>, in which "the list of characters in the play is not included in the manuscript given to me by the author, but we thought that the published version of the play should have a list of characters nonetheless (as is, in fact, the case of most of Shakespeare's plays in which the dramatis personae list is an invention of the editor, not found in the original text)."

    She also notes that she has had to correct some stage directions, and would like to use @resp on <stage>.

     
    Last edit: Martin Holmes 2013-05-31
  • Martin Holmes

    Martin Holmes - 2013-05-31

    Expanding on my previous post: in our Nxaʔamxcín dictionary project, we need to ascribe responsibility for:

    • Individual pronunciations of an item (<pron>)
    • Transcriptions of those pronunciations made in the field (for which we use <seg> inside <pron>)
    • Transcriptions which are later narrow versions of phonemic field transcriptions, or phonemic versions of narrow field transcriptions (<seg>)
    • Definitions for words and phrases provided by informants in the field and later (<sense>, <def>)
    • Example phrases and sentences provided by informants, as well as their definitions, in-the-field transcriptions, and derived transcriptions (<cit>, <quote>, <seg>)
    • Division of a form into individual morphemes (<hyph>, <m>)
    • Identification of a component of a definition as a suitable short gloss for the entry (<gloss>)
    • Assignment of feature structure information to an entry (<fs>)

    This may seem excessively pernickety, but this is a project with a 50-year history, and takes place in a cultural context in which appropriate acknowledgement and attribution of contributions, elder authority, etc. are profoundly important.

     
  • Laurent Romary

    Laurent Romary - 2013-05-31

    What Martin says should be true for any serious dictionary project with more than one editing person. It is very important to maintain a source document that traces back contributions.

     
  • Laura Estill

    Laura Estill - 2013-06-09

    I would like to be able to use @resp on \<label>. For instance, I have a seventeenth-century manuscript with some labels from the 17th C and some from the 19th C. Some could also be added by archivists.

     
  • Lou Burnard

    Lou Burnard - 2013-06-10

    Are these labels or seals or stamps? Anyway, are you describing them as
    part of your <msDesc> or are you actually planning to transcribe them
    as part of the text?

     
    Last edit: BODARD Gabriel 2013-06-27
    • Laura Estill

      Laura Estill - 2013-06-11

      I'm transcribing them as part of the text (though also mentioning them in the header). They are not seals or stamps.

       
  • Scott Vanderbilt

    I have many, many instances in RIB where various items of metadata, as well as transcriptions, translations, notes, and entries in bibliography and apparatus where @source would be immensely useful in attributing additions and modifications thereto. @resp is not ideal, not only because it is one level of indirection away from the actual authority (usu. a bibliographical item), but also because it is not sufficiently granular when there may be multiple bibl. entries from the same author/editor; @resp alone won't unambiguously point to the actual authoritative reference.

    While I have no stand on the global vs. non-global argument, I would very much like to see @source on the following (at the very least): <objectType>, <material>, <dimensions>, <condition>, <layout>, <handnote>, <decoNote>, <provenance>, <location>, <rdg>, and <bibl>.

     
  • Martin Holmes

    Martin Holmes - 2013-06-19

    Thanks Scott. I would say that wherever there's an argument for @source, the argument can also be applied to @resp, because wherever attribution is being assigned to a bibliographical item, it might perfectly well be assigned to an individual editor who made a decision not based on antecedent authority.

     
  • BODARD Gabriel

    BODARD Gabriel - 2013-06-27

    I think I would like to start by, (1) pretty much right now adding @source to att.responsibility, so that it is available everywhere that @resp is, which I believe is pretty uncontroversial (I at least am completely convinced by Martin's arguments to this effect); and then, (2) more luxuriously gradually adding that class to more elements/classes as argued elsewhere in this ticket. The former would have the benefit of making @source available on <rdg> etc., which would be incredibly useful, and it wouldn't prejudice the ongoing discussion of the latter.

    Incidentally: why do <respons> and <space> have @resp defined separately, rather than membership of att.responsibility? Is it just so that they don't inherit @cert? We have a better way to do this now, don't we? (I ask because I think I'd want them both to inherit @source as well...)

     
<< < 1 2 3 4 5 > >> (Page 2 of 5)

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks