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

Every note should have a type attribute to indicate its purpose; many Bible editions show
different kinds of notes in different places. The pre-defined note types <strong>are</strong> listed below;
they <strong>are</strong> 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-".
• allusion The note explains an implicit reference the text makes to another text or
concept.
• alternative The note records an alternate possible reading of the text, whether due
to ambiguity in translation or to manuscript variation.
• background The note provides background information, such as cultural norms,
explanations of geographic or other information original readers would have
known, and so on.
• citation The note cites a supporting text or further explanation of some kind.
• crossReference The note provides a cross-reference to a related passage or other
text.
• devotional The note includes information of interest for devotional reading.
• exegesis The note discusses a relevant point of exegesis or interpretation
• explanation The note explains implicit, ambiguous, or otherwise non-obvious
aspects of the passage.
• 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".
• study The note provides helps for a deeper study of the passage.
• 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.
• variant The note records a textual variation in manuscript tradition, relevant at its
location.
Sometimes a verse or chapter 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
verse or chapter tags must be used. This usage is explained in the next section.
11. Elements that cross other elements
The normal form of an element is a start tag and an end tag: .... 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 sID attribute
(the start of the traditional element) and the eID attribute (the end of the traditional
element), the values of which must match.