[osis-core] Segmentation strategy

[Patrick Durusau]

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