<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On Feb 4, 2007, at 4:18 AM, Chris Little wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Troy A. Griffitts wrote:</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV> <BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">I thought we left the OSIS specification to say that osisRef defaulted<SPAN class="Apple-converted-space"> </SPAN></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">to Bible.KJV if no prefix was specified in the osisRef and no<SPAN class="Apple-converted-space"> </SPAN></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">osisRefWork was defined.<SPAN class="Apple-converted-space"> </SPAN>We tried to steer OSIS as much as we could to<SPAN class="Apple-converted-space"> </SPAN></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">match how SWORD operates in areas we felt SWORD has already flushed out<SPAN class="Apple-converted-space"> </SPAN></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">reasonable behavior over the years.</DIV> </BLOCKQUOTE><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Actually, it was Bible.NRSVA. But that's 99.9% identical to a KJV +<SPAN class="Apple-converted-space"> </SPAN></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Apocrypha.</DIV></BLOCKQUOTE><BR></DIV><DIV>I can't comment on what was decided at the OSIS meetings, but the current manual says:</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><FONT class="Apple-style-span" face="Times New Roman" size="4"><SPAN class="Apple-style-span" style="font-size: 14px;"><B>"Appendix K.1 Prefix: (optional)</B></SPAN></FONT><FONT class="Apple-style-span" face="Times New Roman"></FONT></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><FONT class="Apple-style-span" face="Times New Roman">Note that if you omit the prefix on an </FONT><FONT class="Apple-style-span" face="Times New Roman"><B>osisRef</B></FONT><FONT class="Apple-style-span" face="Times New Roman">, it is optional afterall, your reference can only point to another</FONT><FONT class="Apple-style-span" face="Times New Roman"> location in the OSIS text where you are inserting the <B>osisRef</B>. This is the equivalent of the <B>osisID</B> without a prefix, it defaults to the text that you are working in at the moment."</FONT></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><BR class="khtml-block-placeholder"></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><BR class="khtml-block-placeholder"></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">This may be an error/inconsistency in the documentation, as there is the osisRefWork, which in every example in the manual has it as "Bible" or "bible", which is described as follows:</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><BR class="khtml-block-placeholder"></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><FONT class="Apple-style-span" face="Times New Roman">"Every </FONT><FONT class="Apple-style-span" face="Times New Roman"><B>osisText</B></FONT><FONT class="Apple-style-span" face="Times New Roman"> element specifies what reference or versification scheme any osisRefs within it refer to. This</FONT><FONT class="Apple-style-span" face="Times New Roman"> may or may not be the same work."</FONT></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><FONT class="Apple-style-span" face="Times New Roman"><FONT class="Apple-style-span" face="Helvetica"> </FONT></FONT></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">There is a deprecation of the osisRefWork in favor of a new mechanism workPrefix, which allows one to associate specific paths with a workID. However, it is, in my opionion, an unnecessary complication for this discussion.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><BR class="khtml-block-placeholder"></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">I think that the core behavior that needs to be added is the distinction between internal and external references. I don't know that we need a robust external reference system.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><BR class="khtml-block-placeholder"></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">One or the other needs to have a prefix. Currently Sword only supports Bible links and probably the majority of links in a Bible are blblical, as well as the links in a commentary. From a minimization of storage and the preseveration of current behavior, it makes sense to presume a default biblical osisWorkRef.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><BR class="khtml-block-placeholder"></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">The question then is what do we use for self references in a non-Bible?</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><BR class="khtml-block-placeholder"></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">The immediately obvious answer is to use the [name] of the module.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><BR class="khtml-block-placeholder"></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">The workID mechanism of OSIS requires that every prefix in a work be declared in the document's header. This is a mapping of a symbolic name to another work or the same work. From what I can tell, we could give the workIDs non-sensical values, such as "xyz" or "doesNotMatter".</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><BR class="khtml-block-placeholder"></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">With this we could declare a workID of "self" for the osisRefs pointing to self. (Or any other good value.)</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><BR class="khtml-block-placeholder"></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">The question is then "Does this paint us into a corner, if we ever decide to have a general reference system?" In such a case where we need to refer to a specific external work, we would need to add support for other prefixes.</DIV></BODY></HTML>