Difference between revisions of "Talk:OSIS Genbooks"

Revision as of 17:49, 16 March 2023

Internal structure of a Genbook module made using xml2gbs

xml2gbs 1.0 is the OSIS/ThML/TEI General Book module creation tool for the SWORD Project.

The XML multilevel div element structure is converted by xml2gbs to a module internal structure that seems to deviate from the strict specification for OSIS. For example, the output of mod2imp BaptistConfession1646 contains the following IMP format references:

$$$
$$$/Confession
$$$/Confession/Introduction
$$$/Confession/Section 1
$$$/Confession/Section 2
$$$/Confession/Section 3
$$$/Confession/Section 4
$$$/Confession/Section 5
$$$/Confession/Section 6
$$$/Confession/Section 7
$$$/Confession/Section 8
$$$/Confession/Section 9
$$$/Confession/Section 10
$$$/Confession/Section 11
$$$/Confession/Section 12
$$$/Confession/Section 13
$$$/Confession/Section 14
$$$/Confession/Section 15
$$$/Confession/Section 16
$$$/Confession/Section 17
$$$/Confession/Section 18
$$$/Confession/Section 19
$$$/Confession/Section 20
$$$/Confession/Section 21
$$$/Confession/Section 22
$$$/Confession/Section 23
$$$/Confession/Section 24
$$$/Confession/Section 25
$$$/Confession/Section 26
$$$/Confession/Section 27
$$$/Confession/Section 28
$$$/Confession/Section 29
$$$/Confession/Section 30
$$$/Confession/Section 31
$$$/Confession/Section 32
$$$/Confession/Section 33
$$$/Confession/Section 34
$$$/Confession/Section 35
$$$/Confession/Section 36
$$$/Confession/Section 37
$$$/Confession/Section 38
$$$/Confession/Section 39
$$$/Confession/Section 40
$$$/Confession/Section 41
$$$/Confession/Section 42
$$$/Confession/Section 43
$$$/Confession/Section 44
$$$/Confession/Section 45
$$$/Confession/Section 46
$$$/Confession/Section 47
$$$/Confession/Section 48
$$$/Confession/Section 49
$$$/Confession/Section 50
$$$/Confession/Section 51
$$$/Confession/Section 52
$$$/Confession/Conclusion
$$$/Appendix
$$$/Appendix/Appx_Introduction
$$$/Appendix/Appx_Section 1
$$$/Appendix/Appx_Section 2
$$$/Appendix/Appx_Section 3
$$$/Appendix/Appx_Section 4
$$$/Appendix/Appx_Section 5
$$$/Appendix/Appx_Section 6
$$$/Appendix/Appx_Section 7
$$$/Appendix/Appx_Section 8
$$$/Appendix/Appx_Section 9
$$$/Appendix/Appx_Section 10
$$$/Appendix/Appx_Section 11
$$$/Appendix/Appx_Section 12
$$$/Appendix/Appx_Section 13
$$$/Appendix/Appx_Section 14
$$$/Appendix/Appx_Section 15
$$$/Appendix/Appx_Section 16
$$$/Appendix/Appx_Section 17
$$$/Appendix/Appx_Section 18
$$$/Appendix/Appx_Section 19
$$$/Appendix/Appx_Section 20
$$$/Appendix/Appx_Section 21
$$$/Appendix/Appx_Section 22

Observe that the level 1 div elements with type="majorSection" had osisID="Confession" and osisID="Appendix" in the source XML file. Likewise, the level 2 div elements with type="chapter" had osisID="Introduction" and osisID="Section 1", etc. The use of the / separator within the module structure is why this separator is required in each internal osisRef string in order to make it work as a link. David Haslam (talk) 08:49, 25 June 2020 (UTC)

Did the baptist already post the document in an xml format somewhere? A brief search located other formats such as pdf from The New Orleans Baptist Theological seminary (NOBTS), html from the reformed reader, html from the puritans mind, something for 32 Bit Winows Operating systems, etc. Also, the SWORD mod2osis utility discouraged recovering the original file (osis/xml). If the xml is not on the net, does it make sense to assist the baptist to publish an xml version that could then be read by SWORD? Individuals not belonging to a baptist church may not be the best candidates for editing the confession.

As a workaround to not having the xml file, the mod2imp output and a bdt file in the module install location (/usr/share/sword/) were processed instead. Unexpected internal structure was observed in these other files, but in a different way. In the bdt file and mod2imp output, the table of contents was split between two <list> tags, one for each level 1 section (Confession; Appendix). The unexpected thing was that no div tag was observed. Reference 1 below predicted a

tag for the table of contents.

Rudimentary software was made to parse these other files (bdt / mod2imp), but the parsing quit early. The early quit was assumed to be caused by not having a root tag in those files. A root tag was temporarily added to the local copy of the bdt file and then the parsing progressed as expected. Then the new root tag was removed to return to the original configuration.

reference 1: OSIS Users Manual (OSIS Schema 2.1.1) By Patrick Durusau; table of contents was mentioned in section 7.5. "The div Element" and Appendix F "USFM to OSIS Mapping"

Gregs650 (talk) 23:34, 14 March 2023 (UTC)

Example OSIS Genbook - test

The example/tutorial was developed a little more, but is not yet complete as described at this link. No table of contents was observed for this module in the bishop app after installation.

--Gregs650 (talk) 22:13, 28 February 2023 (UTC)

bug report duration and focus

The subsection “Making a Genbook module” noted a Windows bug. Some details for the bug could help know when the bug report can be removed. Otherwise, the bug's duration could be too long, since no one knew to remove it (Leviticus 19:15-16).

If the bug was reported to the crosswire support page, a reference to find the description would be great. The description could help clarify if it involves an internal modification to SWORD software, or if the bug is suitable to repost on a software board/forum. --Gregs650 (talk) 19:23, 1 March 2023 (UTC)

deleted

Comments / question on the schema were deleted. More learning may resolve the questions.