OSIS? 2.0.1 User's Manual - Web services are running on AMBIB
OSIS? 2.0.1 User's Manual - Web services are running on AMBIB
OSIS? 2.0.1 User's Manual - Web services are running on AMBIB
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
value for this attribute. Such additi<strong>on</strong>s systems should be brought to the attenti<strong>on</strong> of the<br />
<str<strong>on</strong>g>OSIS</str<strong>on</strong>g> editors.<br />
• acrostic Use for tites where alignment of first or final letters of words in the title<br />
<str<strong>on</strong>g>are</str<strong>on</strong>g> meaningful.<br />
• c<strong>on</strong>tinued Use for titles that <str<strong>on</strong>g>are</str<strong>on</strong>g> c<strong>on</strong>tinuati<strong>on</strong>s of some other part of the title.<br />
• main Use for the main title of a work.<br />
• parallel Use where titles <str<strong>on</strong>g>are</str<strong>on</strong>g> given in alternative languages.<br />
• psalm Use in the Psalms where what <str<strong>on</strong>g>are</str<strong>on</strong>g> c<strong>on</strong>sidered "titles" in the English text <str<strong>on</strong>g>are</str<strong>on</strong>g><br />
actually numbered as verses in the Hebrew text.<br />
• sub Use for subparts of a title.<br />
21. osisIDs: C<strong>on</strong>structi<strong>on</strong> Rules<br />
The really adventerous reader will c<strong>on</strong>sult the osisCore.2.0 schema for the regular<br />
expressi<strong>on</strong> that governs the form of osisIDs. For those in a hurry or who simply want to<br />
avoid the complexity of XML Schema regexes (the abbreviated form of regular<br />
expressi<strong>on</strong>s) the following guide should suffice.<br />
Any osisID is divided into a number of parts, some of which <str<strong>on</strong>g>are</str<strong>on</strong>g> opti<strong>on</strong>al, that is they can<br />
be omitted and still have a valid osisID. The following breaks out the structure of an<br />
osisID into its various parts and notes what is allowed in each part and what parts <str<strong>on</strong>g>are</str<strong>on</strong>g><br />
required.<br />
21.1. Prefix: (opti<strong>on</strong>al)<br />
The prefix to an osisID must c<strong>on</strong>tain at least <strong>on</strong>e letter, number or underscore, that may<br />
be followed by any number of letters, numbers or underscores, separated by periods, and<br />
c<strong>on</strong>cluding in a col<strong>on</strong> ":". Note that if you use a prefix, the col<strong>on</strong> is required. The prefix<br />
is opti<strong>on</strong>al.<br />
Some examples of valid prefixes include:<br />
• Bible:<br />
• Bible.French:<br />
• Spurge<strong>on</strong>.Commentaries_Job:<br />
21.2. Main (required)<br />
The main part of an osisID c<strong>on</strong>sists of at least <strong>on</strong>e letter, number or underscore, that may<br />
be followed by any number of letters, numbers or underscores, separated by periods. The<br />
main part of the osisID is required.<br />
Note that <strong>on</strong>e difference from traditi<strong>on</strong>al identificati<strong>on</strong> of Bible verses that <str<strong>on</strong>g>OSIS</str<strong>on</strong>g> uses a<br />
period to separate the verse from the chapter. One usually sees, Gen. 1:1. That is what<br />
should be displayed to the reader of a <str<strong>on</strong>g>OSIS</str<strong>on</strong>g> text, but use of whitespace as a separator