[osis-core] RE: Work Issue

[Todd Tillinghast]

Patrick,

Your example a couple of things added to demonstrate the problem.

<osisText osisIDWork="kjv1612">
    <header>
        <work osisWork="kjv1612">
         lots of metadata
        </work>
        <work osisWork="nrsv1988">
         lots of metadata
        </work>
	</header>
	<div>
		<verse osisID="kjv1612:Ps.1.1
hebrewRefSystem:Ps.1.2">.</verse>
	</div>
</osisText>

In the osisID there are two reference systems present.  Both reference
systems are for THIS work and should be specified within the single
<work> element that describes THIS work.  With the current schema, there
is no place to define "hebrewRefSystem".


My proposal:

<osisText osisIDWork="kjv1612">
   <work>
     lots of metadata
	<refSystem id="kjv1612">Bible.KJV1612</refSystem>
	<refSystem id="hebrewRefSystem">Bible.Hebrew</refSystem>
   </work>    
   <header>
        <work osisWork="nrsv1988">
         lots of metadata
        </work>
	</header>
	<div>
		<verse osisID="kjv1612:Ps.1.1
hebrewRefSystem:Ps.1.2">.</verse>
	</div>
</osisText>

The THIS <work> element does not need to be identified in <osisText>
because it is obvious based on its position.  The default reference
system to use in osisIDs is identified by "osisIDWork" in <osisText>.
As required, multiple reference systems are allowed within the THIS
<work> and each has an id attribute for use within osisIDs and with
osisIDWork.

If you dislike having two elements with the same name but different
structure and meaning then we can pick a different name for the special
THIS <work> element.  With a different name it could be in either inside
or outside <header>.
 
Note: a <reference> element could use "prefix" values from either
"osisWork" attributes of <work> elements within <header> OR "id"
attributes from <refSystem> elements within the THIS <work>.

Note: This is the remaining open issue related to <work>.  Other issues
related to the meaning of an osisRef and osisID that were resolved or
clarified in Toronto were stated in the earlier email and are not
repeated here.

Todd
-----Original Message-----
From: Patrick Durusau [mailto:pdurusau@emory.edu] 
Sent: Wednesday, January 29, 2003 2:52 PM
To: osis-core@bibletechnologieswg.org
Cc: Todd Tillinghast
Subject: Work Issue

Todd,

I am gathering up all the stuff for another run at the Work issue and 
wanted to ask you if this is a good common starting point:

<osisText osisIDWork="kjv1612">
    <header>
        <work osisWork="kjv1612">
         lots of metadata
        </work>
        <work osisWork="nrsv1988">
         lots of metadata
        </work>

Now, without rewriting the example to give me your solution, which I 
appreciate but have yet to find helpful, please tell me what is 
ambiguous about the osisIDWork="kjv1612" reference in osisText? Note I 
am not asking about osisRefs or multiple reference systems, or anything 
else, yet, just on this one point, what, if anything, do you see as 
ambiguous about this reference?

BTW, I see osisWork="kjv1612" as tying any reference to that value by 
osisIDWork, to the entire set of metadata that appears in <work>.

Do not confuse this with the issue of needing a common set of <work> 
elements that have a well known osisWork value that we have produced for

various popular bibles to promote interchange of texts.

I am trying to get all the notes, etc. I need together to make a mad 
dash at the user manual so comments, suggestions, samples, would be
helpful.

Once we finish the users manual, I guess we need to gather up some more 
sophisticated documentation for maintenance and extension of the schema.

Sigh, it is always one thing or another. ;-)

Patrick

-- 
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
pdurusau@emory.edu
Co-Editor, ISO Reference Model for Topic Maps