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

A few languages use traditional reference schemes that completely differ from the
familiar book/chapter/verse one.
Many works of Classical literature likewise have more than one standard canonical
reference scheme, such a Loeb numbers plus another method.
In such cases, where there <strong>are</strong> large and systematic differences, different "versification
schemes" must be defined and named. On the other hand, nearly every edition of the
Bible has some slight deviations from a standard versification scheme that it otherwise
follows: for example, subdividing verses into parts "a" and "b", combining verses into a
larger translation unit, and so on. It is highly undesirable to call these separate
versification schemes, because they differ so slightly; because the differences can be
mechanically resolved; and because there is considerably overhead to maintaining and
mapping among versification schemes. Thus, as described below such minor extensions
can be done without an edition having to say it is using a completely different
versification scheme.
BTG intends to develop an XML schema for declaration files that can express such
systems, and their mapping to other systems. This work has not been completed.
However, we have reserved names for the major versification systems, see: XML and
<strong>OSIS</strong> declarations above.
Each work must identify which versification scheme(s) it uses; this is done by a reference
to the versification scheme decl<strong>are</strong>d by a work declaration in the header except that the
predefined versification systems need not have work declarations.
References can also state what versification scheme they <strong>are</strong> expressed in, so that they
may be correctly interpreted.
HTML may provide targets that look like canonical Bible references, but this would not
remove the requirement to specify osisID where applicable. An osisID is mandatory
when applicable.
17. Conformance requirements
17.1. Conformance levels
There <strong>are</strong> 4 levels of <strong>OSIS</strong> conformance for the markup in <strong>OSIS</strong> documents:
17.1.1. Level 1: "Minimal <strong>OSIS</strong> document"
The document must be a well-formed and valid XML document according to the <strong>OSIS</strong>
schema.
The document must be complete in accordance with the scope declaration in its work
declaration. For example, a document with a missing chapter is not <strong>OSIS</strong>-conforming.