[sword-devel] Links in OSIS GenBooks

DM Smith dmsmith555 at yahoo.com
Tue Nov 14 16:59:01 MST 2006

On Nov 14, 2006, at 6:20 PM, Daniel Hilton wrote:

> DM Smith wrote:
> [snip] ... when a prefix is absent, there are two
> different mechanisms for determining the document to which the osisRef
> refers. It is possible to map particular elements via the
> workPrefixDefault header element to a work. Lacking that an osisRef
> refers to the same work.
> You are right about that... In my own assumption I chose to ignore  
> the workPrefixDefault for simplicity's sake. But for full osis  
> compliance, both methods would have to be accounted for.
> If I am not mistaken, Sword currently assumes that all osisRefs are  
> to a
> bible of the user's choice...
> Is there a consesus that this is an acceptable assumption?  Or does  
> anyone agree that the original document should determine each  
> osisRef's target?

It is really not a question of whether it is acceptable. It isn't

It works for the most part in Bibles because they are mostly used for  
cross references and it works in commentaries because they are mostly  
referring to bibles.

The difficulty is more a question of how to move forward.

And yes for an OSIS document an unqualified osisRef is to the same  
document. So I guess the best way to proceed is to do the lookup in  
the current document, failing that fall back to the current behavior.

> ...Personally, I'd rather that we have the header for an OSIS work  
> so that
> we can use it's metadata rather than creating new mappings in the
> current conf.
> It would definitely be useful to preserve the osis header metadata,  
> but that doesn't solve the problem of mapping osisWork identifiers  
> to sword module names.  There could possibly be some way to encode  
> that into a <work> tag ( maybe <format type="x-sword">moduleName</ 
> format> ) if such a hack could be agreed upon, but the conf file  
> seemed to me the most appropriate place for that information, since  
> it is useful only in the Sword environment, and would be irrelevant  
> to the OSIS document in other contexts.

While an original OSIS document may refer to a particular version of  
the Bible, I think that Sword will continue to allow the user to pick  
the Bible they want to use. For example, a commentary may be based on  
the RSV, which is not available as a Sword module, but the user,  
being German, may want to read the verses in German from their  
favorite German Sword module.

It may be of interest that a particular reference is to a particular  
translation/version and perhaps that should be preserved. If so, I'd  
suggest changing the module creation program osis2mod (which handles  
Bibles and commentaries) to map the workIDs into module names.

BTW, where this interest me is that I am a developer for JSword and I  
know it does not handle it the way it should.

Also, I'd be willing to contribute changes to osis2mod as needed.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.crosswire.org/pipermail/sword-devel/attachments/20061114/f60f2098/attachment.html 

More information about the sword-devel mailing list