[osis-core] OsisRef problem -- more thoughts

[Patrick Durusau]

Harry,

I am trying to finish a chapter that is due (collected work ) by Monday 
but after that goes out I will start ramping back up on OSIS issues.

A quick response on the encoding issue.

I am not sure this is an encoding issue. What you want is behavior in 
the interface that is presented to the user. I have not tried this but 
don't see any reason why encountering a series of <reference> elements, 
cat the values following ":" to a comma delimited string and display as 
a hyperlink. The hyperlink points to a set of individual links (hidden 
from the user) which is activated upon selection of the main link and 
creates a popup window with each of the references displayed. 

Not suggesting to avoid changing the <reference> syntax (entirely at any 
rate!) because I can imagine uses where I would want to filter the 
references for display, which if they are encoded separately, seems like 
an easier task. Separate encoding also makes pointing from an index a 
little easier as well.

(If you are interested in what has consumed a number of cycles recently, 
take a look at the Just-In-Time-Trees (JITTs) paper at: 
http://www.sbl-site2.org/Extreme2002. Matt O'Donnell and I have 
developed a model where trees are asserted about markup at the time of 
processing, which allows a fuller range of structural encoding than is 
presently available with XML software. Not to mention DOM "Lite," 
DATATAG, error correction, dynamic datatyping, and a couple of other 
features. Have a demo in XSLT and am looking for someone to hack an XML 
parser for a more robust implementation of the idea.)

Hope this finds one and all in good health and spirits!

Patrick

Harry Plantinga wrote:

>Below I describe something that osisRefs can't do. It's something
>I use in the CCEL and have become quite fond of, though I'm aware
>others will probably consider it unclean somehow and not want to
>add it to OSIS. Still, I mention it for future consideration.
>
>Jonathan Edwards really gets into giving scripture references
>to support his position.  He might have a whole string of them --
>e.g.
>
>forewarned him of the fatal consequences of his refusal, from time to
>time; (<scripRef>Exod. chap. viii. 1, 2, 20, 21, ix. 1-5, 13-17, and x.
>3, 6</scripRef>)
>
>What I'd like is to link mark all of those as a single set of 
>scripture passages that will pop up in a single window if clicked
>upon.
>
>You can't do that with <reference> elements because osisRefs can
>take only a single osisID or range and you can't nest them. 
>
>Todd's suggestion below, 
>
>  <reference osisRef="Bible:Exod.8.1-Exod.8.2"/>
>  <reference osisRef="Bible:Exod.8.20-Exod.8.21"/>
>  <reference osisRef="Bible:Exod.9.1-Exod.9.5"/>
>  <reference osisRef="Bible:Exod.9.13-Exod.9.15"/>
>  <reference osisRef="Bible:Exod.10.3"/>
>  <reference osisRef="Bible:Exod.10.6">Exod. chap. 
>     viii. 1, 2, 20, 21; ix. 1-5, 13-17; and x. 3, 6</reference>
>
>doesn't do the job because if <reference> is treated as a link,
>only Exod.10.6 will be linked.
>
>One might also suggest something like this:
>
>  Exod. chap. viii. 
>  <reference osisRef="Bible:Exod.8.1-Exod.8.2">1, 2</reference>,
>  <reference osisRef="Bible:Exod.8.20-Exod.8.21">20, 21</reference>,
>  <reference osisRef="Bible:Exod.9.1-Exod.9.5"/>ix. 1-5</reference>,
>  <reference osisRef="Bible:Exod.9.13-Exod.9.15"/>13-17</reference>, and
>  <reference osisRef="Bible:Exod.10.3"/>x. 3</reference>,
>  <reference osisRef="Bible:Exod.10.6">6</reference>
>
>But that doesn't really do it either. Then you have to click on each
>separate reference to see the corresponding text. I want them all
>to appear with a single click in a single window. 
>
>The ideal solution to this problem (in my opinion warped though
>it be by practical considerations) would be to allow a list
>of ranges in osisRef, e.g.
>
>osisRef="Bible:Exod.8.1-Exod.8.2 Bible:Exod.8.20-Exod.8.21 ..."
>
>-Harry
>
>
>>-----Original Message-----
>>From: owner-osis-core@bibletechnologieswg.org 
>>[mailto:owner-osis-core@bibletechnologieswg.org] On Behalf Of 
>>Todd Tillinghast
>>Sent: Thursday, September 26, 2002 3:11 PM
>>To: osis-core@bibletechnologieswg.org
>>Subject: RE: [osis-core] OsisRef problem
>>
>>
>>Harry and Patrick,
>>
>>No need for a snippet.
>>
>>osisRef="Bible:Matt.1.3 Bible:Matt.1.4" IS invalid.
>>
>>ONLY osisID allows a list of ids (and "range" ids are ONLY 
>>allowed in osisRef). 
>>
>>You would have to either create two <reference> elements as in: 
>><reference osisRef="Bible:Matt.1.3"/>
>><reference osisRef="Bible:Matt.1.4"/>
>>
>>OR 
>> 
>>Create a range reference as in:
>>
>><reference osisRef="Bible:Matt.1.3-Matt.1.4"/>
>>
>>Todd
>>
>>>Harry,
>>>
>>>Can you forward just a snippet sufficient to duplicate the problem?
>>>
>>Not
>>
>>>sure why XML Spy would be choking on the attribute value.
>>>
>>>Will probably be upgrading to the "Professional" version 
>>>
>>this weekend
>>so
>>
>>>I can let  you know if it is a version specific problem. (I will try
>>>
>>to
>>
>>>duplicate the problem before and after I upgrade.)
>>>
>>>Patrick
>>>
>>>Harry Plantinga wrote:
>>>
>>>>We're just about there in creating valid OSIS documents in 
>>>>
>>conversion 
>>
>>>>from ThML documents.
>>>
>>>>The problem we are still having is in creating osisRefs that the
>>>>
>>schema
>>
>>>>will accept.  We're doing something like this:
>>>>
>>>>osisRef="Bible:Matt.1.3 Bible:Matt.1.4"
>>>>
>>>>The XML Spy parser seems to choke on such things.
>>>>
>>>>What should I be doing?
>>>>
>>>>-Harry
>>>>
>>>--
>>>Patrick Durusau
>>>Director of Research and Development
>>>Society of Biblical Literature
>>>pdurusau@emory.edu
>>>
>>>
>>

-- 
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
pdurusau@emory.edu