[osis-core] OSIS Candidate.1.1_001 - 3 splitID!

[Todd Tillinghast]

I notice that splitID is an positiveInteger.

I CANNOT accommodate segmented <q> and <div> (and likely other elements
that I have not yet come across) elements that don't have an osisID with
a splitID that is a positiveInteger AND relies on the existence of an
osisID.

See prior posts on this topic.

If we want to have a positiveInteger value then we should call it
splitSeq and also a splitID that carries an IDENTICAL value for all
elements that are a part of the split that is also UNIQUE from all other
values used for other split elements.

PROPOSAL:

splitSeq that is of type xs:positiveInteger
splitID that is simply xs:string

Remove these attributes from globalAttributes and create splitAttributes
and put these two attributes in that attributeGroup.

Determine which elements should be split and put splitAttributes in
those elements alone.  Remember special considerations will have to be
made for elements that can be split when writing style sheets.

Suggested elements for splitAttributes
<p>
<div>
<q>
<verse>
<lineGroup>
<line>
<list>
<item>

Not sure about 
<speech>
<signed>
<salute>
<inscription>
<mentioned>
<table>, <row>, <cell>

(It does not make since to split <title>, <figure>, <note>, etc...)

Does this make sense or have I totally missed the boat on the purpose
for split (which seems take 

Todd