[osis-core] Latest version attached!

Patrick Durusau osis-core@bibletechnologieswg.org
Sun, 16 Nov 2003 16:18:28 -0500


This is a multi-part message in MIME format.
--------------090305060603020601050909
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Greetings!

Well, off the to usual start!

Someday Todd is going to design a system that knows what I am thinking! 
  Not sure how I will feel about having my own computer being a witness 
against me once the thought police get in full swing. ;-)

Latest version is attached this time!

Hope everyone is having a great day!

Patrick

-- 
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
Patrick.Durusau@sbl-site.org
Chair, V1 - Text Processing: Office and Publishing Systems Interface
Co-Editor, ISO 13250, Topic Maps -- Reference Model

Topic Maps: Human, not artificial, intelligence at work!

--------------090305060603020601050909
Content-Type: text/html; charset=us-ascii;
 name="osisUserManual_06.html"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="osisUserManual_06.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&#8482; 2.0 User's Manual (draft)</title>
      <link rel="stylesheet" type="text/css" href="/stylesheets/tei-oucs.css">
      <meta name="DC.Title" content="OSIS&#8482; 2.0 User's Manual (draft)">
      <meta name="DC.Author" content="Patrick Durusau, Patrick.Durusau@sbl-site.org">
      <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">Bible Technologies Group</h2>
            </td>
         </tr>
         <tr>
            <td align="left">
               <h1 class="maintitle">OSIS&#8482; 2.0 User's Manual (draft)</h1>
            </td>
         </tr>
      </table>
      <hr>
      <h2>Contents</h2>
      <ul class="toc">
         <li class="toc">1. <a class="toc" href="#body.1_div.1">Introduction to OSIS&#8482;</a></li>
         <li class="toc">2. <a class="toc" href="#body.1_div.2">Getting started</a><ul class="toc">
               <li class="toc">2.1. <a class="toc" href="#osisUserManual_06-div-d0e246">Some authoring tools</a></li>
            </ul>
         </li>
         <li class="toc">3. <a class="toc" href="#body.1_div.3">Your First OSIS Document</a></li>
         <li class="toc">4. <a class="toc" href="#body.1_div.4">XML and OSIS declarations</a></li>
         <li class="toc">5. <a class="toc" href="#body.1_div.5">Canonical vs. non-canonical parts of a work</a><ul class="toc">
               <li class="toc">5.1. <a class="toc" href="#osisUserManual_06-div-d0e422">Meaning of thecanonicalattribute</a></li>
            </ul>
         </li>
         <li class="toc">6. <a class="toc" href="#body.1_div.6">The OSIS text header</a><ul class="toc">
               <li class="toc">6.1. <a class="toc" href="#osisUserManual_06-div-d0e459">The Revision Description</a></li>
               <li class="toc">6.2. <a class="toc" href="#osisUserManual_06-div-d0e509">Work Declarations</a></li>
               <li class="toc">6.3. <a class="toc" href="#osisUserManual_06-div-d0e580">The Dublin Core</a><ul class="toc">
                     <li class="toc">6.3.1. <a class="toc" href="#osisUserManual_06-div-d0e596">title</a></li>
                     <li class="toc">6.3.2. <a class="toc" href="#osisUserManual_06-div-d0e620">creator</a></li>
                     <li class="toc">6.3.3. <a class="toc" href="#osisUserManual_06-div-d0e632">contributor</a></li>
                     <li class="toc">6.3.4. <a class="toc" href="#osisUserManual_06-div-d0e650">date</a></li>
                     <li class="toc">6.3.5. <a class="toc" href="#osisUserManual_06-div-d0e695">publisher</a></li>
                     <li class="toc">6.3.6. <a class="toc" href="#osisUserManual_06-div-d0e712">language</a></li>
                     <li class="toc">6.3.7. <a class="toc" href="#osisUserManual_06-div-d0e726">type</a></li>
                     <li class="toc">6.3.8. <a class="toc" href="#osisUserManual_06-div-d0e743">identifier</a></li>
                     <li class="toc">6.3.9. <a class="toc" href="#osisUserManual_06-div-d0e763">coverage</a></li>
                     <li class="toc">6.3.10. <a class="toc" href="#osisUserManual_06-div-d0e771">description</a></li>
                     <li class="toc">6.3.11. <a class="toc" href="#osisUserManual_06-div-d0e785">format</a></li>
                     <li class="toc">6.3.12. <a class="toc" href="#osisUserManual_06-div-d0e799">relation</a></li>
                     <li class="toc">6.3.13. <a class="toc" href="#osisUserManual_06-div-d0e810">rights</a></li>
                     <li class="toc">6.3.14. <a class="toc" href="#osisUserManual_06-div-d0e827">subject</a><ul class="toc">
                           <li class="toc">6.3.14.1. <a class="toc" href="#osisUserManual_06-div-d0e840">subject classification systems</a></li>
                           <li class="toc">6.3.14.2. <a class="toc" href="#osisUserManual_06-div-d0e941">source</a></li>
                           <li class="toc">6.3.14.3. <a class="toc" href="#osisUserManual_06-div-d0e955">type</a></li>
                        </ul>
                     </li>
                     <li class="toc">6.3.15. <a class="toc" href="#osisUserManual_06-div-d0e970">Non-Dublin Core Elements and Attributes in the Work Declaration</a><ul class="toc">
                           <li class="toc">6.3.15.1. <a class="toc" href="#osisUserManual_06-div-d0e974">scope</a></li>
                        </ul>
                     </li>
                  </ul>
               </li>
               <li class="toc">6.4. <a class="toc" href="#osisUserManual_06-div-d0e993">Identifying a Work given a work declaration element</a></li>
               <li class="toc">6.5. <a class="toc" href="#osisUserManual_06-div-d0e1043">Date formats</a></li>
            </ul>
         </li>
         <li class="toc">7. <a class="toc" href="#body.1_div.7">Title Pages</a></li>
         <li class="toc">8. <a class="toc" href="#body.1_div.8">Basic Elements</a></li>
         <li class="toc">9. <a class="toc" href="#body.1_div.9">Simple paragraphing, quotes, and notes</a></li>
         <li class="toc">10. <a class="toc" href="#body.1_div.10">Elements that cross other elements</a></li>
         <li class="toc">11. <a class="toc" href="#body.1_div.11">Special Text Types</a><ul class="toc">
               <li class="toc">11.1. <a class="toc" href="#osisUserManual_06-div-d0e1543">Markup for epistles and similar materials</a><ul class="toc">
                     <li class="toc">11.1.1. <a class="toc" href="#osisUserManual_06-div-d0e1550">salute</a></li>
                     <li class="toc">11.1.2. <a class="toc" href="#osisUserManual_06-div-d0e1564">signed</a></li>
                     <li class="toc">11.1.3. <a class="toc" href="#osisUserManual_06-div-d0e1699">closer</a><ul class="toc">
                           <li class="toc">11.1.3.1. <a class="toc" href="#osisUserManual_06-div-d0e1725">benediction</a></li>
                        </ul>
                     </li>
                  </ul>
               </li>
               <li class="toc">11.2. <a class="toc" href="#osisUserManual_06-div-d0e1748">Dramatic texts</a></li>
               <li class="toc">11.3. <a class="toc" href="#osisUserManual_06-div-d0e1846">speaker</a></li>
               <li class="toc">11.4. <a class="toc" href="#osisUserManual_06-div-d0e1866">speech</a></li>
               <li class="toc">11.5. <a class="toc" href="#osisUserManual_06-div-d0e1892">Marking up poetic material</a><ul class="toc">
                     <li class="toc">11.5.1. <a class="toc" href="#osisUserManual_06-div-d0e1905">lg</a></li>
                     <li class="toc">11.5.2. <a class="toc" href="#osisUserManual_06-div-d0e1913">l</a></li>
                     <li class="toc">11.5.3. <a class="toc" href="#osisUserManual_06-div-d0e1933">lb</a></li>
                  </ul>
               </li>
               <li class="toc">11.6. <a class="toc" href="#osisUserManual_06-div-d0e1950">Lists, tables, genealogies, figures and other material</a><ul class="toc">
                     <li class="toc">11.6.1. <a class="toc" href="#osisUserManual_06-div-d0e1957">list</a></li>
                     <li class="toc">11.6.2. <a class="toc" href="#osisUserManual_06-div-d0e1965">label</a></li>
                     <li class="toc">11.6.3. <a class="toc" href="#osisUserManual_06-div-d0e1973">item</a></li>
                     <li class="toc">11.6.4. <a class="toc" href="#osisUserManual_06-div-d0e1986">table</a></li>
                     <li class="toc">11.6.5. <a class="toc" href="#osisUserManual_06-div-d0e1994">row</a></li>
                     <li class="toc">11.6.6. <a class="toc" href="#osisUserManual_06-div-d0e2002">cell</a></li>
                     <li class="toc">11.6.7. <a class="toc" href="#osisUserManual_06-div-d0e2012">figure</a></li>
                     <li class="toc">11.6.8. <a class="toc" href="#osisUserManual_06-div-d0e2074">caption</a></li>
                  </ul>
               </li>
               <li class="toc">11.7. <a class="toc" href="#osisUserManual_06-div-d0e2083">milestone</a></li>
               <li class="toc">11.8. <a class="toc" href="#osisUserManual_06-div-d0e2161">milestoneStart and milestoneEnd</a></li>
            </ul>
         </li>
         <li class="toc">12. <a class="toc" href="#body.1_div.12">Common elements in all texts</a><ul class="toc">
               <li class="toc">12.1. <a class="toc" href="#osisUserManual_06-div-d0e2180">a</a></li>
               <li class="toc">12.2. <a class="toc" href="#osisUserManual_06-div-d0e2197">index</a></li>
               <li class="toc">12.3. <a class="toc" href="#osisUserManual_06-div-d0e2241">reference</a></li>
               <li class="toc">12.4. <a class="toc" href="#osisUserManual_06-div-d0e2260">abbr</a></li>
               <li class="toc">12.5. <a class="toc" href="#osisUserManual_06-div-d0e2274">catchWord</a></li>
               <li class="toc">12.6. <a class="toc" href="#osisUserManual_06-div-d0e2285">divineName</a></li>
               <li class="toc">12.7. <a class="toc" href="#osisUserManual_06-div-d0e2296">foreign</a></li>
               <li class="toc">12.8. <a class="toc" href="#osisUserManual_06-div-d0e2307">hi</a></li>
               <li class="toc">12.9. <a class="toc" href="#osisUserManual_06-div-d0e2342">seg</a></li>
               <li class="toc">12.10. <a class="toc" href="#osisUserManual_06-div-d0e2356">inscription</a></li>
               <li class="toc">12.11. <a class="toc" href="#osisUserManual_06-div-d0e2382">mentioned</a></li>
               <li class="toc">12.12. <a class="toc" href="#osisUserManual_06-div-d0e2405">name</a></li>
               <li class="toc">12.13. <a class="toc" href="#osisUserManual_06-div-d0e2468">q</a></li>
               <li class="toc">12.14. <a class="toc" href="#osisUserManual_06-div-d0e2481">rdg</a></li>
               <li class="toc">12.15. <a class="toc" href="#osisUserManual_06-div-d0e2504">transChange</a></li>
               <li class="toc">12.16. <a class="toc" href="#osisUserManual_06-div-d0e2550">w</a></li>
            </ul>
         </li>
         <li class="toc">13. <a class="toc" href="#body.1_div.13">Canonical refererence (or versification) schemes</a><ul class="toc">
               <li class="toc">13.1. <a class="toc" href="#osisUserManual_06-div-d0e2606">Partial identifiers</a></li>
               <li class="toc">13.2. <a class="toc" href="#osisUserManual_06-div-d0e2626">Works</a></li>
               <li class="toc">13.3. <a class="toc" href="#osisUserManual_06-div-d0e2643">Sub-identifiers</a></li>
               <li class="toc">13.4. <a class="toc" href="#osisUserManual_06-div-d0e2660">Grouping</a></li>
               <li class="toc">13.5. <a class="toc" href="#osisUserManual_06-div-d0e2677">Other details of osisIDs</a></li>
               <li class="toc">13.6. <a class="toc" href="#osisUserManual_06-div-d0e2691">Coding multiple versification or reference schemes in a single document</a></li>
            </ul>
         </li>
         <li class="toc">14. <a class="toc" href="#body.1_div.14">OSIS references</a></li>
         <li class="toc">15. <a class="toc" href="#body.1_div.15">Different versification systems</a></li>
         <li class="toc">16. <a class="toc" href="#body.1_div.16">Conformance requirements</a><ul class="toc">
               <li class="toc">16.1. <a class="toc" href="#osisUserManual_06-div-d0e2819">Conformance levels</a><ul class="toc">
                     <li class="toc">16.1.1. <a class="toc" href="#osisUserManual_06-div-d0e2826">Level 1: "Minimal OSIS document"</a></li>
                     <li class="toc">16.1.2. <a class="toc" href="#osisUserManual_06-div-d0e2864">Level 2: "Basic OSIS Document"</a></li>
                     <li class="toc">16.1.3. <a class="toc" href="#osisUserManual_06-div-d0e2914">Level 3: Complete OSIS document</a></li>
                     <li class="toc">16.1.4. <a class="toc" href="#osisUserManual_06-div-d0e2925">Level 4: Scholarly OSIS document</a></li>
                  </ul>
               </li>
               <li class="toc">16.2. <a class="toc" href="#osisUserManual_06-div-d0e2943">Quality levels</a></li>
               <li class="toc">16.3. <a class="toc" href="#osisUserManual_06-div-d0e2951">Level 1: Sub-OCR Quality</a></li>
               <li class="toc">16.4. <a class="toc" href="#osisUserManual_06-div-d0e2959">Level 2: OCR Quality</a></li>
               <li class="toc">16.5. <a class="toc" href="#osisUserManual_06-div-d0e2967">Level 3: Proof Quality</a></li>
               <li class="toc">16.6. <a class="toc" href="#osisUserManual_06-div-d0e2975">Level 4: Trusted Quality</a></li>
            </ul>
         </li>
         <li class="toc">17. <a class="toc" href="#body.1_div.17">Application Requirements</a></li>
         <li class="toc">18. <a class="toc" href="#body.1_div.18">Alphabetical list of Elements</a></li>
         <li class="toc">19. <a class="toc" href="#body.1_div.19">Alphabetical list of Attributes and normative values</a><ul class="toc">
               <li class="toc">19.1. <a class="toc" href="#osisUserManual_06-div-d0e3451">Global attributes</a></li>
               <li class="toc">19.2. <a class="toc" href="#osisUserManual_06-div-d0e3662">Normative values for the type attribute, by element</a><ul class="toc">
                     <li class="toc">19.2.1. <a class="toc" href="#osisUserManual_06-div-d0e3672">annotation</a></li>
                     <li class="toc">19.2.2. <a class="toc" href="#osisUserManual_06-div-d0e3727">calendar</a></li>
                     <li class="toc">19.2.3. <a class="toc" href="#osisUserManual_06-div-d0e3765">milestoneStart and milestoneEnd (deprecated)</a></li>
                     <li class="toc">19.2.4. <a class="toc" href="#osisUserManual_06-div-d0e3841">change types</a></li>
                     <li class="toc">19.2.5. <a class="toc" href="#osisUserManual_06-div-d0e3879">div</a></li>
                     <li class="toc">19.2.6. <a class="toc" href="#osisUserManual_06-div-d0e4050">osisMilestonePt</a></li>
                     <li class="toc">19.2.7. <a class="toc" href="#osisUserManual_06-div-d0e4093">name</a></li>
                     <li class="toc">19.2.8. <a class="toc" href="#osisUserManual_06-div-d0e4126">notes</a></li>
                     <li class="toc">19.2.9. <a class="toc" href="#osisUserManual_06-div-d0e4189">titles</a></li>
                  </ul>
               </li>
            </ul>
         </li>
         <li class="toc">20. <a class="toc" href="#body.1_div.20">Selected Contributor Roles</a></li>
         <li class="toc">21. <a class="toc" href="#body.1_div.21">Normative Abbreviations for canonical and deutero-canonical books</a><ul class="toc"></ul>
         </li>
         <li class="toc">22. <a class="toc" href="#body.1_div.22">Encoding commentaries</a></li>
         <li class="toc">23. <a class="toc" href="#body.1_div.23">Encoding devotionals, lectionaries, and time-organized documents</a></li>
         <li class="toc">24. <a class="toc" href="#body.1_div.24">Encoding multilingual editions</a></li>
         <li class="toc">25. <a class="toc" href="#body.1_div.25">Encoding glossaries, dictionaries, and lexica</a></li>
         <li class="toc">26. <a class="toc" href="#body.1_div.26">Standard OSIS Codes for Bible Editions</a><ul class="toc">
               <li class="toc">26.1. <a class="toc" href="#osisUserManual_06-div-d0e4815">Ancient language editions</a><ul class="toc">
                     <li class="toc">26.1.1. <a class="toc" href="#osisUserManual_06-div-d0e4864">English Editions (prefix "en:")</a></li>
                     <li class="toc">26.1.2. <a class="toc" href="#osisUserManual_06-div-d0e5408">Non-English Modern Languages</a></li>
                  </ul>
               </li>
            </ul>
         </li>
         <li class="toc">27. <a class="toc" href="#body.1_div.27">Complete list of USMARC Relator Codes</a></li>
         <li class="toc">28. <a class="toc" href="#body.1_div.28">The Bible Technology Group</a></li>
      </ul>
      
          
      <div class="teidiv">
         <h2><a name="body.1_div.1"></a>1. Introduction to OSIS&#8482;
         </h2>
         
              
         
         
         <p><a name="d0e196"></a>
                 Welcome to the OSIS (Open Scriptural Information Standard&#8482;)
            User's Manual. OSIS is a set of XML structures that can be used to
            produce Bibles, commentaries, and related texts that can be easily
            interchanged with other users, formatted as HTML, PDF, Postscript or
            any other desired format, and searched on any personal computer. It
            provides a standard way to express such documents, which is important
            because it saves time, money, and effort for:
            
         </p>
         
         
         <ul>
            <li><a name="d0e201"></a>
               authors, who will have less need to adjust their manuscripts for each
               different potential publisher;
               
            </li>
            <li><a name="d0e204"></a>
               publishers, who will gradually come to experience lower costs by not
               having to manage converting texts presented by authors in so wide a
               variety of formats, and by not having to provide texts in a different
               form to each electronic-book system vendor out there (or pay
               indirectly for those vendors to do the conversions).
               
            </li>
            <li><a name="d0e207"></a>
               and software vendors, who can avoid writing a lot of code to manage
               different formats, and thus make their programs smaller, faster, and
               more reliable.
               
            </li>
         </ul>
         
         
         <p><a name="d0e211"></a>
            The OSIS development team closely studied previous Bible encoding
            forms, as well as tools for literary encoding in general. By doing
            this we hope we have avoided some weaknesses, and gained from some
            strengths, of each one, and we thank the many people who worked on
            those prior specifications, as well as those who have provided help
            and feedback in developing OSIS itself, and testing it by encoding
            large numbers of Biblical and related texts. A list of participants
            may be found in an Appendix.
         </p>
         
         
         <p><a name="d0e214"></a>Users familiar with the Text Encoding Initiative will find OSIS
            markup quite familiar, because the bulk of the elements we define
            correspond directly to TEI elements, and almost always have the same
            name (though often simplified content). The schema also provides a
            TEIform attribute for such elements, so they can be recognized by
            form-aware processors as equivalent to their TEI counterparts. We
            have attempted to point out any elements below that do not have TEI
            equivalents, for the sake of anyone using both systems.
            
         </p>
         
         
         <p><a name="d0e217"></a>OSIS is provided as a free resource by the Bible Technologies
            Group&#8482; (or BTG&#8482;), which is a collaborative effort of the
            American Bible Society, the Society of Biblical Literature, the
            Summer Institute of Linguistics, the United Bible Societies, other
            Bible Societies and related groups, and individual volunteers around
            the world. OSIS is designed to meet the needs of diverse user
            communities who read, study, research, translate or distribute
            biblical texts. This introduction gives a brief overview of OSIS
            before leading you step by step through producing your first OSIS
            text.
         </p>
         
         
         <p><a name="d0e220"></a>
            For more information on OSIS, you may wish to join the OSIS Users'
            Group. To do so, send mail to osis-user@whi.wts.edu, setting the
            Subject line to "subscribe". Online information about OSIS is also
            available at http://www.bibletechnologies.org and
            http://www.bibletechnologieswg.org.
            
         </p>
         
         
      </div>
      
          
      <div class="teidiv">
         <h2><a name="body.1_div.2"></a>2. Getting started
         </h2>
         
              
         <p><a name="d0e228"></a>The first question that is often asked when learning that OSIS
            uses XML (a markup language) is: "I'm not a computer person. Can
            I learn to use OSIS?" If you can type and use even the most
            basic word processor or computer text-editing program, the answer is
            clearly "Yes!" OSIS was designed to be offer the beginning
            user a simple way to do the basic "markup" required for a standard
            biblical text. "Markup" refers to markers placed within the text,
            that indicate where useful units (or "elements") such as verses,
            quotations, cross-references, and other things begin and end.
         </p>
         
         
         <p><a name="d0e231"></a>If you know HTML, you already know most of what you need to know
            to use OSIS; OSIS uses the same pointy-bracket syntax as HTML (or
            XHTML to be completely precise). It merely provides a different set
            of element and attribute names. A few names such as "p" and "div" are
            the same; others are new, such as "verse". The core set of elements
            for OSIS is actually smaller than the set for HTML 3.2. To be sure,
            there are some complex cases that we deal with later, but you can do
            useful work with no more information than is provided in this basic
            manual.
         </p>
         
         
         <p><a name="d0e234"></a>The second question that is most often asked is: &#8216;Do I need an
            XML editor to do OSIS?&#8217; This question often comes up after a
            friend of a friend has recommended some editor, and you then checked
            its price. XML editors vary from free to over $10,000.00 (US), and
            many are difficult to use (though XMetal&#8482; is a notable
            exception, and not very expensive).
         </p>
         
         
         <p><a name="d0e240"></a>
            The basic answer is no, you do not need any special software. You can
            use any text editor you like to create OSIS documents (or any other
            XML documents, for that matter). Many will even color the tags for
            you, because they know how to color HTML tags and the languages are
            similar enough. However, you should have a way to check your documents
            for errors -- if your editor doesn't know enough about XML to warn you
            if you misspell a tag, or forget to end some element that you started,
            you will want to check for errors periodically using an "XML
            validator". Many such program are available for various computers;
            some are available as Web services. (See Appendix ***, Validating Your
            OSIS Document for pointers and instructions on web based validation
            services.) Both Internet Explorer and Netscape can also validate an
            OSIS file once you have installed the OSIS rules file (called a
            "schema") and an appropriate stylesheet.
            
         </p>
         
         
         <p><a name="d0e243"></a>
            An OSIS-aware text editor will do this checking for you, either on
            demand or continuously. A friendlier OSIS-aware text editor will
            provide help by showing you just which elements are permitted at any
            given place (for example, you can't insert a Bible book within a
            footnote). The friendliest editors also give you the option to see
            and edit a fully-formatted view on demand, rather than staring
            directly at pointy-brackets. The choice between the many tools is a
            personal one, dictated by your working style, level of technical
            sophistication, goals, budget, and other factors.
            
         </p>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e246"></a>2.1. Some authoring tools
            </h3>
            
            
            
            <p><a name="d0e251"></a>
               The OSIS team is working even as this manual is being written to
               adapt free authoring tools that will hide most if not all of the
               markup from the casual user of OSIS. In the meantime, the best way to
               learn OSIS is to use a simple text editor, such as WordPad or Kedit
               on Windows, BBEdit or Alpha on MacOS, or vi or emacs on Linux. You
               can even use a word processor, though any formatting that you do in
               it won't matter (you would simply save the file as "text only".
               
            </p>
            
            
            <p><a name="d0e254"></a>The examples in this manual have been kept deliberately short and
               can be downloaded as a package from the OSIS website. After you have
               gained some basic skill using OSIS, you may want try out more
               sophisticated editors.
            </p>
            
            
            
            <p><a name="d0e257"></a>
               Editing is much easier with an editing program that is aware of XML
               rules in general, and OSIS in particular. For example, rather than
               seeing literal tags with pointy-brackets, you can have a choice of
               seeing that, or structural views of your document (say, as a tree or
               expandable outline), or fully-formatted views to facilitate print
               layout.
               
            </p>
            
            
            <p><a name="d0e260"></a>
               Many products are available that can help you edit XML documents. One
               style shows the literal XML source file, but colors tags, attributes,
               and other things to make them stand out. Most such programs also read
               an XML schema and ensure that you only insert elements and attributes
               are permitted by the OSIS schema (schemas, such as the OSIS one,
               declare what elements and attributes are permitted where in documents
               of a particular kind). One free and helpful tool of this kinds is
               jEdit, which runs on most platforms. It can be set up to know about
               many kinds of files, including XML files, and OSIS in particular.
               
            </p>
            
            
            
            <p><a name="d0e263"></a>
               With such an editor, you can see or print a basic a formatted view by
               using most any Web browser. Later in this manual are instructions for
               setting up an OSIS file with a style sheet (generally in CSS) so that
               typical browsers can deal with it.
               
            </p>
            
            
            <p><a name="d0e266"></a>
               There are also more word-processor-like XML editors, which primarily
               show a formatted view defined by some style sheet. These are mainly
               commercial. XML Spy is one such tool (see http://www.xmlspy.com/);
               XMetal (see
               http://www.corel.com/servlet/Satellite?pagename=Corel/Products/productInfo&amp;id=1042152754863)
               is another.
               
            </p>
            
            
            <p><a name="d0e269"></a>
               For high-end layout and typesetting from XML source files, usually a
               stylesheet language called XSL-FO is used. Two of the more popular
               commercial XSL-FO solutions are 3b2 (see http://www.3b2.com/), and
               Antenna House (see http://www.antennahouse.com/). Non-XML-based
               composition systems such as Quark&#8482; and TeX generally have ways
               to import XML, but using them for XML composition requires
               substantial expertise and effort.
               
            </p>
            
            
         </div>
         
         
      </div>
      
      
      <div class="teidiv">
         <h2><a name="body.1_div.3"></a>3. Your First OSIS Document
         </h2>
         
              
         <p><a name="d0e278"></a>Like HTML documents, an OSIS document starts with a header,
            and then goes on to the actual text content. The header identifies
            the file as being XML, and as using the OSIS schema. It also
            provides places to declare a bibliographical description of the work
            and of any other works cited; and a place to record a history of
            editing changes. Here is a short, but valid, OSIS document:
         </p>
         
         <pre class="eg">

&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;osis xmlns="http://www.bibletechnologies.net/2003/OSIS/namespace" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bibletechnologies.net/2003/OSIS/namespace osisCore.2.0.xsd"&gt;
	&lt;osisText osisIDWork="thisWork" osisRefWork="bible" xml:lang="en-US"&gt;
		&lt;header&gt;
			&lt;work osisWork="thisWork"&gt;
				&lt;title&gt;Contemporary English Version&lt;/title&gt;
				&lt;type type="OSIS"&gt;Bible&lt;/type&gt;
				&lt;identifier type="OSIS"&gt;Bible.en.CEV.1995&lt;/identifier&gt;
				&lt;rights type="x-copyright"&gt;Copyright 1995 American Bible Society&lt;/rights&gt;
				&lt;scope&gt;Esth.1.1-Esth.1.4&lt;/scope&gt;
				&lt;refSystem&gt;Bible&lt;/refSystem&gt;
			&lt;/work&gt;
			&lt;work osisWork="bible"&gt;
				&lt;type type="OSIS"&gt;Bible&lt;/type&gt;
				&lt;refSystem&gt;Bible&lt;/refSystem&gt;
			&lt;/work&gt;
		&lt;/header&gt;
	&lt;div type="section" scope="Esth.1.1-Esth.1.4"&gt;
				&lt;title&gt;Queen Vashti Disobeys King Xerxes&lt;/title&gt;
				&lt;p&gt;
&lt;verse sID="Esth.1.1-Esth.1.2" osisID="Esth.1.1 Esth.1.2" n="1-2"/&gt;King Xerxes of Persia lived in his capital city of Susa and ruled one hundred twenty-seven provinces from India to Ethiopia.&lt;verse eID="Esth.1.1-Esth.1.2"/&gt;
&lt;verse sID="Esth.1.3" osisID="Esth.1.3"/&gt;During the third year of his rule, Xerxes gave a big dinner for all his officials and officers. The governors and leaders of the provinces were also invited, and even the commanders of the Persian and Median armies came.&lt;verse eID="Esth.1.3"/&gt;
&lt;verse sID="Esth.1.4" osisID="Esth.1.4"/&gt;For one hundred eighty days he showed off his wealth and spent a lot of money to impress his guests with the greatness of his kingdom.&lt;verse eID="Esth.1.4"/&gt;
&lt;/p&gt;
&lt;/div&gt;
&lt;/osisText&gt;
&lt;/osis&gt;


</pre>
         
             </div>
      
          
      <div class="teidiv">
         <h2><a name="body.1_div.4"></a>4. XML and OSIS declarations
         </h2>
         
         
         <p><a name="d0e289"></a>
                The first several lines of any OSIS document will generally be identical:
            
         </p>
         
         
         <p><a name="d0e292"></a>
                The first line above identifies the document as being XML; this
            is required in exactly the form shown, and enables computers to
            identify how to process the rest of the document.
            
         </p>
         
         
         <p><a name="d0e295"></a>
            The second through third lines are a very long start-tag for the
            outermost OSIS element, which is called "osis." All elements in an
                 OSIS document must be declared within the OSIS namespace. There
                 are two ways to achieve this and other than remembering to pick
                 one of the two following methods, that is all you need remember
                 about it to start encoding texts using OSIS 2.0.
            
         </p>
         
             
         <p><a name="d0e298"></a><b>OSIS Namespace, Method 1</b>: Copy the
                 following lines just after &lt;?xml version="1.0"
                 encoding="UTF-8"/&gt;:
            
            <pre class="eg">

&lt;osis xmlns="http://www.bibletechnologies.net/2003/OSIS/namespace"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://www.bibletechnologies.net/2003/OSIS/namespace osisCore.2.0.xsd"&gt;

     </pre>
                </p>
         
         <p><a name="d0e306"></a><b>OSIS Namespace, Method 2</b>: Copy the
                 following lines just after &lt;?xml version="1.0"
                 encoding="UTF-8"/&gt;:
            <pre class="eg">

&lt;osis:osis xmlns:osis="http://www.bibletechnologies.net/2003/OSIS/namespace"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://www.bibletechnologies.net/2003/OSIS/namespace osisCore.2.0.xsd"&gt;

     </pre>
            Note with the second method, the last closing element must be:
                 &lt;/osis:osis&gt;. The first method is simpler but both are
                 legitimate.</p>
         
         
         <p><a name="d0e314"></a>
            At this point, the OSIS document has begun. This sample is a single
                 document rather than a collection of documents, so the next element
            opened is <b>osisText</b>:
            
         </p>
         
         <pre class="eg">

    &lt;osisText osisIDWork="CEV" osisRefWork="Bible" lang="en"&gt;

</pre>
         
         
         
         
         
         
         
         
         <p><a name="d0e333"></a>Every <b>osisText</b> needs to supply an <b>osisIDWork</b> attribute and value. The value will
                  generally be the short name of what is being encoded, in this
                  case the Contemporary English Version, or CEV. This sets things
                  up for some of the later elements nested within the <b>osisText</b> element. One such element is <b>work</b>. It requires an <b>osisWork</b> attribute. That attribute's value has
                  to be the same as the value found on the <b>osisIDWork</b> attribute of <b>osisText</b> (see line 7 of the sample). Other
                  elements use/require an <b>osisID</b> attribute
                  which refer back to the <b>osisIDWork</b>
                  attribute of <b>osisText</b> (see lines 19 and 21
                  of the sample).
         </p>
         
         
         <p><a name="d0e366"></a>
            Every <b>osisText</b> also needs to specify what reference or versification
            scheme any osisRefs within it refer to. This may or may not be the
            same work. Depending on how finely you distinguish things, there are
            several major versification traditions, and countless fine-grained
            variations. For the present, we identify and reserve names for these
            major traditional reference systems:
            
         </p>
         
         
         <p><a name="d0e372"></a>NRSVA -- 
            
                
         </p>
         
         
         <p><a name="d0e375"></a>
                NA27 -- Nestle-Aland, 27th Edition of the Greek New Testament.
            
         </p>
         
         
         <p><a name="d0e378"></a>KJV -- King James Version or Authorized Version (AV)
         </p>
         
         
         <p><a name="d0e381"></a>LXX -- Septuagint
         </p>
         
         
         <p><a name="d0e384"></a>
                MT -- Masoretic Text.Hebrew tradition varies in several respects, the best
            known being that it number the proscriptions above Psalms as verse 1,
            and the beginning of the psalm proper as verse 2.
            
         </p>
         
         
         <p><a name="d0e387"></a>
                SamPent -- the Samaritan Pentateuch used a quite different
            numbering system.
            
         </p>
         
         
         <p><a name="d0e390"></a>Synodal -- Russian
         </p>
         
         
         <p><a name="d0e393"></a> Vugl -- Vulgate
            
                
         </p>
         
         
         
         <p><a name="d0e396"></a>
                Loeb -- This system is used for most classical literature,
            though many major works have other systems as well.
            
         </p>
         
         
         <p><a name="d0e399"></a>
            OSIS is developing a schema for declaring versification systems
            formally, and for declaring some systems in terms of others. This
            will enable programs to map between systems. However, at this time we
            merely reserve the names above for some systems we know to be
            substantially different and important.
            
         </p>
         
         
      </div>
      
      
      <div class="teidiv">
         <h2><a name="body.1_div.5"></a>5. Canonical vs. non-canonical parts of a work
         </h2>
         
         
         <p><a name="d0e407"></a>
            The element <b>osisText</b> has one other important attribute that is not shown above.
            It is called "canonical", and always have a value of "true" or
            "false". When true, it asserts that the content is a part of the text
            being encoded. For example, the "text" of the Bible includes the content
            of books, chapters, and verses but does not include notes,
            section-headings added by editors or translators, etc.
            
         </p>
         
         
         <p><a name="d0e413"></a>
            The canonical attribute is available on all elements. Its value
            inherits in the same manner as xml:lang. Because of this inheritance,
            encoders will seldom need to make this attribute explicit. In <b>osisText</b> this attribute is set to a default
                 value of "true", while header, note, and
            reference that setting is overidden by setting the value of that
                 attribute to be "false."
            
         </p>
         
         
         <p><a name="d0e419"></a>
            In books other than the Bible, a similar distinction holds: the text
            proper of Herodotus' Histories must be contained in elements with
            canonical="true", while notes, header data, and the like must not.
            
         </p>
         
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e422"></a>5.1. Meaning of thecanonicalattribute
            </h3>
            
            
            <p><a name="d0e429"></a>
               The meaning of this attribute is limited. It must not be used to
               encode interpretive or theological judgements about canonicity. For
               example, encoders who include the apocryphal books of the Bible, or
               the alternate longer ending to the Gospel of Mark, must mark them as
               canonical (whether by default or explicitly). This is simply because
               they are part of the text being encoded. Users of a text are never
               justified in drawing conclusions about a translator's, editor's, or
               encoder's position on questions of inspiration or other theological
               questions based on how they set the <b>canonical</b>
               attribute, because the attribute does not mean that.
               
            </p>
            
            
            <p><a name="d0e435"></a>
               In most cases use of the <b>canonical</b> attribute is
               straightforward, and we expect that the default values will almost
               always produce the intended result. However, there will arise truly
               difficult cases: for example, one may be encoding an ancient text
               with annotations of its own. In that case those notes would be
               canonical, while any added by the current editor would not be. In
               such cases, the practice chosen and its rationale should be described
               in the work's documentation.
               
            </p>
            
            
         </div>
            
      </div>
      
      <div class="teidiv">
         <h2><a name="body.1_div.6"></a>6. The OSIS text header
         </h2>
         
         
         <p><a name="d0e447"></a>
            The first element within every <b>osisText</b> must be a
            <b>header</b>. The <b>header</b> declares
            various works (including the work being encoded and any that are
            being referenced), and provides a place to keep a revision history of
            the text.
            
         </p>
         
             
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e459"></a>6.1. The Revision Description
            </h3>
            
            
            <p><a name="d0e463"></a>
               To record changes or edits to the text, authors and editors are
               encouraged to insert a <b>change</b> element every time
               significant editing is done. Each <b>change</b> element
               should contain a <b>date</b> element which says when
               those edits were completed, in the form
               
            </p>
            
            <pre class="eg">
    yyyy-mm-ddThh:mm:ss
</pre>
            
            <p><a name="d0e478"></a>
               Note that all fields must have exactly the number of digits shown
               (4-digit year, 2-digit month, etc.). It is permissible to omit the
               time and the preceding "T", thus giving just a date. For example,
               December 25th of 1999 CE would be:
            </p>
            
            <pre class="eg">
    1999-12-25
</pre>
            
            <p><a name="d0e484"></a>A <b>date</b> element in the revision description is
               followed by any number of <b>p</b> (paragraph) elements,
               in which the changes made are summarized. The person responsible for
               making the changes should also be identified, using the <b>resp</b> attribute on the <b>change</b>
               element.
               
            </p>
            
            
            <p><a name="d0e499"></a>
               Recommended practice is that more recent <b>change</b>
               elements appear earlier in the document. That is, entries should
               occur in reverse chronological order. For example:
               
            </p>
            
            <pre class="eg">

    &lt;change&gt;&lt;date&gt;2003-09-11&lt;/date&gt;
    &lt;p&gt;sjd: Filling in the gaps. Adding some info for 2.0 as defined
at the Calvin College meetings.&lt;/p&gt;
    &lt;/change&gt;
    &lt;change&gt;&lt;date&gt;2003-07-01&lt;/date&gt;
    &lt;p&gt;sjd: Annotated alpha list of elements. Reworked reference and
work sections and added type, scope, and explanations of type and
subtype for work. Explained more elements and attributes.&lt;/p&gt;
    &lt;/change&gt;
    &lt;change&gt;&lt;date&gt;2003-06-17&lt;/date&gt;
    &lt;p&gt;sjd: Wrote conformance section. Added lists of elements and
attributes, USMARC list. Inserted placeholders for doc on all element
types. Got document back to XML WF. Wrote CSS stylesheet.&lt;/p&gt;
    &lt;/change&gt;

</pre>
            
                </div>
         
             
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e509"></a>6.2. Work Declarations
            </h3>
            
            
            <p><a name="d0e513"></a>
                   A <b>work</b> element is a declaration. It provides
               information comparable to that found on the title page of a printed
               work, using the fields defined by the Dublin Core Initiative (see
               http://dublincore.org/).
               
            </p>
            
                 
            <p><a name="d0e519"></a>The <b>work</b> element serves two purposes. The
                     <b>work</b> element in the <b>header</b> with an <b>osisWork</b>
                     attribute that matches the <b>osisIDRef</b> in the
                     <b>osisText</b> element identifies the work in which it occurs -- much
               like the title page in a printed work. For example:
            </p>
            
            <pre class="eg">

	&lt;osisText osisIDWork="CEV" osisRefWork="Bible" lang="en"&gt;
		&lt;header&gt;
			&lt;work osisWork="CEV"&gt;

</pre>
            
            <p><a name="d0e543"></a>Note that the match between <b>osisIDWork="CEV"</b>
                     in <b>osisText</b> and <b>osisWork="CEV"</b> in the <b>work</b>
                     element links this <b>osisText</b> to this
                     particular <b>work</b> element.
            </p>
            
                 
            <p><a name="d0e564"></a>Subsequent <b>work</b> elements identify other
               works -- much like a citation in a footnote or bibliography in a
               printed work. Each assigns a <i>local name</i> to
               each one, using the <b>osisWork</b> attribute. Works so
               declared can then be referred to from osisIDs or osisRefs throughout
               the text. For Bibles, this should generally be the accepted acronym
               or abbreviated form of the translation's name (some standard version
               abbreviations are listed in an appendix). No periods, hypens, spaces,
               or colons are allowed in short names.
               
            </p>
            
            
            <p><a name="d0e576"></a>Note: This mechanism of declaring a short name and using it later
               as a prefix, is very similar to the XML Namespace mechanism defined
               at http://www.w3.org/TR/xml-names11/.
            </p>
            
            
                
         </div>
         
             
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e580"></a>6.3. The Dublin Core
            </h3>
            
                 
            <p><a name="d0e584"></a>Each <b>work</b> element describes a single
               publication using several pieces of information, primarily title,
               creator, date, publisher, identifier and language. All of the standard
               "Dublin Core" fields may be used, plus a few OSIS-specific additions
               (further information on the Dublin Core system may be found at
               http://www.dublincore.org). All of the Dublin core fields may be
               repeated as necessary, but must be encoded in the order shown
               here. For example:
            </p>
            
            <pre class="eg">

&lt;work osisWork="EG"&gt;
    &lt;title&gt;Egyptian Grammar&lt;/title&gt;
    &lt;creator role="aut"&gt;Alan Gardiner&lt;/creator&gt;
    &lt;contributor role="dte"&gt;Francis Llewellyn Griffith&lt;/contributor&gt;
    &lt;date event="original" type="gregorian"&gt;1927&lt;/date&gt;
    &lt;date event="eversion" type="gregorian"&gt;2003&lt;/date&gt;
    &lt;type type="x-grammar"&gt;Grammar&lt;/type&gt;
    &lt;publisher&gt;Griffith Institute, Ashmolean Museum, Oxford&lt;/publisher&gt;
    &lt;language type="ISO-639"&gt;EN&lt;/language&gt;
    &lt;language type="Ethnologue"&gt;EG-ancient&lt;/language&gt;
    &lt;identifier type="ISBN"&gt;0900416351&lt;/identifier&gt;
    &lt;identifier type="LCCN"&gt;95230980&lt;/identifer&gt;
&lt;/work&gt;

</pre>
            
            <pre class="eg">

&lt;work osisWork="CPV"&gt;
    &lt;title&gt;Cotton Patch Version of Luke and Acts: Jesus' Doings and
the Happenings&lt;/title&gt;
    &lt;creator role="aut"&gt;Clarence Jordan&lt;/creator&gt;
    &lt;date event="original" type="gregorian"&gt;1969&lt;/date&gt;
    &lt;date event="eversion" type="gregorian"&gt;2003&lt;/date&gt;
    &lt;type type="x-bible"&gt;Bible&lt;/type&gt;
    &lt;publisher&gt;Association Press
       &lt;name type="place"&gt;New York, NY&lt;/name&gt;&lt;/publisher&gt;
    &lt;language type="ISO-639"&gt;EN&lt;/language&gt;
    &lt;identifier type="ISBN"&gt;0809617250&lt;/identifier&gt;
    &lt;identifier type="LCCN"&gt;69-18840&lt;/identifer&gt;
    &lt;scope osisRef="Luke" /&gt;
    &lt;scope osisRef="Acts" /&gt;
&lt;/work&gt;

</pre>
            
                <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e596"></a>6.3.1. title
               </h4>
               
               
               <p><a name="d0e601"></a>A <b>title</b> element <i>must</i> be
                  provided in the <b>work</b> element and contain the main
                  title of the work. Additional titles may also be specified, using the
                  <b>type</b> attribute to identify them as main, sub,
                  part, monographicSeries, or another kind of title. No OSIS-specific
                  types are established for this <b>type</b> attribute.
               </p>
                   
            </div>
            
            
                
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e620"></a>6.3.2. creator
               </h4> 
               <p><a name="d0e625"></a>The <b>creator</b> element is used to specify the person(s) or
                  organization(s) who are primarily responsible for the intellectual
                  content of a work. The role attribute must specify the particular role
                  the primary responsible party played. The most common values would be
                  aut (author), edt (editor), cmm (commentator), trl (translator). A
                         short list of such codes appears in Appendix D: Contributor
                         Roles, with the complete set being found in Appendix G: USMARC
                         Relator Codes.
                  
               </p>
               
            </div>
            
                
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e632"></a>6.3.3. contributor
               </h4>
               
               
               <p><a name="d0e637"></a>Many people may contribute to a work in roles other than the
                  primary role listed under creator. They should be listed using the <b>contributor</b> element. Their specific role should be
                  recorded in the <b>role</b> attribute of their <b>contributor</b> element. See Appendix G: USMARC Relator
                         Codes for the
                  complete list of role codes provided by the USMARC organization.
               </p>
               
            </div>
            
                
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e650"></a>6.3.4. date
               </h4>
               
                    
               <p><a name="d0e654"></a><b>Date</b> elements in the <b>work</b> element record significant dates in the
                  production or publication process. Use the <b>role</b>
                  attribute to identify the particular date contained in each of the
                  date elements. Those defined roles are:
               </p>
               
               
               <ul>
                  <li><a name="d0e667"></a>original: The original publication date of the first
                     edition
                  </li>
                  <li><a name="d0e672"></a>edition: The date of publication of the referenced or
                     source edition
                  </li>
                  <li><a name="d0e677"></a>imprint: The printing date of the referenced or source
                     edition
                  </li>
                  <li><a name="d0e682"></a>eversion: The revision date of the present electronic
                     edition
                  </li>
               </ul>
               
               
                   
               <p><a name="d0e688"></a>The <b>type</b> attribute is used, instead, to
                  identify the calendrical system in which the date is expressed, from
                  the list: Chinese, Gregorian, Islamic, ISO, Jewish, and Julian. At
                  this time, OSIS only defines a syntax for Gregorian dates:
                  yyyy:mm:dd. See the later section on "Date Formats".
               </p>
                   
            </div>
            
                
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e695"></a>6.3.5. publisher
               </h4>
               
                    
               
               
               
               <p><a name="d0e705"></a>Publisher elements in the work element use the <b>type</b> attribute to specify which particular publisher
                  is identified in that element. For example, the original and later
                  editions of a work may have different publishers, as may reprints or
                  digital editions.  The publisher types are the same as the date roles
                  listed above.
               </p>
               
                   
            </div>
            
               
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e712"></a>6.3.6. language
               </h4>
               
                 
               <p><a name="d0e716"></a>A <b>language</b> element must be provided for each
                  language used substantially in a work. The language may be specified
                  using an ISO 639 or ISO 639-2, or SIL Ethnologue codes. The type
                  attribute must be set to "ISO-639," "ISO-639-2,"
                  or "SIL," respectively. In the rare case that none of these
                  is sufficient, a prose description should be inserted in the element
                  and the <b>type</b> attribute set to "other".
               </p>
               
                   
            </div>
            
               
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e726"></a>6.3.7. type
               </h4>
               
               
               <p><a name="d0e730"></a>
                     The nature or genre of the content of the resource. This element
                  includes terms describing general categories, functions, genres, or
                  aggregation levels for content. Dublin Core's recommended best
                  practice is to select a value from a controlled vocabulary (for
                  example, the DCMI Type Vocabulary -- see
                  http://dublincore.org/documents/dcmi-type-vocabulary/). OSIS does not
                  provide such a controlled vocabulary at this time. If you encode this
                  element, the controlled vocabulary in use should be identified via
                  the <b>type</b> attribute (for example, <b>&lt;type type="DCMI"&gt;</b>). To describe the physical or
                  digital manifestation of the resource, use the <b>format</b> element instead.
                  
               </p>
               
                   
            </div>
            
            
            
               
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e743"></a>6.3.8. identifier
               </h4>
               
               
                    
               <p><a name="d0e747"></a>The <b>identifier</b> elements provide one or more
                  formal identifiers for the work. Common types of identifier are
                  International Standard Book Number, Library of Congress Control
                  Number, or Serial Item and Contribution Identifier. Recommended
                  values for the identifier type attribute are: "ISBN,"
                  "SICI" (a SICI is an ISSN with fields added to identify a
                  particular issue of the serial publication, and a particular article
                  or other contribution within that issue), "LCCN,", and
                  "PURL."
               </p>
               
               
               <p><a name="d0e753"></a>ISBN and LCCN numbers must be recorded without spaces or hyphens.
                  ISBNs must contain ten digits (that is, they must include the final
                  check digit).
               </p>
               
                    
               <p><a name="d0e756"></a>We strongly recommend the assignment of an ISBN to each
                  published work using OSIS. This number must, if available, be
                  specified in the <b>identifier</b> field for the work.
                  
               </p>
               
                   
            </div>
            
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e763"></a>6.3.9. coverage
               </h4>
               
               
               <p><a name="d0e767"></a>This element may be used to specify the spatial location (a place
                  name or geographic coordinates), temporal period (a period label,
                  date, or date range) or jurisdiction (such as a named administrative
                  entity) to which the work applies. For example, an edition of
                  Herodotus could be specified as Greek/Hellenic, Classical Period. Or
                  a study of medieval Bibles could declare coverage as "medieval".
               </p>
                  
            </div>
            
               
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e771"></a>6.3.10. description
               </h4>
               
               <p><a name="d0e775"></a>
                     An account of the content of the resource.
               </p>
               
               
               <p><a name="d0e778"></a>Examples of <b>description</b> include, but are not limited to: an
                  abstract, table of contents, reference to a graphical representation
                  of content or a free-text account of the content.
                  
               </p>
                  
            </div>
            
               
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e785"></a>6.3.11. format
               </h4>
               
               <p><a name="d0e789"></a>
                     The physical or digital manifestation of the resource.
               </p>
               
               
               <p><a name="d0e792"></a>Typically, <b>format</b> may include the media-type or
                  dimensions of the resource. Format may be used to identify the
                  software, hardware, or other equipment needed to display or operate
                  the resource. Examples of dimensions include size and
                  duration. Recommended best practice is to select a value from a
                  controlled vocabulary (for example, the list of Internet Media Types
                  [MIME] defining computer media formats).
                  
               </p>
                  
            </div>
            
               
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e799"></a>6.3.12. relation
               </h4>
               
               <p><a name="d0e803"></a>
                     A reference to a related resource.
               </p>
               
               
               <p><a name="d0e806"></a>Recommended best practice is to identify the referenced resource
                  by means of a string or number conforming to a formal identification
                  system.
                  
               </p>
                  
            </div>
            
               
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e810"></a>6.3.13. rights
               </h4>
               
               <p><a name="d0e814"></a>
                     	Information about rights held in and over the resource.
               </p>
               
               
               <p><a name="d0e817"></a>Typically, <b>rights</b> will contain a rights
                  management statement for the resource, or reference a service
                  providing such information.  Rights information often encompasses
                  Intellectual Property Rights (IPR), Copyright, and other property
                  rights. The <b>rights</b> element is informative
                  only. Legal rights and penalties for violation of those rights vary
                  from jurisdiction to jurisdiction. Reuse of any resource should be
                  done only after obtaining the necessary rights and permissions or
                  ascertaining that none is required.
                  
               </p>
                  
            </div>
            
               
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e827"></a>6.3.14. subject
               </h4>
               
               <p><a name="d0e831"></a>
                     A topic of the content of the resource.
               </p>
               
               
               <p><a name="d0e834"></a>Typically, <b>subject</b> will be expressed as keywords, key phrases or
                  classification codes that describe a topic of the resource.
                  Recommended best practice is to select a value from a controlled
                  vocabulary or formal classification scheme.
                  
               </p>
               
               <div class="teidiv">
                  <h5><a name="osisUserManual_06-div-d0e840"></a>6.3.14.1. subject classification systems
                  </h5>
                  
                  <p><a name="d0e844"></a>The <b>type</b> attribute on <b>subject</b>
                     	 allows the user to specify what classification system the
                     	 subject entered can be found.
                  </p>
                  <pre class="eg">


&lt;subject type="ATLA"&gt;Fathers of the Church&lt;/subject&gt;



	</pre>
                  
                  <p>Means that the subject "Fathers of the Church" is a subject found
                     	 in the listing of subjects maintained by the American
                     	 Theological Libraries Association (ATLA). To assist users, an
                     	 admittedly partial list of the more well known subject
                     	 classification systems have been prepared by the OSIS
                     	 project. Those systems with their abbreviations for use with
                     	 an OSIS encoded text are as follows:
                     
                     
                  </p>
                  <ul>
                     <li><a name="d0e860"></a>ATLA: American Theological Libraries Association
                     </li>
                     <li><a name="d0e865"></a>BILDI: Biblewissenschaftliche Literaturdokumentation Innsbruck
                     </li>
                     <li><a name="d0e870"></a>DBC: Dutch Basic Classification
                     </li>
                     <li><a name="d0e875"></a>DDC: Dewey Decimal Classification
                     </li>
                     <li><a name="d0e880"></a>EUT: Estonian Universal Thesaurus
                     </li>
                     <li><a name="d0e885"></a>FGT: Finnish General Thesaurus
                     </li>
                     <li><a name="d0e890"></a>LCSH: Library of Congress Subject Heading
                     </li>
                     <li><a name="d0e895"></a>MeSH: Medical Subject Headings
                     </li>
                     <li><a name="d0e900"></a>NLSH: National Library Subject Headings (National Library
                        	  of Poland)
                     </li>
                     <li><a name="d0e905"></a>RSWK: Regeln f&uuml;r den Schlagwortkatalog
                     </li>
                     <li><a name="d0e910"></a>SEARS: Sears List of Subject Headings
                     </li>
                     <li><a name="d0e915"></a>SOG: Soggettario
                     </li>
                     <li><a name="d0e920"></a>SWD_RSWK: Swiss National Library
                     </li>
                     <li><a name="d0e925"></a>UDC: Universal Decimal Classification
                     </li>
                     <li><a name="d0e930"></a>VAT: Vatican Library
                     </li>
                  </ul>
                  <p>
                     
                     For classification systems not listed, insert the classification
                      system with a leading "x-" in the <b>type</b> attribute
                     and notify the OSIS team if that system should be added in a future
                      revision of the schema.
                     	  
                  </p>
                  
                     
               </div>
               
                  
               <div class="teidiv">
                  <h5><a name="osisUserManual_06-div-d0e941"></a>6.3.14.2. source
                  </h5>
                  
                  <p><a name="d0e945"></a>
                        A reference to a resource from which the present resource is derived.
                  </p>
                  
                  
                  <p><a name="d0e948"></a>The present resource may be derived from the <b>source</b> resource in whole or in part. Recommended best
                     practice is to identify the referenced resource by means of a string
                     or number conforming to a formal identification system.
                     
                  </p>
                     
               </div>
               
                  
               <div class="teidiv">
                  <h5><a name="osisUserManual_06-div-d0e955"></a>6.3.14.3. type
                  </h5>
                  
                  <p><a name="d0e959"></a>
                        The nature or genre of the content of the resource.
                  </p>
                  
                  
                  <p><a name="d0e962"></a>Type includes terms describing general categories, functions,
                     genres, or aggregation levels for content. Recommended best practice
                     is to select a value from a controlled vocabulary (for example, the
                     DCMI Type Vocabulary [DCT1]). To describe the physical or digital
                     manifestation of the resource, use the <b>format</b> element.
                     
                  </p>
                  
               </div>
               
               
            </div>
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e970"></a>6.3.15. Non-Dublin Core Elements and Attributes in the Work Declaration
               </h4>
               
               
               <div class="teidiv">
                  <h5><a name="osisUserManual_06-div-d0e974"></a>6.3.15.1. scope
                  </h5>
                  
                  <p><a name="d0e978"></a>The <b>scope</b> element(s) must have an <b>osisRef</b> attribute, which defines what part of the
                     titled work occurs in this electronic edition. For example, an
                     edition may consist of only the New Testament and Psalms, or of only
                     a single book. Contiguous ranges may be specified using the hyphen
                     notation described later for osisRefs in general; discontiguous
                     ranges must be specified by including multiple <b>scope</b> element(s), as shown in the second example
                     above. These should be, but are not required to be, in canonical
                     order.
                     
                  </p>
                  
               </div>
               
               
            </div>
            
            
         </div>
         
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e993"></a>6.4. Identifying a Work given a work declaration element
            </h3>
            
                 
            <p><a name="d0e997"></a>The six elements already described are the primary means of
               identifying a referenced work.
            </p>
            
            
            <p><a name="d0e1000"></a>If a publication matches all of the above elements within work, it
               is presumed to be an acceptable resolution for any reference to that
               work as declared.
            </p>
            
            
            <p><a name="d0e1003"></a>If no perfect match can be found, applications may, indeed should,
               attempt to fall back to the closest available publication. OSIS does
               not define a required method of fallback, or define what "closest"
               must mean in all contexts. HOwever, one possible approach is to
               successively ignore particular elements in this order:
            </p>
            
            
            <ul>
               <li><a name="d0e1008"></a>Identifier: because identifiers are often
                  ambiguous. For example, hardcover and softcover editions of a book
                  typically have different ISBNs, and occasionally publishers re-use an
                  old ISBN for a completely different book.
               </li>
               <li><a name="d0e1013"></a>Date: because a different imprint or edition of
                  the same conceptual work is typically adequate. Precisely targeted
                  links, however, may not refer to the exact location desired.
                  Applications may wish to ignore all dates except for the original
                  publication date.
               </li>
               <li><a name="d0e1018"></a>Publisher: because several publishers may
                  publish a given work (particular older works), publishers may change
                  name, etc.
               </li>
               <li><a name="d0e1023"></a>Language: Accepting a publication that
                  does not match in language is a substantial concession. However, some
                  variations of language are greater than others. For example, some
                  modern Bible translations are available in separate American and
                  British English versions, and substituting one for the other is not
                  unreasonable. This is particularly true because translations
                  generally use translated titles as well, and so if the language is
                  not closely related, the title will probably not match either.
                  Applications may wish to encode some knowledge of language and
                  dialect similarities to implement more sophisticated
                  fallback.
               </li>
               <li><a name="d0e1028"></a>Creator: because some authors have
                  multiple forms of name: St. Augustine vs. Augustine of Hippo vs.
                  Augustine. The Bible Technology Group intends to develop an
                  authority list of normative name-forms for relevant authors, and once
                  such a list is available, using it will help to avoid such problems.
                  As with other elements, more sophisticated applications may wish to
                  attempt some kind of approximate matching in order to achieve better
                  fallback.
               </li>
               <li><a name="d0e1033"></a>Title: the final item to discard is
                  probably title. If a work's title differs, it is probably a different
                  work, or at least a translation into a non-close language. On the
                  other hand, some titles have been used by multiple authors, and so a
                  match on title alone should be considered suspect.
               </li>
            </ul>
            
                 
            <p><a name="d0e1039"></a>Arguments can easily be made for a variety of other fallback
               methods. For example, if the identifier element matches, the work is
               probably right, even though an identifier mismatch is not good
               evidence that the work is wrong.
            </p>
            
                
         </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e1043"></a>6.5. Date formats
            </h3>
            
            
            <p><a name="d0e1047"></a>
               All dates in the header and in attributes should be in this standard
               format, which is based on IETF RFC 3339. However, it uses period
               rather than colon as the field separator (for consistency with other
               OSISis types), and adds features to allow for dates BCE, for
               approximate dates, for date ranges, for yearless dates (as used in
               many daily devotionals), for weekly dates, and for named times of day
               (such as used in many prayer books). There are 3 standard date
               formats; the prefixes that identify them are reserved, and may not be
               redefined via the refSysId attribute of any work element:
            </p>
            
            
            
            <ul>
               <li><a name="d0e1052"></a>yearly:yyyy-mm-ddThh.mm.ss
                  
                  		
                  <p><a name="d0e1056"></a>Any number of fields may be left off from the
                     right end; for example, if the seconds are dropped (along with the
                     preceding colon), the time refers to the entire minute specified; if
                     the entire time section is left off (along with the preceding "T"),
                     the string refers to the entire day.
                  </p>
                  
                  
                  <p><a name="d0e1059"></a>The year must always have 4 digits. However, the year may be
                     entirely omitted to indicate dates that apply to any year, such as in
                     a book of 365 daily readings.
                  </p>
                  
                  
                  <p><a name="d0e1062"></a>To indicates years before the common era, add an underscore ("_")
                     before the first digit of the year (immediately following the colon).
                     A hyphen would be preferable, but it is already in use to indicate
                     ranges in osisRefs.
                  </p>
                  
                  
                  <p><a name="d0e1065"></a>The entire date/time string (possibly including a leading
                     underscore) may be preceded by "~", indicating that the time is
                     approximate. No means is provided to express just how approximate a
                     time may be.
                  </p>
                  
               </li>
               <li><a name="d0e1069"></a>weekly:n
                  
                  
                  <p><a name="d0e1073"></a>When readings or other materials are specified as being for
                     particular days of the week, this form must be used. The 'n' value
                     may range from 1 to 7; 1 indicates Monday, in accordance with ISO
                     8601:2000.
                  </p>
               </li>
            </ul>
            
            
            <p><a name="d0e1077"></a>As an alternative to quantitative times, a small set of named
               times is provided, which can be specified in place of the entire
               (post-"T") time section (the "T" itself remains). For example:
            </p>
            
            <pre class="eg">
     yearly:06-04T~(Vespers)
</pre>
            
            <p><a name="d0e1083"></a>would be the identifier for a prayer, reading, or other work to be
               used at Vespers on June 4 of any year. The named times (which are
               case-sensitive) include: Vigils, Matins, Lauds, Terce, Sext, None,
               Vespers, Compline; Sunrise, Sunset; Morning, Afternoon, Evening,
               Night; AM, PM;
               Fajr, Zuhr, _Asr, Maghhrib, _Isha, Lail, Dzuha, _Id.
            </p>
            
            
            <p><a name="d0e1086"></a>Some works will be primarily organized by dates and times: for
               example, lectionaries, daily devotionals, prayer books, historical
               time lines, etc. In such works, use the osisID attribute to identify
               the retrievable portions; the value should the the applicable time in
               one of the formats just shown.
            </p>
            
            
            <p><a name="d0e1089"></a>Typically, such works are organized in chgronological order of the
               times specified; however, OSIS does not impose that requirement.
            </p>
            
                
         </div>
            
      </div>
      
      <div class="teidiv">
         <h2><a name="body.1_div.7"></a>7. Title Pages
         </h2> 
         
         
         <p><a name="d0e1098"></a>In order to make the encoding of title pages as found in standard
            work easier, OSIS 2.0 introduced the <b>titlePage</b>
            element. This element contains the following elements from the header:
            <b>title</b>, <b>contributor</b>, <b>creator</b>, <b>subject</b>, <b>date</b>, <b>description</b>, <b>publisher</b>, <b>type</b>, <b>format</b>, <b>identifier</b>, <b>source</b>, <b>language</b>, <b>relation</b>, <b>coverage</b>, which are
            explained in the material on the <b>header</b>
            section. Three additional elements are allowed, which are <b>figure</b>, <b>milestone</b>, and, <b>p</b>. Due to the complexity of title pages, all of these
            elements may occur in any order inside the <b>titlePage</b> element.
         </p> 
         
         
         <p><a name="d0e1161"></a>The <b>titlePage</b> element can occur within the <b>osis</b>, <b>osisText</b>, and, <b>osisCorpus</b> elements.
         </p>
         
         
         <p><a name="d0e1176"></a>Users just starting with OSIS should use a minimum headers and
            simple <b>titlePage</b> element until they have gained
            some experience with text encoding and determining what is, or perhaps
            more importantly, what is not useful to have encoded in a work.
         </p>
             
      </div>
      
      
      
      
      
      
      
          
      <div class="teidiv">
         <h2><a name="body.1_div.8"></a>8. Basic Elements
         </h2>
         
         
         
         <p><a name="d0e1189"></a>
            While book, chapter, and verse numbers are a familiar and useful way
            of referring to locations in the Bible, they often conflict with the
            boundaries of parables, stories, genealogies, paragraphs, quotations,
            and other important units of understanding. Even to print a
            well-formatted Bible edition, and much more to support high-end
            search, annotation, and other capabilities, these meaningful units
            must also commonly be marked.
            
         </p>
         
         
         <p><a name="d0e1192"></a>
            It is possible to encode a Bible using only book, chapter, and verse
            markup. However, most encoders also want to also represent sections,
            paragraphs, quotations, and so on. Higher-level structures are tagged
            as <b>div</b>, for "division", with a <b>type</b> attribute to specify the particular significance.
            <b>div</b> elements can occur within other <b>div</b> elements to any number of levels. The first and
            outermost <b>div</b> should occur immediately after the
            end of the header. For example,
            
         </p>
         
         <pre class="eg">

&lt;div type="book" osisID="Gen"&gt;
    &lt;head&gt;Genesis&lt;/head&gt;
    &lt;chapter osisID="Gen.1"&gt;
  	  &lt;head&gt;1&lt;/head&gt;
  	  &lt;verse osisID="Gen.1.1"&gt;In the beginning,...&lt;/verse&gt;
  	  &lt;verse osisID="Gen.1.2"&gt;The earth was formless and void...&lt;/verse&gt;
  	  ...
    &lt;/chapter&gt;
  &lt;/div&gt;
  
  </pre>
         
         <p><a name="d0e1213"></a>
            The <b>div</b> element is used for many top-level
            components, and so makes heavy use of the <b>type</b>
            attribute. The pre-defined types include the most common major
            divisions found in present-day Bibles and related works:
            
         </p>
         
         &#8216;
         
         <p><a name="d0e1224"></a>
            acknowledgement, afterword, annotant, appendix, article, back, body, book, bookGroup,
            chapter, colophon, commentary, concordance, coverPage, dedication, devotional,
            entry, front, gazetteer, glossary, imprimatur, index, introduction,
            majorSection, map, outline, paragraph, preface, section, subSection, titlePage.
            
         </p>
         &#8217;
         
         
         <p><a name="d0e1228"></a>
            The main body of a Bible will typically consist of <b>div</b> elements of <b>type="bookGroup"</b>
            (such as each Testament, the Apocrypha, and perhaps smaller groups
            such as the Pentateuch, the Minor Prophets, etc), plus any front and
            back matter divisions (the selection of which varies greatly between
            editions).
         </p>
         
         
         <p><a name="d0e1237"></a>With each <b>bookGroup div</b>, there will typically
            be <b>book div</b>s corresponding to each included
            Canonical or deutero-canonical book. Some books are divided into
            majorSections (such as the sub-books in Psalms), sections (typically
            topical divisions with headings), subSections (occasional minor
            divisions within sections). A specific <b>chapter</b>
            element is provided and encouraged, though <b>div
               type="chapter"</b> is also permissible. 
         </p>
         
         
         <p><a name="d0e1252"></a>Below this point typical texts switch from successive levels of
            <b>div</b> elements, to more specific markup such as
            paragraphs, lists, quotations, inscriptions, and the like. Also at
            this level, the markup begins commonly to interact with verse markup.
            
         </p>
         
         
         <p><a name="d0e1258"></a>Use of the types defined for <b>div</b> is mandatory
            when a provided type is applicable. For example, a colophon must be
            marked up as <b>&lt;div type='colophon'&gt;</b>.
            If types not provided are needed, they may be added but must begin
            with "x-", to distinguish them from OSIS-standard values.
         </p>
         
         
         <p><a name="d0e1267"></a>
            Such markup forms the primary backbone of an OSIS document. Chapter
            and verse elements are important (particularly for retrieval), but
            considered to be an overlay onto the more linguistic or thematic
            structure. Therefore, so long as verses and chapter do not cross the
            boundaries of other elements, they may be expressed in the normal
            fashion (NASB):
            
         </p>
         
         <pre class="eg">

&lt;chapter osisID="Mark.10"&gt;
    &lt;head&gt;Mark Chapter 10&lt;/head&gt;
	 &lt;div type="section"&gt;&lt;head&gt;Divorce&lt;/head&gt;

&lt;verse osisID="Mark.10.1"&gt;Jesus then left that place and went into
the region of Judea and across the Jordan. Again crowds of people
came to him, and as was his custom, he taught them.
&lt;/verse&gt;
&lt;verse osisID="Mark.10.2"&gt;Some Pharisees came and tested him by
asking, "Is it lawful for a man to divorce his wife?"
&lt;/verse&gt;
&lt;verse osisID="Mark.10.3"&gt;"What did Moses command you?" he replied.
&lt;/verse&gt;
&lt;verse osisID="Mark.10.4"&gt;They said, "Moses permitted a man to write
a certificate of divorce and send her away."
&lt;/verse&gt;
&lt;verse osisID="Mark.10.5"&gt;"It was because your hearts were hard that
Moses wrote you this law," Jesus replied. &lt;/verse&gt;
&lt;verse osisID="Mark.10.6"&gt;"But at the beginning of creation God 'made
them male and female.' &lt;/verse&gt;
&lt;verse osisID="Mark.10.7"&gt;'For this reason a man will leave his
father and mother and be united to his wife,&lt;/verse&gt;
&lt;verse osisID="Mark.10.8"&gt;and the two will become one flesh.' So they
are no longer two, but one. &lt;/verse&gt;
&lt;verse osisID="Mark.10.9"&gt;Therefore what God has joined together, let
man not separate."&lt;/verse&gt;
&lt;verse osisID="Mark.10.10"&gt;When they were in the house again, the
disciples asked Jesus about this. &lt;/verse&gt;
&lt;verse osisID="Mark.10.11"&gt;He answered, "Anyone who divorces his wife
and marries another woman commits adultery against her. &lt;/verse&gt;
&lt;verse osisID="Mark.10.12"&gt;And if she divorces her husband and
marries another man, she commits adultery." &lt;/verse&gt;
&lt;/div&gt;
...
&lt;/chapter&gt;

</pre>
         
         </div>
      
      
      <div class="teidiv">
         <h2><a name="body.1_div.9"></a>9. Simple paragraphing, quotes, and notes
         </h2>
         
         
         <p><a name="d0e1278"></a>Paragraphs (element <b>p</b>), quotations (element <b>q</b>), and other grouping elements can be inserted around
            groups of verses, as shown below. Likewise, <b>note</b>
            elements can be inserted where needed. The paragraph need not give an
            <b>osisID</b> for the set of verse it contains, since
            they are typically provided on the <b>verse</b> elements
            themselves:
         </p>
         
         <pre class="eg">

...
&lt;p&gt;
&lt;verse osisID="Esth.4.10"&gt;Then Esther spoke to Hathach, and gave him
a command for Mordecai: &lt;/verse&gt;

&lt;verse osisID="Esth.4.11"&gt;&lt;q&gt;All the king's servants and the people
of the king's provinces know that any man or woman who goes into the
inner court to the king, who has not been called, he has but one law:
put all to death, except the one to whom the king holds out the
golden scepter, that he may live. Yet I myself have not been called
to go in to the king these thirty days.&lt;/q&gt; &lt;/verse&gt;

&lt;verse osisID="Esth.4.12"&gt;So they told Mordecai Esther's words.
&lt;/verse&gt; &lt;/p&gt;

&lt;p&gt;
&lt;verse osisID="Esth.4.13"&gt;And Mordecai told them to answer Esther:
"Do not think in your heart that you will escape in the king's palace
any more than all the other Jews. &lt;/verse&gt;
&lt;/p&gt;

&lt;p&gt;
&lt;verse osisID="Esth.4.14"&gt;For if you remain completely silent at this
time, relief and deliverance will arise for the Jews from another
place, but you and your father's house will perish. Yet who knows
whether you have come to the kingdom for such a time as this?"
&lt;/verse&gt;
&lt;/p&gt;

&lt;p&gt;
&lt;verse osisID="Esth.4.15"&gt;Then Esther told them to reply to Mordecai: &lt;/verse&gt;
&lt;q&gt;
&lt;verse osisID="Esth.4.16"&gt;"Go, gather all the Jews who are present in
Shushan, and fast for me; neither eat nor drink for three days, night
or day. My maids and I will fast likewise. And so I will go to the
king, which is against the law; and if I perish, I perish!
&lt;/verse&gt;&lt;/q&gt;
&lt;/p&gt;

&lt;p&gt;&lt;verse osisID="Esth.4.17"&gt;So Mordecai went his way and did
according to all that Esther commanded him.&lt;note
type="textual"&gt;Septuagint adds a prayer of Mordecai
here.&lt;/note&gt;&lt;/verse&gt; &lt;/p&gt;


</pre>
         
         <p><a name="d0e1299"></a>
            Notice in this example that all the paragraphs and quotations still
            enclose an exact number of verses; there are exceptions to this, that
            need special handling as explained later.
            
         </p>
         
         
         <p><a name="d0e1302"></a>
            When tagging quotations, do not also include quotation marks. They
            will be generated in the typesetting or display process. This is
            important for several reasons. FIrst, if some people use <b>q</b>, some use punctuation marks, and some use both,
            anyone processing OSIS texts will have to check every text and
            account for all the variations -- this is expensive and
            time-consuming: that is, it will make the Bibles cost more (to
            someone), and be delivered later. Another reason is that punctuation
            for quotes differs around the world; so any given quotation mark may
            be meaningless to other communities. In Spanish, for example, there
            are special rules about how to mark quotes that continue after an
            interruption -- such cases can be distinguished by adding a type
            attribute to the q element, with values such as initial, medial,
            and final.
            
         </p>
         
         
         <p><a name="d0e1308"></a>
            Many editions of the Bible have accompanying notes, often of several
            distinct types. A number of predefined types, and some additional
            internal structure, are discussed later. It is customary to include
            the notes directly within the text, at the point to which they apply.
            This can be done via the <b>note</b> element, which can
            be placed almost anywhere. In the future, it is likely that notes
            will more commonly reside outside of the text, instead residing in
            special notes-files that can be attached (via osisRef) to any Bible
            edition on request.
            
         </p>
         
         
         <p><a name="d0e1314"></a>
            Every <b>note</b> should have a <b>type</b>
            attribute to indicate its purpose; many Bible editions show different
            kinds of notes in different places. The pre-defined note types are
            listed below; they are not sharply-defined, wholly distinct
            categories. In addition, if none of these categories suffice,
            encoders may create their own so long as their names begin with "x-".
            
         </p>
         
         
         <ul>
            <li><a name="d0e1325"></a>allusion: The note explains an implicit reference the text
               makes to another text or concept.
            </li>
            <li><a name="d0e1330"></a>alternative: The note records an alternate possible reading of
               the text, whether due to ambiguity in translation or to manuscript
               variation.
            </li>
            <li><a name="d0e1335"></a>background: The note provides background information, such as
               cultural norms, explanations of geographic or other information
               original readers would have known, and so on.
            </li>
            <li><a name="d0e1340"></a>citation: The note cites a supporting text or further
               explanation of some kind.
            </li>
            <li><a name="d0e1345"></a>crossReference: The note provides a cross-reference to a related
               passage or other text.
            </li>
            <li><a name="d0e1350"></a>devotional: The note includes information of interest for
               devotional reading.
            </li>
            <li><a name="d0e1355"></a>exegesis: The note discusses a relevant point of exegesis or
               interpretation
            </li>
            <li><a name="d0e1360"></a>explanation: The note explains implicit, ambiguous, or
               otherwise non-obvious aspects of the passage.
            </li>
            <li><a name="d0e1365"></a>speaker [2.0]: This type is intended mainly for use in sermons
               and other performance texts, where the performer may wish to make notes to him or herself. For
               example, "tell joke here".
            </li>
            <li><a name="d0e1370"></a>study: The note provides helps for a deeper study of the
               passage.
            </li>
            <li><a name="d0e1375"></a>translation: The note discusses an issue of translation, such
               as a word whose meanining is unclear in the original, or a reasons
               for the translator's choice of phrasing. Bible translation projects
               will likely use this heavily, using the subtype attribute to mark the
               status of each note as resolved or unresolved, the person responsible
               for the note, and so on.
            </li>
            <li><a name="d0e1380"></a>variant: The note records a textual variation in manuscript
               tradition, relevant at its location.
            </li>
         </ul>
         
         
         <p><a name="d0e1386"></a>Sometimes a <b>verse</b> or <b>chapter</b>
            starts or end in the middle of some other unit, such as a poetic line
            group, paragraph, quotation, or speech. In such cases an alternate
            form of the <b>verse</b> or <b>chapter</b>
            tags must be used. This usage is explained in the next section.
         </p>
         
         
      </div>
      
      
      
      <div class="teidiv">
         <h2><a name="body.1_div.10"></a>10. Elements that cross other elements
         </h2>
         
         
         <p><a name="d0e1406"></a>The normal form of an element is a start tag and an end tag: <b>&lt;verse&gt;...&lt;/verse&gt;</b>. For handling markup
            that crosses boundaries, however, a special form must be used. It
            consists of two totally empty instances of the same element type: one
            to mark the starting point, and one to mark the ending point. The two
            empty elements identify themselves as to which is the start and which is
            the end, and co-identify themselves by the <b>sID</b>
                 attribute (the start of the traditional element) and the <b>eID</b> attribute (the end of the traditional
                element), the values of which must match. 
         </p>
         
         
         <p>Elements that are "milestoneable" in the OSIS schema are:
            
                 
         </p>
         <ul>
            <li><a name="d0e1422"></a><b>abbr</b></li>
            <li><a name="d0e1426"></a><b>chapter</b></li>
            <li><a name="d0e1430"></a><b>closer</b></li>
            <li><a name="d0e1434"></a><b>div</b></li>
            <li><a name="d0e1438"></a><b>foreign</b></li>
            <li><a name="d0e1442"></a><b>l</b></li>
            <li><a name="d0e1446"></a><b>lg</b></li>
            <li><a name="d0e1450"></a><b>q</b></li>
            <li><a name="d0e1454"></a><b>salute</b></li>
            <li><a name="d0e1458"></a><b>seg</b></li>
            <li><a name="d0e1462"></a><b>signed</b></li>
            <li><a name="d0e1466"></a><b>speech</b></li>
            <li><a name="d0e1470"></a><b>verse</b></li>
         </ul>
         <p>
                
         </p>
         
         
         <p><a name="d0e1476"></a>This is particularly useful where modern translations break up
                 verses or other traditional divisions in a Bible text. For
                 example, a paragraph based encoding of part of the Book of Esther
                 would appears as follows:
         </p>
         
         <pre class="eg">

&lt;p&gt;
	&lt;verse sID="Esth.2.7" osisID="Esth.2.7"/&gt;Mordecai had a very beautiful cousin named Esther, whose Hebrew name was Hadassah. He had raised her as his own daughter, after her father and mother died.&lt;verse eID="Esth.2.7"/&gt;
	&lt;verse sID="Esth.2.8" osisID="Esth.2.8"/&gt;When the king ordered the search for beautiful women, many were taken to the king's palace in Susa, and Esther was one of them.&lt;/p&gt;
&lt;p&gt;Hegai was put in charge of all the women,&lt;verse eID="Esth.2.8"/&gt;
	&lt;verse sID="Esth.2.9" osisID="Esth.2.9"/&gt;and from the first day, Esther was his favorite. He began her beauty treatments at once. He also gave her plenty of food and seven special maids from the king's palace, and they had the best rooms.&lt;verse eID="Esth.2.9"/&gt;
&lt;/p&gt;

    </pre>
         
         <p>There are two things to note about the Esther example:
            
            
         </p>
         <ul>
            <li><a name="d0e1486"></a>Esther 2:8 is divided by a paragraph (the <b>p</b> element and so must be marked using the <b>verse</b> element as a milestones with the <b>sID</b> and <b>eID</b> attributes
               	to link those two milestones together.
            </li>
            <li><a name="d0e1501"></a>Where overlapping elements are necessary, the milestoneable
                      element technique must be used for the entire text. That is, it
                      is an error to mark some verses in Esther with traditional <b>verse</b> elements, i.e., as containers and others
                      with the milestoneable verses. The reason is quite simple,
                      inconsistent markup is more difficult to process and makes the
                      encoded text less useful for everyone.
            </li>
         </ul>
         <p>
                
         </p>
         
         
         <p><a name="d0e1509"></a>
            This is equivalent to the TEI "milestone" method for marking such
            phenomena. It has the advantage that milestones representing a given
            type of element have the same name as the element, and automatically
            have the same attributes. Although XML itself will not detect a
            validation error if attributes other than <b>eID</b> are
            specified on the ending <b>milestone</b>, <b>eID</b> is specified on the starting <b>milestone</b>, or the start and end milestones are in the
            wrong order, each of these conditions is an OSIS error.
            
         </p>
         
         
         <p><a name="d0e1524"></a>
            For OSIS purposes, there is no semantic difference between marking up
            a chapter or verse as a container using a start and end tag, versus
            marking it up as a "milestone pair" consisting of two empty tags.
            
         </p>
         
         
         
         
         <p><a name="d0e1527"></a>Note: Typesetting and layout systems vary in their ability to
            accommodate non-hierarchical markup such as this. Fortunately, in
            most Bible editions the only formatting consequence of a <b>verse</b> element is insertion of the verse number, and
            perhaps insertion of a line-break; these are within the capabilities
            of most layout and style systems even though the verse is not a
            container in XML terms.
         </p>
         
         
      </div>
      
      
      
      
      <div class="teidiv">
         <h2><a name="body.1_div.11"></a>11. Special Text Types
         </h2>
         
         
         <p><a name="d0e1540"></a>The bulk of the remaining OSIS elements fall into a few simple
            classes: First, markup for special text types, such as epistles and
            drama. Second, generic structures such as lists, tables and
            glossaries (typically found in appendixes of printed Bibles). And
            finally, small-scale elements that mark, quotations, notes, names,
            index entries, and the like.
         </p>
         
         
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e1543"></a>11.1. Markup for epistles and similar materials
            </h3>
            
            
            <p><a name="d0e1547"></a>
               Letters, epistles, and similar texts are marked up in basically the
               same way as any other text. However, three special elements are
               available for marking portions unique to this genre:
               
            </p>
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e1550"></a>11.1.1. salute
               </h4>
               
               <p><a name="d0e1554"></a>The <b>salute</b> element encloses the salutation or
                  greeting, typically at the very beginning of a letter. It should
                  include the whole salutation, including (if present) the "to",
                  "from", and any following greeting or blessing. If the boundaries of
                  a salutation are the same as the boundaries of a paragraph, section,
                  or other unit, that unit should be placed outside, with the salute
                  element directly within. For example (LBP):
                  
               </p>
               
               <pre class="eg">

&lt;div type="book" osisID="1Tim"&gt;
    &lt;head&gt;The First Epistle to Timothy&lt;/head&gt;
    &lt;chapter osisID="1Tim.1"&gt;
       &lt;salute&gt;
          &lt;verse osisID="1Tim.1.1"&gt;FROM: PAUL, a missionary of Jesus Christ,
          sent out by the direct command of God our Savior and by Jesus Christ
          our Lord -- our only hope.&lt;/verse&gt;
          &lt;verse osisID="1Tim.1.2"&gt;To: Timothy. Timothy, you are like a son
          to mein the things of the Lord. May God our Father and Jesus Christ
          our Lord show you his kindness and mercy and give you great peace
          of hear and mind.&lt;/verse&gt;
       &lt;/salute&gt;
       &lt;verse osisID="1Tim.1.3"&gt;...&lt;/verse&gt;
	&lt;/chapter&gt;
    ...
&lt;/div&gt;

</pre>
               
               </div>
            
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e1564"></a>11.1.2. signed
               </h4>
               
               <p><a name="d0e1568"></a>The <b>signed</b> element surrounds the name of the
                  author and/or amanuensis of a letter and its immediately surrounding
                  phrase of opening or closing (if any). In Biblical epistles, it is
                  common for the author to be named only at the beginning; this should
                  still be marked up with the <b>signed</b> element.
               </p>
               
               
               <p><a name="d0e1577"></a><b>signed</b> may appear with or without an
                  accompanying <b>closer</b> or <b>salute</b>
                  element, and the name may or may not also be tagged as a <b>name</b> (if it is, the <b>name</b> should be
                  the inner element even if it includes all the text content of the <b>signed</b> element. In New Testament epistles, there is  not
                  generally an obvious, final signature. However, this element may be
                  used somewhat more broadly of a phrase or portion judged as intended
                  to identify the writer. As shown below, the signature of an
                  amanuensis may also be marked up in this way. For example (RSV):
                  
               </p>
               
               
               <ul>
                  <li><a name="d0e1599"></a>	   &lt;verse osisID="Rom.16.22"&gt;&lt;signed&gt;I Tertius
                     salute you which wrote this epistle in the Lorde.&lt;signed&lt;/verse&gt;
                     	
                     <p><a name="d0e1603"></a>		[English, Tyndale, 1525/1530]
                     </p>
                  </li>
                  <li><a name="d0e1606"></a>	   &lt;verse
                     osisID="1Cor.16.21"&gt;&lt;signed&gt;I, Paul, write this greeting with
                     my own hand.&lt;/signed&gt;&lt;/verse&gt;
                     	
                     <p><a name="d0e1610"></a>	[English, RSV]
                     </p>
                  </li>
                  <li><a name="d0e1613"></a>		&lt;verse
                     osisID="2Cor.1.1"&gt;&lt;signed&gt;Paul, an apostle of Jesus Christ by
                     the will of God, and Timothy [our] brother, to the church of God
                     which is at Corinth, with all the saints who are in all
                     Achaia:&lt;/signed&gt;&lt;/verse&gt;
                     	
                     <p><a name="d0e1617"></a>	[English, Webster]
                     </p>
                  </li>
                  <li><a name="d0e1620"></a>		   &lt;verse
                     osisID="Gal.6.11"&gt;&lt;signed&gt;See with what large letters I am
                     writing to you with my own hand.&lt;/signed&gt;&lt;/verse&gt;
                     	
                     <p><a name="d0e1624"></a>	[English, RSV]
                     </p>
                  </li>
                  <li><a name="d0e1627"></a>		&lt;verse
                     osisID="Eph.1.1"&gt;&lt;signed&gt;Paul, an apostle of Christ Jesus
                     through the will of God, to the saints that are at Ephesus, and the
                     faithful in Christ Jesus:&lt;/signed&gt;&lt;/verse&gt;
                     	
                     <p><a name="d0e1631"></a>	[English, American Standard Version, 1901]
                     </p>
                  </li>
                  <li><a name="d0e1634"></a>		&lt;verse
                     osisID="Phil.1.1"&gt;&lt;signed&gt;Pablo y Timoteo, siervos de Jes?l
                     Cristo, a todos los santos en el Cristo Jes?e est&#7072;en Filipos, y
                     a los obispos y di&#6383;nos: &lt;/signed&gt;&lt;/verse&gt;
                     	
                     <p><a name="d0e1638"></a>	[Spanish, Sagradas Escrituras Version Antigua, 1569]
                     </p>
                  </li>
                  <li><a name="d0e1641"></a>	&lt;verse osisID="Col.4.18"&gt;&lt;signed&gt;A
                     k?nt?a saj&#7456;kezemmel, a P&#6953;val, [van ?a]. Eml&#39653;zzetek meg
                     az &#39840;bilincseimr?A kegyelem veletek. men.
                     &lt;/signed&gt;&lt;/verse&gt;
                     	
                     <p><a name="d0e1645"></a>	[Hungarian Karoli]
                     </p>
                  </li>
                  <li><a name="d0e1648"></a>&lt;verse osisID=""&gt;&lt;signed&gt;Paul, and
                     Silvanus, and Timothy, to the church of the Thessalonians which is in
                     God the Father and in the Lord Jesus Christ: Grace to you, and peace.
                     &lt;/signed&gt;&lt;/verse&gt;
                     	
                     <p><a name="d0e1652"></a>[English, RKJNT]
                     </p>
                  </li>
                  <li><a name="d0e1655"></a>&lt;verse osisID="2Thes.3.17"&gt;&lt;signed&gt;Der
                     Gru&#2016;mit meiner, des Paulus, Hand; dies ist das Zeichen in jedem
                     Briefe, so schreibe ich.  &lt;/signed&gt;&lt;/verse&gt;
                     	
                     <p><a name="d0e1659"></a>[German, Schlacter Bible, 1951]
                     </p>
                  </li>
                  <li><a name="d0e1662"></a>&lt;verse osisID="1TIm.1.1"&gt;&lt;signed&gt;Paul,
                     an apostle of Jesus Christ, according to the commandment of God our
                     Savior, and of Christ Jesus our
                     hope:&lt;/signed&gt;&lt;/verse&gt;
                     	
                     <p><a name="d0e1666"></a>[English, Douay-Rheims Bible, Challoner Revision]
                     </p>
                  </li>
                  <li><a name="d0e1669"></a>&lt;verse
                     osisID="2Tim.1.1"&gt;&lt;signed&gt;Paulus, ved Guds vilje Kristi Jesu
                     apostel til &#22571;unngj?? om livet i Kristus
                     Jesus&lt;/signed&gt;&lt;/verse&gt;
                     	
                     <p><a name="d0e1673"></a>[Norsk, Bibelen]
                     </p>
                  </li>
                  <li><a name="d0e1676"></a>&lt;signed&gt;&lt;verse osisID="TIt.1.1"&gt;Paolo,
                     servitore di Dio e apostolo di Ges?sto per la fede degli eletti
                     di Dio e la conoscenza della verit&#2083;he &#34867;econdo piet&#2854;lt;/verse&gt;
                     &lt;verse osisID="TIt.1.2"&gt;nella speranza della vita eterna la quale
                     Iddio, che non pu?ntire, promise avanti i secoli,&lt;/verse&gt;
                     &lt;verse osisID="TIt.1.3"&gt;manifestando poi nei suoi propri tempi la
                     sua parola mediante la predicazione che &#34867;tata a me affidata per
                     mandato di Dio, nostro Salvatore,&lt;/verse&gt;&lt;/signed&gt;
                     	
                     <p><a name="d0e1680"></a>[Italian, Riveduta Bibbie, 1927]
                     </p>
                  </li>
                  <li><a name="d0e1683"></a>&lt;verse osisID="Phm.1.1"&gt;&lt;signed&gt;Mimi
                     Paulo, mfungwa kwa ajili ya Kristo Yesu, na ndugu
                     Timotheo,&lt;/signed&gt; ninakuandikia wewe Filemoni mpendwa,
                     mfanyakazi mwenzetu&lt;/verse&gt;
                     &lt;verse osisID="Phm.1.2"&gt;na kanisa linalokutana nyumbani kwako, na
                     wewe dada Afia, na askari mwenzetu Arkupo.&lt;/verse&gt;
                     	
                     <p><a name="d0e1687"></a>[Swahili NT]
                     </p>
                  </li>
                  <li><a name="d0e1690"></a>&lt;verse
                     osisID="James.1.1"&gt;&lt;signed&gt;Jacques, serviteur de Dieu et du
                     Seigneur J&#40181;s-Christ, &lt;/signed&gt;aux douze tribus qui sont dans
                     la dispersion, salut!&lt;/verse&gt;
                     	
                     <p><a name="d0e1694"></a>[French, Louis Segond, 1910]
                     </p>
                  </li>
               </ul>
               
               
            </div>
            
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e1699"></a>11.1.3. closer
               </h4>
               
               <p><a name="d0e1703"></a>The <b>closer</b> element surrounds the closing portion of a letter,
                  typically consisting of final greetings or blessing, and a signature
                  (see <b>signed</b>). It is a matter of judgement just where a <b>closer</b> begins and ends. For example:
                  
               </p>
               
               
               <ul>
                  <li><a name="d0e1717"></a>   &lt;verse osisID="1John.5.21"&gt;&lt;closer&gt;Dear
                     children, keep away from
                     		anything that might take God's place in your hearts. Amen.
                     	Sincerely, &lt;signed&gt;John&lt;/signed&gt;&lt;/closer&gt;&lt;/verse&gt;
                     	
                     <p><a name="d0e1721"></a>[LBP]
                     </p>
                  </li>
               </ul>
               
               
               
               <div class="teidiv">
                  <h5><a name="osisUserManual_06-div-d0e1725"></a>11.1.3.1. benediction
                  </h5>
                  
                  
                  <p><a name="d0e1729"></a>OSIS presently provides no special markup for benedictions and
                     blessings. Recommended practice at this time if an encoder wishes to
                     identify them in a text, is to use <b>seg
                        type="benediction"</b>. For example:
                  </p>
                  
                  
                  <ul>
                     <li><a name="d0e1737"></a>   &lt;verse osisID="2Cor.13.14"&gt;&lt;seg
                        type="benediction"&gt;The grace of the Lord Jesus Christ, and the love
                        of God, and the communion of the Holy Spirit, [be] with you all.
                        Amen.&lt;/seg&gt;&lt;/verse&gt;
                        
                        		
                        <p><a name="d0e1741"></a>[Webster]
                        </p>
                     </li>
                  </ul>
                  
                  
               </div>
               
               
            </div>
                
         </div>
         
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e1748"></a>11.2. Dramatic texts
            </h3>
            
            
            <p><a name="d0e1752"></a>
               OSIS provides two main features for marking up dramatic texts: A way
               to declare the list of characters, or castList; and a way to identify
               speeches and speakers in the body of a dramatic text.
               
            </p>
            
            
            <p><a name="d0e1755"></a>
               A <b>castList</b> element contains a structured list of
               the roles, or cast, of a dramatic work. It is drawn directly from the
               TEI structure for the same thing. For example, in the Song of Songs,
               some translations may present the list of characters at the start of
               the book: lover, beloved, and friends. The same might be done for
               Job. However, these elements will be most commonly used for
               extra-Biblical materials, such as a play based on the Bible, or
               dramas in classical or other literature.
               
            </p>
            
            
            <p><a name="d0e1761"></a>
               A simple example of a castList is shown below, perhaps for a dramatic
               re-enactment of Job:
               
            </p>
            
            <pre class="eg">

&lt;castList&gt;
    &lt;castGroup&gt;
       &lt;head&gt;Cast of characters&lt;/head&gt;
       &lt;castItem&gt;
          &lt;actor&gt;Patrick Durusau&lt;/actor&gt;
          &lt;role&gt;Job&lt;/role&gt;
          &lt;roleDesc&gt;A man of God who suffers greatly&lt;/roleDesc&gt;
       &lt;/castItem&gt;

       &lt;castItem&gt;
          &lt;actor&gt;(a whirlwind)&lt;/actor&gt;
          &lt;role&gt;God&lt;/role&gt;
          &lt;roleDesc&gt;The Almighty, who permits Job's suffering, and
          responds to his questions about it.&lt;/roleDesc&gt;
       &lt;/castItem&gt;

       &lt;castItem&gt;
          &lt;actor&gt;(a disembodied voice)&lt;/actor&gt;
          &lt;role&gt;Satan&lt;/role&gt;
          &lt;roleDesc&gt;The instigator of Job's suffering&lt;/roleDesc&gt;
       &lt;/castItem&gt;

       &lt;castItem&gt;
          &lt;actor&gt;Todd Tillinghast&lt;/actor&gt;
          &lt;role&gt;Eliphaz&lt;/role&gt;
          &lt;roleDesc&gt;The first of Job's friends to speak&lt;/roleDesc&gt;
       &lt;/castItem&gt;

       &lt;castItem&gt;
          &lt;actor&gt;Chris Little&lt;/actor&gt;
          &lt;role&gt;Bildad&lt;/role&gt;
          &lt;roleDesc&gt;The second of Job's friends to speak&lt;/roleDesc&gt;
       &lt;/castItem&gt;

       &lt;castItem&gt;
          &lt;actor&gt;Steve DeRose&lt;/actor&gt;
          &lt;role&gt;Zophar&lt;/role&gt;
          &lt;roleDesc&gt;The third of Job's friends to speak&lt;/roleDesc&gt;
       &lt;/castItem&gt;

       &lt;castItem&gt;
          &lt;actor&gt;Troy Griffiths&lt;/actor&gt;
          &lt;role&gt;Elihu&lt;/role&gt;
          &lt;roleDesc&gt;The youngest and last of Job's friends to speak,
          who was slightly less clueless than the rest.&lt;/roleDesc&gt;
       &lt;/castItem&gt;
    &lt;/castGroup&gt;
&lt;/castList&gt;

</pre>
            
            <p><a name="d0e1767"></a>
               The <b>castList</b> element contains the entire casting
               List, and consists of one or more <b>castGroup</b>
               elements. Multiple castGroups, each with its own head, would be used
               if there were multiple sub-groups of the cast to be listed
               separatelyl; more typically there will be only one <b>castGroup</b> within a <b>castList</b>.
               
            </p>
            
            
            <p><a name="d0e1782"></a>
               At this time, <b>castList</b> can only occur in a <b>work</b> declaration, after the Dublin Core elements.
               Thus, if a Bible encoder wishes to include the casts of Song of Songs
               and of Job, they would each need to be marked as a separate <b>castGroup</b> within that one <b>castList</b>.
               
            </p>
            
            
            <p><a name="d0e1797"></a>
               The <b>castItem</b> element contains the full information
               for a single character. This must include a name for the <b>role</b> being played, and should include a <b>roleDesc</b>, that is, a description of that role. It may
               also include the name of an <b>actor</b>, if the text
               being encoded represents a particular enactment rather than, say, a
               libretto or script.
               
            </p>
            
            
            <p><a name="d0e1812"></a>
               In general there is no need to also encode an actor name or role name
               with an explicit <b>name</b> element, unless the encoder
               wishes to provide a normalized form for later reference; in that
               case, the <b>name</b> element would be placed just <i>within</i> the <b>actor</b> or <b>role</b> element, not surrounding it.
               
            </p>
            
            
            <p><a name="d0e1830"></a>
               It is strongly recommended that each <b>castGroup</b> and
               <b>castItem</b> have an <b>ID</b> attribute.
               Since IDs must be unique across all element types in a document,
               encoders may wish to prefix certain kinds of IDs to separate them and
               avoid conflicts. For example, an appropriate ID for a <b>castItem</b> representing the Friends in Song of Songs
               would be "cast.friends", or perhaps "cast.song.friends".
               
            </p>
            
         </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e1846"></a>11.3. speaker
            </h3>
            
            <p><a name="d0e1850"></a>The speaker element is used to identify the person or role that is
               uttering the content of an associated speech.
               
            </p>
            
            <pre class="eg">


&lt;div osisID="NRSV.Song.2"&gt;
&lt;speech&gt;
	&lt;speaker&gt;woman&lt;/speaker&gt;
&lt;verse osisID="NRSV.Song.2.1"&gt;I am a rose of Sharon, a lilly of the valleys.&lt;/verse&gt;
&lt;/speech&gt;
&lt;/div&gt;


	</pre>
            
            <p><a name="d0e1856"></a>Which is the equivalent to:
            </p>
            
            <pre class="eg">


&lt;div osisID="NRSV.Song.2"&gt;
&lt;speech who="woman"&gt;
&lt;verse osisID="NRSV.Song.2.1"&gt;I am a rose of Sharon, a lilly of the valleys.&lt;/verse&gt;
&lt;/speech&gt;
&lt;/div&gt;



	</pre>
            <p><a name="d0e1862"></a>Either method is correct but careful encoders will choose one or
               	 the other and be consistent in using one method or the
               	 other. Other than document invalidity, nothing makes use of
               	 an encoded document more difficult than correct, but
               	 inconsistent encoding.
            </p>
            
            
         </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e1866"></a>11.4. speech
            </h3>
            
            <p><a name="d0e1870"></a>The speech element is used to indicate quoted direct speech. In
               that sense it represents a kind of quotation. However, the <b>q</b> element is to be used for quotations in general,
               where the <b>speech</b> element is limited to accounts of
               an individualmaking an actual speech in some kind of performance
               context. In general, both elements should not be applied to the same
               text portion. Just as with the <b>q</b> element, using
               the <b>speech</b> element makes quotation marks
               unnecessary, and they must not be used. For example:
               
            </p>
            
            <pre class="eg">


&lt;chapter osisID="Acts.7"&gt;
&lt;head&gt;Stephen's Speech to the Sanhedrin&lt;/head&gt;

&lt;p&gt;
&lt;verse osisID="Acts.7.1"&gt;Then the high priest asked him, &lt;speech&gt;Are
these charges true?&lt;/speech&gt;
&lt;/verse&gt;
&lt;/p&gt;


&lt;p&gt;
&lt;verse osisID="Acts.7.2" sID='a72'/&gt;To this he replied:
&lt;speech&gt;Brothers and fathers, listen to me! The God of glory appeared
to our father Abraham while he was still in Mesopotamia, before he
lived in Haran. &lt;verse eID='a72'&gt;

&lt;verse osisID="Acts.7.3"&gt;'Leave your country and your people,' God
said, 'and go to the land I will show you.'&lt;/verse&gt;
&lt;/p&gt;

&lt;p&gt;
&lt;verse osisID="Acts.7.4"&gt;"So he left the land of the Chaldeans and
settled in Haran. After the death of his father, God sent him to this
land where you are now living. &lt;/verse&gt;

&lt;verse osisID="Acts.7.5"&gt;He gave him no inheritance here, not even a
foot of ground. But God promised him that he and his descendants
after him would possess the land, even though at that time Abraham
had no child. &lt;/verse&gt;

&lt;verse osisID="Acts.7.6"&gt;God spoke to him in this way: 'Your
descendants will be strangers in a country not their own, and they
will be enslaved and mistreated four hundred years. &lt;/verse&gt;

&lt;verse osisID="Acts.7.7"&gt;But I will punish the nation they serve as
slaves,' God said, 'and afterward they will come out of that country
and worship me in this place.'&lt;/verse&gt;

&lt;verse osisID="Acts.7.8"&gt;Then he gave Abraham the covenant of
circumcision. And Abraham became the father of Isaac and circumcised
him eight days after his birth. Later Isaac became the father of
Jacob, and Jacob became the father of the twelve
patriarchs.&lt;/verse&gt;&lt;/p&gt;

...

&lt;verse osisID="Acts.7.53"&gt;you who have received the law that was put
into effect through angels but have not obeyed it.
&lt;/verse&gt;
&lt;/speech&gt;
...&lt;/chapter&gt;


</pre>
            
            <p><a name="d0e1888"></a>Note that in this example the high priest's short speech in verse
               1 is marked up as a normal container element with normal start- and
               end-tags, because it fits within the bounds of the verse. However,
               Stephen's speech starts in the middle of verse 2 and continues to the
               end of verse 53. This necessitates marking up verse 2 using a
               milestone pair, as shown. The other verses are entirely enclosed
               within the speech, and so need not be marked up using milstone pairs.
               When a conflict arises between the scope of chapter/verse units and
               other units, the chapter/verse units give way by being represented as
               milestones. If a conflict arises between two other units (say, a
               quote that encompasses part but not all of each of two paragraphs),
               it is left to the encoder's discretion which or them is represented
               via milestones.
            </p>
            
         </div>
         
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e1892"></a>11.5. Marking up poetic material
            </h3>
            
            
            <p><a name="d0e1896"></a>
               Although poetic material is commonly called "verse" material, OSIS
               avoids that term because of potential confusion with the
               book/chapter/verse reference system. Thus, like TEI, markup of poetry
               refers to lines and line groups.
               
            </p>
            
            
            <p><a name="d0e1899"></a>
               In addition, OSIS provides a typographic line-break element. This is
               because in at least some editions of the Bible, the exact placement
               of typographic line-breaks within poetic lines is considered very
               important; while on the other hand it is determined in part by
               presentational concerns (for example, column width), rather than by
               linguistic characteristics of either the source or target language.
               
            </p>
            
            
            <p><a name="d0e1902"></a>
               OSIS provides three main elements for marking up poetic material:
               
            </p>
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e1905"></a>11.5.1. lg
               </h4>
               
               <p><a name="d0e1909"></a>The lg or "line group" element is used to contain any group of
                  poetic lines. Thus it covers for units like couple, stanza, and
                  entire poem. Line groups can contain smaller line groups as well.
                  
               </p>
               
            </div>
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e1913"></a>11.5.2. l
               </h4>
               
               <p><a name="d0e1917"></a>The l element is used to mark poetic lines, as determined by the
                  linguistic nature of poetry in the language of the work. For example,
                  much English poetry consists of lines that can be located by the
                  position of rhyming words, and/or by counting syllables; Hebrew poety
                  can often be divided into lines based on parallelism of thought or
                  meaning.
               </p>
               
               
               <p><a name="d0e1920"></a>The following example shows an encoding of the first two verses of
                  	  Psalm 7 from the CEV which uses the <b>lg</b>
                  	  and <b>l</b> elements to mark poetic
                  	  material.
               </p>
               
               <pre class="eg">



&lt;div type='section' scope='Ps.7.1-Ps.7.17'&gt;
	&lt;title&gt;The &lt;divineName type='x-yhwh'&gt;LORD&lt;/divineName&gt; Always Does Right&lt;/title&gt;
		&lt;lg&gt;
	   &lt;l&gt;
	   &lt;verse sID='Ps.7.1' osisID='Ps.7.1'/&gt;You, &lt;divineName type='x-yhwh'&gt;LORD&lt;/divineName&gt; God,&lt;lb type='x-secondLine'/&gt;are my protector.&lt;/l&gt;
	   &lt;l&gt;Rescue me and keep me safe&lt;lb type='x-secondLine'/&gt;from all who chase me.&lt;verse eID='Ps.7.1'/&gt;
	  &lt;/l&gt;
	   &lt;l&gt;
	   &lt;verse sID='Ps.7.2' osisID='Ps.7.2'/&gt;Or else they will rip me apart&lt;/l&gt;
	   &lt;l&gt;like lions&lt;lb type='x-secondLine'/&gt;attacking a victim,&lt;lb type='x-secondLine'/&gt;and no one will save me.&lt;verse eID='Ps.7.2'/&gt;
	  &lt;/l&gt;
	  &lt;/lg&gt;
	 &lt;/div&gt;


	  </pre>
               
               </div>
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e1933"></a>11.5.3. lb
               </h4>
               
               <p><a name="d0e1937"></a>The lb element, or "line break", is used to mark line breaks that
                  are not the result of linguistically or poetically significant
                  structure, but are primarily part of the typography and layout. For
                  example, a lone line might be broken to fit into a narrow column. The
                  lb element is an empty element used to mark where such breaks
                  occurred in an important copy text, or where they should be placed in
                  a text to be rendered.
                  
                  
                  
                  
               </p>
               
               
               <p><a name="d0e1942"></a>
                  Bible typesetting has a long tradition involving placement of such
                  breaks. In some cases, translators have carefully decided preferred
                  or required break-points for various set widths. These can be
                  accommodated by using the type attribute of lb. For example,
                  type="wide-pref" and type="narrow-pref" might be used to identify the
                  locations of preferred line-breaks for wide and narrow column
                  layouts. Similarly, type might be used to distinguish various levels
                  of indentation following the break, or other typographic factors
                  deemed important.
                  
               </p>
               
               
               <p><a name="d0e1945"></a>
                  The lb element should not be used merely to record where line breaks
                  in general happened to occur in a source edition. For most source
                  editions this information is unimportant; for manuscripts it may be
                  imortant, but must be marked up using the milestone element instead.
                  
               </p>
               
               
            </div>
            
            
         </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e1950"></a>11.6. Lists, tables, genealogies, figures and other material
            </h3>
            
            
            <p><a name="d0e1954"></a>
               Simple glossaries such as appear at the back of many Bibles, may be
               encoded at this time using the simple list/label/item elements
               described below. A dicitonary extension is well along in development,
               and should be available as an extension module within the next few
               months. That module should be used for any but the simplest lexical
               tools; and once available, OSIS may decide to recommend against
               further use of list to represent even simple glossaries.
               
            </p>
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e1957"></a>11.6.1. list
               </h4>
               
               <p><a name="d0e1961"></a>All types of lists are marked using the list element; they can be
                  distinguished by type attribute valuess such as "ordered",
                  "unordered", "compact", "definition", and type. A list consists of
                  any number of items, some or all preceded by labels, which
                  corresponded to the definition-terms of definition lists in various
                  schemas.
                  
               </p>
               
            </div>
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e1965"></a>11.6.2. label
               </h4>
               
               <p><a name="d0e1969"></a>A leading label for a given list item. Labels are optional.
                  
               </p>
               
            </div>
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e1973"></a>11.6.3. item
               </h4>
               
               <p><a name="d0e1977"></a>The main content or description for each list item.
                  
               </p>
               
               
               <p><a name="d0e1980"></a>
                  
                  	 
               </p>
               
               
            </div>
            
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e1986"></a>11.6.4. table
               </h4>
               
               <p><a name="d0e1990"></a>OSIS provides only very rudimentary tables: a table consists of
                  rows, which in turn consist of cells. Formatting and layout is not
                  part of the table markup; it can either be done automatically, as in
                  HTML browsers, or by inserting some signal to the layout engine, such
                  as type attributes or processing instructions.
                  
               </p>
               
            </div>
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e1994"></a>11.6.5. row
               </h4>
               
               <p><a name="d0e1998"></a>
                  
               </p>
               
            </div>
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e2002"></a>11.6.6. cell
               </h4>
               
               <p><a name="d0e2006"></a>
                  
                  
                  
                  
               </p>
               
            </div>
            
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e2012"></a>11.6.7. figure
               </h4>
               
               <p><a name="d0e2016"></a>The <b>figure</b> element is used to insert graphic
                  	  non-textual materials, in other words, maps, pictures,
                  	  drawings into an encoded text. The <b>figure</b>
                  	  element in OSIS may contain <b>caption</b> (see
                  	  next section) along with optional <b>index</b>
                  	  and <b>note</b> elements.
                  
               </p>
               
               <p><a name="d0e2034"></a>
                  An example of a <b>figure</b> in an OSIS text might be:
                  
                  <pre class="eg">



&lt;figure src="Beckmann_1917.jpg" alt="Painting by Max Beckmann, titled
	   Christ and the Woman taken in Adultery"&gt;&lt;caption&gt;Christ and
	   the Woman Taken in Adultery by Max Beckmann,
	   1917&lt;/caption&gt;&lt;index index="illustrations"
	   index1="Beckmann, Max"&gt;
&lt;/figure&gt;



	  </pre>
                  
                  	 </p>
               
               <p><a name="d0e2043"></a>At first it may look odd that the material in the <b>alt</b> attribute is repeated in the <b>caption</b> element. The <b>alt</b>
                  	   attribute is important for situations where the application
                  	   or user (for the visually impaired) cannot use or see the
                  	   image that has been inserted in the text. The <b>alt</b> attribute is a friendly way of insuring
                  	   that the encoded text will be understandable by the widest
                  	   range of both applications and users.
                  	 
               </p>
               
               <p><a name="d0e2058"></a>The <b>index</b> attribute allows the encoder to encode
                  	 the information necessary to automatically create an index,
                  	 for either an online version of this material or a more
                  	 traditional back of the book index. The <b>index</b> attribute gives the type of index where this
                  	 item will appear and <b>index1</b> provides the material that
                  	 will appear in that index. See <b>index</b>
                  	 (below) for more information on this element.
               </p>
               
               
            </div>
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e2074"></a>11.6.8. caption
               </h4>
               
               <p><a name="d0e2078"></a>
                  
               </p>
               
            </div>
            
            
         </div>
         
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2083"></a>11.7. milestone
            </h3>
            
            
            <p><a name="d0e2087"></a>
               The milestone element is an empty element, and so is represented as
               &lt;milestone/&gt; rather than as a typical start- or end-tag. It is
               used to mark point events in a text, often involving the layout of
               the original text, or special points of access into the electronic
               text.
               
            </p>
            
            
            <p><a name="d0e2090"></a>
               For example, when digitizing a manuscript, it may be considered
               important to record where the page, column, and line boundaries of
               the original manuscript fell. This would be done as shown here:
               
            </p>
            
            <pre class="eg">

&lt;milestone type="pb" n="37-verso"/&gt;
&lt;p&gt;The Lord said to Eliphaz:&lt;milestone type="line"/&gt;
What my servant Job has said about me is true, &lt;milestone type="line"/&gt;
but I am angry with you and your two friends for &lt;milestone type="line"/&gt;
not telling the truth. &lt;verse osisID="Job.42.8"&gt;So I want you to go
over to &lt;milestone type="line"/&gt;
Job and offer seven bulls and seven goats on an &lt;milestone type="line"/&gt;
alter as a sacrifice to please me. After this, Job &lt;milestone type="line"/&gt;
will pray, and I will agree not to punush you for &lt;milestone
type="line"/&gt;your foolishness.&lt;/verse&gt;&lt;milestone type="line"/&gt;
&lt;verse osisID="Job.42.9"&gt;Eliphaz, Bildad, and Zophar obeyed the Lord,
and he answered Job's prayer.&lt;/verse&gt;

</pre>
            
            <p><a name="d0e2096"></a>
               Note that because milestone is an empty or point element, not a
               container, it may be placed freely without concern about violating
               the boundaries of other elements in the same region.
               
            </p>
            
            
            <p><a name="d0e2099"></a>
               Where a break to be represented by a milestone occurs between other
               units, such as verses or paragraphs, the milestone should be placed
               between those units, rather then just within either.
               
            </p>
            
            
            <p><a name="d0e2102"></a>When setting attribute n on a milestone, it should indicate the
               number of the unit starting, not the unit ending. For example,
               &lt;milestone type="page&gt; n="3"/&gt; indicates the break between
               pages 2 and 3, not between pages 3 and 4. Numbering does not need to
               be unique across various types of milestones -- for example, the 24th
               line on page 5 of a manuscript may be marked simpley n="5", rather
               than n="24.5" or similar.
            </p>
            
            
            <p><a name="d0e2105"></a>Several predefined types are provided for the milestone element:
            </p>
            
            
            <ul>
               <li><a name="d0e2110"></a>pb: 
                  
                  <p><a name="d0e2114"></a>Marks the location of a page break in the source text.
                  </p>
               </li>
               <li><a name="d0e2117"></a>column: 
                  
                  <p><a name="d0e2121"></a>Marks the location of a column break in the source text. The start
                     of the first column need not be marked unless something else (such as
                     a footer) precedes it in the encoding of the page. Columns should be
                     numbered in the order of reading (for example, right to left in
                     Hebrew texts). In the case of, say, an English/Hebrew diglot edition,
                     where there is no principled order of reading among the columns, the
                     direction used for the pages (Hebrew or Greek) should be considered
                     the dominant direction, and the same direction should be used for
                     numbering columns.
                  </p>
               </li>
               <li><a name="d0e2124"></a>header: 
                  
                  <p><a name="d0e2128"></a>A milestone of type "header" should precede the encoding of the
                     page header if it is being included in the encoded text. This would
                     normally be true only for digitized editions of manuscripts or other
                     important copy editions, because in modern print Bibles headers are
                     typically automatically generated.
                  </p>
               </li>
               <li><a name="d0e2131"></a>footer: 
                  
                  <p><a name="d0e2135"></a>Type "footer" should be used just like type "header", except that
                     it marks the page footer area instead.
                  </p>
               </li>
               <li><a name="d0e2138"></a>line: 
                  
                  <p><a name="d0e2142"></a>Line milestones should be used to mark line breaks in the copy
                     text when they are considered significant. This will normally only be
                     true for important manuscripts, where line numbering may be needed
                     for paleographic or reference use. Line milestones must not be used
                     to represent linguistically significant line breaks, such as in
                     poetry, for which the lg and l elements are provided.
                  </p>
               </li>
               <li><a name="d0e2145"></a>halfLine: 
                  
                  <p><a name="d0e2149"></a>In certain languages it is important to mark half-line units, and
                     this type is provided for such cases.
                  </p>
               </li>
               <li><a name="d0e2152"></a>screen: 
                  
                  <p><a name="d0e2156"></a>The milestone of type "screen" is to be used to mark preferred
                     break points in an on-screen rendering of the text. For example, if
                     the user requests to be taken to the book of Psalms in a given
                     electronic edition, it may be best not to take them to Psalm.1.1, but
                     to an earlier point, preceding any introductory material. In many
                     cases this can be accomplished by taking them to the appropriate div
                     (since the &lt;div type="book" osisID="Ps"&gt; should precede and
                     Psalms-specific introductory material); but this milestone type is
                     available for other cases. The OSIS specification does not impose
                     requirements on how applications make use of such
                     milestones.
                  </p>
               </li>
            </ul>
            
            
         </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2161"></a>11.8. milestoneStart and milestoneEnd
            </h3>
            
            
            <p><a name="d0e2165"></a>These elements are deprecated (that is, we strongly recommend
               against their use). They represent an earlier version's way of
               marking up elements that cross other element's boundaries.
               
            </p>
            
            
            <p><a name="d0e2168"></a>
               In OSIS versions prior to 1.5, an element that crossed another's
               boundary, such as a quote crossing a paragraph boundary, could be
               encoded using these elements.
            </p>
            
            
         </div>
         
             
      </div>
      
      
      <div class="teidiv">
         <h2><a name="body.1_div.12"></a>12. Common elements in all texts
         </h2>
         
         <p><a name="d0e2177"></a>The elements found in this section can be found in almost any
                  encoded text.
         </p>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2180"></a>12.1. a
            </h3>
            
            <p><a name="d0e2184"></a>The <b>a</b> element is exactly analogous to the HTML
               <b>a</b> element, and likewise may be used to encode
               links within a document. This eases integration of OSIS documents
               into the Web environment. For example:
               
            </p>
            
            <pre class="eg">
    &lt;p&gt;See Edwards' famous treatise on &lt;a
href="http://www.ccel.org/e/edwards/affections/religious_affections.html"&gt;religious
affections&lt;/a&gt; for additional information.&lt;/p&gt;
</pre>
            </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2197"></a>12.2. index
            </h3>
            
            <p><a name="d0e2201"></a>The <b>index</b> element may be placed at any point in
               the document to indicate a topic under which that location should be
               indexed. It is always an empty element. Multiple indexes (such as of
               places, names, theological or ethical issues, etc) must be
               distinguished via the <b>name</b> attribute. 
            </p>
            
            
            <p><a name="d0e2210"></a>Indexes with up to 4 levels of headings are supported. The primary
               index entry name is specified on the <b>level1</b>
               attribute, followed by sub-headings <b>level2</b>, <b>level3</b>, and <b>level4</b>. For example:
            </p>
            
            <pre class="eg">
    &lt;head&gt;On Justice&lt;index name="topic" level1="Virtues"
level2="Justice"/&gt;
</pre>
            
            <p><a name="d0e2228"></a>There is also a <b>see</b> attribute, which may be
               used to represent the need for a cross-reference to another index
               entry; such elements should be placed together at the end of the
               document body (since they do not refer to a particular location). For
               example:
               
            </p>
            <pre class="eg">
    &lt;index name="topic" level1="Virtues" level2="Justice" see="Fairness"/&gt;
</pre>
            
            <p><a name="d0e2237"></a>No separate "see also" type is provided at this time.
            </p>
            
            
         </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2241"></a>12.3. reference
            </h3>
            
            
            <p><a name="d0e2245"></a>The <b>reference</b> element is used to encode an
               explicit cross-reference to another passage or work (the work
               referred to need not be Biblical, but must be declared via a <b>work</b> element in the header, and by accessible via some
               canonical referencing scheme defined in osisID syntax. Reference
               elements will often occur within notes, but may also occur freely in
               text (the latter is more common when encoding non-Biblical works).
               For example:
               
            </p>
            
            <pre class="eg">



</pre>
            
            </div>
         
         
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2260"></a>12.4. abbr
            </h3>
            
            <p><a name="d0e2264"></a>Marks a portion of the content as an abbreviation. The expanded
               value should be supplied as the value of the expansion attribute. For
               example:
               
            </p>
            
            <pre class="eg">



&lt;abbr expansion="Journal of Biblical Literature"&gt;JBL&lt;/abbr&gt;


</pre>
            
            <p><a name="d0e2270"></a>Most often seen in notes, where citations are often abbreviated and
               users may not be familiar with the abbreviation. Putting expansion in
               the expansion attribute allows software to chose to diplay the
               expansion instead of the abbreviation or to display it upon request by
               the reader.
            </p>
            
            
         </div>
         
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2274"></a>12.5. catchWord
            </h3>
            
            <p><a name="d0e2278"></a>Catchwords and catchphrases are those parts of notes that are
               copied from the main text, to orient the reader as to the note's
               precise applicability. Catchwords in notes must be marked when
               present. For example:
               
            </p>
            
            <pre class="eg">


&lt;verse osisID="NRSV:Ezek.19.5"&gt;When she saw that she was thwarted,
that her hope was lost, she took another of her cubs and made him a
young lion.&lt;/verse&gt; &lt;note&gt;It is uncertain to which king &lt;catchWord
osisRef="Ezek.19.5"&gt;another of her cubs&lt;/catchWord&gt; refers....&lt;/note&gt;


</pre>
            
            </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2285"></a>12.6. divineName
            </h3>
            
            <p><a name="d0e2289"></a>divineName is only for the Deity. Angels, demons, idols, and the
               like should be tagged with &lt;name type='nonhuman'&gt;  For example:
               
            </p>
            
            <pre class="eg">



&lt;divineName&gt;El Shaddai&lt;/divineName&gt;



</pre>
            
            </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2296"></a>12.7. foreign
            </h3>
            
            <p><a name="d0e2300"></a>Marks an insertion of text not in the primary language, such as
               "Talitha Cum" in Mark 5:41. The specific language should be indicated
               via the xml:lang attribute. For example:
               
            </p>
            
            <pre class="eg">



&lt;verse osisID="NRSV:Mark.5.41"&gt;He took her by the hand and said to her: &lt;q&gt;&lt;foreign xml:lang="arc"&gt;Talitha cum&lt;/foreign&gt;&lt;/q&gt;, which means, &lt;q&gt;Little girl, get up!&lt;/q&gt;&lt;/verse&gt;





</pre>
            
            </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2307"></a>12.8. hi
            </h3>
            
            <p><a name="d0e2311"></a>Provides simple text highlighting capability; types can be
               distinguished as to their purpose (emphasis, marking of interpolated
               or transliterated foreign words, boldness for headings, etc.) must
               instead be marked using the appropriate, more specific, element. The
               hi element (short for "highlighted") is reserved for cases where the
               purpose of the highlighting or other typographic distinction is
               unclear, or known to be unimportant.
               
            </p>
            
            
            
            <p>The type attribute on the &lt;hi&gt; element allows the user to
               specify what typographic distinction was observed in the text. As
               noted above this is not meant as a guide for stylesheets but for
               recording what was observed. If it is known why a word or phrase
               appears in italic, for example a foreign phrase, then the
               &lt;foreign&gt; element should be use to mark it. To enable
               consistency in the marking of such distinct texts, the OSIS schema
               provides seven (7) standards values for the type attribute on the
               &lt;hi&gt; element as follows:
               
               
            </p>
            <ul>
               <li><a name="d0e2318"></a>bold
               </li>
               <li><a name="d0e2321"></a>illuminated
               </li>
               <li><a name="d0e2324"></a>italic
               </li>
               <li><a name="d0e2327"></a>line-through
               </li>
               <li><a name="d0e2330"></a>normal
               </li>
               <li><a name="d0e2333"></a>small-caps
               </li>
               <li><a name="d0e2336"></a>underline
               </li>
            </ul>
            <p>
               
            </p>
            
            
         </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2342"></a>12.9. seg
            </h3>
            
            
            
            <p><a name="d0e2346"></a>This is primarily used for segmentation of text in ways not
               provided by the OSIS schema. For example, the lowest level of division
               that has a defined element in OSIS is word. Note that for this version
               of the schema, it is presumed that a word is distinguished by being
               bounded on either side by white space. The OSIS core team was aware
               that such a definition is too crude to be useful for a number of
               modern and ancient languages and intends to address that issue in a
               future release of the schema.
               
            </p>
            
            <p><a name="d0e2349"></a>In cases where subdivisions of words need to be encoded, prefixes,
               suffixes, morphemes, the &lt;seg&gt; element is the correct element to
               be used. It can also be used, with caution, to mark a textual
               feature that is not otherwise provided for by the schema. It should be
               noted that this element can only contain very small elements and
               cannot contain things like verses or paragraphs.
            </p>
            <pre class="eg">



&lt;!-- insert one of Troy's morphological markup --&gt;



</pre>
            
            </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2356"></a>12.10. inscription
            </h3>
            
            <p><a name="d0e2360"></a>inscriptions should not also be tagged as quotations. For example,
               where Paul refers to an alter inscription in Athens (NIV): 
            </p>
            
            <pre class="eg">



&lt;verse osisID="Acts.17.23"&gt;For as I walked around and looked carefully
    at your objects of worship, I even found an altar with this inscription:|
    &lt;inscription&gt;To an unknown god&lt;/inscription&gt;


</pre>
            
            <pre class="eg">



&lt;p&gt;&lt;verse osisID="Dan.5.22"&gt;&lt;q sID="q.Dan.83"/&gt;But you
his son, O Belshazzar, have not humbled yourself, though you knew all
this.&lt;/verse&gt;
&lt;verse osisID="Dan.5.23"&gt;Instead, you have set yourself up against
the Lord of heaven. You had the goblets from his temple brought to
you, and you and your nobles, your wives and your concubines drank
wine from them. You praised the gods of silver and gold, of bronze,
iron, wood and stone, which cannot see or hear or understand. But you
did not honor the God who holds in his hand your life and all your
ways.&lt;/verse&gt;
&lt;verse osisID="Dan.5.24"&gt;Therefore he sent the hand that wrote the
inscription.&lt;/verse&gt;&lt;/p&gt;

&lt;p&gt;&lt;verse osisID="Dan.5.25"&gt;This is the inscription that was written:
&lt;inscription&gt;Mene, Mene, Tekel, Parsin&lt;/inscription&gt;&lt;/verse&gt;




</pre>
            
            <p><a name="d0e2369"></a>Note the use of an empty tag to represent the start of Daniel's
               quotation, which ends at the end of verse 28 (where &lt;q
               eID="q.Dan.83"/&gt; would appear to end the quotation). There is no need
               for quotation marks, either at the start of verse 22 or of verse 25
               (after a paragraph break within the quotation) -- the appropriate
               punctuation conventions for the language and publisher involved will
               be provided via a stylesheet mechanism.
            </p>
            
            
            <p><a name="d0e2372"></a>In the example from Daniel, the repetition of words from the
               inscription (in verse 26-28) should not also be marked as
               inscriptions.
            </p>
            
            
            <p><a name="d0e2375"></a>Inscriptions are found in Exod.39.30, Dan.5.25, 2Tim.2.19. There
               are additional passages where inscriptions are mentioned without
               being quoted verbatim, such as Matt.22.20; these would not be encoded
               using the <b>inscription</b> element.
            </p>
            
            
            
         </div>
         
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2382"></a>12.11. mentioned
            </h3>
            
            <p><a name="d0e2386"></a>This element marks meta-linguistic use of a term. That is, it
               encloses a word, phrase, or other unit that is not being <i>used</i>, but only <i>mentioned</i>.
               For example:
               
               
            </p>
            
            <pre class="eg">


&lt;verse osisID="NRSV:John.1.42"&gt;He brought Simon to Jesus, who looked
at him and said, &lt;q&gt;Your are Simon sone of John. You are to be called
&lt;mentioned&gt;Cephas&lt;/mentioned&gt;&lt;/q&gt; (which is translated Peter).&lt;/verse&gt;



</pre>
            
            <p><a name="d0e2398"></a>In this example, <i>Cephas</i> is not being used by
               Jesus to call Simon to him but is being used to tell him his new name.
            </p>
            
            
         </div>
         
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2405"></a>12.12. name
            </h3>
            
            <p><a name="d0e2409"></a>When a <i>name</i> appears in a text, it is
               important to mark it with this element and to use the type attribute
               to record what type of name has been marked. Remember that a computer
               cannot distinguish <i>Job,</i> as in the man from Ur,
               from <i>job,</i> as in &#8216;I have a job
               for you...&#8217; without your assistance. Despite what you may read in
               the newspaper, computers are very literal and quite dumb when it comes
               to reading texts.
               
            </p>
            
            
            <p><a name="d0e2424"></a>The formal types or names provided are:
            </p>
            
            
            <ul>
               <li><a name="d0e2429"></a>geographic
                  <p><a name="d0e2432"></a></p>
               </li>
               <li><a name="d0e2434"></a>holiday
                  <p><a name="d0e2437"></a></p>
               </li>
               <li><a name="d0e2439"></a>nonhuman
                  <p><a name="d0e2442"></a></p>
               </li>
               <li><a name="d0e2444"></a>person
                  <p><a name="d0e2447"></a></p>
               </li>
               <li><a name="d0e2449"></a>ritual
                  <p><a name="d0e2452"></a></p>
               </li>
            </ul>
            
            <pre class="eg">



&lt;verse osisID="NRSV:Job.1.1"&gt;There once was a man in the land of &lt;name type="geographic"&gt;Uz&lt;/name&gt; whose name was &lt;name type="person"&gt;Job&lt;/name&gt;. That man was blameless and upright, one who feared &lt;divineName&gt;God&lt;/divineName&gt; and turned away from evil.&lt;/verse&gt;


</pre>
            
            <p><a name="d0e2458"></a>Note that there are three names in that verse, one geographic, one of a person, and one of the Deity. The first two are marked
               with the <i>name</i> element and appropriate type attribute. Any use of any form of the name of the Deity is marked with <i>divineName</i>.
            </p>
            
            
         </div>
         
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2468"></a>12.13. q
            </h3>
            
            <p><a name="d0e2472"></a>The q element marks all quotations, whether inline or
               block-length. It often crosses the boudnaries of other units, and so
               may be encoded using empty elements with sID and eID attributes. The
               positioning of q elements will not always coincide with the placement
               of quotations marks in a printed version. For example, there are
               varying conventions about how to punctuate quotations that are
               continued across paragraph boundaries, or continued after a marker
               such as "he said, graciously."
               
            </p>
            
            <pre class="eg">



</pre>
            
            </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2481"></a>12.14. rdg
            </h3>
            
            <p><a name="d0e2485"></a>This element is used to mark variant or alternate readings. At
               this time it is intended for use within <b>note</b>hi&gt;
               elements. For example:
               
            </p>
            
            <pre class="eg">



&lt;verse osisID="NRSV.Song.2.1"&gt;I am a rose&lt;note
	 osisRef="NRSV.Song.2.1@s[rose]"&gt;Heb &lt;rdg&gt;crocus&lt;/rdg&gt;&lt;/note&gt; of Sharon, a lilly of the valleys.&lt;/verse&gt;



</pre>
            
            <p><a name="d0e2494"></a>This example illustrates (or reinforces several points): 1. A note
               	 appear directly in the textual material where the user would
               	 normally see a raised letter or number to indicate a
               	 note. 2. The <b>osisRef</b> attribute allows the
               	 note to point at a particular word in the text to which the
               	 note applies. 3. The <b>rdg</b> element holds an
               	 alternative word or reading to the one found in the text. The
               	 interested reader will note that the identification of
               	 "crocus" is unclear but it is known that there were no
               	 "roses" in the modern sense of the word growing on the plain
               	 of Sharon (northern Israel) in biblical times.
            </p>
            
            
         </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2504"></a>12.15. transChange
            </h3>
            
            <p><a name="d0e2508"></a>This element should be used to mark text that was changed in a
               notable way in translation. For example, the KJV traditionally
               distinguishes all words inserted in translation (often via italics);
               the Aplified Bible has several punctuation conventions for marking
               explanatory or other expansions; and some translations indicate where
               the tense of verbs has been changed, perhaps due to sequence-of-tense
               requirements in the target language. Several sub-types are provided,
               as listed below; others may be coined if needed, so long as their
               names begin "x-".
               
            </p>
            
            <ul>
               <li><a name="d0e2513"></a>added
                  <p><a name="d0e2516"></a></p>
               </li>
               <li><a name="d0e2518"></a>amplified
                  <p><a name="d0e2521"></a></p>
               </li>
               <li><a name="d0e2523"></a>changed
                  <p><a name="d0e2526"></a></p>
               </li>
               <li><a name="d0e2528"></a>deleted
                  <p><a name="d0e2531"></a></p>
               </li>
               <li><a name="d0e2533"></a>moved
                  <p><a name="d0e2536"></a></p>
               </li>
               <li><a name="d0e2538"></a>tenseChange
                  <p><a name="d0e2541"></a></p>
               </li>
            </ul>
            
            <pre class="eg">



</pre>
            
            </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2550"></a>12.16. w
            </h3>
            
            <p><a name="d0e2554"></a>The <b>w</b> element provides a place to put
               rudimentary word-level annotation, such as part of speech
               identifiers, lemma or Strong's numbers, and the like. Formal systems
               for expressing such information are under development; in the
               meantime, <b>w</b> provides a convenient placeholder so
               at least the most basic such information can be easily located for
               use by processors.
               
            </p>
            
            <pre class="eg">



</pre>
            
            </div>
         
         
         
      </div>
      
      
      
      
      
      
      <div class="teidiv">
         <h2><a name="body.1_div.13"></a>13. Canonical refererence (or versification) schemes
         </h2>
         
         
         <p><a name="d0e2576"></a>
            A canonical refererence scheme is a system of agreed names and/or
            numbers for for referring to parts of a document. In the Bible, the
            traditional system used in most languages consists of a book name
            (such as Genesis), then a chapter number, then a verse number. Most
            works of Classical literature have similar schemes, nearly all of
            which are also hierarchical (that is, they work from larger units to
            smaller).
            
         </p>
         
         
         <p><a name="d0e2579"></a>
            The basic form for Biblical verse references is strictly defined by
            OSIS, so that various electronic Bible versions can interoperate
            easily. Standard abbreviations for the canonical and deuterocanonical
            books are provided; chapter and verse numbers follow the book
            abbreviation separated by periods. For example:
            
         </p>
         
         <pre class="eg">
    Matt.1.1
</pre>
         
         
         <p><a name="d0e2585"></a>
            OSIS uses such identifiers in several places:
            
         </p>
         
         
         <ul>
            <li><a name="d0e2590"></a>To identify a portion of text from an actual canonical
               work, such as a verse of the Bible. The verse element bears an osisID
               attribute which must include the identifier appropriate to the verse.
               For example, &lt;v osisID="Matt.1.1"&gt;&gt;....
            </li>
            <li><a name="d0e2593"></a>To identify a reference <b>i</b>to&lt;/i&gt; a Biblical or other passage, that is not
               contained at the point of reference. For example, <b>p</b>The correctness of my exegesis is incontrovertibly
               proven by &lt;reference osisRef="Matt.1.1"&gt;the first verse of
               Matthew.&lt;/p&gt;
            </li>
            <li><a name="d0e2602"></a>In the header, to identify what portions of the Bible
               are included in a declared work. For example, a particular edition
               may include only the NT and Psalms. The scope element may be used to
               specify each relevant portion.
            </li>
         </ul>
         
         
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2606"></a>13.1. Partial identifiers
            </h3>
            
            
            <p><a name="d0e2610"></a>
               It is permissible to refer to an entire chapter by simply omitting
               the verse number and the preceding ".", for example:
               
            </p>
            
            <pre class="eg">
      Matt.5
</pre>
            
            <p><a name="d0e2616"></a>
               Similarly, it is permissible to refer to an entire book by omitting
               the chapter and verse number and both corresponding periods:
               
            </p>
            
            <pre class="eg">
      1Cor
</pre>
            
            <p><a name="d0e2622"></a>
               For those books of the Bible that have only 1 chapter, the chapter
               number "1" must be specified:  The first verse of Jude is thus
               Jude.1.1, not Jude.1.
               
            </p>
            
            
         </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2626"></a>13.2. Works
            </h3>
            
            
            <p><a name="d0e2630"></a>
               A reference can also identify a place in a particular edition or
               translation of the Bible, or to other works entirely, such as
               Josephus, writing of the Apostolic fathers, classical or modern
               literature, and so on. We discuss later how to declare particular
               works and give them local short names. Once that is done, the short
               name for any declared work can be put before any reference to it, for
               example:
               
            </p>
            
            <pre class="eg">
    NIV:Matt.1.1
</pre>
            
            <p><a name="d0e2636"></a>
               The colon is required, to make it is clear where the work ends and
               the within-work reference begins. Most commonly, however, the work is
               omitted (the default work used then is whatever work was named on the
               osisWorkID attribute of the osisText element).
               
            </p>
            
            
            <p><a name="d0e2639"></a>
               It is possible to refer to an entire work, such as the whole CEV,
               NIV, KJV, the Iliad, etc. However, to do so the work name must be
               stated, and the following colon must be included (without the colon,
               it would be interpreted as a top-level identifier within the work).
               
            </p>
            
            
         </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2643"></a>13.3. Sub-identifiers
            </h3>
            
            
            <p><a name="d0e2647"></a>
               Translations also often split verses into parts, provided labels such
               as "a" and "b" for the separate parts. Encoders may freely add
               sub-identifiers below the lowest standardized level. They are set off
               from the standardized portion by the character "!" (as opposed to "."
               between levels of the standard system). For example:
               
            </p>
            
            <pre class="eg">
      Rev.2.20!b
</pre>
            
            <p><a name="d0e2653"></a>
               Such subdivisions are not standard across different translations, so
               applications must be prepared to discard them when trying to locate a
               referenced location in a different edition.
               
            </p>
            
            
            <p><a name="d0e2656"></a>
               These extensions are not considered a formal part of the canonical
               reference scheme, and so a work that uses them need not claim it is
               using a different scheme.
               
            </p>
            
            
         </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2660"></a>13.4. Grouping
            </h3>
            
            
            <p><a name="d0e2664"></a>
               Translators often group several adjacent verses into a single block,
               so that they can translate them using word order more natural in the
               target language. In such cases, the larger unit (commonly a paragraph
               or p element), gets an osisID that lists all the individual osisIDs
               for the verses included, separated by white space. For example:
               
            </p>
            
            <pre class="eg">
    &lt;p osisID="Matt.1.1 Matt.1.2 Matt.1.3"&gt;...&lt;/p&gt;
</pre>
            
            <p><a name="d0e2670"></a>
               osisIDs never allow the use of ranges. Only osisRefs (discussed later) do.
               
            </p>
            
            
            <p><a name="d0e2673"></a>Ranges are prohibited for osisIDs in order to simplify
               implementation of tools that search for particular passages by
               reference. If an encoder wished to mark IDs at, say, the pericope
               level, the markup would be quite verbose because many verses would
               need to be listed in a single attribute on the div type="pericope".
               However, there is no need to do this if the verses within the
               pericope are themselves identified. 
            </p>
            
            
         </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2677"></a>13.5. Other details of osisIDs
            </h3>
            
            
            <p><a name="d0e2681"></a>
               The "."-separated parts of an osisID are defined to represent a
               hierarchy. In the traditional versification (introded by Whittingham
               about ????), these would be book, chapter, and verse numbers. In
               other schemes for the Bible, or schemes for entirely different works,
               the names of the parts may differ, but the expectation is that they
               still form a hierarchy.
               
            </p>
            
            
            <p><a name="d0e2684"></a>
               The parts of an osisID may contain any mixture of numbers, letters,
               hyphens, and underscore. However, to avoid conflict with the other
               punctuations used (such as ":" to separate the work from the in-work
               location, "@" to separate fine-grained references in osisRefs, and
               "!" to separate work-specifiec extensions to a versification scheme),
               no other characters are allowed.
               
            </p>
            
            
            <p><a name="d0e2687"></a>
               As with XML in general, these identifiers are case-sensitive: "Matt"
               is the correct form, and there is no Bible book in OSIS that is
               called "matt" or "MATT". Applications for end users may choose to
               accept case variants in such names, but applications for encoders
               (such as OSIS editors) must not produce documents with invalid
               reference names.
               
            </p>
            
            
         </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2691"></a>13.6. Coding multiple versification or reference schemes in a single document
            </h3>
            
            
            <p><a name="d0e2695"></a>
               "!" as the terminator (after which encoders may append names and/or
               numbers to provide finer-grained reference points).
               
            </p>
            
            
            
            <p><a name="d0e2698"></a>
               A work may provide identifiers drawn from multiple distinct
               versification schemes. A Bible may wish to provide both the Hebrew
               and Greek traditional verse numberings; while a work of classical
               literature may be made more accessible by marking the boundaries of
               canonical units drawn from completely unrelated systems, such as Loeb
               and Whiston for Josephus (and 4 more systems for Josephus' Jewish War
               specifically -- see H. Douglas Buckwalter and Mary K. Shoaff, Guide
               to Reference Systems for the Works of Flavious Josephus, Evangelical
               Theological Society, 1995, ISBN 093205501X).
               
            </p>
            
            
            <p><a name="d0e2701"></a>
               A simpler case may also arise where multiple reference schemes are in
               use: an osis Corpus that includes several osisTexts, each of which
               uses a different reference scheme. This case is simpler, since each
               osisText can provide its own default reference system, using the
               osisRefWork attribute on osisText.
               
            </p>
            
            
            <p><a name="d0e2704"></a>
               This is accomplished in the same way as just described for discursive
               translations: the multiple identifiers are simply placed where
               needed, separated by spaces when they co-occur on a single element.
               Each reference system used much be declared as a work in the header,
               and each identifier much indicate the reference system from which it
               is drawn. For example, a line of Josephus that has two distinct
               identifiers would appear like this (presuming the appropriate work
               declarations in the header):
               
            </p>
            
            <pre class="eg">
    &lt;l osisID="josephus-war:loeb:245.22 josephus-war:whiston:22.3.14b"&gt;
</pre>
            
            <p><a name="d0e2710"></a>
               Because verse, chapter, and similar elements can be expressed by
               empty-element pairs when necessary, it is possible to encode multiple
               reference systems even though they may have completely unrelated
               start and end points for their units. For example, a work that has
               one reference system based on sentences, and another based on lines
               of a normative print edition, can co-exist. However, taken to
               extremes this would get rather messy, and be difficult to maintain
               without OSIS-aware software to assist.
               
            </p>
            
            
         </div>
         
         
         
      </div>
      
      
      
      
      
      
      <div class="teidiv">
         <h2><a name="body.1_div.14"></a>14. OSIS references
         </h2>
         
         
         <p><a name="d0e2721"></a>
            An OSIS reference is very much like an osisID. The fundamental
            difference is that while an osisID <strong>identifies</strong> the actual
            occurrence of canonical text, an osisRef is used to <strong>refer</strong> to
            canonical text from somewhere else. For example, a footnote
            (particularly one of type="crossReference") may refer to a related
            passage, or a section heading in the Mark may include references to
            the parallel passages in Matthew and Luke; in such cases an osisRef
            rather than an osisID is used.
            
         </p>
         
         
         
         <p><a name="d0e2730"></a>
            Any valid osisID is also a valid osisRef, and refers to the same
            thing. Thus for example, a commentary might say:
            
         </p>
         
         <pre class="eg">
    &lt;p&gt;The same interpretive method applies also in &lt;reference
    osisRef="Luke.1.1"&gt;the first verse of Luke&lt;/reference&gt;.&lt;/p&gt;
</pre>
         
         
         <p><a name="d0e2736"></a>
            However, osisRefs provide additional capabilities. They can refer to
            a contiguous range of books, chapters, verses (or other units, as
            applicable to the work being referenced), and they can refer to
            precise locations within a given canonically-reference unit.
            
         </p>
         
         
         <p><a name="d0e2739"></a>
            To refer to a range, simply include two osisIDs, one for the first
            verse (or chapter or book) of the range, and one for the last.
            Separate the 2 values by a single hyphen (white space is also
            permitted, but not recommended, on either or both sides of the
            hyphen). For example:
            
         </p>
         
         <pre class="eg">
    John.3.14-John.3.16
    Prov.30-Prov.31
    Esth-Song
    Ps.149-Prov.3.4
</pre>
         
         <p><a name="d0e2745"></a>
            Both sides of the hyphen must hold complete references. It is not
            correct to abbreviate the first example above to merely
            "John.3.14-16" (as always, the values of osisID and osisRef
            attributes need not be the same values displayed to the reader).
            
         </p>
         
         
         <p><a name="d0e2748"></a>
            A single osisRef cannot identify a discontiguous range of a work. For
            example, a complex reference such as "John 3:14-16, 18; 4:1-2; 19-20"
            cannot be encoded as a single reference. It must instead be encoded
            as several parts, each contiguous:
            
         </p>
         
         <pre class="eg">



&lt;p&gt;See also
    &lt;reference osisRef="John.3.14-John.3.6"&gt;John 3:14-16,
&lt;/reference&gt;
    &lt;reference osisRef="John.3.18"&gt;18; &lt;/reference&gt;
    &lt;reference osisRef="John.4.1-John.4.2"&gt;4:1-2; &lt;/reference&gt;
    &lt;reference osisRef="John.19-John.20"&gt;4:1-2;
&lt;/reference&gt;.&lt;/p&gt;


</pre>
         
         <p><a name="d0e2754"></a>It is permissible for osisRefs, including those on either side of
            a hyphen in a range reference, to use osisIDs that include the
            work-specific extension fields ("!" followed by a name).
         </p>
         
         
         
         <p><a name="d0e2757"></a>To refer to specific locations within a named canonical reference
            element, give the osisID as usual, followed by a "grain identifier",
            which consists of the character "@", and then an identifier for the
            portion desired. Such identifiers are of the form:
         </p>
         
         <pre class="eg">
    grainType(parameters)
</pre>
         
         <p><a name="d0e2763"></a>
            Two grain types are defined at this time:
            
         </p>
         
         
         <p><a name="d0e2766"></a>
            cp (short for "code point") counts through the character content of
            the referenced element, essentially by characters. Technically, the
            units counted are Unicode code points, a term which is defined more
            precisely than the generic term "character". The first code point of
            content is number 1, not 0.
            
         </p>
         
         
         <p><a name="d0e2769"></a>
            No markup included within the element specifies is counted, and
            markup does not imply a space for purposes of counting even if it may
            for purposes of layout or printing.
            
         </p>
         
         
         <p><a name="d0e2772"></a>
            When referring to a location in canonical content, text within
            non-canonical elements is not counted. Thus, the intuitive count will
            not be changed by the insertion of notes, references, critical
            apparatus, and the like). When referring to a location in
            non-canonical content, all text in all included elements counts,
            whether canonical or not.
            
         </p>
         
         
         
         
         <p><a name="d0e2775"></a>
            Grains: s finds the first match of the string value specified, with
            regard to case, within the canonical reference specified. If the
            canonical reference is one of several applied to the same target
            element (for example, when a paragraph has osisRef="Matt.1.1 Matt.1.2
            Matt.1.3), that whole element is searched. If the string is not
            found, the user agent must warn the user, and may offer to suggest a
            best guess (for example, by searching again while ignoring case,
            whitespace, punctuation, accents, spelling variation, etc).
            
         </p>
         
         
      </div>
      
      
      
      
      
      
      <div class="teidiv">
         <h2><a name="body.1_div.15"></a>15. Different versification systems
         </h2>
         
         
         <p><a name="d0e2785"></a>
            Hebrew tradition numbers the proscriptions above Psalms (such as "A
            Maskil according to David") as verse one, and goes on from there;
            Greek tradition does not number the proscriptions, and start verse 1
            after it. Of course, this would make all references in Psalms be off
            by one verse if the version reached is from the other tradition.
            
         </p>
         
         
         <p><a name="d0e2788"></a>
            A few languages use traditional reference schemes that completely
            differ from the familiar book/chapter/verse one.
            
         </p>
         
         
         <p><a name="d0e2791"></a>
            Many works of Classical literature likewise have more than one
            standard canonical reference scheme, such a Loeb numbers plus another
            method.
            
         </p>
         
         
         
         <p><a name="d0e2794"></a>
            In such cases, where there are large and systematic differences,
            different "versification schemes" must be defined and named. On the
            other hand, nearly every edition of the Bible has some slight
            deviations from a standard versification scheme that it otherwise
            follows: for example, subdividing verses into parts "a" and "b",
            combining verses into a larger translation unit, and so on. It is
            highly undesirable to call these separate versification schemes,
            because they differ so slightly; because the differences can be
            mechanically resolved; and because there is considerably overhead to
            maintaining and mapping among versification schemes. Thus, as
            described below such minor extensions can be done without an edition
            having to say it is using a completely different versification scheme.
            
         </p>
         
         
         <p><a name="d0e2797"></a>
            BTG intends to develop an XML schema for declaration files that can
            express such systems, and their mapping to other systems. This work
            has not been completed. However, we reserve the following names for
            versification schemes we already know to be relevant:
            
         </p>
         
         <pre class="eg">
    Hebrew
    NA27
    SamPent
    LXX
</pre>
         
         
         
         <p><a name="d0e2803"></a>
            Each work must identify which versification scheme(s) it uses; this
            is done on the work's entry in the header.
            
         </p>
         
         
         <p><a name="d0e2806"></a>
            References can also state what versification scheme they are
            expressed in, so that they may be correctly interpreted.
            
         </p>
         
         
         
         <p><a name="d0e2809"></a>
            HTML may provide targets that look like canonical Bible references,
            but this would not remove the requirement to specify osisID where
            applicable. osisID is mandatory when applicable.
            
         </p>
         
         
         
             
      </div>
      
      
      
      
          
      <div class="teidiv">
         <h2><a name="body.1_div.16"></a>16. Conformance requirements
         </h2>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2819"></a>16.1. Conformance levels
            </h3>
            
            <p><a name="d0e2823"></a>
                   There are 4 levels of OSIS conformance for the markup in OSIS documents:
               
            </p>
            
                
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e2826"></a>16.1.1. Level 1: "Minimal OSIS document"
               </h4>
               
               
               <p><a name="d0e2830"></a>
                      The document must be a well-formed and valid XML document
                  according to the OSIS schema.
                  
               </p>
               
               
               <p><a name="d0e2833"></a>
                      The document must be complete in accordance with the scope
                  declaration in its work declaration. For example, a document with a
                  missing chapter is not OSIS-conforming.
                  
               </p>
               
               
               <p><a name="d0e2836"></a>
                      The document must mark all canonical references where applicable
                  (for example, book, chapter, and verse boundaries in Bibles. Marking
                  in groups,
                  for example a paragraph that includes several verses, is permissible.
                  
               </p>
               
               
               <p><a name="d0e2839"></a>
                      The header must include work declarations for the document itself,
                  and for the versification system it uses.
                  
               </p>
               
               
               <p><a name="d0e2842"></a>
                      All work declarations must provide unique <b>osisWorkID</b> values, and <strong>only</strong> those values may
                  appear as work identifiers in osisIDs and osisRefs (whether by
                  default or explicit) in the document.
                  
               </p>
               
               
               <p><a name="d0e2851"></a>
                      All work declarations must provide at least title, creator, and
                  date(s). Creator may be coded as "(anonymous)" or "(unknown)" if
                  applicable. The date of electronic publication is required; other
                  dates may be omitted or coded as "(unknown)" if applicable, though
                  they should be provided if known.
                  
               </p>
               
               
               <p><a name="d0e2854"></a>
                      At least one revision description element must be included,
                  describing the most recent substantial changes to the document. The
                  name and email address of the last responsible party should be
                  included.
                  
               </p>
               
               
               <p><a name="d0e2857"></a>Empty elements substituted for containers (such as verse, q, etc.)
                  must occur in matched pairs. Each end must actualloy be expressed by
                  a true XML empty element, not by start and end tags with nothing
                  between. The earlier member of each pair must have an sID attribute
                  and no eID attribute; the later member of each pair must have an eID
                  attribute and no sID or any other attributes. The sID and eID values
                  for a pair must match (including as to case), and must be distinct
                  from all other sID and eID attribute values in the document.
               </p>
               
               
               <p><a name="d0e2860"></a>
                      All elements must be used substantially in accordance with their
                  intended meaning as conveyed in this documentation (including
                  documentation and standards referred to, such as Dublin Core, USMARC
                  Relator Codes, and so on).
                  
               </p>
               
               
            </div>
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e2864"></a>16.1.2. Level 2: "Basic OSIS Document"
               </h4>
               
               
               <p><a name="d0e2868"></a>
                      All requirements of Level 1 conformance must be fulfilled.
                  
               </p>
               
               
               <p><a name="d0e2871"></a>
                      A clear statement of rights must be provided within the <b>rights</b> element. If the document is licensed for free
                  copying under certain conditions, those conditions or a reliable URI
                  to them must be provided. If there are encumbrances or if clearance
                  is required to copy or use the work, contact information for the
                  responsible party must be provided directly within the <b>rights</b> element.
                  
               </p>
               
               
               <p><a name="d0e2880"></a>
                     The source edition from which the electronic edition was produced
                  must be clearly identified, or clearly stated as unknown (the latter
                  practice is deprecated, and encoders are strongly encouraged to make
                  a serious effort to identify the source edition).
                  
               </p>
               
               
               <p><a name="d0e2883"></a>
                      All inscriptions (for example, "mene mene tekel parsin") must be
                  marked where applicable.
                  
               </p>
               
               
               <p><a name="d0e2886"></a>
                      All instances, translations, or transliterations of the
                  tetragrammaton must be marked via the <b>divineName</b>
                  element.
                  
               </p>
               
               
               <p><a name="d0e2892"></a>
                      All languages substantially appearing in the text must be
                  identified, and all
                      points where the text itself identifies a phrase as coming from a
                  particular language must be marked up to match (for example, "Talitha
                  cumi").
                  
               </p>
               
               
               <p><a name="d0e2895"></a>
                      All epistolary markup (opener, closer, signature, salute) must be
                  provided where applicable.
                  
               </p>
               
               
               <p><a name="d0e2898"></a>
                     Poetic text must be marked sufficiently to enable rendering it
                  readably as poetry. The distinction of using <b>l</b> for
                  linguistically or poetically significant line breaks, versus using
                  <b>lb</b> for typographically significant or preferred
                  line breaks, must be maintained.
                  
               </p>
               
               
               <p><a name="d0e2907"></a>
                     If the source edition had section, paragraph, block quotation, or
                  other similar demarcations in addition to book, chapter, and verse
                  numbering, they  must be included and appropriately marked up.
                  
               </p>
               
               
               <p><a name="d0e2910"></a>
                     If the source edition had footnotes, sidenotes, endnotes, or other
                  notes, they must be included, and must be distinguished into as many
                  types as can be readily distinguished by observing the typographic
                  conventions of the source edition. Once OSIS standardizes a format
                  for external annotation files, this requirement may be fulfilled
                  either by inline encoding of annotations, or external.
                  
               </p>
               
               
            </div>
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e2914"></a>16.1.3. Level 3: Complete OSIS document
               </h4>
               
               
               <p><a name="d0e2918"></a>
                     All the requirements of Level 2 must be fulfilled.
                  
               </p>
               
               
               <p><a name="d0e2921"></a>
                     All notes, front and back matter, illustrations, section heads, and
                  other non-canonical phenomena of the source edition must be included.
                  
               </p>
               
               
            </div>
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e2925"></a>16.1.4. Level 4: Scholarly OSIS document
               </h4>
               
               
               <p><a name="d0e2929"></a>
                     All the requirements of Level 3 must be fulfilled.
                  
               </p>
               
               
               <p><a name="d0e2932"></a>
                     Substantial critical apparatus must be available in the text, such
                  as: Strong's or comparable numbering of words; part-of-speech and/or
                  other linguistic markup; encoding of variant readings, critical
                  apparatus, and the like; extensive translation, scholarly,
                  interpretive, or other notes.
                  
               </p>
               
               
               <p><a name="d0e2935"></a>
                     At least highly significant persons and places in the text must be
                  marked as names, and refer to the normative form of the corresponding
                  individual (the BIble Technologies Group is preparing normative lists
                  at this time). Where such identification is a matter of non-obvious
                  interpretation, that fact must be marked, and the encoders' practices
                  and biases should be duly noted in the front matter.
                  
               </p>
               
               
               <p><a name="d0e2938"></a>
                     The text must also conform to the requirements of Level 3 Quality
                  as described below.
                  
               </p>
               
               
            </div>
            
         </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2943"></a>16.2. Quality levels
            </h3>
            
            
            <p><a name="d0e2947"></a>
               The conformance levels defined above do not specify the level of
               accuracy and proofreading of the text proper. This is instead
               measured by the following scale of "Quality":
               
            </p>
            
            
         </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2951"></a>16.3. Level 1: Sub-OCR Quality
            </h3>
            
            
            <p><a name="d0e2955"></a>
               The text may have many typographical errors; essentially, it is
               unproofread text from automated OCR, probably of a less-than-ideal
               original.
               
            </p>
            
            
         </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2959"></a>16.4. Level 2: OCR Quality
            </h3>
            
            
            <p><a name="d0e2963"></a>
               The text may have up to 5 typographical errors per source page. It
               may be unproofead output from ideal OCR of an ideal source, or may
               have been run at least through rudimentary spell-checking or
               vocabulary counting and repair, or entered by a double-keying or
               similar service that maintains accuracy to the required level.
               
            </p>
            
            
         </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2967"></a>16.5. Level 3: Proof Quality
            </h3>
            
            
            <p><a name="d0e2971"></a>
               There may not be more than an average of 1 error per source page (or
               per 2000 characters of content) as compared with the stated copy
               text. This requirement does not preclude producing new editions,
               which for example may fix typos in the original, normalize spelling
               of older texts, and so on. Howeve, in such cases it is recommended
               that the best available copy of the source text as it existed prior
               to such modernizations, also be made available.
               
            </p>
            
            
         </div>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e2975"></a>16.6. Level 4: Trusted Quality
            </h3>
            
            
            <p><a name="d0e2979"></a>
               A Trusted Quality document must fulfill all the requirements of a
               Proof Quality document, and must also have been in public use for at
               least one year, and read by at least 5 independent proofreaders, with
               all noted errors fixed. The text should have available a complete log
               of changes made since it reached Proof Quality. Random spot-checks of
               at least 3% of the text must come up with no instances of more than 1
               error per 5 pages (or 10,000 characters of content).
               
            </p>
            
            
         </div>
         
      </div>
      
      
      
          
      <div class="teidiv">
         <h2><a name="body.1_div.17"></a>17. Application Requirements
         </h2>
         
         
         <p><a name="d0e2990"></a>
            Applications should avoid making any processing distinctions between
            elements represented as non-crossing single elements or as milestone
            pairs.
            
         </p>
         
         
         <p><a name="d0e2993"></a>Applications must interpret OSIS references as accurately as is
            feasible, but apply smart fallback as needed. For example, grains
            will not map across translations or languages, though most will
            typically survive changes between successive editions of the same
            text, or differences between British and American English versions.
            Applications should in general at least offer to take the user to the
            nearest reliably-findable place; in this case, the verse. 
         </p>
         
         
         <p><a name="d0e2996"></a>
            Applications must be able to interpret the OSIS elements and process
            them in a manner consistent with their express intent as specified in
            this document, and in accordance with standard practices of Bible
            publishing. For example, applications should be capable of
            distinguishing the typography used for inscriptions, the divine Name,
            verse labels and references, foreign insertions in the text, notes,
            and so on in ways readily recognizable to users of print Bibles.
            
         </p>
         
         
         <p><a name="d0e2999"></a>
            The Bible Technologies group also strongly advocates making all
            software, and especially all OSIS-aware software, accessible to
            print-disabled users. This includes details such as providing text
            alternates for all graphics, not marking up poetry such that it can
            only be line-broken given certain line widths or font sizes; not
            making crucial distinctions only via color, subtleties of font, etc.;
            and not using tables gratuitously to achieve formatting goals rather
            than to represent truly tabular information. Subtle technical factors
            can also ruin otherwise accessible software, for example, the order
            in which panes are drawn. Implementors are strongly encouraged to
            consult with experts on accessibility, and obtain specific critical
            testing and review by print-disabled users before finalizing product
            releases. The Bible Technology will, as resources permit, be glad to
            help connect implementors with accessibility experts.
            
         </p>
         
             
      </div>
      
      
      
      
      
      
      
          
      <div class="teidiv">
         <h2><a name="body.1_div.18"></a>18. Alphabetical list of Elements
         </h2>
         
         
         <ul>
            <li><a name="d0e3013"></a>NAME: PLACEMENT
            </li>
            <li><a name="d0e3018"></a><b>a: </b>Content, inline
            </li>
            <li><a name="d0e3024"></a><b>abbr: </b>Content, inline
            </li>
            <li><a name="d0e3030"></a><b>actor: </b>castGroup structure
            </li>
            <li><a name="d0e3036"></a><b>caption: </b>Figure structure
            </li>
            <li><a name="d0e3042"></a><b>castGroup: </b>castGroup structure
            </li>
            <li><a name="d0e3048"></a><b>castItem: </b>castGroup structure
            </li>
            <li><a name="d0e3054"></a><b>castList: </b>castGroup structure
            </li>
            <li><a name="d0e3060"></a><b>catchWord: </b>Annotation
            </li>
            <li><a name="d0e3066"></a><b>cell: </b>table structure
            </li>
            <li><a name="d0e3072"></a><b>chapter: </b>Main content
            </li>
            <li><a name="d0e3078"></a><b>closer: </b>Epistolary
            </li>
            <li><a name="d0e3084"></a><b>contributor: </b>Dublin Core (in work)
            </li>
            <li><a name="d0e3090"></a><b>coverage: </b>Dublin Core (in work)
            </li>
            <li><a name="d0e3096"></a><b>creator: </b>Dublin Core (in work)
            </li>
            <li><a name="d0e3102"></a><b>date: </b>Dublin Core (in work)
            </li>
            <li><a name="d0e3108"></a><b>description: </b>Dublin Core (in work)
            </li>
            <li><a name="d0e3114"></a><b>div: </b></li>
            <li><a name="d0e3119"></a><b>divineName: </b></li>
            <li><a name="d0e3124"></a><b>figure: </b>Figure structure
            </li>
            <li><a name="d0e3130"></a><b>foreign: </b>Main content
            </li>
            <li><a name="d0e3136"></a><b>format: </b>Dublin Core (in work)
            </li>
            <li><a name="d0e3142"></a><b>head: </b>Main content
            </li>
            <li><a name="d0e3148"></a><b>header: </b>Header
            </li>
            <li><a name="d0e3154"></a><b>hi: </b>Main content
            </li>
            <li><a name="d0e3160"></a><b>identifier: </b>Dublin Core (in work)
            </li>
            <li><a name="d0e3166"></a><b>index: </b>Main content
            </li>
            <li><a name="d0e3172"></a><b>inscription: </b>Main content
            </li>
            <li><a name="d0e3178"></a><b>item: </b>List structure
            </li>
            <li><a name="d0e3184"></a><b>l: </b>Poetic structure
            </li>
            <li><a name="d0e3190"></a><b>label: </b>List structure
            </li>
            <li><a name="d0e3196"></a><b>language: </b>Dublin Core (in work)
            </li>
            <li><a name="d0e3202"></a><b>lb: </b>Poetic structure
            </li>
            <li><a name="d0e3208"></a><b>lg: </b>Poetic structure
            </li>
            <li><a name="d0e3214"></a><b>list: </b>List structure
            </li>
            <li><a name="d0e3220"></a><b>mentioned: </b>Annotation
            </li>
            <li><a name="d0e3226"></a><b>milestone: </b>Annotation
            </li>
            <li><a name="d0e3232"></a><b>milestoneEnd: </b>(deprecated -- do not use)
            </li>
            <li><a name="d0e3238"></a><b>milestoneStart: </b>(deprecated -- do not use)
            </li>
            <li><a name="d0e3244"></a><b>name: </b>Main content
            </li>
            <li><a name="d0e3250"></a><b>note: </b>Annotation
            </li>
            <li><a name="d0e3256"></a><b>osis: </b>Header
            </li>
            <li><a name="d0e3262"></a><b>osisCorpus: </b>Header
            </li>
            <li><a name="d0e3268"></a><b>osisText: </b>Header
            </li>
            <li><a name="d0e3274"></a><b>p: </b>Main content
            </li>
            <li><a name="d0e3280"></a><b>publisher: </b>Dublin Core (in work)
            </li>
            <li><a name="d0e3286"></a><b>q: </b>Main content
            </li>
            <li><a name="d0e3292"></a><b>rdg: </b>Annotation
            </li>
            <li><a name="d0e3298"></a><b>reference: </b>Reference system
            </li>
            <li><a name="d0e3304"></a><b>refSystem: </b></li>
            <li><a name="d0e3309"></a><b>relation: </b>Dublin Core (in work)
            </li>
            <li><a name="d0e3315"></a><b>revisionDesc: </b>Header
            </li>
            <li><a name="d0e3321"></a><b>rights: </b>Dublin Core (in work)
            </li>
            <li><a name="d0e3327"></a><b>role: </b>castGroup structure
            </li>
            <li><a name="d0e3333"></a><b>roleDesc: </b>castGroup structure
            </li>
            <li><a name="d0e3339"></a><b>row: </b>table structure
            </li>
            <li><a name="d0e3345"></a><b>salute: </b>Epistolary
            </li>
            <li><a name="d0e3351"></a><b>scope: </b>Dublin Core (in work)
            </li>
            <li><a name="d0e3357"></a><b>seg: </b>Main content
            </li>
            <li><a name="d0e3363"></a><b>signed: </b>Epistolary
            </li>
            <li><a name="d0e3369"></a><b>source: </b>Dublin Core (in work)
            </li>
            <li><a name="d0e3375"></a><b>speaker: </b></li>
            <li><a name="d0e3380"></a><b>speech: </b></li>
            <li><a name="d0e3385"></a><b>subject: </b>Dublin Core (in work)
            </li>
            <li><a name="d0e3391"></a><b>table: </b>table structure
            </li>
            <li><a name="d0e3397"></a><b>teiHeader: </b>Header
            </li>
            <li><a name="d0e3403"></a><b>title: </b>Dublin Core (in work)
            </li>
            <li><a name="d0e3409"></a><b>titlePage: </b>Main Content
            </li>
            <li><a name="d0e3415"></a><b>transChange: </b>Annotation
            </li>
            <li><a name="d0e3421"></a><b>type: </b>Dublin Core (in work)
            </li>
            <li><a name="d0e3427"></a><b>verse: </b>Reference system
            </li>
            <li><a name="d0e3433"></a><b>w: </b>Annotation
            </li>
            <li><a name="d0e3439"></a><b>work: </b>Header
            </li>
         </ul>
         
      </div>
      
      
          
      <div class="teidiv">
         <h2><a name="body.1_div.19"></a>19. Alphabetical list of Attributes and normative values
         </h2>
         
         	
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e3451"></a>19.1. Global attributes
            </h3>
            
            
            <p><a name="d0e3455"></a>
               These global attributes are in addition to xml:base, xml:lang, and
               xml:space which are defined by the XML standard itself.
               
            </p>
            
            <p><a name="d0e3458"></a>
               
               <div align="left">
                  <table>
                     
                     <tr>
                        	
                        <td valign="top" colspan="1">Attribute name</td>
                        	
                        <td valign="top" colspan="1">DataType</td>
                        	
                        <td valign="top" colspan="1">Usage</td>
                        	
                        <td valign="top" colspan="1">Description</td>
                        	
                     </tr>
                     
                     
                     <tr>
                        	
                        <td valign="top" colspan="1">annotateWork</td>
                        	
                        <td valign="top" colspan="1">xs:string</td>
                        	
                        <td valign="top" colspan="1">optional</td>
                        	
                        <td valign="top" colspan="1"></td>
                        	
                     </tr>
                     
                     
                     
                     <tr>
                        	
                        <td valign="top" colspan="1">annotateType</td>
                        	
                        <td valign="top" colspan="1">osisAnnotation</td>
                        	
                        <td valign="top" colspan="1">optional</td>
                        	
                        <td valign="top" colspan="1"></td>
                        	
                     </tr>
                     
                     
                     
                     
                     <tr>
                        	
                        <td valign="top" colspan="1">ID</td>
                        	
                        <td valign="top" colspan="1">xs:ID</td>
                        	
                        <td valign="top" colspan="1">optional</td>
                        	
                        <td valign="top" colspan="1">May be added to any element, generally to make that
                           element accessible as a link target for generic hypertext browsers,
                           or for the OSIS a element.
                        </td>
                        	
                     </tr>
                     
                     
                     <tr>
                        	
                        <td valign="top" colspan="1">osisID</td>
                        	
                        <td valign="top" colspan="1">osisIDType</td>
                        	
                        <td valign="top" colspan="1">optional</td>
                        	
                        <td valign="top" colspan="1">The osisID attribute identifies the element bearing it
                           as a container for actual canonically-referenceable text, and
                           provides the applicable osisID: osisID="Matt.1.1". It must not be
                           used on elements that merely refer to, or discuss, a
                           canonically-referenceable text. For those cases, use the annoteWork
                           and osisRef attributes, instead. See the section on reference systems
                           for details on the form required for this attribute's value.
                        </td>
                        	
                     </tr>
                     
                     
                     <tr>
                        	
                        <td valign="top" colspan="1">canonical</td>
                        	
                        <td valign="top" colspan="1">true | false</td>
                        	
                        <td valign="top" colspan="1">optional</td>
                        	
                        <td valign="top" colspan="1">The canonical attribute identifies the element bearing
                           it as containing actual text of the work being encoded, as opposed to
                           annotations, commentary, inserted headings, header metadata, notes,
                           and other (non-canonical) information. Its value inherits in the same
                           way as xml:lang. That is, the value applies to all descendant
                           elements except where overridden.
                        </td>
                        	
                     </tr>
                     
                     
                     <tr>
                        	
                        <td valign="top" colspan="1">resp</td>
                        	
                        <td valign="top" colspan="1">xs:string</td>
                        	
                        <td valign="top" colspan="1">optional</td>
                        	
                        <td valign="top" colspan="1">This attribute, whose name is short for "responsible
                           party", may be coded on any element to identify the party primarily
                           responsible for that element and its content. For example, it might
                           identify a member of a translation team; or on a note, it might
                           identify the author of the note. Each distinct responsible party must
                           be identified by the same value of this attribute wherever they are
                           identified at all (that is, it is not permitted to use their initials
                           sometimes, their last names other times, etc.). A list of responsible
                           parties should be provided in the front matter or in the
                           header.
                        </td>
                        	
                     </tr>
                     
                     
                     <tr>
                        	
                        <td valign="top" colspan="1">type</td>
                        	
                        <td valign="top" colspan="1">xs:string (several element types restrict the values,
                           as listed below).
                        </td>
                        	
                        <td valign="top" colspan="1">optional</td>
                        	
                        <td valign="top" colspan="1">The type attribute allows encoders to identify more
                           precise distinctions within the borad applicability of any given
                           element. For example, the div (division) element has many subtypes,
                           such as bookGroup, concordance, dedication, glossary, etc. Many other
                           element types also have pre-defined values provided for the type
                           attribute. Some but not all of those element types also permit users
                           to add their own values, so long as they begin with "x-". When a
                           predefined type is applicable, it must be used instead of creating a
                           new type. 
                        </td>
                        	
                     </tr>
                     
                     
                     <tr>
                        	
                        <td valign="top" colspan="1">subType</td>
                        	
                        <td valign="top" colspan="1">xs:string</td>
                        	
                        <td valign="top" colspan="1">optional</td>
                        	
                        <td valign="top" colspan="1">In the rare event that the type attribute does not
                           provide a fine-enough grained distinction of element types, the
                           sub-type attribute may be used to make such distinctions. There are
                           generally no restrictions on the values permitted for subType, except
                           that the encoder should be consistent, and should document the
                           meaning of any values used.
                        </td>
                        	
                     </tr>
                     
                     
                     <tr>
                        	
                        <td valign="top" colspan="1">n</td>
                        	
                        <td valign="top" colspan="1">xs:string</td>
                        	
                        <td valign="top" colspan="1">optional</td>
                        	
                        <td valign="top" colspan="1">This attribute is identical to the TEI n attribute, and
                           may be used to provide a name or number to identify the particular
                           element instance. However, it should not be used to encode a value
                           for which the osisID, osisRef, or ____ attribute is applicable.
                        </td>
                        	
                     </tr>
                     
                     
                     <tr>
                        	
                        <td valign="top" colspan="1">xml:lang</td>
                        	
                        <td valign="top" colspan="1">xs:language</td>
                        	
                        <td valign="top" colspan="1">optional</td>
                        	
                        <td valign="top" colspan="1">This attribute is defined by the XML standard itself,
                           and identifies the primary natural language of the content of an
                           element. The value of this attribute is inherited; that is, any
                           contained elements are presumed to be in the same language, unless
                           they override it by specifying their own explicit <b>xml:lang</b> attribute value. The form of the <b>xml:lang</b> attribute is constrained by Internet
                           specifications, particularly IETF RFC 1766, <strong>Tags for the
                              Identification of Languages.</strong> Such tags consist of a 2-letter
                           language code from ISO 639 (see
                           http://www.oasis-open.org/cover/iso639a.html), optionally followed by
                           a two letter country code from ISO 3166 (see
                           http://www.oasis-open.org/cover/country3166.html). For example, "de"
                           or "en-GB"
                           Alternatively, they may be codes from the IANA registry at
                           http://www.isi.edu/in-notes/iana/assignments/languages/. Remaining
                           languages should use SIL Ethnologue codes (see
                           http://www.ethnologue.com/codes/).
                        </td>
                        	
                     </tr>
                     
                     
                     <tr>
                        	
                        <td valign="top" colspan="1">script</td>
                        	
                        <td valign="top" colspan="1">osisScripts</td>
                        	
                        <td valign="top" colspan="1">optional</td>
                        	
                        <td valign="top" colspan="1">This attribute provides a slight extension beyond the
                           capabilities of the <b>xml:lang</b> attribute. For many
                           languages, it is enough to specify the language itself, and the
                           country where it is spoken (say, Canadian vs. French dialects of the
                           French language). However, there are cases where a given language
                           community may use multiple writing systems: either different
                           character sets and character usage rules; different spelling or other
                           conventions; etc. In such cases, the particular script system used
                           for writing the current work (or element within a work) must be
                           specified via this attribute. This attribute inherits in precisely
                           the same manner as xml:lang.
                        </td>
                        	
                     </tr>
                     
                  </table>
               </div>
               
            </p>
                
         </div>
         
         
             
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e3662"></a>19.2. Normative values for the type attribute, by element
            </h3>
            
            
            <p><a name="d0e3666"></a>
               The heading for each basic element type below, indicates whether the
               list of values provided is extensible (by adding names beginning with
               "x-", or non-extensible).
               
            </p>
            
            
            <p><a name="d0e3669"></a>
               Users who find values potentially of general use, that are not
               already provided, are asked to send them to the editors for possible
               incorporation into future versions of the specification. Likewise,
               users who discover any substantial ambiguity in the values provided,
               are asked to notify us and to provide examples and explanations, so
               that we can attempt to rectify any such problem.
               
            </p>
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e3672"></a>19.2.1. annotation
               </h4>
               
               
               <ul>
                  <li><a name="d0e3678"></a>commentary
                     <p><a name="d0e3681"></a></p>
                  </li>
                  <li><a name="d0e3683"></a>exposition
                     <p><a name="d0e3686"></a></p>
                  </li>
                  <li><a name="d0e3688"></a>meditation
                     <p><a name="d0e3691"></a></p>
                  </li>
                  <li><a name="d0e3693"></a>outline
                     <p><a name="d0e3696"></a></p>
                  </li>
                  <li><a name="d0e3698"></a>poeticRendering
                     <p><a name="d0e3701"></a></p>
                  </li>
                  <li><a name="d0e3705"></a>rebuttal
                     <p><a name="d0e3708"></a></p>
                  </li>
                  <li><a name="d0e3710"></a>sermon
                     <p><a name="d0e3713"></a></p>
                  </li>
                  <li><a name="d0e3715"></a>studyGuide
                     <p><a name="d0e3718"></a></p>
                  </li>
                  <li><a name="d0e3720"></a>translation
                     <p><a name="d0e3723"></a></p>
                  </li>
               </ul>
               
            </div>
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e3727"></a>19.2.2. calendar
               </h4>
               
               
               <ul>
                  <li><a name="d0e3733"></a>Chinese
                     <p><a name="d0e3736"></a></p>
                  </li>
                  <li><a name="d0e3738"></a>Gregorian
                     <p><a name="d0e3741"></a></p>
                  </li>
                  <li><a name="d0e3743"></a>Islamic
                     <p><a name="d0e3746"></a></p>
                  </li>
                  <li><a name="d0e3748"></a>ISO
                     <p><a name="d0e3751"></a></p>
                  </li>
                  <li><a name="d0e3753"></a>Jewish
                     <p><a name="d0e3756"></a></p>
                  </li>
                  <li><a name="d0e3758"></a>Julian
                     <p><a name="d0e3761"></a></p>
                  </li>
               </ul>
               
            </div>
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e3765"></a>19.2.3. milestoneStart and milestoneEnd (deprecated)
               </h4>
               
               
               <p><a name="d0e3769"></a>
                  In OSIS 1.1.1, only one pair of element types was provided for marking
                  up elements that cross others: milestoneStart and milestoneEnd. Each
                  would set its type attribute to the name of the element it was
                  standing in for. The types listed below were the only types permitted
                  to be expressed via milestone pairs. This method, and thus this
                  list, is now obsolete.
                  
               </p>
               
               
               <ul>
                  <li><a name="d0e3774"></a>abbr
                     <p><a name="d0e3777"></a></p>
                  </li>
                  <li><a name="d0e3779"></a>chapter
                     <p><a name="d0e3782"></a></p>
                  </li>
                  <li><a name="d0e3784"></a>closer
                     <p><a name="d0e3787"></a></p>
                  </li>
                  <li><a name="d0e3789"></a>div
                     <p><a name="d0e3792"></a></p>
                  </li>
                  <li><a name="d0e3794"></a>foreign
                     <p><a name="d0e3797"></a></p>
                  </li>
                  <li><a name="d0e3799"></a>l
                     <p><a name="d0e3802"></a></p>
                  </li>
                  <li><a name="d0e3804"></a>lg
                     <p><a name="d0e3807"></a></p>
                  </li>
                  <li><a name="d0e3809"></a>q
                     <p><a name="d0e3812"></a></p>
                  </li>
                  <li><a name="d0e3814"></a>salute
                     <p><a name="d0e3817"></a></p>
                  </li>
                  <li><a name="d0e3819"></a>seg
                     <p><a name="d0e3822"></a></p>
                  </li>
                  <li><a name="d0e3824"></a>signed
                     <p><a name="d0e3827"></a></p>
                  </li>
                  <li><a name="d0e3829"></a>speech
                     <p><a name="d0e3832"></a></p>
                  </li>
                  <li><a name="d0e3834"></a>verse
                     <p><a name="d0e3837"></a></p>
                  </li>
               </ul>
               
            </div>
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e3841"></a>19.2.4. change types
               </h4>
               
               
               <ul>
                  <li><a name="d0e3847"></a>added
                     <p><a name="d0e3850"></a></p>
                  </li>
                  <li><a name="d0e3852"></a>amplified
                     <p><a name="d0e3855"></a></p>
                  </li>
                  <li><a name="d0e3857"></a>changed
                     <p><a name="d0e3860"></a></p>
                  </li>
                  <li><a name="d0e3862"></a>deleted
                     <p><a name="d0e3865"></a></p>
                  </li>
                  <li><a name="d0e3867"></a>moved
                     <p><a name="d0e3870"></a></p>
                  </li>
                  <li><a name="d0e3872"></a>tenseChange
                     <p><a name="d0e3875"></a></p>
                  </li>
               </ul>
               
            </div>
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e3879"></a>19.2.5. div
               </h4>
               
               
               <p><a name="d0e3883"></a>
                  The type attribute for div mainly identifies larger sections that
                  occur in print volumes, especially Bibles. This list was determined
                  in part by examining a large selection of print Bibles, and covers
                  most things that seem to be common. However, the list may be extended
                  if necessary by adding names beginning "x-".
                  
               </p>
               
               
               <ul>
                  <li><a name="d0e3888"></a>acknowledgement
                     <p><a name="d0e3891"></a></p>
                  </li>
                  <li><a name="d0e3893"></a>afterword
                     <p><a name="d0e3896"></a></p>
                  </li>
                  <li><a name="d0e3898"></a>annotant
                     <p><a name="d0e3901"></a></p>
                  </li>
                  <li><a name="d0e3903"></a>appendix
                     <p><a name="d0e3906"></a></p>
                  </li>
                  <li><a name="d0e3908"></a>back
                     <p><a name="d0e3911"></a></p>
                  </li>
                  <li><a name="d0e3913"></a>body
                     <p><a name="d0e3916"></a></p>
                  </li>
                  <li><a name="d0e3918"></a>book
                     <p><a name="d0e3921"></a></p>
                  </li>
                  <li><a name="d0e3923"></a>bookGroup
                     <p><a name="d0e3926"></a></p>
                  </li>
                  <li><a name="d0e3928"></a>chapter
                     <p><a name="d0e3931"></a></p>
                  </li>
                  <li><a name="d0e3933"></a>colophon
                     <p><a name="d0e3936"></a></p>
                  </li>
                  <li><a name="d0e3938"></a>commentary
                     <p><a name="d0e3941"></a></p>
                  </li>
                  <li><a name="d0e3943"></a>concordance
                     <p><a name="d0e3946"></a></p>
                  </li>
                  <li><a name="d0e3948"></a>coverPage
                     <p><a name="d0e3951"></a></p>
                  </li>
                  <li><a name="d0e3953"></a>dedication
                     <p><a name="d0e3956"></a></p>
                  </li>
                  <li><a name="d0e3958"></a>devotional
                     <p><a name="d0e3961"></a></p>
                  </li>
                  <li><a name="d0e3963"></a>entry
                     <p><a name="d0e3966"></a></p>
                  </li>
                  <li><a name="d0e3968"></a>front
                     <p><a name="d0e3971"></a></p>
                  </li>
                  <li><a name="d0e3973"></a>gazetteer
                     <p><a name="d0e3976"></a></p>
                  </li>
                  <li><a name="d0e3978"></a>glossary
                     <p><a name="d0e3981"></a></p>
                  </li>
                  <li><a name="d0e3983"></a>imprimatur
                     <p><a name="d0e3986"></a></p>
                  </li>
                  <li><a name="d0e3988"></a>index
                     <p><a name="d0e3991"></a></p>
                  </li>
                  <li><a name="d0e3993"></a>introduction
                     <p><a name="d0e3996"></a></p>
                  </li>
                  <li><a name="d0e3998"></a>majorSection
                     <p><a name="d0e4001"></a></p>
                  </li>
                  <li><a name="d0e4003"></a>map
                     <p><a name="d0e4006"></a></p>
                  </li>
                  <li><a name="d0e4008"></a>outline
                     <p><a name="d0e4011"></a></p>
                  </li>
                  <li><a name="d0e4013"></a>paragraph
                     <p><a name="d0e4016"></a></p>
                  </li>
                  <li><a name="d0e4018"></a>part
                     <p><a name="d0e4021"></a></p>
                  </li>
                  <li><a name="d0e4023"></a>preface
                     <p><a name="d0e4026"></a></p>
                  </li>
                  <li><a name="d0e4028"></a>section
                     <p><a name="d0e4031"></a></p>
                  </li>
                  <li><a name="d0e4033"></a>subSection
                     <p><a name="d0e4036"></a></p>
                  </li>
                  <li><a name="d0e4038"></a>summary
                     <p><a name="d0e4041"></a></p>
                  </li>
                  <li><a name="d0e4043"></a>titlePage
                     <p><a name="d0e4046"></a></p>
                  </li>
               </ul>
               
            </div>
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e4050"></a>19.2.6. osisMilestonePt
               </h4>
               
               
               <ul>
                  <li><a name="d0e4056"></a>column
                     <p><a name="d0e4059"></a></p>
                  </li>
                  <li><a name="d0e4061"></a>footer
                     <p><a name="d0e4064"></a></p>
                  </li>
                  <li><a name="d0e4066"></a>halfLine
                     <p><a name="d0e4069"></a></p>
                  </li>
                  <li><a name="d0e4071"></a>header
                     <p><a name="d0e4074"></a></p>
                  </li>
                  <li><a name="d0e4076"></a>line
                     <p><a name="d0e4079"></a></p>
                  </li>
                  <li><a name="d0e4081"></a>pb
                     <p><a name="d0e4084"></a></p>
                  </li>
                  <li><a name="d0e4086"></a>screen
                     <p><a name="d0e4089"></a></p>
                  </li>
               </ul>
               
            </div>
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e4093"></a>19.2.7. name
               </h4>
               
               
               <ul>
                  <li><a name="d0e4099"></a>geographic
                     <p><a name="d0e4102"></a></p>
                  </li>
                  <li><a name="d0e4104"></a>holiday
                     <p><a name="d0e4107"></a></p>
                  </li>
                  <li><a name="d0e4109"></a>nonhuman
                     <p><a name="d0e4112"></a></p>
                  </li>
                  <li><a name="d0e4114"></a>person
                     <p><a name="d0e4117"></a></p>
                  </li>
                  <li><a name="d0e4119"></a>ritual
                     <p><a name="d0e4122"></a></p>
                  </li>
               </ul>
               
            </div>
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e4126"></a>19.2.8. notes
               </h4>
               
               
               <ul>
                  <li><a name="d0e4132"></a>allusion
                     <p><a name="d0e4135"></a></p>
                  </li>
                  <li><a name="d0e4137"></a>alternative
                     <p><a name="d0e4140"></a></p>
                  </li>
                  <li><a name="d0e4142"></a>background
                     <p><a name="d0e4145"></a></p>
                  </li>
                  <li><a name="d0e4147"></a>citation
                     <p><a name="d0e4150"></a></p>
                  </li>
                  <li><a name="d0e4152"></a>crossReference
                     <p><a name="d0e4155"></a></p>
                  </li>
                  <li><a name="d0e4157"></a>devotional
                     <p><a name="d0e4160"></a></p>
                  </li>
                  <li><a name="d0e4162"></a>exegesis
                     <p><a name="d0e4165"></a></p>
                  </li>
                  <li><a name="d0e4167"></a>explanation
                     <p><a name="d0e4170"></a></p>
                  </li>
                  <li><a name="d0e4172"></a>study
                     <p><a name="d0e4175"></a></p>
                  </li>
                  <li><a name="d0e4177"></a>translation
                     <p><a name="d0e4180"></a></p>
                  </li>
                  <li><a name="d0e4182"></a>variant
                     <p><a name="d0e4185"></a></p>
                  </li>
               </ul>
               
            </div>
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e4189"></a>19.2.9. titles
               </h4>
               
               
               <ul>
                  <li><a name="d0e4195"></a>acrostic
                     <p><a name="d0e4198"></a></p>
                  </li>
                  <li><a name="d0e4200"></a>continued
                     <p><a name="d0e4203"></a></p>
                  </li>
                  <li><a name="d0e4205"></a>main
                     <p><a name="d0e4208"></a></p>
                  </li>
                  <li><a name="d0e4210"></a>parallel
                     <p><a name="d0e4213"></a></p>
                  </li>
                  <li><a name="d0e4215"></a>psalm
                     <p><a name="d0e4218"></a></p>
                  </li>
                  <li><a name="d0e4220"></a>sub
                     <p><a name="d0e4223"></a></p>
                  </li>
               </ul>
               
               
            </div>
                
         </div>
            
      </div>
      
      <div class="teidiv">
         <h2><a name="body.1_div.20"></a>20. Selected Contributor Roles
         </h2>
         
         <p><a name="d0e4233"></a>This is a selected set of the most common role names likely to be needed for basic encoding. The full set of relator codes
            on which this listing (and the descriptions are based, was taken from: MARC Code List: Relator Codes -- Term Sequence (http://lcweb.loc.gov/marc/relators/re0002r1.html).
            This listing will be followed for later OSIS modules.
         </p>
         
         <ul>
            <li><a name="d0e4238"></a>ann: Annotator: Use for a person who writes manuscript annotations on a printed item.
            </li>
            <li><a name="d0e4243"></a>art: Artist: Use for a person (e.g., a painter) who conceives, and perhaps also implements, an original graphic design or
               work of art.
            </li>
            <li><a name="d0e4248"></a>aut: Author: Use for a person or corporate body chiefly responsiblefor the intellectual or artistic content of a work, usually
               printed text.  This term may also be used when more than one person or body bears such responsibility.
            </li>
            <li><a name="d0e4253"></a>cwt: Commentator for written text: Use for a person or corporate body responsible for the commentary or explanatory notes
               about a text.  For the writer of manuscript annotations in a printed book, use Annotator
            </li>
            <li><a name="d0e4258"></a>com: Compiler: Use for a person who produces a work or publication by selecting and putting together material from the works
               of various persons or bodies.
            </li>
            <li><a name="d0e4263"></a>ctb: Contributor: Use for one whose work has been contributed to a larger work, such as an anthology, serial publication,
               or other compilation of individual works. Do not use for someone whose sole function in relation to a work is as author, editor,
               compiler or translator.
            </li>
            <li><a name="d0e4268"></a>cre: Creator: Use for a person or corporate body responsible for the intellectual or artistic content of a work.
            </li>
            <li><a name="d0e4273"></a>edt: Editor: Use for a person who prepares for publication a work not primarily his/her own, such as by elucidating text,
               adding introductory or other critical matter, or technically directing an editorial staff.
            </li>
            <li><a name="d0e4278"></a>ill: Illustrator: Use for the person who conceives, and perhaps also implements, a design or illustration, usually to accompany
               a written text.
            </li>
            <li><a name="d0e4283"></a>pbl: Publisher
            </li>
            <li><a name="d0e4288"></a>trl: Translator: Use for a person who renders a text from one language into another, or from an older form of a language into
               the modern form.
            </li>
         </ul>
         
      </div>
      
      
      
      
      
      
      
      <div class="teidiv">
         <h2><a name="body.1_div.21"></a>21. Normative Abbreviations for canonical and deutero-canonical books
         </h2>
         
         
         <p><a name="d0e4301"></a>
            These names are taken from the SBL Manual of Style, which also
            provides normative abbreviations for works of classical literature,
            manuscripts, journals, and other information objects of interest to
            Biblical studies.
            
         </p>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e4304"></a>21.1. 
            </h3>
            
            <p><a name="d0e4306"></a>Hebrew Bible/Old Testament
            </p>
            
            
            <ul>
               <li><a name="d0e4311"></a>Gen: 		Genesis
               </li>
               <li><a name="d0e4316"></a>Exod: 		Exodus
               </li>
               <li><a name="d0e4321"></a>Lev: 		Leviticus
               </li>
               <li><a name="d0e4326"></a>Num: 		Numbers
               </li>
               <li><a name="d0e4331"></a>Deut: 		Deuteronomy
               </li>
               <li><a name="d0e4336"></a>Josh: 		Joshua
               </li>
               <li><a name="d0e4341"></a>Judg: 		Judges
               </li>
               <li><a name="d0e4346"></a>Ruth: 		Ruth
               </li>
               <li><a name="d0e4351"></a>1Sam: 		1 Samuel
               </li>
               <li><a name="d0e4356"></a>2Sam: 		2 Samuel
               </li>
               <li><a name="d0e4361"></a>1Kgs: 		1 Kings
               </li>
               <li><a name="d0e4366"></a>2Kgs: 		2 Kings
               </li>
               <li><a name="d0e4371"></a>1Chr: 		1 Chronicles
               </li>
               <li><a name="d0e4376"></a>2Chr: 		2 Chronicles
               </li>
               <li><a name="d0e4381"></a>Ezra: 		Ezra
               </li>
               <li><a name="d0e4386"></a>Neh: 		Nehemiah
               </li>
               <li><a name="d0e4391"></a>Esth: 		Esther
               </li>
               <li><a name="d0e4396"></a>Job: 		Job
               </li>
               <li><a name="d0e4401"></a>Ps: 		Psalms
               </li>
               <li><a name="d0e4406"></a>Prov: 		Proverbs
               </li>
               <li><a name="d0e4411"></a>Eccl: 		Ecclesiastes
               </li>
               <li><a name="d0e4416"></a>Song: 		Song of Solomon
               </li>
               <li><a name="d0e4421"></a>Isa: 		Isaiah
               </li>
               <li><a name="d0e4426"></a>Jer: 		Jeremiah
               </li>
               <li><a name="d0e4431"></a>Lam: 		Lamentations
               </li>
               <li><a name="d0e4436"></a>Ezek: 		Ezekiel
               </li>
               <li><a name="d0e4441"></a>Dan: 		Daniel
               </li>
               <li><a name="d0e4446"></a>Hos: 		Hosea
               </li>
               <li><a name="d0e4451"></a>Joel: 		Joel
               </li>
               <li><a name="d0e4456"></a>Amos: 		Amos
               </li>
               <li><a name="d0e4461"></a>Obad: 		Obadiah
               </li>
               <li><a name="d0e4466"></a>Jonah: 		Jonah
               </li>
               <li><a name="d0e4471"></a>Mic: 		Micah 
               </li>
               <li><a name="d0e4476"></a>Nah: 		Nahum
               </li>
               <li><a name="d0e4481"></a>Hab: 		Habakkuk
               </li>
               <li><a name="d0e4486"></a>Zeph: 		Zephaniah
               </li>
               <li><a name="d0e4491"></a>Hag: 		Haggai
               </li>
               <li><a name="d0e4496"></a>Zech: 		Zechariah
               </li>
               <li><a name="d0e4501"></a>Mal: 		Malachi
               </li>
            </ul>
            
            
            
            <p><a name="d0e4507"></a>New Testament
            </p>
            
            
            <ul>
               <li><a name="d0e4512"></a>Matt: 		Matthew
               </li>
               <li><a name="d0e4517"></a>Mark: 		Mark
               </li>
               <li><a name="d0e4522"></a>Luke: 		Luke
               </li>
               <li><a name="d0e4527"></a>John: 		John
               </li>
               <li><a name="d0e4532"></a>Acts: 		Acts
               </li>
               <li><a name="d0e4537"></a>Rom: 		Romans
               </li>
               <li><a name="d0e4542"></a>1Cor: 		1 Corinthians
               </li>
               <li><a name="d0e4547"></a>2Cor: 		2 Corinthians
               </li>
               <li><a name="d0e4552"></a>Gal: 		Galatians
               </li>
               <li><a name="d0e4557"></a>Eph: 		Ephesians
               </li>
               <li><a name="d0e4562"></a>Phil: 		Philippians
               </li>
               <li><a name="d0e4567"></a>Col: 		Colossians
               </li>
               <li><a name="d0e4572"></a>1Thess: 		1 Thessalonians
               </li>
               <li><a name="d0e4577"></a>2Thess: 		2 Thessalonians
               </li>
               <li><a name="d0e4582"></a>1Tim: 		1 Timothy
               </li>
               <li><a name="d0e4587"></a>2Tim: 		2 Timothy
               </li>
               <li><a name="d0e4592"></a>Titus: 		Titus
               </li>
               <li><a name="d0e4597"></a>Phlm: 		Philemon
               </li>
               <li><a name="d0e4602"></a>Heb: 		Hebrews
               </li>
               <li><a name="d0e4607"></a>Jas: 		James
               </li>
               <li><a name="d0e4612"></a>1Pet: 		1 Peter
               </li>
               <li><a name="d0e4617"></a>2Pet: 		2 Peter
               </li>
               <li><a name="d0e4622"></a>1John: 		1 John
               </li>
               <li><a name="d0e4627"></a>2John: 		2 John
               </li>
               <li><a name="d0e4632"></a>3John: 		3 John
               </li>
               <li><a name="d0e4637"></a>Jude: 		Jude
               </li>
               <li><a name="d0e4642"></a>Rev: 		Revelation
               </li>
            </ul>
            
            
            <p><a name="d0e4648"></a>Apocrypha and Septuagint
            </p>
            
            
            <ul>
               <li><a name="d0e4653"></a>Bar: 		Baruch
               </li>
               <li><a name="d0e4658"></a>AddDan: 		Additions to Daniel
               </li>
               <li><a name="d0e4663"></a>PrAzar: 		Prayer of Azariah
               </li>
               <li><a name="d0e4668"></a>Bel: 		Bel and the Dragon
               </li>
               <li><a name="d0e4673"></a>SgThree: 		Song of the Three Young
                  Men
               </li>
               <li><a name="d0e4678"></a>Sus: 		Susanna
               </li>
               <li><a name="d0e4683"></a>1Esd: 		1 Esdras
               </li>
               <li><a name="d0e4688"></a>2Esd: 		2 Esdras
               </li>
               <li><a name="d0e4693"></a>AddEsth: 		Additions to Esther
               </li>
               <li><a name="d0e4698"></a>EpJer: 		Epistle of Jeremiah
               </li>
               <li><a name="d0e4703"></a>Jdt: 		Judith
               </li>
               <li><a name="d0e4708"></a>1Macc: 		1 Maccabees
               </li>
               <li><a name="d0e4713"></a>2Macc: 		2 Maccabees
               </li>
               <li><a name="d0e4718"></a>3Macc: 		3 Maccabees
               </li>
               <li><a name="d0e4723"></a>4Macc: 		4 Maccabees
               </li>
               <li><a name="d0e4728"></a>PrMan: 		Prayer of Manasseh
               </li>
               <li><a name="d0e4733"></a>Sir: 		Sirach/Ecclesiasticus
               </li>
               <li><a name="d0e4738"></a>Tob: 		Tobit
               </li>
               <li><a name="d0e4743"></a>Wis: 		Wisdom of Solomon
               </li>
            </ul>
            
            
            <p><a name="d0e4749"></a>These abbreviations are as defined in the <i>SBL
                  Handbook of Style</i> published by the Society of Biblical
               Literature, except that spaces have been removed from the
               abbreviations for some Apocryphal and Septuagint books.
            </p>
            
            
            <p><a name="d0e4755"></a>Note that because XML prohibits digits as the first character of
               IDs and other XML names, these abbreviations cannot be used directly
               as XML IDs, and are not of that schema datatype.
            </p>
            
         </div>
         
         
      </div>
      
      
      
      
      
          
      <div class="teidiv">
         <h2><a name="body.1_div.22"></a>22. Encoding commentaries
         </h2>
         
              
         <p><a name="d0e4766"></a>(this section is still to be written)
         </p>
         
             
      </div>
      
      
      
      
      
      
          
      <div class="teidiv">
         <h2><a name="body.1_div.23"></a>23. Encoding devotionals, lectionaries, and time-organized documents
         </h2>
         
              
         <p><a name="d0e4776"></a>Information that is organized by time, must mark those
            organizational units using the appropriate <b>div</b> or
            other elements; the applicable time goes on the <b>osisID</b> attribute. 
         </p>
         
             
      </div>
      
      
      
          
      <div class="teidiv">
         <h2><a name="body.1_div.24"></a>24. Encoding multilingual editions
         </h2>
         
              
         <p><a name="d0e4792"></a>(this section is still to be written)
         </p>
         
             
      </div>
      
      
      
      
      
      
          
      <div class="teidiv">
         <h2><a name="body.1_div.25"></a>25. Encoding glossaries, dictionaries, and lexica
         </h2>
         
              
         <p><a name="d0e4802"></a>A set of dictionary markup elements, drawn directly from the
            TEI, is currently in preparation, and is expected to be added in the
            next release of OSIS, as an optional add-on module. The main entry
            terms will be used as the osisID values.
         </p>
         
             
      </div>
      
      
      
      
      
      
      <div class="teidiv">
         <h2><a name="body.1_div.26"></a>26. Standard OSIS Codes for Bible Editions
         </h2>
         
         
         <p><a name="d0e4812"></a>All Bible Edition codes must have the language code for the target
            language in question, then a colon, then the abbreviation shown
            here.
         </p>
         
         
         <div class="teidiv">
            <h3><a name="osisUserManual_06-div-d0e4815"></a>26.1. Ancient language editions
            </h3>
            
            
            
            <ul>
               <li><a name="d0e4821"></a><b>Steph: </b>		Stephanus GNT, 1551
               </li>
               <li><a name="d0e4827"></a><b>Vul: </b>		Latin Vulgate, 1405
               </li>
               <li><a name="d0e4833"></a><b>Erasmus: </b>		Latin translation by
                  Desiderius Erasmus Roterodamus, 1516
               </li>
               <li><a name="d0e4839"></a><b>Mas: </b>		Masoretic text (various,
                  ~900-1100)
               </li>
               <li><a name="d0e4845"></a><b>BHS: </b>		Biblia Hebraica
                  Stuttgartsiensa
               </li>
               <li><a name="d0e4851"></a><b>NA: </b>		Nestle-Aland Greek New Testament
                  (may suffix edition number, such as "NA27")
               </li>
               <li><a name="d0e4857"></a><b>LXX: </b>		Greek Septuagint
               </li>
            </ul>
            
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e4864"></a>26.1.1. English Editions (prefix "en:")
               </h4>
               
               
               
               <ul>
                  <li><a name="d0e4872"></a><b>AAT: </b>		The Complete Bible: An
                     American Translation, by Edgar Goodspeed and J. M. Powis Smith,
                     1939.
                  </li>
                  <li><a name="d0e4878"></a><b>ABT: </b>		The Afro Bible
                     Translation
                  </li>
                  <li><a name="d0e4884"></a><b>ATB: </b>		The Alternate Translation
                     Bible
                  </li>
                  <li><a name="d0e4890"></a><b>ASV: </b>		American Standard Version
                  </li>
                  <li><a name="d0e4896"></a><b>AB: </b>			The Amplified Bible
                  </li>
                  <li><a name="d0e4902"></a><b>ALT: </b>		Analytical-Literal
                     Translation
                  </li>
                  <li><a name="d0e4908"></a><b>ASL: </b>		American Sign Language
                     Translation
                  </li>
                  <li><a name="d0e4914"></a><b>AV: </b>			Authorized Version (same
                     as KJV)
                  </li>
                  <li><a name="d0e4920"></a><b>Bar: </b>		The New Testament: A New
                     Translation, by William Barclay
                  </li>
                  <li><a name="d0e4926"></a><b>BB: </b>			The Biker Bible
                  </li>
                  <li><a name="d0e4932"></a><b>BWE: </b>		Bible in WorldWide
                     English
                  </li>
                  <li><a name="d0e4938"></a><b>CCB: </b>		Christian Community Bible
                  </li>
                  <li><a name="d0e4944"></a><b>COM: </b>		The Common Edition: New
                     Testament
                  </li>
                  <li><a name="d0e4950"></a><b>COV: </b>		Covenant Edition New
                     Testament
                  </li>
                  <li><a name="d0e4956"></a><b>CJB: </b>		Complete Jewish Bible
                  </li>
                  <li><a name="d0e4962"></a><b>CONC: </b>		Concordant Version
                  </li>
                  <li><a name="d0e4968"></a><b>CEV: </b>		Contemporary English
                     Version
                  </li>
                  <li><a name="d0e4974"></a><b>CPV: </b>		Cotton Patch Version, tr.
                     Clarence Jordan
                  </li>
                  <li><a name="d0e4980"></a><b>Dar: </b>		Darby
                  </li>
                  <li><a name="d0e4986"></a><b>DR: </b>			Douay-Rheims
                  </li>
                  <li><a name="d0e4992"></a><b>DRP: </b>		David Robert Palmer's
                     translations of the gospels
                  </li>
                  <li><a name="d0e4998"></a><b>EMTV: </b>		English Majority Text
                     Version
                  </li>
                  <li><a name="d0e5004"></a><b>ENT: </b>		Extreme New Testament
                  </li>
                  <li><a name="d0e5010"></a><b>ERV: </b>		Easy-to-Read Version
                  </li>
                  <li><a name="d0e5016"></a><b>ESV: </b>		English Standard Version
                  </li>
                  <li><a name="d0e5022"></a><b>FF: </b>			Ferrar Fenton Bible
                  </li>
                  <li><a name="d0e5028"></a><b>GLW: </b>		God's Living Word
                  </li>
                  <li><a name="d0e5034"></a><b>GNC: </b>		God's New Covenant: A New
                     Testament Translation, by Heinz W. Cassirer 
                  </li>
                  <li><a name="d0e5040"></a><b>GW: </b>			God's Word
                  </li>
                  <li><a name="d0e5046"></a><b>GNB: </b>		Good News Bible (TEV)
                  </li>
                  <li><a name="d0e5052"></a><b>HCSB: </b>		Holman Christian Standard
                     Bible
                  </li>
                  <li><a name="d0e5058"></a><b>ICB: </b>		International Children's
                     Bible  (children's version of the NCV)
                  </li>
                  <li><a name="d0e5064"></a><b>ISB: </b>		International Standard
                     Bible (formerly titled The Simple English Bible)
                  </li>
                  <li><a name="d0e5070"></a><b>ISV: </b>		The International Standard
                     Version
                  </li>
                  <li><a name="d0e5076"></a><b>JBP: </b>		New Testament in Modern
                     English, by J.B. Phillips
                  </li>
                  <li><a name="d0e5082"></a><b>JNT: </b>		Jewish New Testament: A
                     Translation of the New Testament That Expresses Its
                     Jewishness
                  </li>
                  <li><a name="d0e5088"></a><b>KJV: </b>		King James Version
                  </li>
                  <li><a name="d0e5094"></a><b>DKJB: </b>		Defined King James Bible
                  </li>
                  <li><a name="d0e5100"></a><b>KJII: </b>		King James Version II
                     (renamed to Literal Translation of the Holy Bible)
                  </li>
                  <li><a name="d0e5106"></a><b>KJ21: </b>		King James for the 21st
                     Century
                  </li>
                  <li><a name="d0e5112"></a><b>KJ2000: </b>		King James 2000
                  </li>
                  <li><a name="d0e5118"></a><b>LITV: </b>		The Literal Translation of
                     the Holy Bible (formerly named King James II)
                  </li>
                  <li><a name="d0e5124"></a><b>MKJV: </b>		Modern King James Version
                  </li>
                  <li><a name="d0e5130"></a><b>RAV: </b>		Revised Authorised Version
                     (British edition of the NKJV)
                  </li>
                  <li><a name="d0e5136"></a><b>RKJV: </b>		Revised King James New
                     Testament
                  </li>
                  <li><a name="d0e5142"></a><b>TMB: </b>		The Third Millennium
                     Bible
                  </li>
                  <li><a name="d0e5148"></a><b>UKJV: </b>		Updated King James
                     Version
                  </li>
                  <li><a name="d0e5154"></a><b>LB: </b>			Living Bible
                  </li>
                  <li><a name="d0e5160"></a><b>MAEV: </b>		Modern American English
                     Vernacular
                  </li>
                  <li><a name="d0e5166"></a><b>MLB: </b>		Modern Language Bible: New
                     Berkeley Version
                  </li>
                  <li><a name="d0e5172"></a><b>Mof: </b>		Bible: James Moffatt
                     Translation
                  </li>
                  <li><a name="d0e5178"></a><b>NAB: </b>		New American Bible
                  </li>
                  <li><a name="d0e5184"></a><b>NASB: </b>		New American Standard
                     Bible
                  </li>
                  <li><a name="d0e5190"></a><b>MLB: </b>		New Berkeley Version (see
                     Modern Language Bible)
                  </li>
                  <li><a name="d0e5196"></a><b>NCV: </b>		New Century Version
                  </li>
                  <li><a name="d0e5202"></a><b>NEB: </b>		New English Bible
                  </li>
                  <li><a name="d0e5208"></a><b>NET: </b>		New English Translation
                  </li>
                  <li><a name="d0e5214"></a><b>NEvT: </b>		New Evangelical
                     Translation
                  </li>
                  <li><a name="d0e5220"></a><b>NIrV: </b>		New Internation Reader's
                     Version
                  </li>
                  <li><a name="d0e5226"></a><b>NIV: </b>		New International Version
                  </li>
                  <li><a name="d0e5232"></a><b>NJB: </b>		New Jerusalem Bible
                  </li>
                  <li><a name="d0e5238"></a><b>NKJV: </b>		New King James Version
                  </li>
                  <li><a name="d0e5244"></a><b>NLV: </b>		New Life Version
                  </li>
                  <li><a name="d0e5250"></a><b>NLT: </b>		New Living Translation
                  </li>
                  <li><a name="d0e5256"></a><b>NRSV: </b>		New Revised Standard
                     Bible
                  </li>
                  <li><a name="d0e5262"></a><b>NWT: </b>		New World Translation
                     (published by the Watchtower Bible and Tract Society of the Jehovah's
                     Witnesses)
                  </li>
                  <li><a name="d0e5268"></a><b>OBP: </b>		The Original Bible
                     Project
                  </li>
                  <li><a name="d0e5274"></a><b>OSB: </b>		Orthodox Study Bible
                  </li>
                  <li><a name="d0e5280"></a><b>ONT: </b>		The Original New
                     Testament: The First Definitive Translation of the New Testament in
                     2000 Years, by Hugh Schonfield
                  </li>
                  <li><a name="d0e5286"></a><b>PMB: </b>		Postmodern Bible - Amos
                  </li>
                  <li><a name="d0e5292"></a><b>Rec: </b>		Recovery Version
                  </li>
                  <li><a name="d0e5298"></a><b>REB: </b>		The Revised English Bible
                     (revision of NEB)
                  </li>
                  <li><a name="d0e5304"></a><b>RSV: </b>		Revised Standard Version
                  </li>
                  <li><a name="d0e5310"></a><b>RV: </b>			Revised Version, 1885
                  </li>
                  <li><a name="d0e5316"></a><b>Sch: </b>		The Schocken Bible
                  </li>
                  <li><a name="d0e5322"></a><b>SEB: </b>		The Simple English Bible
                  </li>
                  <li><a name="d0e5328"></a><b>TM: </b>			The Message
                  </li>
                  <li><a name="d0e5334"></a><b>TMB: </b>		The Third Millennium
                     Bible
                  </li>
                  <li><a name="d0e5340"></a><b>TEV: </b>		Today's English Version
                  </li>
                  <li><a name="d0e5346"></a><b>TNIV: </b>		Today's New International
                     Version
                  </li>
                  <li><a name="d0e5352"></a><b>Tyn: </b>		Tyndale
                  </li>
                  <li><a name="d0e5358"></a><b>Wey: </b>		Weymouth
                  </li>
                  <li><a name="d0e5364"></a><b>WEB: </b>		World English Bible
                  </li>
                  <li><a name="d0e5370"></a><b>Wms: </b>		The New Testament in the
                     Language of the People, by Charles B. Williams)
                  </li>
                  <li><a name="d0e5376"></a><b>WNT: </b>		Wesley's New Testament
                  </li>
                  <li><a name="d0e5382"></a><b>Wuest: </b>		The New Testament (An
                     Expanded Translation)
                  </li>
                  <li><a name="d0e5388"></a><b>Wyc: </b>		Wycliffe
                  </li>
                  <li><a name="d0e5394"></a><b>Yes: </b>		Yes Word (update of
                     Tyndale translation)
                  </li>
                  <li><a name="d0e5400"></a><b>YLT: </b>		Young's Literal
                     Translation of the Bible
                  </li>
               </ul>
               
            </div>
            
            
            <div class="teidiv">
               <h4><a name="osisUserManual_06-div-d0e5408"></a>26.1.2. Non-English Modern Languages
               </h4>
               
               
               
               <p><a name="d0e5413"></a>Thousands of additional languages have Bibles or portions; most of
                  these have only one translation in the language. In those cases the
                  language code as defined elsewhere in OSIS may be used, with no
                  following name required.
               </p>
               
               
               <ul>
                  <li><a name="d0e5418"></a><b>Luther: </b>		German by Martin Luther,
                     1534
                  </li>
                  <li><a name="d0e5424"></a><b>Algonquin: </b>		Tr. John Eliot, 1662
                  </li>
                  <li><a name="d0e5430"></a><b>ReinaV: </b>		Spanish Reina Valera
                  </li>
               </ul>
               
            </div>
            
            
         </div>
         
            
      </div>
      
      
      
      <div class="teidiv">
         <h2><a name="body.1_div.27"></a>27. Complete list of USMARC Relator Codes
         </h2>
         
         
         <ul>
            <li><a name="d0e5448"></a><b>Actor   [act] : </b>Use for a person who
               principally exhibits acting skills in a musical or dramatic
               presentation or entertainment.
            </li>
            <li><a name="d0e5454"></a><b>Adapter   [adp] : </b>Use for a person who 1)
               reworks a musical composition, usually for a different medium, or 2)
               rewrites novels or stories for motion pictures or other audiovisual
               medium.
            </li>
            <li><a name="d0e5460"></a><b>Annotator   [ann] : </b>Use for a person who writes
               manuscript annotations on a printed item.
            </li>
            <li><a name="d0e5466"></a><b>Architect   [arc]: </b></li>
            <li><a name="d0e5471"></a><b>Applicant   [app]: </b></li>
            <li><a name="d0e5476"></a><b>Appraiser : </b>USE Expert
            </li>
            <li><a name="d0e5482"></a><b>Arranger   [arr] : </b>Use for a person who
               transcribes a musical composition, usually for a different medium
               from that of the original; in an arrangement the musical substance
               remains essentially unchanged.
            </li>
            <li><a name="d0e5488"></a><b>Artist   [art] : </b>Use for a person (e.g., a
               painter) who conceives, and perhaps also implements, an original
               graphic design or work of art, if specific codes (e.g., [egr], [etr])
               are not desired.  For book illustrators, prefer Illustrator [ill].
               (UF Graphic technician)
            </li>
            <li><a name="d0e5494"></a><b>Assignee   [asg] : </b>Use for a person or
               organization to whom a license for printing or publishing has been
               transferred.
            </li>
            <li><a name="d0e5500"></a><b>Associated name   [asn] : </b>Use as a general
               relator for a name associated with or found in an item or collection,
               or which cannot be determined to be that of a Former owner [fmo] or
               other designated relator indicative of provenance.
            </li>
            <li><a name="d0e5506"></a><b>Attributed name   [att] : </b>Use to relate an
               author, artist, etc. to a work for which there is or once was
               substantial authority for designating that person as author, creator,
               etc. of the work. (UF  Supposed name)
            </li>
            <li><a name="d0e5512"></a><b>Auctioneer   [auc] : </b>Use for a person or
               corporate body in change or the estimation and public auctioning of
               goods, particularly books, artistic works, etc.
            </li>
            <li><a name="d0e5518"></a><b>Author   [aut] : </b>Use for a person or corporate
               body chiefly responsible for the intellectual or artistic content of
               a work.  This term may also be used when more than one person or body
               bears such responsibility. (UF  Joint author)
            </li>
            <li><a name="d0e5524"></a><b>Author in quotations or text extracts [aqt]
                  : </b>Use for a person whose work is largely quoted or extracted
               in a works to which he or she di not contribute directly.  Such
               quotations are found particularly in exhibition catalogs, collections
               of photographs, etc.
            </li>
            <li><a name="d0e5530"></a><b>Author of afterword, colophon, etc. [aft] : </b>Use
               for a person or corporate body responsible for an afterword,
               postface, colophon, etc. but who is not the but who is not the chief
               author of a work.
            </li>
            <li><a name="d0e5536"></a><b>Author of introduction, etc. [aui] : </b>Use for a
               person or corporate body responsible for an introduction, preface,
               foreword, afterword, or other critical matter, but who is not the
               chief author.
            </li>
            <li><a name="d0e5542"></a><b>Author of screenplay, etc.   [aus] : </b>Use for a
               person or corporate body responsible for a motion picture screenplay,
               dialog, spoken commentary, etc.
            </li>
            <li><a name="d0e5548"></a><b>Bibliographic antecedent   [ant] : </b>Use for the
               author responsible for a work upon which the work represented by the
               catalog record is based.  This may be appropriate for adaptations,
               sequels, continuations, indexes, etc.
            </li>
            <li><a name="d0e5554"></a><b>Binder   [bnd]: </b></li>
            <li><a name="d0e5559"></a><b>Binding designer   [bdd] : </b> (UF Designer of
               binding)
            </li>
            <li><a name="d0e5565"></a><b>Book designer   [bkd] : </b>Use for the person or
               firm responsible for the entire graphic design of a book, including
               arrangement of type and illustration, choice of materials, and
               process used. (UF Designer of book)
            </li>
            <li><a name="d0e5571"></a><b>Book producer   [bkp] : </b>Use for the person or
               firm responsible for the production of books and other print media,
               if specific codes (e.g., [bkd], [egr], [tyd], [prt]) are not desired.
               (UF  Producer of book)
            </li>
            <li><a name="d0e5577"></a><b>Bookjacket designer  [bjd] : </b> (UF Designer of
               bookjacket)
            </li>
            <li><a name="d0e5583"></a><b>Bookplate designer   [bpd] : </b> (UF Designer of
               bookplate)
            </li>
            <li><a name="d0e5589"></a><b>Bookseller   [bsl]: </b></li>
            <li><a name="d0e5594"></a><b>Bowdlerizer : </b>USE Censor
            </li>
            <li><a name="d0e5600"></a><b>Calligrapher   [cll]: </b></li>
            <li><a name="d0e5605"></a><b>Cartographer   [ctg]: </b></li>
            <li><a name="d0e5610"></a><b>Censor   [cns] : </b>Use for a censor, bowdlerizer,
               expurgator, etc., official or private. (UF Bowdlerizer,
               Expurgator)
            </li>
            <li><a name="d0e5616"></a><b>Choreographer   [chr] : </b>Use for a person who
               composes or arranges dances or other movements (e.g., "master of
               swords") for a musical or dramatic presentation or
               entertainment.
            </li>
            <li><a name="d0e5622"></a><b>Client   [cli] : </b>Use for a person or
               organization for whom another person or organization is
               acting.
            </li>
            <li><a name="d0e5628"></a><b>Collaborator   [clb] : </b>Use for a person or
               corporate body that takes a limited part in the elaboration of a work
               of another author or that brings complements (e.g., appendices,
               notes) to the work of another author
            </li>
            <li><a name="d0e5634"></a><b>Collector   [col] : </b>Use for a person who has
               brought together material from various sources, which has been
               arranged, described, and cataloged as a collection.  The collector is
               neither the creator of the material nor the person to whom
               manuscripts in the collection may have been addressed.
            </li>
            <li><a name="d0e5640"></a><b>Collotyper   [clt]: </b></li>
            <li><a name="d0e5645"></a><b>Commentator   [cmm] : </b>Use for a person who
               provides interpretation, analysis, or a discussion of the subject
               matter on a recording, motion picture, or other audiovisual
               medium.
            </li>
            <li><a name="d0e5651"></a><b>Compiler   [com] : </b>Use for a person who
               produces a work or publication by selecting and putting together
               material from the works of various persons or bodies.
            </li>
            <li><a name="d0e5657"></a><b>Complainant   [cpl] : </b>Use for the party who
               applies to the courts for redress, usually in an equity
               proceeding.
            </li>
            <li><a name="d0e5663"></a><b>Complainant-appellant   [cpt] : </b>Use for a
               complainant who takes an appeal from one court or jurisdiction to
               another to reverse the judgment, usually in an equity
               proceeding.
            </li>
            <li><a name="d0e5669"></a><b>Complainant-appellee   [cpe] : </b>Use for a
               complainant against whom an appeal is taken from one court or
               jurisdiction to another to reverse the judgment, usually in an equity
               proceeding.
            </li>
            <li><a name="d0e5675"></a><b>Composer   [cmp] : </b>Use for a person who creates
               a musical work, usually a piece of music in manuscript or printed
               form.
            </li>
            <li><a name="d0e5681"></a><b>Compositor   [cmt] : </b> (UF Typesetter)
            </li>
            <li><a name="d0e5687"></a><b>Conceptor   [ccp] : </b>Use for a person or
               corporate body responsible for the original idea on which a work is
               based, this includes the scientific author of an audio-visual item
               and the conceptor of an advertisement.
            </li>
            <li><a name="d0e5693"></a><b>Conductor   [cnd] : </b>Use for a person who
               directs a performing group (orchestra, chorus, opera,
               etc.).
            </li>
            <li><a name="d0e5699"></a><b>Consultant [csl] : </b>Use for the person called
               upon for professional advice or services in a specialized field of
               knowledge or training.
            </li>
            <li><a name="d0e5705"></a><b>Contestant   [cos] : </b>Use for the party who
               opposes, resists, or disputes, in a court of law, a claim, decision,
               result, etc.
            </li>
            <li><a name="d0e5711"></a><b>Contestant-appellant   [cot] : </b>Use for a
               contestant who takes an appeal from one court of law or jurisdiction
               to another to reverse the judgment.
            </li>
            <li><a name="d0e5717"></a><b>Contestant-appellee   [coe] : </b>Use for a
               contestant against whom an appeal is taken from one court of law or
               jurisdiction to another to reverse the judgment.
            </li>
            <li><a name="d0e5723"></a><b>Contestee   [cts] : </b>Use for the party defending
               a claim, decision, result, etc. being opposed, resisted, or disputed
               in a court of law.
            </li>
            <li><a name="d0e5729"></a><b>Contestee-appellant   [ctt] : </b>Use for a
               contestee who takes an appeal from one court or jurisdiction to
               another to reverse the judgment.
            </li>
            <li><a name="d0e5735"></a><b>Contestee-appellee   [cte] : </b>Use for a
               contestee against whom an appeal is taken from one court or
               jurisdiction to another to reverse the judgment.
            </li>
            <li><a name="d0e5741"></a><b>Contractor   [ctr] : </b>Use for the person or
               corporate body who enters into a contract with another person or
               corporate body to perform a specific task.
            </li>
            <li><a name="d0e5747"></a><b>Copyright claimant  [cpc] : </b>Use for the person
               listed as as copyright owner at the time of registration.  Copyright
               can be granted or later transfered to another person or agent, at
               which time the claimant becomes the copyright holder.
            </li>
            <li><a name="d0e5753"></a><b>Copyright holder [cph]: </b></li>
            <li><a name="d0e5758"></a><b>Corrector   [crr] : </b>Use for a corrector of
               manuscripts, such as the scriptorium official who corrected the work
               of a scribe.  For printed matter, use Proofreader [pfr].
            </li>
            <li><a name="d0e5764"></a><b>Correspondent   [crp] : </b>Use for a person or
               organization who was either the writer or recipient of a letter or
               other communication.
            </li>
            <li><a name="d0e5770"></a><b>Costume designer  [cst] : </b>Use for a person who
               designs or makes costumes, fixes hair, etc., for a musical or
               dramatic presentation or entertainment.
            </li>
            <li><a name="d0e5776"></a><b>Counterfeiter : </b>USE Forger
            </li>
            <li><a name="d0e5782"></a><b>Curator of an exhibition  [cur] : </b>Use for a
               person who is responsible for conceiving and organizing an
               exhibition.
            </li>
            <li><a name="d0e5788"></a><b>Dancer   [dnc] : </b>Use for a person who
               principally exhibits dancing skills in a musical or dramatic
               presentation or entertainment.
            </li>
            <li><a name="d0e5794"></a><b>Dedicatee   [dte] : </b>Use for a person or
               organization to whom a book, manuscript, etc., is dedicated (not the
               recipient of a gift).
            </li>
            <li><a name="d0e5800"></a><b>Dedicator   [dto] : </b>Use for the author of a
               dedication, which may be a formal statement or in epistolary or verse
               form.
            </li>
            <li><a name="d0e5806"></a><b>Defendant   [dfd] : </b>Use for the party defending
               or denying allegations made in a suit and against whom relief or
               recovery is sought in the courts, usually in a legal
               action.
            </li>
            <li><a name="d0e5812"></a><b>Defendant-appellant   [dft] : </b>Use for a
               defendant who takes an appeal from one court or jurisdiction to
               another to reverse the judgment, usually in a legal action.
            </li>
            <li><a name="d0e5818"></a><b>Defendant-appellee   [dfe] : </b>Use for a
               defendant against whom an appeal is taken from one court or
               jurisdiction to another to reverse the judgment, usually in a legal
               action.
            </li>
            <li><a name="d0e5824"></a><b>Delineator   [dln] : </b>Use for a person or
               organization executing technical drawings from others'
               designs.
            </li>
            <li><a name="d0e5830"></a><b>Depositor   [dpt] : </b>Use for a person or
               organization placing material in the physical custody of a library or
               repository without transferring the legal title.
            </li>
            <li><a name="d0e5836"></a><b>Designer   [dsr] : </b>Use for a person or
               organization responsible for design if specific codes (e.g., [bkd],
               [tyd]) are not desired.
            </li>
            <li><a name="d0e5842"></a><b>Designer of binding : </b>USE Binding designer 
            </li>
            <li><a name="d0e5848"></a><b>Designer of book : </b>USE Book designer 
            </li>
            <li><a name="d0e5854"></a><b>Designer of bookjacket : </b>USE  Bookjacket
               designer 
            </li>
            <li><a name="d0e5860"></a><b>Designer of bookplate : </b>USE Bookplate designer
               
            </li>
            <li><a name="d0e5866"></a><b>Designer of type : </b>USE  Type designer 
            </li>
            <li><a name="d0e5872"></a><b>Director   [drt] : </b>Use for a person who is
               responsible for the general management of a work or who supervises
               the production of a performance for stage, screen, or sound
               recording.
            </li>
            <li><a name="d0e5878"></a><b>Dissertant   [dis] : </b>Use for a person who
               presents a thesis for a university or higher-level educational
               degree.
            </li>
            <li><a name="d0e5884"></a><b>Distributor   [dst] : </b>Use for an agent or
               agency that has exclusive or shared marketing rights for an
               item.
            </li>
            <li><a name="d0e5890"></a><b>Donor   [dnr] : </b>Use for the donor of a book,
               manuscript, etc., to its present owner.  Donors to  previous owners
               are designated as Former owner [fmo] or Inscriber [ins].
            </li>
            <li><a name="d0e5896"></a><b>Draftsman  [drm] : </b>Use for the person who
               prepares technical or mechanical drawings. (UF Technical
               draftsman)
            </li>
            <li><a name="d0e5902"></a><b>Dubious author   [dub] : </b>Use for a person or
               corporate body to which authorship has been dubiously or incorrectly
               ascribed.
            </li>
            <li><a name="d0e5908"></a><b>Editor   [edt] : </b>Use for a person who prepares
               for publication a work not primarily his/her own, such as by
               elucidating text, adding introductory or other critical matter, or
               technically directing an editorial staff.
            </li>
            <li><a name="d0e5914"></a><b>Electrotyper   [elt]: </b></li>
            <li><a name="d0e5919"></a><b>Engineer   [eng] : </b>Use for a person or
               organization that is responsible for technical planning and design,
               particularly with construction.
            </li>
            <li><a name="d0e5925"></a><b>Engraver   [egr]: </b></li>
            <li><a name="d0e5930"></a><b>Etcher   [etr]: </b></li>
            <li><a name="d0e5935"></a><b>Expert   [exp] : </b>Use for a person in charge of
               the description and appraisal of the value of goods, particularly
               rare items, works of art, etc. (UF Appraiser)
            </li>
            <li><a name="d0e5941"></a><b>Expurgator : </b>USE Censor
            </li>
            <li><a name="d0e5947"></a><b>Film editor   [flm] : </b>Use for an editor of a
               motion picture film. This term is used regardless of the medium upon
               which the motion picture is produced or manufactured (e.g., acetate
               film, video tape). (UF Motion picture editor)
            </li>
            <li><a name="d0e5953"></a><b>Forger   [frg] : </b> (UF Counterfeiter)
            </li>
            <li><a name="d0e5959"></a><b>Former owner   [fmo] : </b>Use for the person or
               organization who owned an item at any time in the past.  Includes
               those to whom the material was once presented. The person or
               organization giving the item to the present owner is designated as
               Donor [dnr]
            </li>
            <li><a name="d0e5965"></a><b>Funder   [fnd] : </b>Use for the person or agency
               that furnished financial support for the production of the
               work.
            </li>
            <li><a name="d0e5971"></a><b>Graphic technician : </b>USE Artist
            </li>
            <li><a name="d0e5977"></a><b>Honoree   [hnr] : </b>Use for the person in memory
               or honor of whom a book, manuscript, etc. is donated. (UF
               Memorial)
            </li>
            <li><a name="d0e5983"></a><b>Host   [hst] : </b>Use for the person who is
               invited or regularly leads a program (often broadcast) that includes
               other guests, performers, etc. (e.g., talk show host).
            </li>
            <li><a name="d0e5989"></a><b>Illuminator   [ilu]: </b></li>
            <li><a name="d0e5994"></a><b>Illustrator   [ill] : </b>Use for the person who
               conceives, and perhaps also implements, a design or illustration,
               usually to accompany a written text.
            </li>
            <li><a name="d0e6000"></a><b>Imprimatur : </b>USE Licensor
            </li>
            <li><a name="d0e6006"></a><b>Inscriber   [ins] : </b>Use for the person who
               signs a presentation statement.
            </li>
            <li><a name="d0e6012"></a><b>Instrumentalist   [itr] : </b>Use for a person who
               principally plays an instrument in a musical or dramatic presentation
               or entertainment.
            </li>
            <li><a name="d0e6018"></a><b>Interviewee   [ive]: </b></li>
            <li><a name="d0e6023"></a><b>Interviewer   [ivr]: </b></li>
            <li><a name="d0e6028"></a><b>Inventor   [inv]: </b></li>
            <li><a name="d0e6033"></a><b>Investigator : </b>USE Originator
            </li>
            <li><a name="d0e6039"></a><b>Joint author : </b>USE Author
            </li>
            <li><a name="d0e6045"></a><b>Landscape architect  [lsa] : </b>Use for the person
               or organization whose work involves coordinating the arrangement of
               existing and proposed land features and structures.
            </li>
            <li><a name="d0e6051"></a><b>Lender   [len] : </b>Use for a person or
               organization permitting the temporary use of a book, manuscript,
               etc., such as for photocopying or microfilming.
            </li>
            <li><a name="d0e6057"></a><b>Libelant   [lil] : </b>Use for the party who files
               a libel in an ecclesiastical or admiralty case.
            </li>
            <li><a name="d0e6063"></a><b>Libelant-appellant   [lit] : </b>Use for a libelant
               who takes an appeal from one ecclesiastical court or admiralty to
               another to reverse the judgment.
            </li>
            <li><a name="d0e6069"></a><b>Libelant-appellee   [lie] : </b>Use for a libelant
               against whom an appeal is taken from one ecclesiastical court or
               admiralty to another to reverse the judgment.
            </li>
            <li><a name="d0e6075"></a><b>Libelee   [lel] : </b>Use for the party against
               whom a libel has been filed in an ecclesiastical court or
               admiralty.
            </li>
            <li><a name="d0e6081"></a><b>Libelee-appellant   [let] : </b>Use for a libelee
               who takes an appeal from one ecclesiastical court or admiralty to
               another to reverse the judgment.
            </li>
            <li><a name="d0e6087"></a><b>Libelee-appellee   [lee] : </b>Use for a libelee
               against whom an appeal is taken from one ecclesiastical court or
               admiralty to another to reverse the judgment.
            </li>
            <li><a name="d0e6093"></a><b>Librettist   [lbt] : </b>Use for the writer of the
               text of an opera, oratorio, etc.
            </li>
            <li><a name="d0e6099"></a><b>Licensee   [lse] : </b>Use for the original
               recipient of the right to print or publish.
            </li>
            <li><a name="d0e6105"></a><b>Licensor   [lso] : </b>Use for the signer of the
               license, impri- matur, etc. (UF Imprimatur)
            </li>
            <li><a name="d0e6111"></a><b>Lithographer   [ltg] : </b>Use for the person who
               prepares the stone or plate for lithographic printing, including a
               graphic artist creating a design directly on the surface from which
               printing will be done.
            </li>
            <li><a name="d0e6117"></a><b>Lyricist   [lyr] : </b>Use for the writer of the
               text of a song.
            </li>
            <li><a name="d0e6123"></a><b>Memorial : </b>USE Honoree
            </li>
            <li><a name="d0e6129"></a><b>Metadata contact   [mdc] : </b>Use for the person
               or organization primarily responsible for compiling and maintaining
               the original description of a metadata set (e.g., geospatial metadata
               set).
            </li>
            <li><a name="d0e6135"></a><b>Metal-engraver   [mte]: </b></li>
            <li><a name="d0e6140"></a><b>Moderator   [mod] : </b>Use for the person who
               leads a program (often broadcast) where topics are discussed, usually
               with participation of experts in fields related to the
               discussion.
            </li>
            <li><a name="d0e6146"></a><b>Monitor   [mon] : </b>Use for a person or
               organization that supervises compliance with the contract and is
               responsible for the report and controls its distribution.  Sometimes
               referred to as the grantee, or controlling agency.
            </li>
            <li><a name="d0e6152"></a><b>Motion picture editor : </b>USE Film editor 
            </li>
            <li><a name="d0e6158"></a><b>Musician   [mus] : </b>Use for the person who
               performs music or contributes to the musical content of a work when
               it is not possible or desirable to identify the function more
               precisely.
            </li>
            <li><a name="d0e6164"></a><b>Narrator   [nrt] : </b>Use for the speaker who
               relates the particulars of an act, occurrence, or course of
               events.
            </li>
            <li><a name="d0e6170"></a><b>Originator   [org] : </b>Use for the author or
               agency performing the work, i.e., the name of a person or
               organization associated with the intellectual content of the work.
               This category does not include the publisher or personal affiliation,
               or sponsor except where it is also the corporate author. Includes a
               person designated in the work as investigator or principal
               investigator. (UF Principal investigator)
            </li>
            <li><a name="d0e6176"></a><b>Other   [oth] : </b>Use for relator codes from
               other formats which have no equivalent in USMARC or for terms which
               have not been assigned a code.
            </li>
            <li><a name="d0e6182"></a><b>Papermaker   [ppm]: </b></li>
            <li><a name="d0e6187"></a><b>Patent holder   [pth]: </b></li>
            <li><a name="d0e6192"></a><b>Patron  [pat] : </b>Use for the person responsible
               for commissioning a work. Usually a patron uses his or her means or
               influence to support the work of artists, writers, etc.  This
               includes those who commission and pay for individual works.
            </li>
            <li><a name="d0e6198"></a><b>Performer   [prf] : </b>User for a person who
               exhibits musical or acting skills i a musical or dramatic presentation
               or entertainment, if specific codes for those functions ([act],
               [dnc], [itr], [voc], etc.) are not used. If specific codes are used,
               [prf] is used for a person whose principal skill is not known or
               specified.
            </li>
            <li><a name="d0e6204"></a><b>Photographer   [pht] : </b>Use for the person or
               organization responsible for taking photographs, whether they are
               used in their original form or as reproductions.
            </li>
            <li><a name="d0e6210"></a><b>Plaintiff   [ptf] : </b>Use for the party who
               complains or sues in court in a personal action, usually in a legal
               proceeding.
            </li>
            <li><a name="d0e6216"></a><b>Plaintiff-appellant   [ptt] : </b>Use for a
               plaintiff who takes an appeal from one court or jurisdiction to
               another to reverse the judgment, usually in a legal
               proceeding.
            </li>
            <li><a name="d0e6222"></a><b>Plaintiff-appellee   [pte] : </b>Use for a
               plaintiff against whom an appeal is taken from one court or
               jurisdiction to another to reverse the judgment, usually in a legal
               proceeding.
            </li>
            <li><a name="d0e6228"></a><b>Platemaker   [plt]: </b></li>
            <li><a name="d0e6233"></a><b>Plates, Printer of : </b>USE Printer of Plates 
            </li>
            <li><a name="d0e6239"></a><b>Principal investigator : </b>USE Originator
            </li>
            <li><a name="d0e6245"></a><b>Printer   [prt] : </b>Use for the person or
               organization who prints texts, whether from type or plates.
            </li>
            <li><a name="d0e6251"></a><b>Printer of plates   [pop] : </b>Use for the person
               or organization who prints illustrations from plates. (UF Plates,
               Printer of)
            </li>
            <li><a name="d0e6257"></a><b>Process contact   [prc] : </b>Use for a person or
               organization primarily responsible for performing or initiating a
               process, such as is done with the collection of metadata
               sets.
            </li>
            <li><a name="d0e6263"></a><b>Producer   [pro] : </b>Use for a person who is
               responsible for the making of a motion picture, including business
               aspects, management of the productions, and the commercial success of
               the work.
            </li>
            <li><a name="d0e6269"></a><b>Producer of book : </b>USE Book producer 
            </li>
            <li><a name="d0e6275"></a><b>Production personnel   [prd] : </b>Use for a person
               who is associated with the production (props, lighting, special
               effects, etc.) of a musical or dramatic presentation or
               entertainment.
            </li>
            <li><a name="d0e6281"></a><b>Programmer   [prg] : </b>Use for a person or
               corporate body responsible for the creation and/or maintenance of
               computer program design documents, source code, and
               machine-executable digital files and supporting
               documentation.
            </li>
            <li><a name="d0e6287"></a><b>Promoter : </b>USE Thesis advisor 
            </li>
            <li><a name="d0e6293"></a><b>Proofreader   [pfr] : </b>Use for a person who
               corrects printed matter.  For manuscripts, use Corrector
               [crr].
            </li>
            <li><a name="d0e6299"></a><b>Publisher   [pbl]: </b></li>
            <li><a name="d0e6304"></a><b>Publishing director   [pbd] : </b>Use for a person
               who presides over the elaboration of a collective work to ensure its
               coherence or continuity.  This includes editors-in-chief, literary
               editors, editors of series, etc.
            </li>
            <li><a name="d0e6310"></a><b>Recipient   [rcp] : </b>Use for the person to whom
               correspondence is addressed.
            </li>
            <li><a name="d0e6316"></a><b>Recording engineer   [rce] : </b>Use for a person
               who supervises the technical aspects of a sound or video recording
               session.
            </li>
            <li><a name="d0e6322"></a><b>Redactor   [red] : </b>Use for a person who writes
               or develops the framework for an item without being intellectually
               responsible for its content.
            </li>
            <li><a name="d0e6328"></a><b>Renderer  [ren] : </b>Use for the draftsman who
               prepares drawings of architectural designs (i.e., renderings) in
               accurate, representational perspective to show what the project will
               look like when completed.
            </li>
            <li><a name="d0e6334"></a><b>Respondent   [rsp] : </b>Use for the party who
               makes an answer to the courts pursuant to an application for redress,
               usually in an equity proceeding.
            </li>
            <li><a name="d0e6340"></a><b>Respondent-appellant   [rst] : </b>Use for a
               respondent who takes an appeal from one court or jurisdiction to
               another to reverse the judgment, usually in an equity
               proceeding.
            </li>
            <li><a name="d0e6346"></a><b>Respondent-appellee   [rse] : </b>Use for a
               respondent against whom an appeal is taken from one court or
               jurisdiction to another to reverse the judgment, usually in an equity
               proceeding.
            </li>
            <li><a name="d0e6352"></a><b>Reviewer   [rev] : </b>Use for a person or
               corporate body responsible for the review of book, motion picture,
               performance, etc.
            </li>
            <li><a name="d0e6358"></a><b>Rubricator   [rbr]: </b></li>
            <li><a name="d0e6363"></a><b>Scenarist   [sce] : </b>Use for the author of a
               motion picture screenplay.
            </li>
            <li><a name="d0e6369"></a><b>Scientific advisor   [sad] : </b>Use for a person
               who brings scientific, pedagogical, or historical competence to the
               conception and realization on a work, particularly in the case of
               audio-visual items.
            </li>
            <li><a name="d0e6375"></a><b>Scribe   [scr] : </b>Use for a person who makes
               pen-facsimiles of printed matter, as well as for an amanuensis, and
               for a writer of manuscripts proper.
            </li>
            <li><a name="d0e6381"></a><b>Sculptor   [scl] : </b>Use when the more general
               term Artist [art] is not desired.
            </li>
            <li><a name="d0e6387"></a><b>Secretary   [sec] : </b>Use for a recorder,
               redactor, or other person responsible for expressing the views of a
               corporate body.
            </li>
            <li><a name="d0e6393"></a><b>Signer   [sgn] : </b>Use for the person whose
               signature appears without a presentation or other statement
               indicative of provenance.  When there is a presentation statement,
               use Inscriber [ins].
            </li>
            <li><a name="d0e6399"></a><b>Singer   [sng] : </b>Use for a person who uses his
               or her voice with or without instrumental accompanyment to produce
               music.  A singer's performance may or may not include actual
               words.
            </li>
            <li><a name="d0e6405"></a><b>Speaker   [spk] : </b>Use for a person who
               participates in a program (often broadcast) and makes a formalized
               contribution or presentation generally prepared in advance.
            </li>
            <li><a name="d0e6411"></a><b>Sponsor   [spn] : </b>Use for the person or agency
               that issued a contract or under the auspices of which a work has been
               written, printed, published, etc.
            </li>
            <li><a name="d0e6417"></a><b>Stereotyper   [str]: </b></li>
            <li><a name="d0e6422"></a><b>Supposed name : </b>USE Attributed name 
            </li>
            <li><a name="d0e6428"></a><b>Surveyor   [srv] : </b>Use for a person or
               organization who does measurements of tracts of land, etc. to
               determine location, forms, and boundaries.
            </li>
            <li><a name="d0e6434"></a><b>Thesis advisor   [ths] : </b>Use for the person
               under whose supervision a degree candidate develops and presents a
               thesis, memoire, or text of a dissertation. (UF Promoter)
            </li>
            <li><a name="d0e6440"></a><b>Transcriber   [trc] : </b>Use for a person who
               prepares a handwritten or typewritten copy from original material,
               including from dictated or orally recorded material.  For makers of
               pen-facsimiles, use Scribe [scr].
            </li>
            <li><a name="d0e6446"></a><b>Translator   [trl] : </b>Use for a person who
               renders a text from one language into another, or from an older form
               of a language into the modern form.
            </li>
            <li><a name="d0e6452"></a><b>Type designer   [tyd] : </b>Use for the person who
               designed the type face used in a particular item. (UF Designer of
               type)
            </li>
            <li><a name="d0e6458"></a><b>Typesetter : </b>USE Compositor
            </li>
            <li><a name="d0e6464"></a><b>Typographer   [tyg] : </b>Use for the person
               primarily responsible for choice and arrangement of type used in an
               item.  If the typographer is also responsible for other aspects of
               the graphic design of a book (e.g., Book designer [bkd]), codes for
               both functions may be needed.
            </li>
            <li><a name="d0e6470"></a><b>Vocalist   [voc] : </b>Use for a person who
               principally exhibits singing skills in a musical or dramatic
               presentation or entertainment.
            </li>
            <li><a name="d0e6476"></a><b>Wood-engraver   [wde]: </b></li>
            <li><a name="d0e6481"></a><b>Writer of accompanying material [wam] : </b>Use for
               a person who writes significant material which accompanies a sound
               recording or other audiovisual material.
            </li>
         </ul>
         
             
      </div>
      
      
      
      
      
      
      
      
      
      
      
      
      <div class="teidiv">
         <h2><a name="body.1_div.28"></a>28. The Bible Technology Group
         </h2>
         
         
         <p><a name="d0e6497"></a>
            BTG is a joint effort that has been supported most tangibly by the
            American Bible Society and the Society for Biblical Literature, as
            well as by the United Bible Societies, numerous national Bible
            Societies, the Summer Institute of Linguistics, and othe
            organizations.
            
         </p>
         
         
         <p><a name="d0e6500"></a>
            Among the contributors to this work have been:
            
         </p>
         
         
         <ul>
            <li><a name="d0e6505"></a>Patrick Durusau, SBL (primary editor)
            </li>
            <li><a name="d0e6508"></a>Steve Derose (BTG Chair and co-editor)
            </li>
            <li><a name="d0e6511"></a>Kees DeBlois, UBS (BTG Vice-chair)
            </li>
            <li><a name="d0e6514"></a>Kirk Lowery, Westminster Hebrew Institute (chair,
               Linguistic Annotation WG)
            </li>
            <li><a name="d0e6517"></a>Troy Griffiths, Crosswire
            </li>
            <li><a name="d0e6520"></a>Chris Little, 
            </li>
            <li><a name="d0e6523"></a>Todd Tillinghast, 
            </li>
            <li><a name="d0e6526"></a>Adina Hamik, Nida Institute
            </li>
            <li><a name="d0e6529"></a>Harry Plantinga, Calvin College/CCEL
            </li>
            <li><a name="d0e6532"></a>Mike Perez, American Bible Society
            </li>
            <li><a name="d0e6535"></a>Dennis Drescher, SIL
            </li>
            <li><a name="d0e6538"></a>Nathan Miles, SIL
            </li>
            <li><a name="d0e6541"></a>Robert Hodgson, Nida Institute
            </li>
            <li><a name="d0e6544"></a>John Walters, American Bible Society
            </li>
         </ul>
         
         
         <p><a name="d0e6548"></a>
            The work of BTG has also been greatly enhanced by many other members
            of these and other organizations, who have responded to drafts, made
            numerous, useful, and sometimes essential recommendations, and
            encoded texts to test the schemas for usability, consistency, and
            other virtues. Especially notable among these have been Robin Cover,
            Jonathan Robie, and Bob Pritchett.
            
         </p>
         
         
         <p><a name="d0e6551"></a>The official Website for BTG is http://www.bibletechnologies.net,
            and much additional information can be found there.
         </p>
         
         
      </div>
      
      <hr>
      <div class="footer"><a class="plain" target="_top" href="http://www.bibletechnologies.org/">Bible Technologies Group</a>
         | <a class="plain" target="_top" href="http://www.bibletechnologies.org">BTG</a></div>
      <hr>
      <address>Date: 
          (revised 2003:11:15)
          &nbsp;Author: Patrick Durusau, Patrick.Durusau@sbl-site.orgSteve DeRose, sderose@acm.org
          (revised pld).
          <br><a href="/documentation/copyright.html">&copy;</a> Bible Technologies Group.
         <!--
Generated from osisUserManual_06 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-11-16T15:40:25Z-->
      </address>
   </body>
</html>
--------------090305060603020601050909--