[osis-core] Reference Syntax Proposal

[Troy A. Griffitts]

>> Yes, I guess it would follow that if you wished to allow <reference
>> ref="Matt.1.6.a"> from outside this document, you would need to define
>> the Bible.TEV versification scheme.  But then you probably just
>> declare it as extending the KJV (or something else), and then your
 >> references in your document would default to this versification
 >> scheme, and the 'Bible.TEV:' prefix would not be necessary.
 >> What do you think?

> If you don't differentiate then you are back to using a "work" specific
> reference system that users of the document would have to access through
> a map between the standard reference system and the work specific
> reference system that extends the standard reference system.  Although,
> the mapping would likely be trivial in the case we are discussing, there
> would be no way of knowing when the mapping is trivial and when the
> mapping is more involved.  As a result to reliably access a reference,
> users of a document would be forced to use a work specific reference
> system or go through a map.

I'm not sure I completely understand your comments.  After rereading my 
above comment, I believe I was fairly vague.  Let me try to clear up my 
point.

If you desire Matt.1.6.a to ACTUALLY be a target of an osisRef then:

You would need to define your own versification scheme.
Though we haven't decided HOW to define a versification scheme, it would 
probably be an option to 'extend' some other scheme, eg. 
<osisVersificationScheme name="Bible.TEV" extends="Bible.KJV">
...
</osisVersificationScheme>

and somehow cite your variance.

IF you've defined your own scheme, then you will most definitely use 
that scheme as the default versification scheme of your document, thus 
making the 'Bible.TEV:' in:

Bible.TEV:Matt.1.6.a

redundant.

Does that make sense?  I mean, does that at least clear up my thinking 
on the subject?

Also, I believe that IF you don't WANT to define Matt.1.6.a to be a 
target of an EXTERNAL osisRef, then you potentially would not be 
required to define your own versification scheme; but instead, you could 
use something common like: Bible.KJV as the default for the doc, and 
STILL use and osisID like:

<verse osisID="Matt.1.5 Matt.1.6 Matt.1.6.a">
...
</verse>
<verse osisID="Matt.1.6 Matt.1.6.b">
...
</verse>

this would ONLY be required IF you wanted somewhere in your own doc to 
osisRef both Matt.1.6.a and Matt.1.6.b

If you didn't wish them to be the target of an osisRef, then the .a and 
.b IDs could be excluded.



> If only the deviations are specified using the work specific reference
> system identifiers and the rest using the standard reference system,
> including the standard identifiers that correspond to the extended
> identifiers, you can get any verse using the standard identifiers and
> can also get a view of the document specific quirks as needed.

Right, I agree.  I think we'll need to discuss a means to define these 
schemes in detail at a later date, but I'm with you on this.

	-Troy.