[osis-core] OSISScripture_01094 with new regex.

Todd Tillinghast osis-core@bibletechnologieswg.org
Wed, 17 Apr 2002 06:40:28 -0500


I am afraid I caused some confusion in my examples.  I just use a file
that looks like what I sent in the email to validate.  ALL of the
current instance of elements in OSIS use referenceType, milestoneID, and
milestoneIDREF as attributes or elements.

So is valid
<reference refStart="Gen.1.20-22">Genesis 1:20-22</reference> 
However, while this is valid what you probably mean is 
<reference targetStart="Gen.1.20" targetEnd"Gen.1.22">Genesis
1:20-22</reference>
The reason "Gen.1.20-22" is valid is for cases where the people creating
the reference system did not have a distinct verse 20, 21 and 22 but
rather choose to call the set of text traditionally know as verse 20,
21, and 22 by a new name 20-22.  The new name could as easily be called
"elephant" and the name that appears to be a range in not.  I encoders
want to express a range the should use the form shown second above.  (If
you have a printed TEV Bible, Gen.20.17-18 and Matt.1.2-6a are good
examples of these cases.)

Further, the reference system is defined in the "work" attribute of the
<text> element.  If the reference system of a reference is not the one
specified in <text> then the reference system must be included in the
reference attribute.

Ex from Josephus ant.2.3.1:

<text work="Josephus">
...
	<div type="x-section" refStart="ant.2.3.1">
		<p>1. NOW these ...<note noteType="explanation"><p>....
also in all our copies, <reference
refStart="Bible.Cath..Gen.37.10">Genesis
37:10</reference>.</p></note>...</p>
	</div>
...
</text>

Since the default reference system is declared as "Josephus" in <text>
the references to Josephus can default the reference system but the
references to the Bible must specify the reference system.  It would
also be valid for the Josephus references to be expressed as
"Josephus..ant.2.3.1".  Note that ".." separates the reference system
from the simple part of the reference.  If ".." is not present then the
reference system is assumed to be the default reference system.


To reduce the confusion the following are valid:
<reference targetStart="Bible.KJV..Gen"/>
<reference targetStart="Bible.KJV..Gen" targetEnd="Bible.KJV..Rev/>
(NOTE: This is a range that includes the entire KJV Bible.
<reference targetStart="Bible.KJV.A..Gen.a-a.1.1-1"/>
<reference targetStart="Bible.B..Gen"/>
<reference targetStart="Gen.20.16">Genesis 20:16</reference>
<reference targetStart="Gen.20.13" targetEnd="Gen.20.16">Genesis
20:13-16</reference> (NOTE: This is a range.)
<reference targetStart="Gen.20.17-18"/> (NOTE: this is not a range!)
<reference targetStart="Gen.20.13" targetEnd="Gen.20.17-18"/> (NOTE:
this is a range from the verse known as Gen 20:13 to the verse known as
Gen 20:17-18.)
<reference targetStart="Gen.20.17-18.Q-1"/>
<text work="Bible.TEV"/>
<text work="Bible.XYZ"/>
<text work="Bible.h"/>
<text work="Bible.TEV.1998"/>
<text work="Bible.1"/>

Hope that this clears things up.

Let me know if I missed something or just made things more fuzzy.

Todd
> -----Original Message-----
> From: owner-osis-core@bibletechnologieswg.org [mailto:owner-osis-
> core@bibletechnologieswg.org] On Behalf Of Patrick Durusau
> Sent: Wednesday, April 17, 2002 5:48 AM
> To: osis-core@bibletechnologieswg.org
> Subject: Re: [osis-core] OSISScripture_01094 with new regex.
> 
> Troy,
> 
> I will be calling Todd today about the regex problem on reference.
> 
> Troy A. Griffitts wrote:
> 
> >No!  My bad!  Your original assumption was correct:  attribute value
+
> >display text container, vs. Todd's syntax.  The ':' int the attribute
> >value was accidental.  rev v.00002 below
> >
> ><ref refID="Gen.1.20-22">Genesis 1:20-22</ref>
> >
> Thanks for catching this rather serious problem!
> 
> Try the attached revision and see if that fixes the problem. There
> should be NO validation of the string between the <ref refID=....> NO
> Validation here </ref>.
> 
> Patrick
> 
> 
> 
> 
> >
> >Patrick Durusau wrote:
> >
> >>Troy,
> >>
> >>Sorry, the question was the use of a ":" in the attribute value?
> >>
> >>If so, no, is it not allowed.
> >>
> >>Patrick
> >>
> >>Troy A. Griffitts wrote:
> >>
> >>>I LOVE examples, as I am not up on the current XML lingo.
> >>>I don't understand the examples below.
> >>>
> >>>Are we saying that we're not having anything like:
> >>>
> >>><ref refID="Gen.1:20-22">Genesis 1:20-22</ref>
> >>>
> >>>??
> >>>
> >>>
> >>>
> >>>Todd Tillinghast wrote:
> >>>
> >>>>Following are valid:
> >>>>
> >>>><ref>Bible.KJV..Gen</ref>
> >>>><ref>Bible.KJV.A..Gen.a-a.1.1-1</ref>
> >>>><ref>Bible.B..Gen</ref>
> >>>><ref>Gen.20.17-18</ref>
> >>>><ref>Gen.20.17-18.Q-1</ref>
> >>>><rWork>Bible.TEV</rWork>
> >>>><rWork>Bible.XYZ</rWork>
> >>>><rWork>Bible.h</rWork>
> >>>><rWork>Bible.TEV.1998</rWork>
> >>>><rWork>Bible.1</rWork>
> >>>>
> >>>>Following are NOT valid:
> >>>>
> >>>><ref>Bible.KJV..</ref> (A side of me thinks this should be valid
as a
> >>>>reference to the whole work.)
> >>>><ref>Bible.KJV.A..Gen.-a</ref>
> >>>><ref>Bible.TEV-1992..Gen</ref>
> >>>><ref>Gen.20.-18</ref>
> >>>><ref>Gen.20.17-18.-1</ref>
> >>>><ref>Gen.20.17-18-1</ref>
> >>>><ref>Gen 20:17</ref>
> >>>><rWork>Bible.TEV-1998</rWork>
> >>>><rWork>Bible.TEV 1998</rWork>
> >>>><rWork>Bible TEV</rWork>
> >>>><rWork>BIBLE.TEV</rWork>
> >>>>
> >>>>Todd
> >>>>
> >>>>
---------------------------------------------------------------------
> ---
> >>>>                             Name: osisScripture_01094.xsd
> >>>>  osisScripture_01094.xsd    Type: text/xml
> >>>>                         Encoding: quoted-printable
> >>>>
> >>--
> >>Patrick Durusau
> >>Director of Research and Development
> >>Society of Biblical Literature
> >>pdurusau@emory.edu
> >>
> 
> --
> Patrick Durusau
> Director of Research and Development
> Society of Biblical Literature
> pdurusau@emory.edu
>