[osis-core] annotateRef

[Todd Tillinghast]

The issue is not what software will do or what we say the rules are but
the fact that with XML Schema a list is defined to be whitespace
separated.  

It is possible to express in XML Schema that a simple type is a list of
other simple types that allow whitespace.  But a list is defined as
being whitespace separated.  So in practice you must not allow
whitespace in a simple type you use to make a simple type that is a
list.  

My suggestion is to not allow whitespace in the string portion of the
@s: grain structure.

Todd

-----Original Message-----
From: osis-core-admin@bibletechnologieswg.org
[mailto:osis-core-admin@bibletechnologieswg.org] On Behalf Of Harry
Plantinga
Sent: Tuesday, September 09, 2003 9:19 AM
To: osis-core@bibletechnologieswg.org
Subject: RE: [osis-core] Date problems....

It seems to me that the strings are well enough defined,
but processing them with standard tools may be harder. For
example, if XSLT had a function contains-token, you couldn't 
use such a thing if some of the tokens contain whitespace.

-Harry

> -----Original Message-----
> From: osis-core-admin@bibletechnologieswg.org 
> [mailto:osis-core-admin@bibletechnologieswg.org] On Behalf Of 
> Patrick Durusau
> Sent: Tuesday, September 09, 2003 8:13 AM
> To: osis-core@bibletechnologieswg.org
> Subject: Re: [osis-core] Date problems....
> 
> 
> Todd,
> 
> OK, after some sleep, I see what you are talking about, I think.
> 
> Are you saying this is a problem with XML Schema regexes or with the 
> regexes you are using in your application?
> 
> Seems to me, without checking, in the middle of something at 
> the moment, 
> that a regex should match
> 
> [chars + whitespace]
> 
> differently from
> 
> [chars + whitespace] [chars + whitespace] [chars + whitespace]
> 
> Note that I am not matching whitespace but each entire expression.
> 
> Requires better regex handling than simply splitting on whitespace.
> 
> Does that help or am I still missing the issue?
> 
> Hope you are having a great day!
> 
> Patrick
> 
> Todd Tillinghast wrote:
> > Patrick,
> > 
> > annotateRef="Esth.4.14@s[It could] John.3.16@s:[gave his] 
> > Gen.1.1@s:[and the earth]"
> > 
> > Would yield the following whitespace separated tokens
> > Esth.4.14@s[It
> > could]
> > John.3.16@s:[gave
> > his]
> > Gen.1.1@s:[and
> > the
> > earth]
> > 
> > rather than what is expected as follows:
> > Esth.4.14@s[It could]
> > John.3.16@s:[gave his] 
> > Gen.1.1@s:[and the earth]
> > 
> > Todd
> > 
> > 
> > -----Original Message-----
> > From: osis-core-admin@bibletechnologieswg.org
> > [mailto:osis-core-admin@bibletechnologieswg.org] On Behalf 
> Of Patrick 
> > Durusau
> > Sent: Monday, September 08, 2003 4:56 PM
> > To: osis-core@bibletechnologieswg.org
> > Subject: Re: [osis-core] Date problems....
> > 
> > Todd,
> > 
> > Todd Tillinghast wrote:
> > 
> >>Patrick,
> >>
> >>When making annotationRef a list of osisRef patterns we are 
> going to 
> >>have a problem in that we allow white space within the string match
> > 
> > for
> > 
> >>a grain Esth.4.14@s:[It could].
> >>
> >>In order make a list we should not allow there to be a space
> > 
> > character.
> > 
> > 
> > Sorry, it has been a long day and that went by rather fast.
> > 
> > Why does the space in Esth.4.14s:[It could] cause a 
> problem? (I may be
> > zoning on the issue you are raising so could you give a 
> fuller example?)
> > 
> > The space can only occur within [....] or between the 
> osisRefs, which 
> > I
> > would think are distinguishable? Or are you saying there 
> should be some 
> > other delimiter character between the osisRefs other than a space?
> > 
> > BTW, does anyone have any comments on other parts of the minutes? I 
> > plan
> > 
> > on reaching the schema for editing by this weekend.
> > 
> > Hope you are having a great day!
> > 
> > Patrick
> > 
> > 
> > 
> >>Thoughs?
> >>
> >>Todd
> >>
> >>
> >>
> >>_______________________________________________
> >>osis-core mailing list
> >>osis-core@bibletechnologieswg.org
> >>http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
> >>
> > 
> > 
> > 
> 
> 
> -- 
> 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/lis> tinfo/osis-core
> 

_______________________________________________
osis-core mailing list
osis-core@bibletechnologieswg.org
http://www.bibletechnologieswg.org/mailman/listinfo/osis-core