!RE: [osis-core] Alternat text

[Patrick Durusau]

Todd,

What you describe looks a lot like <rdg> and <rdgGrp> (the latter being 
a new element to contain <rdg>. Note that <rdg> does not have <title>.

But, further note that in the one or two editions I have looked at, the 
text is not presented as alternative readings, at least in the 
traditional sense of the word. That is to say that there is additional 
text, not alternative text that forms the material we want to mark. 
(sorry, no pun intended)

In other words, I think we need to distinguish between cases where there 
is truly an alternative text,

<text1>When in the beginning...</text1>

<text2>Long ago and far away...</text2>

versus a text where additional material is presented that is not found 
in the "main" text.

Yes, I realize that the entire text could be considered as a base text 
that duplicates up to that point and the "text" of the main text after 
than is null but that is more of a theoretical concern than a practical 
one.

Certainly don't want:

<verse osisID="kjv.mark.16.9"></verse>
<verse osisID="niv.mark.16.9">When Jesus rose early on the first 
day...</verse>

Is there some reason why you object to the use of a <div> to set off the 
alternative ending and some attribute value to mark it as an alternative?

Hope you are having a great day!

Patrick

Todd Tillinghast wrote:
> Patrick,
> 
> There are three cases for the end of Mark:
> 1) There is a main version and a secondary version (often rendered in
> brackets).
> 2) There are two equal alternant versions.
> 3) There is a main version and the alternant is in a footnote (this case
> is reasonably handled)
> 
> There are other cases where the same situations as the end of Mark exist
> AND there is the case where there is not alternant but the text is
> "tentative".
> 
> It seems that a container that holds all of the alternant versions and
> marks them based on their alternant status would to the best.
> 
> <alternantText> <!-- one main and one secondary version -->
>    <alternant type="primary">...</alternant>
>    <alternant type="secondary">...</alternant>
> </alternantText>
> 
> <alternantText> <!-- two equal alternant versions -->
>    <alternant type="primary">...</alternant>
>    <alternant type="primary">...</alternant>
> </alternantText>
> 
> <alternantText>
>    <alternant type="tenative">...</alternant> <!-- for the case of
> "tentative" text, I am sure "tentative" is the wrong word for it -->
> </alternantText>
> 
> You could put <note> and <title> elements within <alternantText> and
> <alternant> (rendering process could choose to render notes that are
> direct children of <alternantText> or <alternant> inline in the footer
> based on style preferences).
> 
> Todd
> 
> 
>>-----Original Message-----
>>From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
>>admin@bibletechnologieswg.org] On Behalf Of Patrick Durusau
>>Sent: Tuesday, February 24, 2004 1:37 PM
>>To: osis-core@bibletechnologieswg.org
>>Subject: Re: [osis-core] Alternat text
>>
>>Todd,
>>
>>Todd Tillinghast wrote:
>>
>>>We talked about but did not conclude anything regarding alternant or
>>>"tentative" text.
>>>
>>>Alternant endings to Mark and other places where alternant text is
>>>places in the main flow of the text.
>>>
>>>Can we find a solution for this one?
>>>
>>
>>Sure, don't encode alternate endings. :-)
>>
>>Seriously, looked at the NIV, which separate the alternate ending with
> 
> a
> 
>>bar across the column and a note that reads: "[The earliest
> 
> manuscripts
> 
>>and some other ancient witnesses don't have Mark.16-9-20.]"
>>
>>So, looks like an addition <div>, since it is clearly setoff from the
>>principal text. The portion that reads: "[The earliest...]" looks like
> 
> a
> 
>>note to me. Does display inline, which is odd but I don't know of any
>>reason why that could not be done.
>>
>>Since the alternate endings are well known, don't we know that a
>>reference to Mark.16.19 or higher is a reference to a non-standard
>>ending of Mark?
>>
>>Hope you are having a great day!
>>
>>Patrick
>>
>>
>>
>>
>>>Todd
>>>
>>>_______________________________________________
>>>osis-core mailing list
>>>osis-core@bibletechnologieswg.org
>>>http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
>>>
>>
>>
>>--
>>Patrick Durusau
>>Director of Research and Development
>>Society of Biblical Literature
>>Patrick.Durusau@sbl-site.org
>>Chair, V1 - Text Processing: Office and Publishing Systems Interface
>>Co-Editor, ISO 13250, Topic Maps -- Reference Model
>>
>>Topic Maps: Human, not artificial, intelligence at work!
>>
>>
>>_______________________________________________
>>osis-core mailing list
>>osis-core@bibletechnologieswg.org
>>http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
> 
> 
> _______________________________________________
> osis-core mailing list
> osis-core@bibletechnologieswg.org
> http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
> 


-- 
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
Patrick.Durusau@sbl-site.org
Chair, V1 - Text Processing: Office and Publishing Systems Interface
Co-Editor, ISO 13250, Topic Maps -- Reference Model

Topic Maps: Human, not artificial, intelligence at work!