[osis-core] Re: Taxes done, off to 6-flags, and osisID!

[Patrick Durusau]

Todd,

Todd Tillinghast wrote:

>Patrick,
>
<snip>

>
>I suspect there will be errors that need fixing and extra attributes to
>clean up that are found when encoding, but I think this version should
>be a go.  (All that assuming we end up with the "right" solution to
>osisID.)
>
>It has to be like the following examples:
><verse osisID="[Matt.1.6] [Matt.1.7] [Matt.1.8] [Matt.1.9] [Matt.1.10]
>[Matt.1.11] [Bible.KJV:Matt.l.6.a]">
><verse osisID="[Matt.13.1]">
><div osisID="[Matt.1]">
>
>(It does not matter to me if we use [], {}, () to enclose the individual
>identifiers in the list,  I personally like [] the best.)
>
>
I will be calling for the extended explanation!

In prose, what I see for osisIDs is as follows:

1. osisIDs should be constructed using standard reference systems with 
no unique extensions, i.e., no Matt.1.6.a or other additions to the 
standard reference system.

Reasoning: Users should not have to guess or consult documentation to 
create references to osisIDs. Standard references should work.

2. An osisID should appear on an element that contains the same portion 
of the text as identified by the standard reference identifier. In other 
words, a div that is a book, could have Matt, a div that represents a 
chapter could have Matt.1 and a verse that contains a verse of Matthew 
could be Matt.1.1.

3. If an element contains less than the whole portion of a standard 
reference, it should have an osisID that represents the larger portion 
of the text, for example, splitting a verse into two parts would result 
in two verse elements, <verse osisID="Matt.1.1" 
splitID="1"></verse><verse osisID="Matt.1.1" splitID="2"></verse>, while 
results in a standard reference to Matt.1.1 returning both portions of 
the verse, despite their being split in the targeted encoding. Note that 
the splitID can represent a different ordering of the segments of the 
text. (I need to fix the schema to add splitID. Suggested by Steve in 
Montreal but dropped by yours truly.)

4. If an element does not correspond to  a canonical division of the 
text, for example your Matt 1:6-11 (in conventional notation), my first 
reaction is to move the reference to osisRef but the more I look at your 
post, the less useful that seems. Actually I can't imagine a verse with 
the osisIDs you cite, a <p> perhaps(?).

Hmmm, let me think about it and I will try to call Steve for his take 
prior to calling you to visit about your latest proposal.

Patrick


-- 
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
pdurusau@emory.edu