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

In books other than the Bible, a similar distinction holds: the text proper of Herodotus'
Histories must be contained in elements with canonical="true", while notes, header data,
and the like must not.
The meaning of this attribute is limited. It must not be used to encode interpretive or
theological judgements about canonicity. For example, encoders who include the
apocryphal books of the Bible, or the alternate longer ending to the Gospel of Mark, must
mark them as canonical (whether by default or explicitly). This is simply because they
<strong>are</strong> part of the text being encoded. Users of a text <strong>are</strong> never justified in drawing
conclusions about a translator's, editor's, or encoder's position on questions of inspiration
or other theological questions based on how they set the canonical attribute, because the
attribute does not mean that.
In most cases use of the canonical attribute is straightforward, and we expect that the
default values will almost always produce the intended result. However, there will arise
truly difficult cases: for example, one may be encoding an ancient text with annotations
of its own. In that case those notes would be canonical, while any added by the current
editor would not be. In such cases, the practice chosen and its rationale should be
described in the work's documentation.
7. The <strong>OSIS</strong> text header
The first element within every osisText must be a header. The header decl<strong>are</strong>s various
works (including the work being encoded and any that <strong>are</strong> being referenced), and
provides a place to keep a revision history of the text.
7.1. The Revision Description
To record changes or edits to the text, authors and editors <strong>are</strong> encouraged to insert a
change element every time significant editing is done. Each change element should
contain a date element which says when those edits were completed, in the form
yyyy-mm-ddThh:mm:ss
Note that all fields must have exactly the number of digits shown (4-digit year, 2-digit
month, etc.). It is permissible to omit the time and the preceding "T", thus giving just a
date. For example, December 25th of 1999 CE would be:
1999-12-25
A date element in the revision description is followed by any number of p (paragraph)
elements, in which the changes made <strong>are</strong> summarized. The person responsible for making
the changes should also be identified, using the resp attribute on the change element.