[sword-devel] Multi-xref sets
dmsmith at crosswire.org
Thu May 20 06:44:11 MST 2010
On May 20, 2010, at 9:04 AM, Karl Kleinpaste wrote:
> Chris Little <chrislit at crosswire.org> writes:
>> I'm wary of reusing <note> here, since I believe what Karl is talking
>> about are works where the references are in the body of the text, rather
>> than notes.
> ESV Matt 5:38 has this:
> <note n="y" osisID="Matt.5.38!crossReference.y" osisRef="Matt.5.38" type="crossReference">Cited from <reference osisRef="Exod.21.24">Ex. 21:24</reference>; <reference osisRef="Lev.24.20">Lev. 24:20</reference>; <reference osisRef="Deut.19.21">Deut. 19:21</reference></note>
This could also be <note n="y" type="crossReference">Cited from <reference osisRef="Exod.21.24 Lev.24.20 Deut.19.21">Exodus 21:24, Leviticus 24:20 and Deuteronomy 19:21</reference></note>
WRT the note attribute, the osisID is present for completeness. The both SWORD and JSword ignore it. Likewise for the osisRef. By convention, it is the verse that is referenced by the note.
In this rework, I deliberately used the full names of the books for the link text, but it could just have well been in German or Farsi. And I changed the punctuation and also introduced other verbage (i.e. "and").
While the n attribute is currently ignored by SWORD, it is the publisher's supplied footnote marker. Currently, SWORD uses 'x'.
> A ThML Bible module of mine is xref'd identically, in effect:
> <scripRef>Exodus 21:24; Lev. 24:20; Deut. 19:21</scripRef>
I'd like to see <scriptRef> have the passage or osisRef attribute. Preferably the latter as the content is not made of arbitrary/inconsistent book names and has a well defined syntax.
Without the attribute, JSword has to parse the body of the reference, assuming that it is something that can be parsed.
> In Xiphos, hovering on either module's "*x" annotation sends this complete
> verse list to the previewer, where each is then individually clickable to
> navigate there. In BibleCS, either of thees brings up an identical
> floater with the xref'd content.
> In commentary body content, that kind of ThML markup (with passage="..."
> qualifier) operates similarly, still giving the whole list, but sending it
> instead into Xiphos' verse list machinery, just as for what comes out of
> searches and multi-bookmarks. (I'm debating the wisdom of a change so
> that both Bible "*x" xrefs and body content xrefs use the verse list.)
> But in body content, the equivalent OSIS markup gives me a set that's only
> clickable one verse at a time. It's that inconsistency that's bothering me.
With Chris' suggestion you'd have either or both and even under user preference.
<seg type="x-refList" osisRef="Exod.21.24 Lev.24.20 Deut.19.21" n="x">Cited from <reference osisRef="Exod.21.24">Ex. 21:24</reference>; <reference osisRef="Lev.24.20">Lev. 24:20</reference>; <reference osisRef="Deut.19.21">Deut. 19:21</reference></seg>
More information about the sword-devel