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

More documents

Recommendations

Info

All inscriptions (for example, "mene mene tekel parsin") must be marked where applicable. All instances, translations, or transliterations of the tetragrammaton must be marked via the divineName element. 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"). All epistolary markup (opener, closer, signature, salute) must be provided where applicable. Poetic text must be marked sufficiently to enable rendering it readably as poetry. The distinction of using l for linguistically or poetically significant line breaks, versus using lb for typographically significant or preferred line breaks, must be maintained. 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. 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 <strong>OSIS</strong> standardizes a format for external annotation files, this requirement may be fulfilled either by inline encoding of annotations, or external. 17.1.3. Level 3: Complete <strong>OSIS</strong> document All the requirements of Level 2 must be fulfilled. All notes, front and back matter, illustrations, section heads, and other non-canonical phenomena of the source edition must be included. 17.1.4. Level 4: Scholarly <strong>OSIS</strong> document All the requirements of Level 3 must be fulfilled. 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. 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. The text must also conform to the requirements of Level 3 Quality as described below. 17.2. Quality levels 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": 17.3. Level 1: Sub-OCR Quality The text may have many typographical errors; essentially, it is unproofread text from automated OCR, probably of a less-than-ideal original. 17.4. Level 2: OCR Quality The text may have up to 5 typographical errors per source page. It may be unproofread 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 doublekeying or similar service that maintains accuracy to the required level. 17.5. Level 3: Proof Quality There may not be more than an average of 1 error per source page (or per 2000 characters of content) as comp<strong>are</strong>d 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. However, 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. 17.6. Level 4: Trusted Quality 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). 18. Application Requirements Applications should avoid making any processing distinctions between elements represented as non-crossing single elements or as milestone pairs.
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 and 52: . It is permissible for osisRefs, i
Page 53: The document must mark all canonica
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
show all

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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?