#485 add element rs as member of model.linePart

AMBER
closed-rejected
None
5(default)
2014-11-18
2013-11-26
No

In order to mark up general references on the documentary level while using <line>, <rs> should be made a member of model.linePart.

Key questions to be considered:
Should the user be allowed to mix documentary markup with elements of a rather 'interpretative' encoding?
How about the pitfalls of overlapping structures?

Citing Gerrit Brüning from the mailing list:

<line> was invented to allow a rigorously documentary encoding.
It was not invented to draw a fix line between a purely documentary
and a more 'interpretative' encoding. (There are people who even deny
the mere differentiation.)

Discussion

  • Oliver Gasperlin

    Just want to add, that there are rather 'interpretative' elements already available within <line> by way of model.global, for example <interp> or <index> or all the elements from model.global.spoken.
    So <rs> wouldn't be a real revolution within the content model.

     
  • James Cummings

    James Cummings - 2014-05-19

    Assigning to Martin Holmes to triage and report to council

     
  • James Cummings

    James Cummings - 2014-05-19
    • assigned_to: Martin Holmes
     
  • Martin Holmes

    Martin Holmes - 2014-11-18

    Council 2014-06 (http://www.tei-c.org/Activities/Council/Meetings/tcm60.xml#RemainingAmberFR) notes that GB is wrong to say that "<line> was not invented to draw a fix line between a purely documentary and a more 'interpretative' encoding"; in fact it was invented for purely that purpose. Therefore we reject the ticket. Another ticket has been opened (FR [#515]) to address possible confusion arising out of the content model of <line>.

     

    Related

    Feature Requests: #515


    Last edit: Martin Holmes 2014-11-18
  • Martin Holmes

    Martin Holmes - 2014-11-18
    • status: open --> closed-rejected
     

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

Sign up for the SourceForge newsletter:





No, thanks