[osis-core] annotateRef: Question on whitespace

[Patrick Durusau]

Todd,

Todd Tillinghast wrote:
> See below.

<snip>
>>
>>Decision: In user's manual, deprecate annotateWork.
> 
> 
> Does this mean leave it in the OSIS 2.0 schema and schedule its outright
> removal in the next release (OSIS 2.5 or OSIS 3.0)?
> 

I would support that, other comments?

> 
<snip>

> 
>>the @s: grain structure only for annotateRef?
>>
>>Hmmm, I think having whitespace in the string portion of the @s: grain
>>structure is fairly important in other uses of the osisRef regex.
>>
> 
> I agree that it is useful to allow space.
> 
> 
>>General feeling on whether this will be confusing to allow whitespace
>>sometimes but not others?
>>
>>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.


> 
>>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!