[osis-core] line, lineGroup, lineStart, & lineEnd

[Todd Tillinghast]

If it is a case where more than one canonical verse is grouped then you
should use option A.  In this case the reference system be using used does
not have Ps.2.1 and Ps.2.2 but only Ps.2.1-2 where the "1-2" portion is
simply an identifier that describes the text and is not intended to be a
range at all, but is meaning for human readers.  When mapping
Bible.XYZ..Ps.2.1-2 to a "canonical" reference system the single "verse"
would map to two.  (Ex. Bible.NRSV..Ps.2.1 and Bible.NRSV..Ps.2.2).

However according to Patrick, as a result of the meeting in Rome verse,
chapter, and book milestones have been proposed to be eleminated.

Todd

> -----Original Message-----
> From: owner-osis-core@bibletechnologieswg.org
> [mailto:owner-osis-core@bibletechnologieswg.org]On Behalf Of Chris
> Little
> Sent: Friday, May 03, 2002 11:09 PM
> To: osis-core@bibletechnologieswg.org
> Subject: RE: [osis-core] line, lineGroup, lineStart, & lineEnd
>
>
>
> > On a different topic <verseStart MID="Ps.2.1-Ps.2.2"/> should
> > be either
> > <verseStart MID="Ps.2.1-2"/> OR be expressed as two
> > independent milestones.  The purpose of the "-" is to allow
> > for verse name identifiers to include a "-" and is not
> > intended to allow for a start reference and end reference
> > value separated by a "-" implying a range.
>
> How would you suggest that I mark verses that cover a range of canonical
> verses?  Options I can think of:
>
> A) <verseStart MID="Ps.2.1-2"/>...<verseEnd MIDREF="Ps.2.1-2"/>
>
> B) <verseStart MID="Ps.2.1"/><verseStart MID="Ps.2.2"/>...<verseEnd
> MIDREF="Ps.2.1"/><verseEnd MIDREF="Ps.2.2"/>
>
> C) <verseStart MID="Ps.2.1"/><verseStart MID="Ps.2.2"/>...<verseEnd
> MIDREF="Ps.2.2"/><verseEnd MIDREF="Ps.2.1"/>
>
> D) <verseStart MID="Ps.2.1 Ps.2.2"/>...<verseEnd MIDREF="Ps.2.1
> Ps.2.2"/> (I'm sure that's invalid, but you get my point.)
>
> A is simplest from the encoding standpoint.  B, C, & D are more
> difficult to encode, but easier to decode when crossing a chapter
> boundary (luckily that is very uncommon).
>
> --Chris
>
>