<div dir="ltr"><div class="gmail_default" style="font-family:garamond,serif;font-size:large">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. <br><br>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? </div><div class="gmail_default" style="font-family:garamond,serif;font-size:large"><br>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'?<br><br>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. <br><br>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. <br><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, May 5, 2020 at 1:55 PM Karl Kleinpaste <<a href="mailto:karl@kleinpaste.org">karl@kleinpaste.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div>On 5/5/20 1:36 PM, Michael H wrote:<br>
</div>
<blockquote type="cite">it's
the only option listed for genbooks in the howto section</blockquote>
<font face="FreeSerif"><br>
Obligatory "ThML for everything." :-/<br>
<br>
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.)<br>
<br>
Seriously, there's nothing stopping you from using any SourceType=
that you like.<br>
<br>
(Yes, yes, I know...All For OSIS and OSIS For All.)<br>
</font>
</div>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" rel="noreferrer" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page</blockquote></div>