[osis-core] osisID as List

[Todd Tillinghast]

> Greetings,
> 
> Todd took time from dodging the tax man to post several nagging issues
> that we need to resolve (I have divided them up for ease of
> consideration):
> 
> First,
> 
> >1) Outstanding is osisID as a list.  We all need to be clear on what
an
> >osisID is and what we intend to be used for.  If osisID is not a list
I
> >cannot encode things like Matt.1.6-Matt.1.11.
> >
> osisID is a self-identifier in a reference system, most generally
> associated with a book, chapter or verse. The case you cite, from the
> TEV or CEV, is not an osisID, but is an example of an osisRef, i.e., a
> pointer to a reference system that is not present in the work you are
> encoding. That gets you the range operator without either having lists
> in osisID or adding ranges to it.
> 
> I think the reasoning is that there is really no reference system that
> has Matt.1.6-Matt.1.11 as a self-identifier for a portion of text.

Not sure, but I think I may have been unclear.  I am NOT proposing that
we have <verse osisID="Matt.1.6-Matt.1.11"> but only was trying to say
that I will have trouble encoding the element in the first chapter of
Matthew (of the TEV version) that can be identified by ALL of the
following identifiers from Bible.KJV reference system space: Matt.1.6
Matt.1.7 Matt.1.8 Matt.1.9 Matt.1.10 Matt.1.11.  And I propose that we
allow employ the following strategy.  <verse osisID="Matt.1.6 Matt.1.7
Matt.1.8 Matt.1.9 Matt.1.10 Matt.1.11 Bible.TEV:Matt.1.6.b">  

Actually, from the greater view I am proposing <verse osisID="[Matt.1.6]
[Matt.1.7] [Matt.1.8] [Matt.1.9] [Matt.1.10] [Matt.1.11]
[Bible.TEV:Matt.1.6.b]">.  (Which also solves the XPath problem.)

Is this clear?

> 
> Steve, can you confirm?
> 
> Patrick
> 
> --
> Patrick Durusau
> Director of Research and Development
> Society of Biblical Literature
> pdurusau@emory.edu
>