[osis-editors] OSIS 2 manual draft - errata and comments
Daniel Englbauer
osis-editors@bibletechnologieswg.org
Tue, 9 Dec 2003 08:23:14 +0100
Dear editors,
in the draft of the manual for OSIS 2.0 you wrote that
corrections, comments and examples are welcome. Here are some
along with some questions.
In the first section there are comments and questions on the
manual or global on OSIS, esp. on bible and language support.
Second there are recommendations concerning the manual and OSIS:
Standard OSIS Codes for Bible Editions, content for the omitted
sections "table", "row" and "cell" (incl. some examples), then
another example for <figure> and last some other suggestions.
Finally there is a block with errata of some typos and
misspellings found in the draft.
All remarks ascribe to the draft "Date: (revised 2003:11:15)
Author: (revised pld)".
For the Contributor's section here is my contact information:
Name: Daniel Englbauer
Email: osis@englbauer.de
In Christ
Daniel Englbauer
----****----
Daniel Englbauer
Seegartenstr. 23
D-97355 Castell
Germany
Tel.: +49 (0)9325 / 980 546
Fax : +49 (0)1805 39160 - 30846 (0,12 Euro/min in country)
http://daniel.englbauer.de/
http://www.englbauer.de/theol/
mailto:osis@englbauer.de
mailto:info@englbauer.de
BTW: the eMail-adress given in the manual for the OSIS Users'
Group (osis-user@whi.wts.edu) is not working.
There ist no Hello from the mailing list but a Hello from the
mailer demon:
<cite who="mailer demon">
Message:
osis-user@whi.wts.edu
LMTP error after RCPT TO:<osis-user@whi.wts.edu>:
550-Mailbox unknown. Either there is no mailbox associated
with this
550-name or you do not have authorization to see it.
550 5.1.1 User unknown
</cite>
-----------------------------------------------------
---------------- Comments: --------------------------
-----------------------------------------------------
29. Standard OSIS Codes for Bible Editions
All Bible Edition codes must have the language code for the
target language in question, then a colon, then the abbreviation
shown here.
29.1. Ancient language editions
Steph Stephanus GNT, 1551
Vul Latin Vulgate, 1405
Erasmus Latin translation by Desiderius Erasmus Roterodamus, 1516
Mas Masoretic text (various, ~900-1100)
BHS Biblia Hebraica Stuttgartsiensa
NA Nestle-Aland Greek New Testament (may suffix edition number,
such as "NA27")
LXX Greek Septuagint
<question>
Which language code has to be used to specify the
translation?
IANA, IETF, ISO-639-1, ISO-639-2, ISO-639-2-B, ISO-639-2-T,
LINGUIST or SIL?
What is the language code for the "BHS"? The 'hebrew' bible
contains biblical hebrew and biblical aramaic.
Is the Code for LXX "gr:LXX" or "GKO:LXX" or "GRK:LXX"?
</question>
29.1.2. Non-English Modern Languages
Thousands of additional languages have Bibles or portions; most
of these have only one translation in the language. In those
cases the language code as defined elsewhere in OSIS may be used,
with no following name required.
<comment>
It sure is simple to handle it that way, but what will
happen,
in case someone offers another translation in this language?
Then there are two versions and you would have to find
another
way to give a translation type or the first written version
will block the short form. Older versions of OSIS-texts have
to be modified. I think it's better to build a type of
database of OSIS standard codes over the time with a name for
every known bible translation.
</comment>
Luther German by Martin Luther, 1534
Algonquin Tr. John Eliot, 1662
ReinaV Spanish Reina Valera
<question>
The German translation of the bible by Luther in 1534 is
"de:Luther". Is the 1984 revision then "de:Luther1984" if
there is no standard OSIS codes for bible editions yet?
So I make a recommendation for German versions next section.
</question>
<question>
There is a default value for the optional osisRefWork-
attribute (Bible). Are there other given standard attributes
like "comment", "lexica", "book" or "article"?
</question>
<question>
How to mark up verses within a text that are not directly
taken from a given (published) translation, but are
translated
by the author of the book or article?
</question>
-----------------------------------------------------
---------------- Recommendations: -------------------
-----------------------------------------------------
29. Standard OSIS Codes for Bible Editions
29.1.3. German Editions (prefix "de:")
Most common editions in German language
Luther - German by Martin Luther, 1534
Luther1912 - German by Martin Luther, unrevised edition, 1912
Luther1984 - German by Martin Luther, revised edition, 1984
ELO - German Darby Unrevidierte Elberfelder, 1905
ELB - German Elberfelder Bibel, revidierte Fassung, 1993
EIN - German Einheitsübersetzung der Heiligen Schrift,
1980
Schlachter - German Schlachter Version, 1951
GN - German Gute Nachricht
GNa - German Gute Nachricht, with apocrypha
HFA - German Hoffnung für alle
HFA02 - German Hoffnung für alle, revidierte Fassung, 2002
Bengel - German Bengel NT (scope: NT)
Zink - German by Jörg Zink, 1998
BRZ - German by Buber-Rosenzweig (scope: OT)
12.6.4 table
OSIS provides only very rudimentary tables: a table consists of
rows, which in turn consist of cells. Formatting and layout is
not part of the table markup; it can either be done
automatically, as in HTML browsers, or by inserting some signal
to the layout engine, such as type attributes or processing
instructions. Note that a *table* can be nested inside another
*table*. Simply start a new *table* element inside a *cell*
element.
You can specify how many rows and columns there are with the
attributes "rows" and "cols", but this is optional.
In the *head* section you give the table a title or small
description.
Example:
<table cols="2" rows="2">
<head>Demonstration</head>
<row>
<cell>...</cell>
<cell>...</cell>
</row>
<row>
<cell>...</cell>
<cell>...</cell>
</row>
</table>
A detailed example is in "12.6.6 cell" below.
Note again: OSIS provides no attributes or elements to layout the
table, rows and cells, like "width", "cellspacing" or "align" in
(X)HTML. All this has to be done by the rendering software or the
browser. Here is an example out of an XSL-file for XHTML output:
<xsl:stylesheet version = '1.0'
xmlns:xsl='http://www.w3.org/1999/XSL/Transform'>
<xsl:template match="table">
<table class="tab2" border="1">
<xsl:value-of select="."/>
</table>
</xsl:template>
<xsl:template match="row">
<tr>
<xsl:value-of select="."/>
</tr>
</xsl:template>
<xsl:template match="cell">
<td class="tabhigh">
<xsl:value-of select="."/>
</td>
</xsl:template>
</xsl:stylesheet>
12.6.5 row
*row* is the element that binds together a number of cells for a
line. The use is similar to the (X)HTML element <tr>.
12.6.6 cell
Due to the fact that table cells in printed publications can
contain nearly anything, nearly anything is allowed in OSIS'
*cell*s – even verses and other tables.
Example:
<table cols="3" rows="4">
<head>Settlement of the three patriarchs</head>
<row>
<cell>The group of</cell>
<cell>settled nearby</cell>
<cell>belonged to the tribe of</cell>
</row>
<row>
<cell><name type="person">Abraham</name></cell>
<cell><name type="geographic">Mamre</name>
nearby
<name type="geographic">Hebron</name>
(eg. <reference osisRef="Gen.18">Gen 18</reference>,
<reference osisRef="Gen.13.18">Gen 13:18</reference> or
<reference osisRef="Gen.14.13">Gen 14:13</reference>. And
more in the south:
<reference osisRef="Gen.12.9">Gen 12:9</reference> or
<reference osisRef="Gen.13.1">Gen 13:1</reference>)
</cell>
<cell><name type="x-group">Caleb</name> (
<reference osisRef="Num.13">Num 13</reference>) and
later:
<name type="x-group">Judah</name>).
</cell>
</row>
<row>
<cell><name type="person">Isaac</name></cell>
<cell><name type="geographic">Beersheba</name>
(<reference osisRef="Gen.26.23-Gen.26.33">Gen 26:23-33
</reference>)
and
<name type="geographic">Beerlahairoi</name>
in the South (<reference osisRef="Gen.24.62">Gen 24:62
</reference>)
</cell>
<cell><name type="x-group">Simeon</name>
in the South and
<name type="x-group">Joseph</name>
in the North
</cell>
</row>
<row>
<cell><name type="person">Jacob</name></cell>
<cell><name
type="geographic">Peni'el-Mahanaim-Succoth</name>,
<name type="geographic">Sichem</name>
and <name type="geographic">Bethel</name>
</cell>
<cell><name type="x-group">Reuben</name>, later
<name type="x-group">Ephraim-Manasseh</name>
</cell>
</row>
</table>
This example shows the use of *table*, *row* and *cell*. You see
that in a cell you are free to use other elements from the OSIS
scheme. Here esp. *name* and *reference*.
12.6.7. figure
Another example for <figure> showing the use of the
osisRef-attributes.
<figure src="dore1.jpg"
alt="Woodcut by G. Dore, titled The Agony in the Garden"
osisRef="Luke.22.43">
<caption>The Agony in the Garden by Gustave Dore,
1855</caption>
<index index="illustrations" index1="woodcuts" index2="Dore,
Gustave" index3="Agony"/>
<note type="allusion">DORE, Gustave, grafic artist, painter and
sculptor, born 1/6/1832 in Strasburg, died 1/23/1883 in
Paris. - For over 90 books of world literature he has
created woodcutten illustrations and is especially known
for his illustraions of the bible. This work here is an
example for his extraordinary talent.</note>
</figure>
A correction of the given example is in the errata block.
21. osisIDs: Construction Rules & 22. osisRefs: Construction
Rules
I thought of another possible extension as example:
Eg. Gen.18!J for the part of the "Jahwist", E for the "Elohist",
P for the "Priest" and so on.
XSLT-Code snippets
The names of the biblical books differ from language to language.
That makes it hard for people who are not familiar with the
English names, which are normative in OSIS. They cannot identify
the abrreviations for the books. I think it would be a great help
for webdevelopers if you published some kind of code snippets for
XSLT-Files, which translate the book names.
There should be files for the most common languages like Spanish,
French, Italian, German, Russian an Chinese and a
template file for others.
Links to the subject classification systems
If authors are not librarians or doing classifications on a
regular basis they have to "learn" it (if they want to do so).
It would be helpful if there were links to websites or books
provided, where one can get information.
History of Changes & Conversion-Tools
There should be a history of changes in the OSIS core scheme in
the appendix of the manual. This ,would make it easier to convert
texts encoded with an earlier version of OSIS.
It would be nice if there were some tools for converting older
OSIS-versions into the new one, i.g. an XSLT 'program'.
The future of OSIS resp. of the manual
I know this manual is only a first draft. But I'd find it helpful
for my work if soon I had access to information on how to write
articles, books, outlines etc. in OSIS. Most of the most used
bibles seem to be converted into OSIS 2.0 right now.
There was a lack of these passages already in the last draft for
OSIS 1.5. I have no bible to encode but lots of texts since I'm
the webmaster of three websites with theological articles,
abstracts, original writings and outlines. Up to now the drafts
are esp. for the use of OSIS with bibles and there only are
remarks that texts other than bibles have to be encoded
"differently" - but not how to do this in a correct manner.
-----------------------------------------------------
---------------- Errata: ----------------------------
-----------------------------------------------------
7.3.5. publisher
The publisher element in the work element is used to indentify
^^^^^^^^^
identify
7.3.8. identifier
<identifier type="ISBN">0809617250</identifier>
<identifier type="LCCN">69-18840</identifer>
^^^^^^^^^^^^
</identifier>
7.3.14.1. subject classification systems
BILDI Biblewissenschaftliche Literaturdokumentation Innsbruck
^^^^^^
Bibelwissenschaftliche
12.5.2. l
Hebrew poety can often be divided into lines ...
^^^^^
poetry
12.6. Lists, tables, genealogies, figures and other material
A dicitonary extension is well along in development, ...
^^^^^^^^^^
dictionary
12.6.1. list
they can be distinguished by type attribute valuess such as
"ordered", ...
^^^^^^^
values ?
12.6.7 figure
<figure src="Beckmann_1917.jpg" alt="Painting by Max Beckmann,
titled
Christ and the Woman taken in Adultery"><caption>Christ and
the Woman Taken in Adultery by Max Beckmann,
1917</caption><index index="illustrations"
index1="Beckmann, Max">
^^
"/>
</figure>
The <index> tag has to be closed.
13.4. abbr
... the expansion attribute allows software to chose to diplay
the expansion ...
^^^^^^
display
20.2.10. subject
BILDI Biblewissenschaftliche Literaturdokumentation Innsbruck
^^^^^^
Bibelwissenschaftliche
22. osisRefs: Construction Rules
... in part because of the addiional capabilitie ...
^^^^^^^^^
additional
22.4. Grains (optional)
Warning: ... That is to say that you cannot put a phrase between
the square brakets. That limiation is due to the handling of
spaces in XML.
^^^^^^^ ^^^^^^^^^
brackets limitation
29.1. Ancient language editions
BHS Biblia Hebraica Stuttgartsiensa
^^^^^^^^^^^^^^^
Stuttgartensia