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

The ! as the terminator, allows encoders to append names and/or numbers to provide
finer-grained reference points. Such extensions may not be valid across reference systems
so should be used with c<strong>are</strong>.
As with XML in general, these identifiers <strong>are</strong> case-sensitive: "Matt" is the correct form,
and there is no Bible book in <strong>OSIS</strong> that is called "matt" or "MATT". Applications for end
users may choose to accept case variants in such names, but applications for encoders
(such as <strong>OSIS</strong> editors) must not produce documents with invalid reference names.
14.6. Coding multiple versification or reference schemes in a single
document
A work may provide identifiers drawn from multiple distinct versification schemes. A
Bible may wish to provide both the Hebrew and Greek traditional verse numberings;
while a work of classical literature may be made more accessible by marking the
boundaries of canonical units drawn from completely unrelated systems, such as Loeb
and Whiston for Josephus (and 4 more systems for Josephus' Jewish War specifically --
see H. Douglas Buckwalter and Mary K. Shoaff, Guide to Reference Systems for the
Works of Flavious Josephus, Evangelical Theological Society, 1995, ISBN
093205501X).
The work element is not required for the standard reference systems already reserved.
See XML and <strong>OSIS</strong> Declarations.
A simpler case may also arise where multiple reference schemes <strong>are</strong> in use: an
osisCorpus that includes several osisTexts, each of which uses a different reference
scheme. This case is simpler, since each osisText can provide its own default reference
system, using the osisRefWork attribute on osisText.
This is accomplished in the same way as just described for discursive translations: the
multiple identifiers <strong>are</strong> simply placed where needed, separated by spaces when they cooccur
on a single element. Each reference system used much be decl<strong>are</strong>d as a work in the
header, and each identifier much indicate the reference system from which it is drawn.
For example, a line of Josephus that has two distinct identifiers would appear like this
(presuming the appropriate work declarations in the header):
Because verse, chapter, and similar elements can be expressed by empty-element pairs
when necessary, it is possible to encode multiple reference systems even though they may
have completely unrelated start and end points for their units. For example, a work that
has one reference system based on sentences, and another based on lines of a normative
print edition, can co-exist. However, taken to extremes this would get rather messy, and
be difficult to maintain without <strong>OSIS</strong>-aw<strong>are</strong> softw<strong>are</strong> to assist.