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

More documents

Recommendations

Info

Recommended practice is that more recent change elements appear earlier in the document. That is, entries should occur in reverse chronological order. For example: 2003-09-11 sjd: Filling in the gaps. Adding some info for 2.0 as defined at the Calvin College meetings. 2003-07-01 sjd: Annotated alpha list of elements. Reworked reference and work sections and added type, scope, and explanations of type and subtype for work. Explained more elements and attributes. 2003-06-17 sjd: Wrote conformance section. Added lists of elements and attributes, USMARC list. Inserted placeholders for doc on all element types. Got document back to XML WF. Wrote CSS stylesheet. 7.2. Work Declarations A work element is a declaration. It provides information comparable to that found on the title page of a printed work, using the fields defined by the Dublin Core Initiative (see http://dublincore.org/). The work element serves two purposes. The work element in the header with an osisWork attribute that matches the osisIDRef in the osisText element identifies the work in which it occurs -- much like the title page in a printed work. For example: Note that the match between osisIDWork="CEV" in osisText and osisWork="CEV" in the work element links this osisText to this particular work element. Subsequent work elements identify other works -- much like a citation in a footnote or bibliography in a printed work. Each assigns a local name to each one, using the osisWork attribute. Works so decl<strong>are</strong>d can then be referred to from osisIDs or osisRefs throughout the text. For Bibles, this should generally be the accepted acronym or abbreviated form of the translation's name (some standard version abbreviations <strong>are</strong> listed in an appendix). No periods, hypens, spaces, or colons <strong>are</strong> allowed in short names.
Note: This mechanism of declaring a short name and using it later as a prefix, is very similar to the XML Namespace mechanism defined at http://www.w3.org/TR/xmlnames11/. 7.3. The Dublin Core Each work element describes a single publication using several pieces of information, primarily title, creator, date, publisher, identifier and language. All of the standard "Dublin Core" fields may be used, plus a few <strong>OSIS</strong>-specific additions (further information on the Dublin Core system may be found at http://www.dublincore.org). All of the Dublin core fields may be repeated as necessary, but must be encoded in the order shown here. For example: Egyptian Grammar Alan Gardiner Francis Llewellyn Griffith 1927 2003 Grammar Griffith Institute, Ashmolean Museum, Oxford EN EG-ancient 0900416351 95230980 Cotton Patch Version of Luke and Acts: Jesus' Doings and the Happenings Cl<strong>are</strong>nce Jordan 1969 2003 Bible Association Press New York, NY EN 0809617250 69-18840 7.3.1. title A title element must be provided in the work element and contain the main title of the work. Additional titles may also be specified, using the type attribute to identify them as
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: In books other than the Bible, a si
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 and 60: esp xs:string optional This attribu
Page 61 and 62: The annotateType attribute, which i
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?