[osis-core] Segmentation strategy
Todd Tillinghast
osis-core@bibletechnologieswg.org
Wed, 14 Aug 2002 14:57:24 -0600
For which elements are you adding new milestone elements? Are they
start and end pairs? (Not opposing the addition just wanting to
understand more fully.)
If one of the new milestones is specific to verse and/or div it may make
since to allow the start instance of the pair to have an osisID in the
same structure AND meaning as <verse> and <div>.
I gather that splitID is a replacement for segID and that it carrys a
convention of sequence? I think that this element should be xs:string
and not be validated in any way other than possibly to enforce a syntax
related to the convention from which the sequence is derived. <verse
osisID="[Matt.1.2] [Bible.TEV:Matt.1.2.a]" splitID="12345.a"> where
"12345" is an arbitrary value and "a" indicates the first of several.
(This does not preclude "Matt.1.2.a", but what I am saying is that the
"Matt.1.2" portion does not carry any more meaning than "12345". It may
just be easier to keep track of "unique" names that way.)
> Greetings,
>
> Todd's second open issue was about segmentation, or in his words:
>
> >2) I am not clear on the current strategy for segmentation. I know
we
> >have milestones and they can be used for ALL forms of segmentation,
but
> >I thought that we had agreed that the primary mechanism to handle
> >segmentation would be through some sort of prev/next/segID strategy
(or
> >as recently discussed, just segID what follows a convention that
> >specifies order).
> >
> Note an error in the latest version in that it does not include the
> splitID attribute. (Sorry 'bout that.)
>
> Steve and I discussed the various options and although poorly
documented
> (my fault) have added the milestone container semantic for a limited
> number of element types. The primary mechanism should still be use of
> segmentation but since the semantics of the markup are the same, the
> choice becomes one of personal preference.
>
> Steve, can you say a little more about this, noting that I will
correct
> the omission of the splitID on the two added milestone elements?
>
> Patrick
>
> --
> Patrick Durusau
> Director of Research and Development
> Society of Biblical Literature
> pdurusau@emory.edu
>