[osis-core] osisCore1.1 bug?

[Todd Tillinghast]

Harry,

Since there can be multiple <work> elements there is no need for a
separate <works> element that can contain multiple <work> elements.

I also recall that we required the elements you mentioned below to be
within a <work> element and the schema should be fixed.

Todd

> -----Original Message-----
> From: owner-osis-core@bibletechnologieswg.org [mailto:owner-osis-
> core@bibletechnologieswg.org] On Behalf Of Harry Plantinga
> Sent: Wednesday, November 13, 2002 3:18 PM
> To: osis-core@bibletechnologieswg.org
> Subject: [osis-core] osisCore1.1 bug?
> 
> The 1.1 schema still appears to have two places where you
> can put bibliographic information about a document -- in
> the <header> element directly and in a <work> element.
> 
> That is, you can do
> 
>   <header>
>      <title>King James Version of 1611</title>
>      <language>en</language>
>      <identifier type="OSIS">KJV.TutorEncoding</identifier>
>      <work osisWork="KJV">
>        <title>King James Version of 1611</title>
>        <language>en</language>
>        <identifier type="OSIS">KJV.TutorEncoding</identifier>
>        <refSystem>Bible.KJV</refSystem>
>       </work>
> 
> Note that there are two titles.  Which one is correct?
> It was my understanding that we were going to change the schema
> so that you have to put the bibliographic info into the <work>
> element, not outside of it in the header.
> 
> A related problem is that you can put <rights> only in the <header>
> directly, not in a the <work> element.
> 
> I.e. change the content model for the <header> element from
> 
> <xs:sequence>
>         <xs:element ref="title" minOccurs="0"/>
>         <xs:element ref="contributor" minOccurs="0"
> maxOccurs="unbounded"/>
>         <xs:element ref="creator" minOccurs="0"
maxOccurs="unbounded"/>
>         <xs:element ref="subject" minOccurs="0"
maxOccurs="unbounded"/>
>         <xs:element ref="date" minOccurs="0" maxOccurs="unbounded"/>
>         <xs:element ref="description" minOccurs="0"
> maxOccurs="unbounded"/>
>         <xs:element ref="publisher" minOccurs="0"
> maxOccurs="unbounded"/>
>         <xs:element ref="type" minOccurs="0" maxOccurs="unbounded"/>
>         <xs:element ref="format" minOccurs="0" maxOccurs="unbounded"/>
>         <xs:element ref="identifier" minOccurs="0"
> maxOccurs="unbounded"/>
>         <xs:element ref="source" minOccurs="0" maxOccurs="unbounded"/>
>         <xs:element ref="language" minOccurs="0"
maxOccurs="unbounded"/>
>         <xs:element ref="relation" minOccurs="0"
maxOccurs="unbounded"/>
>         <xs:element ref="coverage" minOccurs="0"
maxOccurs="unbounded"/>
>         <xs:element ref="rights" minOccurs="0" maxOccurs="unbounded"/>
>         <xs:element ref="teiHeader" minOccurs="0" maxOccurs="1"/>
>         <xs:element ref="revisionDesc" minOccurs="0"
> maxOccurs="unbounded"/>
>         <xs:element ref="castList" minOccurs="0"
maxOccurs="unbounded"/>
>         <xs:element ref="work" minOccurs="1" maxOccurs="unbounded"/>
> </xs:sequence>
> 
> to
> 
> <xs:sequence>
>         <xs:element ref="revisionDesc" minOccurs="0"
> maxOccurs="unbounded"/>
>         <xs:element ref="rights" minOccurs="0" maxOccurs="unbounded"/>
>         <xs:element ref="work" minOccurs="1" maxOccurs="unbounded"/>
> </xs:sequence>
> 
> or possibly
> 
> <xs:sequence>
>         <xs:element ref="revisionDesc" minOccurs="0"
> maxOccurs="unbounded"/>
>         <xs:element ref="work" minOccurs="1" maxOccurs="unbounded"/>
> </xs:sequence>
> 
> with <rights> moving into <work> also.
> 
> Or am I all wet?
> --------------------------------------------------------------------
> Another issue.
> 
> I had thought we were going to allow the header to have a <work> or a
> <works> containing many <work> elements. That way you could put your
> bibliography in the header in a series of <work> elements.
> 
> However, I can't find a <works> element in the schema.  Was my memory
> faulty, or did I miss a change in the plan?
> 
> -Harry