[osis-core] almost got a text ready

[Todd Tillinghast]

Troy,

I don't disagree that the <refSystem> element makes logical sense for
what you are trying to do. 

However, I was convinced by Harry and Partick that references systems
are really defined by a specific work.  This is very much the case for
everything but Bibles.  With Bibles it seems that he KJV actually
defines the reference system I most often think of, even though I
couldn't have told you that a year ago.  What I want and I think you
want is to be able to create references (osisRef="Matt.1.1") that do not
point to a specific work but rather create a reference to "Matt.1.1"
where "Matt.1.1" is valid in the "namespace" defined by a
work-independent reference system.

By defining "Bible" as an "abstract" work that is the equivalent of what
we would define as a reference system, then we can create references to
that "abstract" work and get the behavior we need.  At the same time we
retain a consistent mechanism to derive "fully formed" references for
use outside and into documents.

We have said that work identifiers are hierarchical.  ("Bible.NIV" is a
child of "Bible" and "Bible.NIV.1993" is a child of "Bible.NIV" and
"Bible.French" is a child of "Bible".)  The hierarchy implying that
there is some commonality between the parent and the child.  My view is
that by defining "Bible" as an "abstract" work and "general reference
system" for Bibles, we provide the mechanism to creating
"work-independent" references and a common starting point for future
mapping structures.  ("Bible:Matt.1.1" does not point to any specific
work but is simply a reference in the context of "Bible".)

By not using <refSystem> and using an "abstract" work in <identifier> we
maintain a consistent and reliable strategy.

I think the <refSystem> element leads to confusion when it comes to
resolving references in osisID and osisRef.  When convincing me that we
did not need to eliminate <refSystem>, Partick said that the <refSystem>
is useful in describing the reference systems that the <work>
participates in/supports BUT has no role or participation in resolving
the "fully formed" reference based on an osisID or osisRef.

Example:
<osisText osisIDWork="KJV" osisRefWork="defaultReferenceScheme">
   <header>
      <work osisWork="KJV">
         <title>King James Version of 1769 with Strongs Numbers</title>
         <identifier type="OSIS">Bible.KJV.1769</identifier> <!-- change
from your doc here -->
         <language>en</language>
         <refSystem>Bible.KJV</refSystem>
      </work>
      <work osisWork="defaultReferenceScheme">
         <identifier type="OSIS">Bible</identifier> <!-- change from
your doc here -->
      </work>
   </header>
...
   <reference osisRef="Matt.1.1"/> <!-- points to the "reference system"
"Bible:Matt.1.1" and not to a specific work -->
...
</osisText>

In this case references to "defaultReferenceScheme" will be
"Bible:Matt.1.1" when we state osisRef="Matt.1.1" and will not point
specifically to the work that is the KJV, while maintaining a consistent
mechanism for "deriving" "fully formed" references.  The key here is to
fact that this is an "abstract" work.  

Patrick, Harry, Troy, Chris, and Steve, have I accurately described how
things should work?

Todd
 
> 
> Todd,
> 	I think there is still a problem that I don't think I made clear
in
> my
> last message.
> 
> 	I understand your comment about the default for the reference
work.
> I
> think we both agree that the default is defaulting the *refSystem*.
So,
> hence I believe your "Bible.KJV" should go in refSystem, and not the
> identifier.
> 
> 	The osisRefWork allow 2 things to be specified:
> 
> 	1) the default refSystem for all osisRef's
> 	2) the default target work for all osisRef's
> 
> 	My understanding is that <refSystem> is for the first function,
and
> <identifier type="OSIS"> is for the second.
> 
> 
> 	In my Bible, I really don't want to specify a work for my
> references.
> Actually, if I did, I would probably want to specify myself as the
work.
>   ACTUALLY, I have no osisRef's in my doc, so it really doesn't
matter!
> :)  But for the sake of clearing this up, it's still good to talk
about
> it.
> 
> 	My thinking: If I was a sermon, and wanted to default my
references
> to
> KJV refSystem, but didn't want to imply any particular translation, I
> would leave my osisRefWork work element as is-- specifying a
refSystem,
> and not an identifier.
> 
> 	What do you think?
> 
> 	-Troy.