[sword-devel] Can a single OSIS document serve to generate both a genbook and a commentary Sword modules ?

[Arnaud Vié]

Hi everyone,

To give come concrete context about my question, I've recently been
interested in a document I would like to import in sword to study it
properly, but which can be considered in two different ways : the visions
of Maria Valtorta.
For those not familiar with it, she was an italian nun from the early 20th
century who claimed to have very detailed visions about the life of Christ,
and put them all in written form, into a book that is known today as "The
Gospel as Revealed to Me".

Note that the discussion I'm starting here is not about the merits of the
text itself, but about how to best represent it in OSIS and sword modules.

There are two distinct ways to consider this text :

On the one hand, it would be practical to consider it a Commentary of the
Gospel, since most of these visions are very detailed accounts of scenes
that are also recounted in the Gospel. By making it a Commentary module,
all existing sword apps can easily synchronise windows so that people can
compare the vision to the original text from scriptures.

On the other hand, it's fundamentally a GenBook : it's entirely
non-canonical, has its own chapter structure, and some of its chapters
don't correlate to the scripture at all. So users should be able to open it
and read it like any regular book.

The OSIS spec itself does not make a firm distinction between GenBook and
Commentary, so I could technically just represent the document structure
like a genbook, and use annotateRef on  divs that can be mapped to passages
from the Gospel.
But will Sword support generating both a GenBook and a Commentary module
from the same OSIS source document, or are there limitations I should pay
attention to ?

I had a look at the source of the CalvinCommentaries module, which looks
similar to the structure I have in mind (except for its use of osisID
attribute on commentary blocks, which is explicitly forbidden by the OSIS
spec).
Would that be a good example to follow for such a document ?

Regards,

Arnaud
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://crosswire.org/pipermail/sword-devel/attachments/20260419/4eb1437e/attachment.htm>