[osis-core] osisWork, refSystem - Summary

Steve DeRose osis-core@bibletechnologieswg.org
Thu, 22 Aug 2002 17:13:25 -0400


At 11:15 AM -0400 08/22/02, Patrick Durusau wrote:
>Guys,
>
>So I take it the common agreement is as follows:
>
>1. Should have attributes on osisText that are osisWork and refSystem.
>
>2. The values of osisWork and refSystem are declared in separate 
>container elements, <works> and <refSystems> respectively, by <work> 
>and <refSystem> elements, each of which has an attribute that acts 
>as an identifier for that entry.
>
>3. Q: Do we need an alias attribute on <work> and <refSystem> so 
>that: Bible.KJV.1611 could be used as KJV? (Harry, that is my 
>understanding of your requirement, may be entirely incorrect. Please 
>correct if I have missed the point.) Note that the alias would still 
>have to meet the requirements of the regular regexes.

I thought the ID was arbitrary -- like a namespace *prefix*. The ID 
is what ties actual references back to the right works and reference 
systems, which are then defined by their full DC block (which would, 
for example, have the 1611 as publication date, English as language, 
etc).


>
>4. On the issue of ID/IDREF for osisID, osisRef and osisWork. Note 
>that use of ID/IDREF forces us to obey the XML name constraint, 
>which we do not enforce, deliberately, for osisID for example. I 
>will be posting a greatly reduced schema to hopefully indicate how 
>we could do key/keyref and avoid that problem.

Oh, on the next round could you suppress the 'diagram' things that 
XML Spy generated the last time? They seemed to double the length, 
and were unreadably small anyway.

>
>5. <works> should be required in header and be required to have at 
>least one child <work> which contains all the header stuff.

Is that required one work the DC entry for the work it occurs in, or 
shall we have a separate DC block elsewhere in the header for that?

>
>Comments?
>
>Will push the next release to 6:00 PM today so I can reach all the 
>other posts that are pending and perhaps have some comments back on 
>proposed changes.
>
>Patrick
>
>--
>Patrick Durusau
>Director of Research and Development
>Society of Biblical Literature
>pdurusau@emory.edu


-- 

Steve DeRose -- http://www.stg.brown.edu/~sjd
Chair, Bible Technologies Group -- http://www.bibletechnologies.net
Email: sderose@speakeasy.net
Backup email: sjd@stg.brown.edu