[osis-core] annotateRef: Question on whitespace

[Todd Tillinghast]

Patrick,

<snip>
> >>
> >>Could do a separate regex for annotateRef that does not allow the
> >>whitespace.
> >>
> >
> >
> > It would be better to be consistent.
> >
> But being consistent would mean no whitespace in @s[blah blah], would
> mean that the grain operator could only point to a single word, rather
> than a phrase.
> 
> 

What if we did not allow whitespace but allowed the user to specify the
occurrence number of the match string with a default to the first
occurrence.

For example:
<verse osisID="X.1.1">The trouble with string matching is that a string
can have whitespace trouble makers.</verse>

<reference osisRef="X.1.1@s[trouble][2]"/> 

where the second [#] is optional but would indicate the #th occurrence
of the match string

Todd

> >
> >>Suggestions, comments?
> >
> >
> > It is possible to require the use of whitespace entities rather than
the
> > characters.  Does anyone know if a whitespace entity is considered
> > equivalent to a whitespace character from an XML perspective?
> >
> >
> No. Entities, that is all entities, are resolved by the XML parser.
Not
> possible to know whether what you have in the stream is a "real"
> whitespace or whitespace from an entity.
> 
> Hope you are having a great day!
> 
> Patrick
> 
> --
> Patrick Durusau
> Director of Research and Development
> Society of Biblical Literature
> Patrick.Durusau@sbl-site.org
> Chair, V1 - Text Processing: Office and Publishing Systems Interface
> Co-Editor, ISO 13250, Topic Maps -- Reference Model
> 
> Topic Maps: Human, not artificial, intelligence at work!
> 
> 
> _______________________________________________
> osis-core mailing list
> osis-core@bibletechnologieswg.org
> http://www.bibletechnologieswg.org/mailman/listinfo/osis-core