[osis-core] bug in 2.1.1 osisGenRegex

[Patrick Durusau]

Chris,

Chris Little wrote:
> Does this list still work? Is anyone still out there? Guess we'll soon 
> find out. :)
>
>   
Yes, there are people out here. ;-)
> Troy and I found a bug in the regex osisGenRegex in the 2.1.1 schema. 
> Currently that regex looks like [1], but it should looks like [2]:
>
> [1]     ((((\p{L}|\p{N}|_)+)(\.(\p{L}|\p{N}|_))*:)?([^:\s])+)
> [2]     ((((\p{L}|\p{N}|_)+)(\.(\p{L}|\p{N}|_)+)*:)?([^:\s])+)
>
>                          (missing + right here ^)
>
>   
Yep.

And we need to check the other regex expressions to make sure they don't 
have the same bug. Once I got part of it "correct" or what I thought was 
correct, I used it in other expressions.
> So our document with the following element isn't valid because the 
> string "Strong" cannot be more than 1 character long in the current schema:
> <w morph="robinson:N-NSF" lemma="lemma.Strong:βίβλος">βίβλος</w>
>
>
>   
Yep.

Question: Do you think we need to issue a quick bug fix schema after 
checking the other regex expressions for the same problem or should we 
fold this into a more expansive release, say timed to occur with the 
Bible technology conference several of us are attending early next year? 
Obviously no major features but tidying up sort of stuff.

Hope you are having a great day!

Patrick
> --Chris
>
> _______________________________________________
> osis-core mailing list
> osis-core at bibletechnologieswg.org
> http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
>   

-- 
Patrick Durusau
patrick at durusau.net
Chair, V1 - US TAG to JTC 1/SC 34
Acting Convener, JTC 1/SC 34/WG 3 (Topic Maps)
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)
Co-Editor, OpenDocument Format (OASIS, ISO/IEC 26300)