Talk:OSIS 211 CR

Introduction

Chris, please add an introductory description to the top of this page. David Haslam 17:56, 12 December 2010 (UTC)

Done - based on Troy's post in the Google group for Open Scriptures. David Haslam 08:11, 4 August 2011 (MDT)

New Features

Troy outlined a couple new features to handle OSIS fragments: https://groups.google.com/d/msg/openscriptures/kygOM0yPHL8/3232AYNQsSIJ Including:

• Shadow/virtual elements
• Remotely referenceable header

David Troidl also had a list of suggestions: https://groups.google.com/d/topic/openscriptures/1lyqiBSUCh8/discussion

--Westonruter 00:23, 10 August 2011 (MDT)

Next SBL meeting?

The SBL meeting mentioned in the opening paragraph is now past. When is the next meeting/opportunity to review OSIS improvements? David Haslam 05:30, 20 October 2012 (MDT)

Corrections to the OSIS Reference Manual

Maybe we should include a separate section to address Corrections to the OSIS Reference Manual? David Haslam 05:37, 20 October 2012 (MDT)

Don't get mixed up

As the OSIS element is called divineName and the USFM equivalent is called Name of Deity, this observation is recorded to serve as a caution against getting abbreviations mixed up when referring to either in emails, etc. (cf. the USFM tag par is \nd_...\nd* ) David Haslam 07:39, 22 February 2014 (MST)

The <speaker> element and poetry markup?

The line group element <lg> does not allow the <speaker> element unless it's within a line element <l>.
I've recently come across OSIS lines generated by usfm2osis.py where the <speaker> element occurred directly within <lg>.

What's the recommended solution or hack? Is a change to OSIS required to facilitate this use? David Haslam 13:59, 2 January 2015 (MST)

The <speaker> element was converted from the USFM tag \sp_text which is described as Speaker Identification (e.g. Job and Song of Songs). It's listed under Titles, Headings and Labels in the USFM Reference. Surely this implies that when this tag is encountered, it should first terminate any existing poetry line group? After all, a title is not part of the poetry in any normal sense. David Haslam 01:58, 3 January 2015 (MST)

If I'm right, then even when \sp_text is found between poetry lines marked using \q#_text, the poetry line element should also be terminated by </l> before the <speaker> element rather than after it (as happens now). The line group should also be terminated. This has a major bearing on the python conversion script. David Haslam 02:12, 3 January 2015 (MST)

Likewise, if \sp_text is found while processing a USFM list, the last item element and the list element should be terminated before rather than after the <speaker> element (as happens now). David Haslam 02:49, 3 January 2015 (MST)

Use only 3 tilde for signed edits on the main page

Talk pages are for discussing improvements to the main page. Signed edits are normally used only in talk pages, in which case it's convenient to use the 4 tilde method of signing, which includes the date & time stamp of the edit. Signed edits on the main page don't really need a time stamp, so the 3 tilde method should suffice. David Haslam (talk) 11:09, 15 March 2016 (MDT)

Even I forgot my own advice and had to correct my recent edits! David Haslam (talk) 05:21, 4 February 2017 (MST)

Classifying names in the Bible

I've begun to classify all the names in the KJV text.
So far, I've come up with at least the following possible types of name (excluding divineName).

Type of name

astronomic

calendric

divinity

ethnic

geographic

hypothetic

language

letter

metaphoric

nonhuman

object

person

philosophic

politic

pronouncement

religious

Some of these types may require several subTypes. This list may be extended as I make further progress.

Observations

Some words may be both a name and not a name in different passages.

Example: "Eli" the priest in 1 Samuel, but the Aramaic word for "My God" in Matthew 27:46 – Jesus' cry of dereliction.
David Haslam (talk) 02:34, 4 February 2017 (MST)

Some words are both the name of a person as well as a geographical name.

Example: "Dan" the son of Jacob and "Dan" the territory allocated for the tribe of "Dan" to settle in.
This example illustrates that such a name can also be ethnic.
Deciding which is which can be quite difficult in some places.
David Haslam (talk) 08:25, 4 February 2017 (MST)

How does one validate the CrossWire OSIS schema?

How does one validate the schema itself? i.e. osisCore.2.1.1-cw-latest.xsd David Haslam (talk) 03:20, 10 February 2017 (MST)

Marking multiword names?

Do we really need two name elements in this example?

