[osis-core] almost got a text ready

[Troy A. Griffitts]

Todd,
	Yeah, I used to have an identifier in there in the 
defaultReferenceScheme work, but didn't know what I thought about that. 
  It seems to imply that I want my references defaulted to the KJV 
Bible, but I really am only saying that I am using the KJV reference 
scheme.  I don't really want my references to default to the KJV of the 
Bible, by any means.

	I think we agreed that MY work entry needed an <identifier type="OSIS"> 
or my osisID tags wouldn't be referencable from outside.  We didn't 
really discuss the osisRefWork work element needing one.  Interesting to 
hear what you think.

	Yes, I probably should use Bible.KJV for my id, but still would like to 
know if I should use something more specific like: 
Bible.KJV.1769.CrossWire. We really should give some recommendations for 
these names.

	-Troy.



Todd Tillinghast wrote:
> Troy,
> 
> Two comments below, one makes the document "OSIS valid" and the other is
> just a comment.
> 
> <osisText osisIDWork="KJV" osisRefWork="defaultReferenceScheme">
>    <header>
>       <work osisWork="KJV">
>          <title>King James Version of 1769 with Strongs Numbers</title>
>          <identifier type="OSIS">KJV</identifier> <!-- Why is this not
> "Bible.KJV" -->
>          <language>en</language>
>          <refSystem>Bible.KJV</refSystem>
>       </work>
>       <work osisWork="defaultReferenceScheme">
>          <refSystem>Bible.KJV</refSystem>
>          <identifier type="OSIS">Bible.KJV</identifier> <!-- added this line
> since you used "defaultReferenceSystem" in <osisText> -->
>       </work>
> </header>
> 
> Todd
> 
> 
>>Thanks guys!
>>
>>Well, I have a doc validating, at least!  I've included the message I
>>sent to Andrew, with links to the text if you'd like to comment on it.
>>
>>-Troy.
>>________________________________________________________
>>
>>
>>Andrew,
>>     My sincere apology for not getting this to you sooner.  I'm
>>including a sample OSIS document for you to post.  This document is the
>>OT of the KJV in standard, valid OSIS markup, and also includes extended
>>OSIS markup for word lemma and morphology, as well as footnotes.  I
>>think it serves as a good example and is freely distributable by ABS.
>>
>>Here are links to the attached file, and also to a complete, OT and NT
>>version.  The NT of this text includes lemma markup to which an
>>individual named Larry Pierce claims a copyright against.  This is the
>>reason for sending you an OT-only version.  The final version of this
>>document will include lemma markup in the NT by us, at CrossWire, which
>>we will place in the public domain.
>>
>>freely distributable KJV OT:
>>http://www.crosswire.org/~scribe/kjvot.zip
>>
>>OT/NT version that CrossWire has obtained permission from Larry Pierce
>>to distribute
>>http://www.crosswire.org/~scribe/kjv.zip
>>
>>
>>Many more to follow in the coming weeks!
>>
>>     -Troy.
>>
>>_________________________________________________________
>>
>>
>>
>>
>>
>>
>>Chris Little wrote:
>>
>>>I'll take a crack at them....
>>>
>>>On Mon, 9 Sep 2002, Troy A. Griffitts wrote:
>>>
>>>
>>>
>>>>1) Seems I don't know where in the xml file to specify that I'm using
>>>>osisCore.1.1.xsd
>>>
>>>
>>>The following is what I have (and XMLSpy likes it):
>>>
>>><?xml version="1.0" encoding="UTF-8"?>
>>><osis xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>xsi:noNamespaceSchemaLocation="osisCore.1.1.xsd">
>>>
>>>
>>>
>>>>2) title doesn't seem to like living in work
>>>
>>>
>>>Those elements within work are in a sequence, so title needs to come
>>>first.
>>>
>>>
>>>
>>>>3) what booknames should I use?  I've still got the "_2cor" type names
>>>>and I'm pretty sure we've changed them to something like "2Cor"
>>>
>>>
>>>I don't know if we have published any kind of standard set, but the SBL
>>>abbreviations were what I remember us agreeing upon.
>>>
>>>How should we make this fact known?
>>>
>>>
>>>
>>>>4) I couldn't use spaces to separate my list of attribute values on some
>>>>of <w>'s attributes, so I've '|' separated them.  Not sure if this is
>>>>ok, but it validates :)
>>>
>>>
>>>Can't help there...
>>>
>>>
>>>
>>>>5) Actually, I NEED spaces for some of <w>'s attributes, eg. were an
>>>>english gloss might be 2 words.
>>>
>>>
>>>I needed spaces for some morphological tags in one of my books and ended
>>>up converting them to underscores.  This is probably not be the most
>>>attractive solution, especially for glosses.
>>>
>>>
>>>--Chris
>>
>>
>>