[osis-core] updated issues list
Patrick Durusau
osis-core@bibletechnologieswg.org
Wed, 21 May 2003 12:25:52 -0400
This is a multi-part message in MIME format.
--------------030502060107000804090208
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Guys,
Apologies to Todd for not having the time with all my email problems to
get his detailed post in, its coming but you won't see it before tomorrow.
Looking forward to Dallas!
Patrick
--
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
Patrick.Durusau@sbl-site.org
Co-Editor, ISO 13250, Topic Maps -- Reference Model
--------------030502060107000804090208
Content-Type: text/html; charset=us-ascii;
name="OSIS_Issues.html"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="OSIS_Issues.html"
<html>
<!--THIS FILE IS GENERATED FROM AN XML MASTER.
DO NOT EDIT-->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>OSIS Schema & Best Practices Issues</title>
<link rel="stylesheet" type="text/css" href="/stylesheets/tei-oucs.css">
<meta name="DC.Title" content="OSIS Schema & Best Practices Issues">
<meta name="DC.Author" content="">
<meta name="DC.Language" content="(SCHEME=iso639) en">
<meta name="DC.Creator" content="Oxford University Computing Services, 13 Banbury Road, Oxford OX2 6NN, United Kingdom">
<meta name="DC.Creator.Address" content="webmaster@oucs.ox.ac.uk">
</head>
<body><a name="TOP"></a><table class="header" width="100%">
<tr>
<td rowspan="3"></td>
<td align="left">
<h2 class="institution">Society of Biblical Literature</h2>
</td>
</tr>
<tr>
<td align="left">
<h1 class="maintitle">OSIS Schema & Best Practices Issues</h1>
</td>
</tr>
</table>
<hr>
<h2>Contents</h2>
<ul class="toc">
<li class="toc">1. <a class="toc" href="#body.1_div.1">Schema Bugs, Errors, Fixes</a><ul class="toc">
<li class="toc">1.1. <a class="toc" href="#OSIS_Issues-div-d0e37">Dead Elements - Removal Suggested</a><ul class="toc">
<li class="toc">1.1.1. <a class="toc" href="#OSIS_Issues-div-d0e42"><cell></a></li>
<li class="toc">1.1.2. <a class="toc" href="#OSIS_Issues-div-d0e51">milestones</a></li>
</ul>
</li>
</ul>
</li>
<li class="toc">2. <a class="toc" href="#body.1_div.2">Content Model Issues</a><ul class="toc">
<li class="toc">2.1. <a class="toc" href="#OSIS_Issues-div-d0e67"><div> attributes</a></li>
<li class="toc">2.2. <a class="toc" href="#OSIS_Issues-div-d0e76">Insert <divineName> in <catchWord></a></li>
<li class="toc">2.3. <a class="toc" href="#OSIS_Issues-div-d0e85">lang/script/ews</a></li>
<li class="toc">2.4. <a class="toc" href="#OSIS_Issues-div-d0e112"><table> in <p> and <speech></a></li>
<li class="toc">2.5. <a class="toc" href="#OSIS_Issues-div-d0e121">osisID as list, pointing at with osisRef with grain</a></li>
<li class="toc">2.6. <a class="toc" href="#OSIS_Issues-div-d0e133">osisRef as list?</a></li>
<li class="toc">2.7. <a class="toc" href="#OSIS_Issues-div-d0e142">xml:lang?</a></li>
</ul>
</li>
<li class="toc">3. <a class="toc" href="#body.1_div.3">Best Practices</a><ul class="toc">
<li class="toc">3.1. <a class="toc" href="#OSIS_Issues-div-d0e157">Major Issues</a><ul class="toc">
<li class="toc">3.1.1. <a class="toc" href="#OSIS_Issues-div-d0e162">Levels of Encoding</a></li>
<li class="toc">3.1.2. <a class="toc" href="#OSIS_Issues-div-d0e177">Milestones: Start and Stop</a></li>
<li class="toc">3.1.3. <a class="toc" href="#OSIS_Issues-div-d0e186">Predominant hierarchy</a></li>
<li class="toc">3.1.4. <a class="toc" href="#OSIS_Issues-div-d0e195">Quotes</a></li>
<li class="toc">3.1.5. <a class="toc" href="#OSIS_Issues-div-d0e204">Text in Verses</a></li>
<li class="toc">3.1.6. <a class="toc" href="#OSIS_Issues-div-d0e213">Verse splits</a></li>
</ul>
</li>
<li class="toc">3.2. <a class="toc" href="#OSIS_Issues-div-d0e235">Lesser Issues</a><ul class="toc">
<li class="toc">3.2.1. <a class="toc" href="#OSIS_Issues-div-d0e240">blockQuote vs. Speech</a></li>
<li class="toc">3.2.2. <a class="toc" href="#OSIS_Issues-div-d0e249">Book Titles</a></li>
<li class="toc">3.2.3. <a class="toc" href="#OSIS_Issues-div-d0e258">catchWord</a></li>
<li class="toc">3.2.4. <a class="toc" href="#OSIS_Issues-div-d0e267">Complex or discontinuous text</a></li>
<li class="toc">3.2.5. <a class="toc" href="#OSIS_Issues-div-d0e276">Continuing Paragraph</a></li>
<li class="toc">3.2.6. <a class="toc" href="#OSIS_Issues-div-d0e285">Copyright pages</a></li>
<li class="toc">3.2.7. <a class="toc" href="#OSIS_Issues-div-d0e294">Cross-References in <title></a></li>
<li class="toc">3.2.8. <a class="toc" href="#OSIS_Issues-div-d0e309">Dictionary</a></li>
<li class="toc">3.2.9. <a class="toc" href="#OSIS_Issues-div-d0e318"><div> following <osisText></a></li>
<li class="toc">3.2.10. <a class="toc" href="#OSIS_Issues-div-d0e327">Dublin Core</a></li>
<li class="toc">3.2.11. <a class="toc" href="#OSIS_Issues-div-d0e336">endings, multiple</a></li>
<li class="toc">3.2.12. <a class="toc" href="#OSIS_Issues-div-d0e345">Footnotes</a></li>
<li class="toc">3.2.13. <a class="toc" href="#OSIS_Issues-div-d0e354">Identifier with element</a></li>
<li class="toc">3.2.14. <a class="toc" href="#OSIS_Issues-div-d0e369">Identity of books, works</a></li>
<li class="toc">3.2.15. <a class="toc" href="#OSIS_Issues-div-d0e387">Introduction</a></li>
<li class="toc">3.2.16. <a class="toc" href="#OSIS_Issues-div-d0e396">Introduction content</a></li>
<li class="toc">3.2.17. <a class="toc" href="#OSIS_Issues-div-d0e405">Lines within a line group</a></li>
<li class="toc">3.2.18. <a class="toc" href="#OSIS_Issues-div-d0e414">Major and minor divisions</a></li>
<li class="toc">3.2.19. <a class="toc" href="#OSIS_Issues-div-d0e423">Matthew text example</a></li>
<li class="toc">3.2.20. <a class="toc" href="#OSIS_Issues-div-d0e432">Milestone Pairs</a></li>
<li class="toc">3.2.21. <a class="toc" href="#OSIS_Issues-div-d0e441">Misc. but common structures</a></li>
<li class="toc">3.2.22. <a class="toc" href="#OSIS_Issues-div-d0e450">Non-canonical text and speech</a></li>
<li class="toc">3.2.23. <a class="toc" href="#OSIS_Issues-div-d0e459">Notes</a></li>
<li class="toc">3.2.24. <a class="toc" href="#OSIS_Issues-div-d0e468">Parallel passages</a></li>
<li class="toc">3.2.25. <a class="toc" href="#OSIS_Issues-div-d0e477">Poetry</a></li>
<li class="toc">3.2.26. <a class="toc" href="#OSIS_Issues-div-d0e486">Presentation Punctuation in References</a></li>
<li class="toc">3.2.27. <a class="toc" href="#OSIS_Issues-div-d0e495">Reference encoding</a></li>
<li class="toc">3.2.28. <a class="toc" href="#OSIS_Issues-div-d0e513">Reference to entire work</a></li>
<li class="toc">3.2.29. <a class="toc" href="#OSIS_Issues-div-d0e522">Special Information</a></li>
<li class="toc">3.2.30. <a class="toc" href="#OSIS_Issues-div-d0e531">Split</a></li>
<li class="toc">3.2.31. <a class="toc" href="#OSIS_Issues-div-d0e540">Stanza</a></li>
<li class="toc">3.2.32. <a class="toc" href="#OSIS_Issues-div-d0e549">Title Page</a></li>
<li class="toc">3.2.33. <a class="toc" href="#OSIS_Issues-div-d0e558">Translator practices</a></li>
<li class="toc">3.2.34. <a class="toc" href="#OSIS_Issues-div-d0e567">Verse value</a></li>
<li class="toc">3.2.35. <a class="toc" href="#OSIS_Issues-div-d0e576">Work related practices</a></li>
</ul>
</li>
</ul>
</li>
</ul>
<div class="teidiv">
<h2><a name="body.1_div.1"></a>1. Schema Bugs, Errors, Fixes
</h2>
<div class="teidiv">
<h3><a name="OSIS_Issues-div-d0e37"></a>1.1. Dead Elements - Removal Suggested
</h3>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e42"></a>1.1.1. <cell>
</h4>
<p><a name="d0e47"></a>Has attributes of rows and columns (delete).
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e51"></a>1.1.2. milestones
</h4>
<p><a name="d0e56"></a>osisMilestoneSe, milestoneSe, osisMilestonePt, and milestonePt should be deleted.
</p>
</div>
</div>
</div>
<div class="teidiv">
<h2><a name="body.1_div.2"></a>2. Content Model Issues
</h2>
<div class="teidiv">
<h3><a name="OSIS_Issues-div-d0e67"></a>2.1. <div> attributes
</h3>
<p><a name="d0e72"></a>Add section, front, body, back, titlePage, introduction, index, preface, afterword, colophon, lexeme to type attribute on
<div>.
</p>
</div>
<div class="teidiv">
<h3><a name="OSIS_Issues-div-d0e76"></a>2.2. Insert <divineName> in <catchWord>
</h3>
<p><a name="d0e81"></a>The <divineName> element is meant to control imposition of styling. If not included in <catchWord>, must use ad hoc methods,
leading to inconsistent encoding and more complex stylesheets.
</p>
</div>
<div class="teidiv">
<h3><a name="OSIS_Issues-div-d0e85"></a>2.3. lang/script/ews
</h3>
<p><a name="d0e90"></a>The lang vs. xml:lang issue is already identified. I
think we should also consider adding a script attribute at the same places
where lang currently is. (Plenty of use cases exist Cyrillic vs. Latin
for Serbian being the most recognizable.) I think I recall TEI having a
similar facility for identifying script.
</p>
<p><a name="d0e93"></a>In terms of best practices for these attributes:
</p>
<p><a name="d0e96"></a>lang should be specified as RFC 3066 (currently the only mention of a
language RFC in the schema is a reference to 1766, which this obsoletes,
in the language element)
</p>
<p><a name="d0e99"></a>In addition, we should specify best practices for languages not covered by
ISO 639. x-E-... was suggested previously as a best practice for
identifying languages included in the Ethnologue, but common practice at
SIL and according to LINGUIST List, seems to be to use x-SIL-...
</p>
<p><a name="d0e102"></a>Additionally, I would recommend we specify LINGUIST List's codes for
languages absent from ISO 639 and Ethnologue, using something like
x-LING-.... (Their codes are available here:
http://saussure.linguistlist.org/cfdocs/new-website/LL-WorkingDirs/forms/langs/GetListOfAncientLgs.cfm
http://saussure.linguistlist.org/cfdocs/new-website/LL-WorkingDirs/forms/langs/GetListOfConstructedLgs.cfm
)
</p>
<p><a name="d0e105"></a>If we choose to add a script attribute, ISO 15924 would be the appropriate
standard to follow, but it is not final. Their pattern for codes is
either of [A-Z][a-z]{3} or [0-9]{3} (Codes can be found here:
http://www.evertype.com/standards/iso15924/document/dis15924.pdf)
</p>
<p><a name="d0e108"></a>I still don't know why ews is necessary, but it should at least be
confined to some set of standard values if such a thing exists.
</p>
</div>
<div class="teidiv">
<h3><a name="OSIS_Issues-div-d0e112"></a>2.4. <table> in <p> and <speech>
</h3>
<p><a name="d0e117"></a>Should table be allowed in <p> and <speech>?
</p>
</div>
<div class="teidiv">
<h3><a name="OSIS_Issues-div-d0e121"></a>2.5. osisID as list, pointing at with osisRef with grain
</h3>
<p><a name="d0e126"></a>Ex. osisID="Matt.1.2 Matt.1.3 Matt.1.4" would osisRef="Matt.1.2@ch14" be the SAME as osisRef="Matt.1.3@ch14"
</p>
<p><a name="d0e129"></a>Problem is that the grain reference has to have a certain staring point and that can only be the first osisID. Other issue
is blind pointing, how do I know if the author has used osisID as a list?
</p>
</div>
<div class="teidiv">
<h3><a name="OSIS_Issues-div-d0e133"></a>2.6. osisRef as list?
</h3>
<p><a name="d0e138"></a>Should osisRef be allowed to be a list, like osisID? Would allow <note> to be applied to discontinuous material, avoiding
Todd's annotation extension.
</p>
</div>
<div class="teidiv">
<h3><a name="OSIS_Issues-div-d0e142"></a>2.7. xml:lang?
</h3>
<p><a name="d0e147"></a>Should we replace lang with xml:lang?
</p>
</div>
</div>
<div class="teidiv">
<h2><a name="body.1_div.3"></a>3. Best Practices
</h2>
<div class="teidiv">
<h3><a name="OSIS_Issues-div-d0e157"></a>3.1. Major Issues
</h3>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e162"></a>3.1.1. Levels of Encoding
</h4>
<p><a name="d0e167"></a>Category A: Bibles with just the scripture text and no notion of paragraphs and organized with a book/chapter/verse hierarchy.
</p>
<p><a name="d0e170"></a>Category B: Bibles with paragraphs but no sections, with the paragraphs held by chapter <div> elements.
</p>
<p><a name="d0e173"></a>Category C: Bibles with sections and paragraphs, where sections as <div type="x-section"> elements contain paragraphs.
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e177"></a>3.1.2. Milestones: Start and Stop
</h4>
<p><a name="d0e182"></a>The use of milestone start and end elements
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e186"></a>3.1.3. Predominant hierarchy
</h4>
<p><a name="d0e191"></a>What is the best hierarchy to use for biblical texts?
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e195"></a>3.1.4. Quotes
</h4>
<p><a name="d0e200"></a>Strategy for quotes (not likely to be the predominant hierarchy)
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e204"></a>3.1.5. Text in Verses
</h4>
<p><a name="d0e209"></a>Strategy to put ALL scripture text within a <verse> element.
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e213"></a>3.1.6. Verse splits
</h4>
<p><a name="d0e218"></a><verse> element split in <lg>, <list>, and <table> and should the
schema be changed
</p>
<p><a name="d0e221"></a>Chris: (Personally I think splidIDs are a bad thing in every circumstance where
I've been forced to use them. They force text to be encoded in an
extrememly unnatural manner.)
</p>
<p><a name="d0e224"></a>Allowing <l> inside of <verse> and allowing <l> to not require <lg> seems
like it would solve the line-related part of the problem.
</p>
<p><a name="d0e227"></a>It seems that issue 3.2.25. Stanza was the reason <lg> was created, wasn't it?
</p>
<p><a name="d0e230"></a>Isn't <lg> just a special version of <p> for lines?
</p>
</div>
</div>
<div class="teidiv">
<h3><a name="OSIS_Issues-div-d0e235"></a>3.2. Lesser Issues
</h3>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e240"></a>3.2.1. blockQuote vs. Speech
</h4>
<p><a name="d0e245"></a>Guidelines on usage?
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e249"></a>3.2.2. Book Titles
</h4>
<p><a name="d0e254"></a>For <title> elements, use the type attributes "short" for the short title like "Matthew", "mainTitle" for the main title,
and "subTitle" for any sub titles for the book. (The same could be applied to testaments and book groups.)
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e258"></a>3.2.3. catchWord
</h4>
<p><a name="d0e263"></a>Catchword (unbalanced quotes, <divineName>, etc..) Chris: Also consider inserting <hi> in <catchWord>. This issue comes up
in the TEV.
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e267"></a>3.2.4. Complex or discontinuous text
</h4>
<p><a name="d0e272"></a>Marking AddEsther where chapters interrupt other chapters and alternant reference systems are present.
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e276"></a>3.2.5. Continuing Paragraph
</h4>
<p><a name="d0e281"></a>How to best encode a continuing paragraph after a block quote of line group.
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e285"></a>3.2.6. Copyright pages
</h4>
<p><a name="d0e290"></a>How to deal with the copyright page and the related <work> element
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e294"></a>3.2.7. Cross-References in <title>
</h4>
<p><a name="d0e299"></a>Should cross-references following a <title> be placed in a child <title> element?
</p>
<p><a name="d0e302"></a>Example:
<pre>
<div type="x-section" osisRef="Matt.3.1-Matt.3.12">
<title type="section">The Preaching of John the Baptist
<title type="cross-ref"><reference
osisRef="Mark.1.1-Mark.1.8" type="parallelPassage">Mark
1.1-8</reference> <reference osisRef="Luke.3.1-Luke.3.18"
type="parallelPassage">Luke 3.1-18</reference> <reference
osisRef="John.1.19-John.1.28" type="parallelPassage">John
1.19-28</reference></title></title>
</pre>
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e309"></a>3.2.8. Dictionary
</h4>
<p><a name="d0e314"></a>How to encode a dictionary and other content at the end of a Bible
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e318"></a>3.2.9. <div> following <osisText>
</h4>
<p><a name="d0e323"></a>How to best organize top level structure for introduction sections, mini-dictionaries, glossaries, maps
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e327"></a>3.2.10. Dublin Core
</h4>
<p><a name="d0e332"></a>What should the DC elements in <work> look like for a document that is a portion of the entire work (ie. a single book, single
chapter, set of books, range of verses, several sections from different books).
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e336"></a>3.2.11. endings, multiple
</h4>
<p><a name="d0e341"></a>Multiple endings (marking container elements and osisIDs)
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e345"></a>3.2.12. Footnotes
</h4>
<p><a name="d0e350"></a>Footnotes (<rdg> and superscripted numbers)
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e354"></a>3.2.13. Identifier with element
</h4>
<p><a name="d0e359"></a>The question I have is how do associate an identifier with an element. For example if I wanted to say that a paragraph or
other block of text is about "anger".
</p>
<p><a name="d0e362"></a>The best I can come up with is a <note> element with an osisRef to desired text. (Similar to a cross reference)
</p>
<p><a name="d0e365"></a>This will work with scripture text with a well defined reference system, but for non-Biblical text that often does not have
osisIDs this becomes an issue. (This would likely be resolved if XPath/XPointer like syntax were allowed in a reference or
reference like element.) (Todd)
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e369"></a>3.2.14. Identity of books, works
</h4>
<p><a name="d0e374"></a>How to identify a book of Esther (Esther vs. Additions to Esther vs. Greek
Esther). (Goes with 3.2.4. Complex or discontinuous text, somewhat.)
</p>
<p><a name="d0e377"></a>How to identify books of Ezra/Nehemiah/Esdras.
</p>
<p><a name="d0e380"></a>Depending on these... potentially, how to identify 1-2Kgs/1-2Chr vs. 1-4Kgdms.
</p>
<p><a name="d0e383"></a>How to identify books that occur multiply within a work (e.g. Esther in NRSVA & others; Psalms in Vulgate; Joshua, Judges,
Daniel, & Tobit in Rahlfs')
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e387"></a>3.2.15. Introduction
</h4>
<p><a name="d0e392"></a>Should the introduction to a book be marked as a <> or a <list>?
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e396"></a>3.2.16. Introduction content
</h4>
<p><a name="d0e401"></a>The text found at the front of a bible, testament, book group, or book. Contain this type of content in a <div type="x-introduction">
element.
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e405"></a>3.2.17. Lines within a line group
</h4>
<p><a name="d0e410"></a>Use type="q", type="q2" (or similar type names) and a set of other standardized types to indicate the specific nature of the
<l> element.
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e414"></a>3.2.18. Major and minor divisions
</h4>
<p><a name="d0e419"></a>Major and minor divisions in the text.
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e423"></a>3.2.19. Matthew text example
</h4>
<p><a name="d0e428"></a>Should Matt.1.2-Matt.1.6a be encoded as osisID="Matt.1.2 Matt.1.3 Matt.1.4 Matt.1.5 Matt.1.6 Matt.1.6a" or osisID="Matt.1.2
Matt.1.3 Matt.1.4 Matt.1.5 Matt.1.6"? The logic being that "a" is simply a TYPOGRAPHIC mechanism to indicate that there are
two blocks of text with Matt.1.6 in them! I believe the latter form is CORRECT even though I have argued for the alternative
in the past.
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e432"></a>3.2.20. Milestone Pairs
</h4>
<p><a name="d0e437"></a>Some guidelines on how to use milestone pairs for chapters, verses, and quotes and how to be consistent in the use of milestones
vs elements.
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e441"></a>3.2.21. Misc. but common structures
</h4>
<p><a name="d0e446"></a>glossary, map, mini-dictionary, Thompson Chain Reference (Todd), see http://www.zondervan.com/media/pdfs/0310912229.pdf for
example (I have a local copy for the meeting. pld)
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e450"></a>3.2.22. Non-canonical text and speech
</h4>
<p><a name="d0e455"></a>How to encode non-canonical text associated with the start of a speech. (<seg type="speechStart">She Speeks</seg>)
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e459"></a>3.2.23. Notes
</h4>
<p><a name="d0e464"></a>A "best practices" guideline for type attributes that indicate the type of note. Chris: Add cross-reference osisNotes type
(unless there seems to be a better practice)
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e468"></a>3.2.24. Parallel passages
</h4>
<p><a name="d0e473"></a>Use a <div type="parallelPassage"> with strictly a set of <reference> elements and the related display text as children.
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e477"></a>3.2.25. Poetry
</h4>
<p><a name="d0e482"></a>How to encode lines of poetry: Line breaks, multiple translator specified line splitting alternatives. What is presentation
and what is data?
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e486"></a>3.2.26. Presentation Punctuation in References
</h4>
<p><a name="d0e491"></a>The best way to encode a series of references with various presentation punctuation.
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e495"></a>3.2.27. Reference encoding
</h4>
<p><a name="d0e500"></a>In OSIS documents that are not Bibles, it is a common to see a quote of
scripture text followed by the reference.
</p>
<p><a name="d0e503"></a>Does it make sense to add an optional osisRef attribute to <q> and
<milestoneStart> to accommodate this frequent issue?
</p>
<p><a name="d0e506"></a>Example:
<q osisRef="Matt.20.28">The Son of Man did not come to be served, but
to serve . . . </q>
</p>
<p><a name="d0e509"></a>rather than
<q>The Son of Man did not come to be served, but to serve . .
.<reference osisRef="Matt.20.28">Matthew 20:28</reference></q> (Todd)
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e513"></a>3.2.28. Reference to entire work
</h4>
<p><a name="d0e518"></a>Introduction to CEV has references to entire works. How to encode? (Todd)
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e522"></a>3.2.29. Special Information
</h4>
<p><a name="d0e527"></a>How to preserve special information related to verse numbers that can not be represented with an osisID ("*1") at Bible.CEV.Gen.49.1.
(Is this really a note?)
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e531"></a>3.2.30. Split
</h4>
<p><a name="d0e536"></a>Only split AND only use the attribute "splitID" for the following elements: <verse>, <div type="chapter">, <div type="x-section">,
and <p>.
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e540"></a>3.2.31. Stanza
</h4>
<p><a name="d0e545"></a>How to best encode "stanza" in the Psalms.
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e549"></a>3.2.32. Title Page
</h4>
<p><a name="d0e554"></a>How to deal with the title page
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e558"></a>3.2.33. Translator practices
</h4>
<p><a name="d0e563"></a>How to encode the idea created by the translator that leads to a blank line being rendered? (This would be additional spacing
than would normally exist between two paragraphs to emphasize a shift in thought.)
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e567"></a>3.2.34. Verse value
</h4>
<p><a name="d0e572"></a>Use the n attribute to indicate the verse value to present when more than one value is present in an osisID. (Eg. <verse
n="1-2" osisID="Matt.1.1 Matt.1.2">)
</p>
</div>
<div class="teidiv">
<h4><a name="OSIS_Issues-div-d0e576"></a>3.2.35. Work related practices
</h4>
<p><a name="d0e581"></a>Work related practices for different scenarios. (I am thinking primarily about the "thisWork" element.)
</p>
</div>
</div>
</div>
<hr>
<div class="footer"><a class="plain" target="_top" href="http://www.ox.ac.uk/">Society of Biblical Literature</a>
| <a class="plain" target="_top" href="http://www.sbl-site.org">SBL</a></div>
<hr>
<address>Date:
Author: .
<br><a href="/documentation/copyright.html">©</a> Society of Biblical Literature.
<!--
Generated from OSIS_Issues using an XSLT version 1 stylesheet
based on http://www.oucs.ox.ac.uk/stylesheets/teihtml.xsl
processed using SAXON 6.5 from Michael Kay on 2003-05-21T12:24:04Z-->
</address>
</body>
</html>
--------------030502060107000804090208--