[osis-core] osisID as list

[Patrick Durusau]

Todd,

Todd Tillinghast wrote:

>I am pretty sure that attributes (with the exception of lists) are
>exempt from the white space removal rules.  Assuming that, there seems
>to be no loss with the "restriction" strategy.  The only down side is
>that we do intend this attribute as a list but are not formally
>declaring it as such.  It would be easier to maintain and derive if it
>were in the "list" form. 
>
How so?

>
>The real benefit of the "restriction" form is that it helps us in
>writing XPath expressions because it eliminates the various options
>available as white space and limits us to only space.
>
Recall that we are not writing the schema to be specific for the current 
XPath standard or its implementations.

BTW, I checked and if you insert something other than one space, you get 
a validation error.

Patrick

>
>Todd
>
>>-----Original Message-----
>>From: owner-osis-core@bibletechnologieswg.org [mailto:owner-osis-
>>core@bibletechnologieswg.org] On Behalf Of Patrick Durusau
>>Sent: Wednesday, August 28, 2002 1:36 PM
>>To: osis-core@bibletechnologieswg.org
>>Subject: Re: [osis-core] osisID as list
>>
>>Todd,
>>
>>I assume you mean by "restr" = "restriction"? (Sorry, so many
>>abbreviations and acronyms that I lose track.)
>>
>>><xs:simpleType name="osisIDType">
>>>		<xs:list itemType="osisIDPrimativeType"/>
>>>	</xs:simpleType>
>>>	<xs:simpleType name="osisIDPrimativeType">
>>>		<xs:restriction base="xs:string">
>>>			<xs:pattern
>>>
>value="(((\p{L}|\p{N}|_)+)((\.(\p{L}|\p{N}|_)+)*)?(\[((\p{L}|\p{N}|_)+)(
>(\
>
>.(\p{L}|\p{N}|_)+)*)?\])?:)?((\p{L}|\p{N}|_)+)((\.(\p{L}|\p{N}|_)+)*)?((
>\s
>
>>(((\p{L}|\p{N}|_)+)((\.(\p{L}|\p{N}|_)+)*)?:)?((\p{L}|\p{N}|_)+
>>)((\.(\p{L}|\p{N}|_)+)*)?)*)?"/>
>>
>>>		</xs:restriction>
>>>	</xs:simpleType>
>>>
>>With the exception of losing the \s in the expression, do you see list
>>as gaining us anything?
>>
>>Patrick
>>
>>
>>Todd Tillinghast wrote:
>>
>>>I was using version 004 when I first got the error saying that osisID
>>>was invalid (only for osisIDs that are lists).
>>>
>>>The list by forcing a space using "restr" rather than "list" in
>>>osisIDType.  Unrelated to whether the current regex works or no do
>>>
>you
>
>>>have thoughts related to my prior post and the use of "restr" rather
>>>than "list"?
>>>
>>>
>>>Todd
>>>
>>>>-----Original Message-----
>>>>From: owner-osis-core@bibletechnologieswg.org [mailto:owner-osis-
>>>>core@bibletechnologieswg.org] On Behalf Of Patrick Durusau
>>>>Sent: Wednesday, August 28, 2002 12:23 PM
>>>>To: osis-core
>>>>Subject: [osis-core] osisID as list
>>>>
>>>>Todd,
>>>>
>>>>If you look at the test schema I forwarded a few minutes ago I think
>>>>
>>>you
>>>
>>>>will find that osisIDs can already be lists. I copied the expression
>>>>
>>>in
>>>
>>>>the test file directly from the lastest release so let me know if it
>>>>does not work for you.
>>>>
>>>>Patrick
>>>>
>>>>--
>>>>Patrick Durusau
>>>>Director of Research and Development
>>>>Society of Biblical Literature
>>>>pdurusau@emory.edu
>>>>
>>--
>>Patrick Durusau
>>Director of Research and Development
>>Society of Biblical Literature
>>pdurusau@emory.edu
>>
>>
>

-- 
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
pdurusau@emory.edu