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

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