[osis-core] Update on OSIS Schema Issues

[Patrick Durusau]

Guys,

Steve and I talked this morning and have the following suggested 
resolutions:

>
>
> 1. Milestone syntax (elements that are normally containers but written 
> as empty elements)

Accept Todd's proposal, but use start, end as the attribute names, use 
Troy's suggestion for the milestoneable syntax (clipped portions follow):

<snip>

>
>
> Todd's proposal: <verse osisID="John.1.1" mB="X"/>In the 
> beginning...<verse mE="X"/>
>
<snip>

>
> Troy agrees that we can create an atributeGroup but would prefer:
>
> // stole regex from osisWorkType
> <xs:simpleType name="mIDType">
>  <xs:restriction base="xs:string">
>    <xs:pattern value="((\p{L}|\p{N}|_)+)((\.(\p{L}|\p{N}|_)+)*)?"/>
>  </xs:restriction>
> </xs:simpleType>
>
>
> // all documentation about Milestoneable behaviour here
> <xs:complexType name="milestoneable">
>  <xs:attribute name="mID" type="mIDType" use="optional"/>
> </xs:complexType>
>
>
> // example element
> <xs:element name="verse">
>  <xs:complexType mixed="true">
>    <xs:complexContent>
>      <xs:extension base="milestoneable"/>
> ...
>    </xs:complexContent>
>  </xs:complexType>
> </xs:element>
>
<snip>

>
> 2. scope attribute on div?

Steve noticed a post on allowing scope on <q>. Does scope mean "what I 
contain?" Is so, isn't that a duplicate of osisID? But, note you can 
have elements that don't have an osisID where you want to indicate what 
it contains.

>
> Todd wants to have a scope attribute on <div> that uses the same regex 
> as osisRef to indicate the range of references in a <div>. Chris 
> agrees but wants to add that scope should  allow a list of osisRefTypes.
>
> 3. osisRef required on <reference>?

Remain optional.
<snip>

>
> 4. <chapter> as child of <p>

Partial victory for Todd. ;-)

Keep the current chapter element (as extension of milestoneable), but 
have a separate chapter element (I know, flood of elements coming into 
the schema) that is the child of <p>, <l>, <speech>, <item>...., but it 
needs a different name. (Because we can't enforce use of only milestones 
from the "real" chapter element in these lesser elements.

BTW, 1st place for explanatory comment goes to Troy for: "The BCV 
numbering from centuries ago sucked." Clear, concise and to the point.

<snip>

>
> 5. Local reference extension: Do we want to use ! or | and can you 
> remind me of the syntax that I need to add to the regex?

Use "|".

Patrick

-- 
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
Patrick.Durusau@sbl-site.org
Co-Editor, ISO 13250, Topic Maps -- Reference Model

Topic Maps: Human, not artificial, intelligence at work!