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

More documents

Recommendations

Info

Applications must interpret <strong>OSIS</strong> 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 ne<strong>are</strong>st reliably-findable place; in this case, the verse. Applications must be able to interpret the <strong>OSIS</strong> 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. The Bible Technologies group also strongly advocates making all softw<strong>are</strong>, and especially all <strong>OSIS</strong>-aw<strong>are</strong> softw<strong>are</strong>, 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 softw<strong>are</strong>, for example, the order in which panes <strong>are</strong> drawn. Implementors <strong>are</strong> 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. 19. Alphabetical list of Elements • NAME: PLACEMENT • a: Content inline • abbr: Content inline • actor: castGroup structure • caption: Figure structure • castGroup: castGroup structure • castItem: castGroup structure • castList: castGroup structure • catchWord: Annotation • cell: table structure • chapter: Main content • closer: Epistolary structure • contributor: Dublin Core (in work) • coverage: Dublin Core (in work) • creator: Dublin Core (in work) • date: Dublin Core (in work) • description: Dublin Core (in work) • div: Main structure
• divineName: Content inline • figure: Figure structure • foreign: Main content • format: Dublin Core (in work) • head: Main content • header: Header • hi: Content inline • identifier: Dublin Core (in work) • index: Content inline • inscription: Content inline • item: List structure • l: Poetic structure • label: List structure • language: Dublin Core (in work) • lb: Poetic structure • lg: Poetic structure • list: List structure • mentioned: Annotation • milestone: Annotation • milestoneEnd: (deprecated -- do not use) • milestoneStart: (deprecated -- do not use) • name: Content inline • note: Content inline • osis: Header • osisCorpus: Header • osisText: Header • p: Content inline • publisher: Dublin Core (in work) • q: Content inline • rdg: Content inline • reference: Reference system • refSystem: Header (in work) • relation: Dublin Core (in work) • revisionDesc: Header • rights: Dublin Core (in work) • role: castGroup structure • roleDesc: castGroup structure • row: table structure • salute: Epistolary • scope: Dublin Core (in work) • seg: Content inline • signed: Epistolary • source: Dublin Core (in work) • speaker: Content structure • speech: Content structure • subject: Dublin Core (in work)
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 and 54: The document must mark all canonica
Page 55: non-obvious interpretation, that fa
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

Create successful ePaper yourself

Delete template?

Save as template?