[tei-council] <witStart>, <witEnd>, <lacunaStart> and <lacunaEnd>

[Mylonas, Elli]

yes, that's a good point - not a problem for people encoding each witness
as a separate document, (probably using lacunaStart/end). but otherwise
it's an issue.

 thanks,  --elli


On Thu, Jun 26, 2014 at 6:44 PM, Hugh Cayless <philomousos at gmail.com> wrote:

> There would have to be a mechanism for identifying which witness each one
> belonged to if they occurred on their own in the text.
>
> Sent from my phone.
>
> > On Jun 26, 2014, at 18:06, "Mylonas, Elli" <elli_mylonas at brown.edu>
> wrote:
> >
> > Hi all:
> >
> > I am writing you to ask for comments on the following TEI feature
> request:
> >
> > The elements listed above, <witStart>, <witEnd>, <lacunaStart> and
> > <lacunaEnd>, are currently allowed only in  <rdg> or <lem> inside <app>.
> >
> > We have had requests to allow these milestone-like elements in the main
> > part of a text - either because witnesses are being encoded separately,
> or
> > because collation is being done automatically, without indicating
> thinking
> > of it as a traditional app crit.
> >
> > solutions:
> > 1. Elegance: add  <witStart>, <witEnd>, <lacunaStart> and <lacunaEnd> to
> > the milestoneLike model and remove them from textcrit.
> > 2. Functionality: use anchor with a type for this purpose.
> >
> > One more point - I see a difference between <lacunaStart> and <lacunaEnd>
> > which could apply to features of a main text and <witStart> and <witEnd>
> > which seem to belong in a main text but refer to other witnesses.
> >
> > I think I cast my vote for opening them up. Comments?
> >
> > thanks, --elli
> > --
> > tei-council mailing list
> > tei-council at lists.village.Virginia.EDU
> > http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
> >
> > PLEASE NOTE: postings to this list are publicly archived
>