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

The first line above identifies the document as being XML; this is required in exactly the
form shown, and enables computers to identify how to process the rest of the document.
The second through third lines <strong>are</strong> a very long start-tag for the outermost <strong>OSIS</strong> element,
which is called "osis." All elements in an <strong>OSIS</strong> document must be decl<strong>are</strong>d within the
<strong>OSIS</strong> namespace. There <strong>are</strong> two ways to achieve this and other than remembering to pick
one of the two following methods, that is all you need remember about it to start
encoding texts using <strong>OSIS</strong> 2.0.
<strong>OSIS</strong> Namespace, Method 1: Copy the following lines just after :
<strong>OSIS</strong> Namespace, Method 2: Copy the following lines just after :
Note with the second method, the last closing element must be: . The first
method is simpler but both <strong>are</strong> legitimate.
At this point, the <strong>OSIS</strong> document has begun. This sample is a single document rather than
a collection of documents, so the next element opened is osisText:
Every osisText needs to supply an osisIDWork attribute and value. The value will
generally be the short name of what is being encoded, in this case the Contemporary
English Version, or CEV. The short name is defined in the work declaration for the
work, described later. The work element that identifies the work being encoded should