[osis-core] Reference Syntax Proposal

[Harry Plantinga]

> > Suppose that Matt.1, Matt.1.1, and Matt.1.2 are defined in a ref 
> > system.  Suppose I put all of Matt.1 in a big div, so I can access
> > the whole chapter at once, but the div has to be split. Perhaps
> > I'd call the pieces Matt.1.a and Matt.1.b.  Matt.1.a contains 
> > Matt.1.1 and Matt.1.2.
> 
> Per Steve's suggestion, both split divs of Matt.1 would include the 
> osisID of 'Matt.1'.  And maybe also include next/prev.  Steve would have 
> to confirm that, either way.
> 
> 
> > If I try to get Matt.1 by searching for all elements with osisID 
> > of Matt.1.*, I'm going to come up with Matt.1.1, Matt.1.2 as well as
> > Matt.1.a, Matt.1.b.  Matt.1.1 and Matt.1.2 will be in the result
> > list twice -- in fact, all of Matt.1 may be duplicated in the result
> > list.
> 
> Applying Patricks rule to your example would resolve to the first test 
> and quit, if I understand it correctly.
> 
> [Patricks rule:
> 
> This is based on the defined behavior for processing being:
> 
> A. Match on exact string match: Ex. Matt.1.6 matches Matt.1.6. If that 
> fails,
> 
> B. Match on Matt.1.6.*. If that fails,


The example correctly misbehaves if Matt.1 is NOT defined in the 
file except as two segments, Matt.1.a and Matt.1.b.

Yes, perhaps we will have to use "Matt.1" on both segments and
some other means of connecting them.

-Harry