<name type="person" regular="Pilate">Pontius <name type="person">Pilate</name></name>

or would this suffice?

<name type="person" regular="Pilate">Pontius Pilate</name>

Note that there's no geographic type in this name. David Haslam (talk) 02:51, 20 February 2017 (MST)

A milestone form of the div element ?

It's become apparent that some OSIS based SWORD modules created using Haiola for the [eBible.org eBible.org] repository contain the milestone form of the div element. Michael uses his own modified OSIS schema (called MOSIS) to validate his XML.

We need to start a discussion on this. 02:41, 8 March 2017 (MST)

Elements that are ‘milestoneable’ in the OSIS 2.1.1 schema are:

• abbr • chapter • closer • foreign • l • lg • q • salute • seg • signed • speech • verse

Observe that this does not include the div element. David Haslam (talk) 02:43, 8 March 2017 (MST)

<contributor> in <work>

The issue with contributor in work was discovered while I was doing some analysis on the morphhb project. See https://github.com/openscriptures/morphhb/issues/48

--David Haslam (talk) 12:32, 28 December 2017 (MST)

Nested seg elements ?

OSIS 2.1.1 explicitly allows a seg element to contain a seg element. Has the SWORD API been designed to adequately cope with such nested seg elements?

e.g. Would the following nested seg structure cause any unexpected interactions between these two module option settings?

• GlobalOptionFilter=OSISMorphSegmentation
• GlobalOptionFilter=OSISVariants

<verse osisID="Ps.10.10">
	<w type="x-ketiv">
		<seg type="x-variant" subType="x-1">
			<seg type="x-morph">ו</seg>
			<seg type="x-morph">דכה</seg>
		</seg>
	</w>
	<w type="x-qere" >
		<seg type="x-variant" subType="x-2">
			<seg type="x-morph">יִדְכֶּ֥ה</seg>
		</seg>
	</w>
	<w>
		<seg type="x-morph">יָשֹׁ֑חַ</seg>
	</w>
	<w>
		<seg type="x-morph">וְ</seg>
		<seg type="x-morph">נָפַ֥ל</seg>
	</w>
	<w>
		<seg type="x-morph">בַּ֝</seg>
		<seg type="x-morph">עֲצוּמָ֗י</seg>
		<seg type="x-morph">ו</seg>
	</w>
	<w type="x-ketiv">
		<seg type="x-variant" subType="x-1">
			<seg type="x-morph">חלכאים</seg>
		</seg>
	</w>
	<w type="x-qere" >
		<seg type="x-variant" subType="x-2">
			<seg type="x-morph">חֵ֣יל</seg>
		</seg>
	</w>
	<w type="x-qere" >
		<seg type="x-variant" subType="x-2">
			<seg type="x-morph">כָּאִֽים</seg>
			<seg type="x-punct" subType="x-sofPasuq">׃</seg>
		</seg>
	</w>
</verse>

David Haslam (talk) 17:11, 9 March 2020 (UTC)

Correct the osisRef syntax for a non-verse-keyed OSIS module

The line in the file osisCore.2.1.1-cw-latest.xsd that requires a change is this one (#1500) in the definition of osisRefRegex:

			<xs:pattern value="(((\p{L}|\p{N}|_)+)((\.(\p{L}|\p{N}|_)+)*)?:)?((\p{L}|\p{N}|_|(\\[^\s]))+)(\.(\p{L}|\p{N}|_|(\\[^\s]))*)*(!((\p{L}|\p{N}|_|(\\[^\s]))+)((\.(\p{L}|\p{N}|_|(\\[^\s]))+)*)?)?(@(cp\[(\p{Nd})*\]|s\[(\p{L}|\p{N})+\](\[(\p{N})+\])?))?(\-((((\p{L}|\p{N}|_|(\\[^\s]))+)(\.(\p{L}|\p{N}|_|(\\[^\s]))*)*)+)(!((\p{L}|\p{N}|_|(\\[^\s]))+)((\.(\p{L}|\p{N}|_|(\\[^\s]))+)*)?)?(@(cp\[(\p{Nd})*\]|s\[(\p{L}|\p{N})+\](\[(\p{N})+\])?))?)?"/>

One or more of the dot separators \. must be what causes the solidus separator / to fail validation.

David Haslam (talk) 21:18, 22 June 2020 (UTC)