[sword-devel] Status of OSIS?

[Michael H]

The reason I'm not just using markdown for everything is that all these
works have references. And it all comes down to how to handle those
references.

ThML scripture references include the attribute "scripRef" which describes
a specific work for the reference, but I'm not aware that ThML has anything
like a "versification" awareness.  So you can accurately specify a
reference to the ESV2011 Psalm 23:6, but if the reader doesn't have the ESV
loaded, and they do have the Douay Rheims Challoner Revision, how would
that reference be handled? Does the click take them anywhere near where the
author of the book intended them to get to?

Psalm 23:6 isn't always Psalm 23:6.. It might be Ps. 23:6, or Ps. 23:7, or
Ps. 24:6 or Ps. 24:7. Since it is ambiguous, it's incomplete. and
incomplete shouldn't be allowed. As far as I can tell ThML isn't designed
to deal with versification confusion. Is there a convention or solution for
this (a master table of values that provides the mapping from 'ThML
scripRef version' to 'versification'?

OSIS has versification awareness:  OSIS at least has the versification
named in the work, and the versification value should be available at every
scripture reference, either by inheritance, or explicitly.

And that's the core reason that OSIS represents a better solution (to me.)
I'm not saying versification as I've described is supported in front ends
properly, but I am saying I can be specific to  the versification of the
reference in each work, making it possible for front ends to work.


On Tue, May 5, 2020 at 1:55 PM Karl Kleinpaste <karl at kleinpaste.org> wrote:

> On 5/5/20 1:36 PM, Michael H wrote:
>
> it's the only option listed for genbooks in the howto section
>
>
> Obligatory "ThML for everything." :-/
>
> I've never produced an OSIS module, but a quick check says I've produced
> 89 ThML modules.  And there's some new ones I'm due to produce (BIBdraft
> and BSBdraft need to be updated/obsoleted, since the final datasets were
> released.)
>
> Seriously, there's nothing stopping you from using any SourceType= that
> you like.
>
> (Yes, yes, I know...All For OSIS and OSIS For All.)
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20200505/82cec531/attachment.html>