[osis-core] reference systems: my thoughts - issues
Harry Plantinga
osis-core@bibletechnologieswg.org
Fri, 30 Aug 2002 13:58:23 -0400
Todd,
Thanks for carefully thinking about the proposal and helping
debug it!
Brief answers here; answers to issues follow in later messages.
-Harry
> Harry,
>
> To make sure I understand your proposal I would like to
> create a few examples and have you confirm them. Can you
> confirm that the following statements are accurate and
> consistent with your proposed strategy?
>
> 1) Work names (namespaces) are hierarchal in nature.
Yes
>
> 2) The top level identifier defines a reference system.
> "Bible" represents a generic reference system. "Bible.NIV"
> represents a work of sub-class of works that complies with
> its parent "Bible" reference system. "Bible.NIV.1992.en"
> represents the 1992 English printing of the NIV sub-class of
> works that all conform to the Bible reference system.
Yes
> 3) The authors name would no longer be the top level
> identifier unless we have defined a reference system based on
> the author's name, which seems unlikely.
>
>
> Can you confirm that the following examples are consistent
> with your proposed strategy?
>
> EXAMPLE 1:
> <osisText> <!-- default the osisWork="Bible" -->
> <header>
> <work workID="LSV">
> <identifier
> type="OSIS">Bible.French.LSV</identifier>
> <refSystem type="OSIS">Bible.French</refSystem>
> </work>
> <work workID="theMessage">
> <identifier
> type="OSIS">Bible.TheMessage.1993</identifier>
> <refSystem type="OSIS">Bible</refSystem>
> </work>
yes and yes, though you wouldn't have to specify the reference
system unless "Bible.French" is incompatible with "Bible.French.LSV"
or "Bible.TheMessage.1993" is incompatible with "Bible".
> <work workID="conf">
> <identifier type="OSIS">confessions_augustine.
> spck1912</identifier> <!-- reference system not specified and
> implied to be the same as the work -->
> </work>
> </header>
yes
> <div osisID="Ps">
> <div osisID="Ps.45">
> <verse osisID="Ps.45.3">...</verse>
> <note>This same text reads interestingly in
> <reference osisRef="theMessasge:Ps.45.3"/>.
> </note> <!-- referring to the 1993 printing of
> "The Message" translated by Eugene H. Peterson -->
Yes, except that I'm not sure what the semantics of <reference/>
are, exactly -- are you using it to insert a bibliographic reference?
> <note>The French translation of
> <reference osisRef="LSV:Ps.44.3"/>however provides a special
> flavor given the rich French language </note> <!-- referring
> to the French Louis Segond Vesion. See notes below. -->
>
> <note>Interesting discussion of this passage
> exists in <reference osisRef="conf:X.3"/>.</note> <!--
> referring the Confessions of Augustine. (Don't go looking
> for a real tie between X.3 and Ps.45.3) -->
> </div>
> </div>
> </osisText>
Looks good.
> EXAMPLE 2:
> Generic scriptural reference Matthew 1:1 would be
> <osisText osisWork="LSV"> <!-- would we use the valud of
> <work>->workID here or the value of <work>-><identifier>? Is
> this the equivalent of an alias? -->
> <header>
> <work workID="LSV">
> <identifier
> type="OSIS">Bible.French.LSV</identifier>
> <refSystem>Bible.French</refSystem>
> </work>
> <work workID="NIV">
> <identifier type="OSIS">Bible.NIV</identifier>
> <refSystem>Bible.NIV</refSystem>
> </work>
> </header>
>
> <div osisID="Ps">
> <div osisID="Ps.44">
> <verse osisID="Ps.44.3">...</verse>
> <note>The English NIV translates this text as
> <reference osisRef="NIV:Ps.45.3"/>.
> <note>Harry could we also say:
> <reference osisRef="Bible.NIV:Ps.45.3"/> and would the
> Bible.NIV mean the work or reference system or are the
> equavelent?</note>
> </div>
> </div>
> </osisText>
>
> QUESTION:
> 1) Is the workID attribute in <work> supposed to act as an
> alias when forming a reference?
We need to know two identifiers for the current text: its workID
(internal, tied to <work> element) and its osisWork (external).
I think it should be done like this.
<osisText workID="LSV">
<header>
<works>
<work workID="LSV">
<identifier type="OSIS">Bible.French.LSV</identifier>
</work>
etc.
So, yes, you are right, the workID acts as an alias or namespace-like
prefix.