[osis-core] osisID as List
Harry Plantinga
osis-core@bibletechnologieswg.org
Wed, 14 Aug 2002 16:44:34 -0400
It was also my understanding of the matter (and my understanding
of Steve's position) that osisIDs are never ranges. I think that's
a direct quote from Steve.
However, that's a slightly different matter from what I understand
Todd to be proposing -- that a single entity such as a paragraph
could have several osisIDs.
Take the Matt.1.6-Matt.1.11 case. If a single element corresponds
to several osisIDs, how would you mark that up?
<p osisID="Matt.1.6">
<p osisID="Matt.1.7">
<p osisID="Matt.1.8">
...
[text of paragraph]
...
</p>
</p>
</p> ?
However, I'm not sure this should really occur. At least in this
example, I would suggest that the CEV is using a different versification
scheme, and it would use some other ID to identify that paragraph,
perhaps Matt.1.6_11 (which is NOT a range, just a single osisID).
A translation would be defined between the two schemes.
But could there ever be cases in which a single elemetn (e.g. paragraph)
corresponds to two or more osisIDs in the chosen reference scheme?
I'm not sure. Perhaps. So maybe we SHOULD allow a list of osisIDs.
-Harry
> -----Original Message-----
> From: owner-osis-core@bibletechnologieswg.org
> [mailto:owner-osis-core@bibletechnologieswg.org] On Behalf Of
> Patrick Durusau
> Sent: Wednesday, August 14, 2002 4:16 PM
> To: osis-core
> Subject: [osis-core] osisID as List
>
>
> 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.
>
> Steve, can you confirm?
>
> Patrick
>
> --
> Patrick Durusau
> Director of Research and Development
> Society of Biblical Literature
> pdurusau@emory.edu
>
>