[osis-core] Free-range grain-fed sacred cows

[Harry Plantinga]

> So my proposal for this would be to disallow grains on self-ids, and 
> to either suggest or (preferably?) require appending a, b,... to the 
> identifiers if you want to make the parts accessible (those should be 
> declared in a reference scheme, but I'm not picky about that part, 
> seems like a  nit at this point). This gives us nice predictable 
> names for the parts of a discontiguous verse (say, for use in the 
> next/prev values), and makes a trivial algorithm to  strip them off. 
> Indeed, we could use the default fallback algorithm, which is to 
> strip off trailing tokens of a reference; to do that we just put '.' 
> before the 'a'.
> 
> S

If I want to use larger verse-like chunks, e.g. 

<p osisID="CEV:Matt.1.1_9">

would it be non-intuitive to use CEV:Matt.1.1_9a, CEV:Matt.1.1_9b, 
etc to refer to parts?

Or, worse, what happens if I add <q> or other tags that spans a verse
boundary and causes another split in the verse container.  Now the part 
of the verse that used to be Matt.1.1b becomes Matt.1.1b and Matt.1.1c, 
and all the subsequent sections of Matt.1.1 are renamed, c->d, d->e, etc.

How about just using osisID of Matt.1.1 for all segments of the verse?
This would require that all segments be in order, but you can retrieve
all pieces by asking for all elements with osisID="Matt.1.1". You'd have
to use grains to access other parts of the verse. But, of course, you'd
be free to define a reference system that uses Matt.1.1.a, Matt.1.1.b, etc.
in addition to Matt.1.1 .

(I assume that we are allowing tree-structured hierarchy in the osisIDs, 
Matt containing Matt.1, Matt.2, Matt.3, ...; Matt.1 containing Matt.1.1, 
etc.)

-Harry