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

More documents

Recommendations

Info

script osisScripts specifying their own explicit xml:lang attribute value. The form of the xml:lang attribute is constrained by Internet specifications, particularly IETF RFC 1766, Tags for the Identification of Languages. Such tags consist of a 2-letter language code from ISO 639 (see http://www.oasis-open.org/cover/iso639a.html), optionally followed by a two letter country code from ISO 3166 (see http://www.oasisopen.org/cover/country3166.html). For example, "de" or "en-GB" Alternatively, they may be codes from the IANA registry at http://www.iana.org/assignments/language-tags. Remaining languages should use SIL Ethnologue codes (see http://www.ethnologue.com/codes/). optional This attribute provides a slight extension beyond the capabilities of the xml:lang attribute. For many languages, it is enough to specify the language itself, and the country where it is spoken (say, Canadian vs. French dialects of the French language). However, there <strong>are</strong> cases where a given language community may use multiple writing systems: either different character sets and character usage rules; different spelling or other conventions; etc. In such cases, the particular script system used for writing the current work (or element within a work) must be specified via this attribute. This attribute inherits in precisely the same manner as xml:lang. 20.2. Normative values for the type attribute, by element The heading for each basic element type below, indicates whether the list of values provided is extensible (by adding names beginning with "x-", or non-extensible). Users who find values potentially of general use, that <strong>are</strong> not already provided, <strong>are</strong> asked to send them to the editors for possible incorporation into future versions of the specification. Likewise, users who discover any substantial ambiguity in the values provided, <strong>are</strong> asked to notify us and to provide examples and explanations, so that we can attempt to rectify any such problem. 20.2.1. annotateType
The annotateType attribute, which is available on all content elements, is to be used along with the annotateRef attribute, to indicate the type of annotation is being made to another work or portion of another work. This sort of reference can point to anything that can be pointed to using an osisRef so the annotation about a word, phrase, verse, chapter or larger portion of text. These values characterize the annotation, not the work that is being annotated. They will be particularly helpful in systems where annotations of a particular type, rebuttal for example, <strong>are</strong> being sought for a particular work. If the type of annotation you <strong>are</strong> making does not appear in this list, use the <strong>OSIS</strong> attribute extension, that is, "x-" in front of your attribute value. • commentary A comment or fuller commentary on the reference given by the annotateRef attribute. • exposition A development of the meaning of the reference given by the annotateRef attribute.. • meditation A mediatation on the reference given by the annotateRef attribute.. • outline An outline of the reference given by the annotateRef attribute.. • rebuttal A rebuttal of one or more points in the reference given by the annotateRef attribute.. • sermon A sermon based on the reference given by the annotateRef attribute. • studyGuide A studyguide on the reference given by the annotateRef attribute. • translation A translation of the reference given by the annotateRef attribute. 20.2.2. calendar The standard calendar varies by historical time period as well as culture. We have not attempted to list all the possible calendars that might be used in <strong>OSIS</strong> documents, but provide the following starter set. Suggestions of other calendars with references to documentation would be greatly appreciated. For cases where the required calendar is not one of the following values, please use the <strong>OSIS</strong> attribute extension mechanism, "x-" in front of the name of your calendar. • Chinese Information on the Chinese calendar can be found at: http://webexhibits.org/calendars/calendar-chinese.html • Gregorian Standard calendar in use in the US and Europe. For further information see: http://www.geocities.com/calendopaedia/gregory.htm • Islamic Standard calendar in Muslim countries and religious communities. For further information see: http://webexhibits.org/calendars/calendar-islamic.html • ISO This is not a separate calendar from the Gregorian but is a specific notation for recording dates. For further information see: http://www.cl.cam.ac.uk/~mgk25/iso-time.html • Jewish Official calendar of Israel and for religious purposes. For further information see: http://webexhibits.org/calendars/calendar-jewish.html
Page 1 and 2:
Bible Technologies Group OS
Page 3 and 4:
12.6.6. cell 12.6.7. figure 12.6.
Page 5 and 6:
provides a standard way to express
Page 7 and 8:
The examples in this manual have be
Page 9 and 10: The first line above identifies the
Page 11 and 12: In books other than the Bible, a si
Page 13 and 14: Note: This mechanism of declaring a
Page 15 and 16: 7.3.6. language A language element
Page 17 and 18: Recommended best practice is to ide
Page 19 and 20: If a publication matches all of the
Page 21 and 22: 8. Title Pages In order to make the
Page 23 and 24: "What did Moses command you?" he re
Page 25 and 26: Every note should have a type attri
Page 27 and 28: Esther with traditional verse eleme
Page 29 and 30: • See with what large letters I a
Page 31 and 32: Todd Tillinghast Eliphaz The first
Page 33 and 34: Stephen's Speech to the Sanhedrin T
Page 35 and 36: The LORD Always Does Right You, L
Page 37 and 38: Christ and the Woman taken in Adult
Page 39 and 40: • line Line milestones should be
Page 41 and 42: software to chose
Page 43 and 44: For as I walked around and looked c
Page 45 and 46: The q element marks all quotations,
Page 47 and 48: • To identify a reference into a
Page 49 and 50: The ! as the terminator, allows enc
Page 51 and 52: . It is permissible for osisRefs, i
Page 53 and 54: The document must mark all canonica
Page 55 and 56: non-obvious interpretation, that fa
Page 57 and 58: • divineName: Content inline •
Page 59: esp xs:string optional This attribu
Page 63 and 64: • chapter Standard chapter as is
Page 65 and 66: The values that are</strong
Page 67 and 68: • explanation Use for a note that
Page 69 and 70: (between Gen. and chapter 1, in XML
Page 71 and 72: • Prov.26.12!b osisRef for the se
Page 73 and 74: • ill Illustrator: Use for the pe
Page 75 and 76: • PrAzar Prayer of Azariah • Be
Page 77 and 78: • ERV Easy-to-Read Version • ES
Page 79 and 80: • Appraiser USE Expert • Arrang
Page 81 and 82: • Contestant-appellee coe Use for
Page 83 and 84: • Instrumentalist itr Use for a p
Page 85 and 86: • Programmer prg Use for a person
Page 87: • Nathan Miles, SIL • Robert Ho
show all

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

Create successful ePaper yourself

Delete template?

Save as template?