OSIS? 2.0.1 User's Manual - Web services are running on AMBIB

More documents

Recommendations

Info

A few languages use traditional reference schemes that completely differ from the familiar book/chapter/verse one. Many works of Classical literature likewise have more than one standard canonical reference scheme, such a Loeb numbers plus another method. In such cases, where there <strong>are</strong> 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. 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 have reserved names for the major versification systems, see: XML and <strong>OSIS</strong> declarations above. Each work must identify which versification scheme(s) it uses; this is done by a reference to the versification scheme decl<strong>are</strong>d by a work declaration in the header except that the predefined versification systems need not have work declarations. References can also state what versification scheme they <strong>are</strong> expressed in, so that they may be correctly interpreted. HTML may provide targets that look like canonical Bible references, but this would not remove the requirement to specify osisID where applicable. An osisID is mandatory when applicable. 17. Conformance requirements 17.1. Conformance levels There <strong>are</strong> 4 levels of <strong>OSIS</strong> conformance for the markup in <strong>OSIS</strong> documents: 17.1.1. Level 1: "Minimal <strong>OSIS</strong> document" The document must be a well-formed and valid XML document according to the <strong>OSIS</strong> schema. 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 <strong>OSIS</strong>-conforming.
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. The header must include work declarations for the document itself, and for the versification system it uses. All work declarations must provide unique osisWorkID values, and only those values may appear as work identifiers in osisIDs and osisRefs (whether by default or explicit) in the document. 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. 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. Empty elements substituted for containers (such as verse, q, etc.) must occur in matched pairs. Each end must actualy 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. 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). 17.1.2. Level 2: "Basic <strong>OSIS</strong> Document" All requirements of Level 1 conformance must be fulfilled. A clear statement of rights must be provided within the rights 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 <strong>are</strong> encumbrances or if clearance is required to copy or use the work, contact information for the responsible party must be provided directly within the rights element. 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 <strong>are</strong> strongly encouraged to make a serious effort to identify the source edition).
Page 1 and 2: Bible Technologies Group OS
Page 3 and 4: 12.6.6. cell 12.6.7. figure 12.6.
Page 5 and 6: provides a standard way to express
Page 7 and 8: The examples in this manual have be
Page 9 and 10: The first line above identifies the
Page 11 and 12: In books other than the Bible, a si
Page 13 and 14: Note: This mechanism of declaring a
Page 15 and 16: 7.3.6. language A language element
Page 17 and 18: Recommended best practice is to ide
Page 19 and 20: If a publication matches all of the
Page 21 and 22: 8. Title Pages In order to make the
Page 23 and 24: "What did Moses command you?" he re
Page 25 and 26: Every note should have a type attri
Page 27 and 28: Esther with traditional verse eleme
Page 29 and 30: • See with what large letters I a
Page 31 and 32: Todd Tillinghast Eliphaz The first
Page 33 and 34: Stephen's Speech to the Sanhedrin T
Page 35 and 36: The LORD Always Does Right You, L
Page 37 and 38: Christ and the Woman taken in Adult
Page 39 and 40: • line Line milestones should be
Page 41 and 42: software to chose
Page 43 and 44: For as I walked around and looked c
Page 45 and 46: The q element marks all quotations,
Page 47 and 48: • To identify a reference into a
Page 49 and 50: The ! as the terminator, allows enc
Page 51: . It is permissible for osisRefs, i
Page 55 and 56: non-obvious interpretation, that fa
Page 57 and 58: • divineName: Content inline •
Page 59 and 60: esp xs:string optional This attribu
Page 61 and 62: The annotateType attribute, which i
Page 63 and 64: • chapter Standard chapter as is
Page 65 and 66: The values that are</strong
Page 67 and 68: • explanation Use for a note that
Page 69 and 70: (between Gen. and chapter 1, in XML
Page 71 and 72: • Prov.26.12!b osisRef for the se
Page 73 and 74: • ill Illustrator: Use for the pe
Page 75 and 76: • PrAzar Prayer of Azariah • Be
Page 77 and 78: • ERV Easy-to-Read Version • ES
Page 79 and 80: • Appraiser USE Expert • Arrang
Page 81 and 82: • Contestant-appellee coe Use for
Page 83 and 84: • Instrumentalist itr Use for a p
Page 85 and 86: • Programmer prg Use for a person
Page 87: • Nathan Miles, SIL • Robert Ho

OSIS? 2.0.1 User's Manual - Web services are running on AMBIB

Create successful ePaper yourself

Delete template?

Save as template?