> On Jul 10, 2025, at 2:28 AM, pinoaffe <pinoa...@gmail.com> wrote:
>
> DM Smith <dmsm...@crosswire.org> writes:
>> OSIS recommends <div type=“bookGroup”> to surround a collection of
>> books. But osis2mod does not require this. (Should it? Should it make
>> any assumptions about a book group?)
> bookgroups can be nested within bookgroups and can refer to any grouping
> a specific bible might want to include, e.g. "Prophets", so I'd be weary
> of making assumptions about book groups.
I had forgotten that bookGroup can be nested. Thanks!!
Earlier osis2mod had code making assumptions about majorSection, which Peter
wisely removed.
>
> I think it might be worthwhile to introduce an osis "testament"
> convention along the lines of <div type="x-testament">, or x-testament-1
> and x-testament-2 which osis2mod can interpret, rather than relying on
> heuristics and guesswork, though maybe that latter approach could be
> fruitful too.
The issue with heuristics is that they essentially enforce assumptions, which
may very well be wrong.
The module team has a usfm2osis.py to convert USFM to OSIS. Michael also has
one. The nature of USFM is that it’s goal is presentation not OSIS’s nature of
semantic markup. I don’t know how that transformation handles intro material.
I’m pretty sure neither has a begin/end testament construct. It is a simple
thing to manually add such after transformation if that fits with one’s
workflow.
I think it’s a shortcoming of the OSIS spec that it is flexible when marking up
testaments. Your suggestion of explicitly marking testament may be the only
real solution. In the KJV’s OSIS it uses type=“bookGroup”
subType=“x-{testament}” where {testament} is OT or NT. It also uses x-DC for
the apocrypha.
I’m wondering whether SWORD’s [ Testament 1|2 Heading ] could/should be
represented as an OSIS ID, type or subType.
Should a mechanism be imposed on OSIS creators? We’ve resisted that as much as
possible.
— DM
>
> May the Lord bless you,
> pinoaffe
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
