[osis-core] <work>, <works>, etc in OSIS schema

[Patrick Durusau]

Harry,

So,

no <header> until <osisText> or <osisCorpus>.

<header> required in <osisText>, <header> optional in <osisCorpus>.

Correct?

Patrick

Harry Plantinga wrote:

>As far as I can tell, there are not just two, but four different
>locations I could put the metadata for an osisText, such as its
>title, author, etc.
>
>-----------------------
><osis>
><header>  
>  <!-- metadata location #1 -->
>  <works>
>    <work workID="myWorkID">
>      <!-- metadata location #2 -->
>    </work>
>  </works>
></header>
><osisText workID="myWorkID">
>  <header>
>     <!-- metadata location #3 -->
>  <works>
>    <work workID="myWorkID">
>      <!-- metadata lcoation #4 -->
>
>
>-----------------------
>
>Patrick's suggestion below eliminates locations 1 and 3
>for metadata in the model above.  However, that still leaves
>two locations, which could still be a nuisance.
>
>How about dropping the optional <header> just below the <osis>
>tag as well when there is only one document? One could add
>the <header> back to the <osisCorpus> element to make room
>for corpus-wide metadata.
>
>That would mean an <osis> is either
><osis>
>  <osisText/>
></osis>
>
>or 
>
><osis>
>  <osisCorpus>
>    <header/>
>    <osisText/>
>    <osisText/>
>    <osisText/>
>       ...
>  </osisCorpus>
></osis>
>
>--------------------------------------------------------
>
>-Harry
>
>>-----Original Message-----
>>From: owner-osis-core@bibletechnologieswg.org 
>>[mailto:owner-osis-core@bibletechnologieswg.org] On Behalf Of 
>>Patrick Durusau
>>Sent: Sunday, August 25, 2002 5:01 PM
>>To: osis-core@bibletechnologieswg.org
>>Subject: [osis-core] <work>, <works>, etc in OSIS schema
>>
>>
>>Guys,
>>
>>Sorry for the long silence over the weekend but I think I have been 
>>catching up on some much needed sleep for the final push!
>>
>>Working on the latest batch of issues and wanted to run the 
>>following by 
>>everyone before sending it out as the next version in the morning.
>>
>>I think Harry's point about duplication is well taken and I would 
>>tenatively suggest the following structure:
>>
>><header> which consists of <works> (one only and it is required)
>>
>><works> is required to have one <work> element (or more) and 
>>it has all 
>>the stuff that was in the header, plus <refSystems>, so you 
>>can declare 
>>a <refSystem) (child of <refSystems>) as part of a work.
>>
>><refSystems> is not required but if used, must have at least one 
>><refSystem> as a child.
>>
>><refSystem> has all the stuff from header but not <refSystems> or 
>><refSystem>
>>
>>I have not mentioned the syntax of the osisIDs, osisRefs but 
>>will get to 
>>that later tonight or early tomorrow.
>>
>>Questions:
>>
>>1. Does this avoid the duplication and possible confusion 
>>that Harry was 
>>justifiably worried about? (Or do you know a better way?)
>>
>>2. Without regard to the syntax of the expressions, do  you like the 
>>idea of having the ability to include refSystem declarations 
>>within the 
>><work> which may be the work you are editing or a work you 
>>intend to cite?
>>
>>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