#267 add <add> and <del> for encoding of manuscripts

Tite
open
Kevin Hawkins
Tite (11)
5
2014-08-18
2010-12-14
Kevin Hawkins
No

Tite is missing both <add> and <del>. These are needed to support encoding of handwritten source material. The member survey that led to Tite detected a desire for vendor encoding of manuscripts, and it was an oversight not to include this in Tite.

In addition to adding them to the schema, some prose documentation will need to be written and inserted into the prose at an appropriate location.

Discussion

  • if you have <add> and <del>, don't you need <choice>, <sic>, <corr> etc as well? not to mention <addSpan> and <delSpan>.

     
  • Kevin Hawkins
    Kevin Hawkins
    2011-02-21

    I asked for comments from Council on this by today but hadn't noticed Sebastian's comment. Sorry about that.

    I believe the reason for including on <add> and <del> but not <sic> or <corr> is that a vendor would only want to determine what was added or deleted but not make determinations of which is correct. You can also make do without <choice> (like we did before P5). As for <addSpan> and <delSpan>, these would be useful in cases where an addition or deletion spans some other element to be tagged, but it also complicates things for the vendor. I imagine vendors would prefer to start and stop an <add> or <del> on each side of the intervening tag, and maybe this would be good enough for clients as well. Might need to think about this some more.

     
  • Lou Burnard
    Lou Burnard
    2011-03-20

    • assigned_to: nobody --> kshawkin
     
  • Lou Burnard
    Lou Burnard
    2011-03-20

    • milestone: --> Tite
     
  • Kevin Hawkins
    Kevin Hawkins
    2011-09-19

    In recent discussion on the tei-council list, Sebastian wrote:

    If the Tite users want <add> and <del>, sure, go and ahead and give it to them. [. . .] If Tite plans to cover hand-written material, I personally think that's such a huge extra burden that the advantages of a standardized Tite are negligible. I think I'd prefer a TiteMS, which is Tite + Handwrititing, rather than giving <add> and <del> to the vast majority of Tite users.

    And James wrote:

    Though there may have been a desire for vendor encoding of manuscripts, this comes with so much overhead that makes Tite as it is unsuitable. (I.e. if we were making TiteMS then there are a lot more things I'd add rather than just add/del.) I would suggest that where manuscripts are concerned a bespoke customisation be agreed with the vendor (this could be Tite + add/del, or entirely different).

     
  • Kevin Hawkins
    Kevin Hawkins
    2011-10-04

    Apex added <add> and <del> but not <sic>, <corr>. and <choice>. Vendors are trying to make as few interpretations as possible. They have not added <addSpan> and <delSpan>, though this is probably just because they haven't needed them yet. Need to consider adding <addSpan> and <delSpan> as well.

     
  • Kevin Hawkins
    Kevin Hawkins
    2011-11-02

    Added <add> and <del> at revision 9559. Keep this ticket open for consideration of <addSpan> and <delSpan>.

     
  • Paul Schaffner
    Paul Schaffner
    2013-11-13

    Even without working with manuscripts, and confining ourselves largely to capturing books as printed, we found the need in TCP to add ADD DEL and CHOICE (the latter confined to a limited content model of ADD DEL ABBR EXPAN). These tend to make things easier for vendors, not harder, since they allow a ready way to capture hand-corrected or hand-deleted books for which there is no other obvious mechanism open to the vendors.