CrossWire Bible Society - User contributions [en]

Copyright

2009-03-24T00:57:56Z

Wlerin: /* Guidelines to Follow in Corresponding with the Copyright Holders */

==Welcome==
The CrossWire has developed a variety of tools that make it easy for people to develop Bible programs. Currently people are developing Bible software that is used on Windows, Linux, Mac, PDA's, phones and even the ability to look up Bible verses right from your Internet browser.

No matter how useful the tools are, or become, their true value lies in the texts on which they operate -- the SWORD modules. These are simple files that contain the text of a variety of well known Bible translations and references. They can either be downloaded with a program's module Install Manager, or from http://www.crosswire.org/sword/modules. They are also available on the SWORD CD.

The problem, however, is that most of the modern Bible translation modules can not be used because they are [http://en.wikipedia.org/wiki/Copyright copyrighted] and we cannot distribute them with out permission.

We need your help as [[volunteers]]! To secure the permission of these copyright holders we need the help of every person using CrossWire's Bible programs and tools. You will find everything you need to be able to help right here!

==Our Policy and Strategy==
The CrossWire Bible Society would like to work with publishers and Bible societies to secure the right to distribute Bible translations for those that use SWORD software. For most Bible societies and publishers, their purpose is to distribute God's word for the benefit of others. That purpose is the same purpose we have. In light of this, the CrossWire Bible Society would like to offer our modules and tools for publishers and Bible societies to use. We will send an official letter to each Bible society and publisher offering to serve them with the tools we have. We hope that this will open up a dialog to be able to distribute their works for users of SWORD and others to use.

You may be asking where you fit into all of this? Well, you are the reason The SWORD Project, Bible societies and publishers were started. So if you sent a letter to a Bible society or publisher asking to be able to use their work with The SWORD Project's software, you would provide the basis for when we open a dialog with them. They will understand that many people support The SWORD Project's efforts, as well as their own (remember most publishers and Bible societies want to get God's word to people, that's you.) Thanks for your help!

==How You Can Help!==
* '''Contact the Copyright Holder'''<br/>You can help by sending a letter to one or more of the copyright holders of a text we do not have, asking that they would grant CrossWire the right to distribute their work. Explaining how useful the SWORD Project is, etc. For more on writing a letter and example letters see below: [[#Contacting Copyright Holders|Contacting Copyright Holders]].

* '''Research Copyright Information'''<br/>You can also help by doing research into what companies or organizations hold the copyrights on some of the texts we don't have and gathering/verifying other copyright information for modules that we do have. (You can browse a list of [http://www.crosswire.org/sword/modules modules].) Note: Where CrossWire has been given permission to distribute, Troy maintains the original correspondence granting permission. Find out what needs to be done to contact those copyright holders, their address, contact information and any other special instructions. E-mail those to [mailto:copyright@crosswire.org copyright@crosswire.org]), so we can put them up on this web site. We especially need help in respect to many of the foreign language modules. So we would appreciate the help of those that can speak many different languages.

* '''Pray For Our Efforts'''<br/>One of the biggest ways you can help is by praying for CrossWire and our efforts in trying to get these companies, etc. to license their works for distribution. We want to be able to come to appropriate agreements with Bible societies and publishers to distribute their works.

==Contacting Copyright Holders==
Below are some guidelines to follow in corresponding and some example form letters you can use.

===Guidelines to Follow in Corresponding with the Copyright Holders===
* Be friendly (remember you are a Christian, act like one)
* Explain you use BibleTime, GnomeSword, or the Windows SWORD Program. These programs use SWORD modules. Tell them you wish to be able to use their work with that program. Emphasize that each of these projects are free software (Open Source), non-commercial and receive NO payment whatsoever.
* Explain you would like to see them support The SWORD Project by either granting The CrossWire Bible Society the right to freely distribute their work or setup up a way to pay a small fee to be able to use their work. Make sure you indicate you would be willing to pay the small fee to be able to use their work.
* Indicate you would be willing to answer any questions they have. If they contact you and you are unable to answer one of their questions, forward it to Troy Griffitts at [mailto:copyright@crosswire.org copyright@crosswire.org] and Troy will find an answer for you.
* If you have sent a letter to a company or organization, e-mail Troy and let him know what you are doing, especially if you receive a reply from a company that he needs to be aware of! He wants to hear what people are doing to help and know that people are sending out letters.

===Form Letters===
Here are some form letters you can print and use.
If you come up with a really good letter that you sent to a company, would you mind sharing with everyone else?! We can turn your letter into a form letter that others can use.

'''Basic Form Letter:'''
====For users of BibleTime====
<pre>
[Date]
[Copyright Holder]
[Copyright Holder's Address]

To Whom It May Concern [or copyright holder's name],

Thank you for your time. I use BibleTime (http://www.bibletime.info). This
Bible study program uses the software library and data modules developed by
The SWORD Project (http://www.crosswire.org/sword/). The SWORD Project is a
free, non-commercial and open source project that develops software tools that
make writing Bible programs easy.
I am writing you in hope that you will grant this wonderful project the right
to distribute your work, [the name of their work, e.g. New International
Version], as a data module that can be used in any of the many Bible study
programs that use The SWORD Project's tools and data modules. I know
personally it would benefit my Bible study if I had access to your very useful
work.
I am ready and willing, not only to pay a small fee to be able to use your
work under BibleTime, but also I am standing ready to field any questions you
might have about the project. You can contact me at the address below.

In Christ,
[Your Name]
[Your Address]
[Your E-mail Address]
</pre>

====For users of Xiphos====
<pre>
[Date]
[Copyright Holder]
[Copyright Holder's Address]

To Whom It May Concern [or copyright holder's name],

Thank you for your time. I use Xiphos
(http://www.xiphos.org). This Bible study program uses the
software library and data modules developed by The SWORD Project
(http://www.crosswire.org/sword/). The SWORD Project is a free, non-commercial
and open source project that develops software tools that make writing Bible
programs easy.
I am writing you in hope that you will grant this wonderful project the right
to distribute your work, [the name of their work, e.g. New International
Version], as a data module that can be used in any of the many Bible study
programs that use The SWORD Project's tools and data modules. I know
personally it would benefit my Bible study if I had access to your very useful
work.
I am ready and willing, not only to pay a small fee to be able to use your
work under Xiphos, but also I am standing ready to field any questions you
might have about the project. You can contact me at the address below.

In Christ,
[Your Name]
[Your Address]
[Your E-mail Address]
</pre>

====For users of The SWORD Project for Windows====
<pre>
[Date]
[Copyright Holder]
[Copyright Holder's Address]

To Whom It May Concern [or copyright holder's name],

Thank you for your time. I use The SWORD Project for Windows.
This Bible study program uses the software
library and data modules developed by The SWORD Project
(http://www.crosswire.org/sword/). The SWORD Project is a free, non-commercial
and open source project that develops software tools that make writing Bible
programs easy.
I am writing you in hope that you will grant this wonderful project the right
to distribute your work, [the name of their work, e.g. New International
Version], as a data module that can be used in any of the many Bible study
programs that use The SWORD Project's tools and data modules. I know
personally it would benefit my Bible study if I had access to your very useful
work.
I am ready and willing, not only to pay a small fee to be able to use your
work under The SWORD Project for Windows, but also I am standing ready to field
any questions you might have about the project. You can contact me at the
address below.

In Christ,
[Your Name]
[Your Address]
[Your E-mail Address]
</pre>
To use these form letters, copy the text into your favorite editor. Then you must
edit them by replacing everything in square brackets "[ ]", with the right
information.

==Locked Modules==
While our desire is that all texts be free and freely available, we respect that some copyright holders wish to charge for their work. To that end, we support 128-bit encryption to lock modules. Since CrossWire is a non-income organization, we do not provide a mechanism to collect monies for locked modules. However, CrossWire will host locked modules with instructions on how to provide payment for an unlock key.
===FAQ about Locked Modules===
'''Q: Why are some modules locked?'''<br/>
A: Some copyright owners have chosen to make their modules available for a fee.

'''Q: Is there anyway to unlock the modules by paying a fee?'''<br/>
A: Each locked module that we host has instructions on how to purchase an unlock code.

'''Q: I have a print version of a translation, can I have the unlock code for the electronic version of this translation?'''<br/>
A: There is no current law, at least in the United States, that allows an owner of a print version to also have the right to an electronic version of the same work. For example if you bought a copy of a novel in print, you could not go to one of the many e-book store sites and ask for the elctronic version of that same novel.

'''Q: I have purchased and lost a key to a locked module. Can you tell me what it is?'''<br/>
A: The SWORD Project does not sell or handle locked module keys. You should contact the module vendor for help in this matter.

'''Q: I have used another Bible Study program and have purchased the unlock code for a translation for that program, can I have the unlock code for The SWORD Project program?'''<br/>
A: The SWORD Project's agreement with the module vendor precludes this.

==Feedback==
Please keep us informed, by sending us e-mail at [[mailto:copyright@crosswire.org copyright@crosswire.org]].

==Next steps==
For CrossWire to host a module, the text either must be in the Public Domain or the Copyright Holder must give written permission to CrossWire. For us to make the module, we require an e-text. It can be in whatever format that the Copyright Holder wishes to provide. We can provide assistance to copyright holders if they choose to make the module themselves.

==Information on Copyrights==
CrossWire respects Copyright and other Intellectual Property Rights.

As such, it discourages the creation, or conversion of resources into a format that is used by The Sword Project unless permission to do so has been obtained.

===US Copyright Law===

''The [http://en.wikipedia.org/wiki/Digital_Millennium_Copyright_Act Digital Millennium Copyright Act] of 1998'' stands as current US Copyright Law.

Under US Copyright law, there is no differentiation between commercial, and non-commercial purposes. Unauthorized creation is a violation of the copyright act. Unauthorized distribution is a violation of the copyright act.

*There is no "safe harbor" defense for creating unauthorized derivative works.

*There is no "safe harbor" defense for unauthorized distribution of copyright material.

===Public Domain===

Generally speaking, in the United States, “Public Domain” can be assumed if all of the following conditions are met:
* The material was originally published in English;
* The material was distributed in the United States prior to 1923;

If those conditions are not met, then the only safe assumption one can make, is that the material is under copyright protection. Obtain permission for creating a resource prior to doing so.

For a more complete description of when a text is Public Domain see: http://www.copyright.cornell.edu/public_domain

===Fair Use Doctrine===
In recent years, courts have greatly restricted what constitutes "Fair Use". US Statute Law does not specifically define "Fair Use".

When an organization claims "Fair Use", the courts apply a four prong test.
* Type of organization that used the material;
* How easy the material is to obtain;
* How old the material is;
* What the material is used for;
* Commercial activity related to distribution;

===International Copyright Law===
For further information on international copyright law, please refer to the following links:
* [http://en.wikipedia.org/wiki/Berne_Convention_for_the_Protection_of_Literary_and_Artistic_Works Berne Convention for the Protection of Literary and Artistic Works]
* [http://en.wikipedia.org/wiki/World_Intellectual_Property_Organization_Copyright_Treaty World Intellectual Property Organization Copyright Treaty]

Talk:OSIS Tutorial

2009-03-24T00:54:15Z

Wlerin: /* Long s */

== Long s ==

I would like to take issue with the representation of the "long s" of the original text with the letter 'f'.

If you look carefully at the graphical representation you link to you will notice that while the letter f has a cross-stroke (extending both sides of the vertical), the long s does NOT have a cross stroke, but merely a stub extending to the left of the vertical.

In fonts corresponding to this older typography, a "long s" was used at the beginning and in the middle of words, while a "round s" (which looks like our s) was used at the end.

It is thus plain wrong (in that it alters the meaning of the content, "fifh" not being the same word as "fish" at all, nor, obviously, to move to the New Testament, is Jefus the same as Jesus) to write f where the original has a long s -- the proper representation of long s in a font which does not have that glyph is the ordinary, "round" s.

:Please sign edits to discussion pages by adding four tilde. This get converted automatically to your username with a timestamp. [[User:David Haslam|David Haslam]] 15:13, 21 November 2008 (UTC)

Long s is equivalent to &#383; and I have replaced 'f' with it in the example text, where appropriate. --[[User:Wlerin|Wlerin]] 00:53, 24 March 2009 (UTC)

Talk:OSIS Tutorial

2009-03-24T00:53:56Z

Wlerin: /* Long s */

== Long s ==

I would like to take issue with the representation of the "long s" of the original text with the letter 'f'.

If you look carefully at the graphical representation you link to you will notice that while the letter f has a cross-stroke (extending both sides of the vertical), the long s does NOT have a cross stroke, but merely a stub extending to the left of the vertical.

In fonts corresponding to this older typography, a "long s" was used at the beginning and in the middle of words, while a "round s" (which looks like our s) was used at the end.

It is thus plain wrong (in that it alters the meaning of the content, "fifh" not being the same word as "fish" at all, nor, obviously, to move to the New Testament, is Jefus the same as Jesus) to write f where the original has a long s -- the proper representation of long s in a font which does not have that glyph is the ordinary, "round" s.

:Please sign edits to discussion pages by adding four tilde. This get converted automatically to your username with a timestamp. [[User:David Haslam|David Haslam]] 15:13, 21 November 2008 (UTC)

Long s is equivalent to &#383;, and I have replaced f with it in the example text, where appropriate. --[[User:Wlerin|Wlerin]] 00:53, 24 March 2009 (UTC)

OSIS Tutorial

2009-03-24T00:38:55Z

Wlerin: /* Creating a Basic OSIS Document */ -- Undoing a very minor change. See top of linked image.

=Creating a Basic OSIS Document=
Creating a basic OSIS document can be an easy task with just a little direction, which this brief tutorial hopes to provide.

Throughout this tutorial, we will be marking up a Bible excerpt: Gen 1:1-3, from the King James Version of the Bible, 1611 edition. The excerpt reads as follows:
THE FIRST BOOKE OF MOSES, called GENESIS.
Chap.j.
The creation of the world.
1 The creation of Heauen and Earth, 3 of the
light, 6 of the firmament, 9 of the earth ſe-
parated from the waters, 11 and made fruit-
full, 14 of the Sunne, Moone and Starres,
20 of fiſh and fowle, 24 of beaſts and cat-
tell, 26 of Man in the Image of God. 29 Al-
ſo the appointment of food.
1. In the beginning
God created the
Heauen and the
Earth.
2. And the
earth was with=
out forme , and
voyd;and darken=
effe ''was'' vpon
the face of the deepe : And the Spirit
of God mooued vpon the face of the
waters.
3. And God ſaid, *Let there be light :
and there was light.
* Pſal.33.6. and 136.5. acts.14.15. and 17.24. hebr.11.3.

While this looks like a bunch of typos, it is a faithful representation of the original.<br/>
For an image of this see: http://dewey.library.upenn.edu/sceti/printedbooksNew/index.cfm?TextID=kjbible&PagePosition=77<br/>
For the entire first chapter of Genesis see: [[KJV 1611]]

==XML==
At the core, OSIS is an XML markup standard and must comply with rules for basic XML documents. This means that we will need a basic XML header to begin our document. This line should do just fine:
<?xml version="1.0" encoding="UTF-8" ?>

==The Root Node==
The root node for an OSIS document has the element name <code>osis</code>. Since OSIS uses XML Schema to define itself, we can place a link in the root node declaring our document's structure definition (we're an OSIS XML document, not just ''any'' XML document). Our complete root node will look like this:
<osis xmlns="http://www.bibletechnologies.net/2003/OSIS/namespace"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bibletechnologies.net/2003/OSIS/namespace osisCore.2.1.xsd">

==The Work Container==
OSIS documents can either be a corpus of multiple works, or merely a single text, like the KJV Bible. The latter will be our OSIS document type. We declare this by placing our entire work in an <code>osisText</code> element. This element will include attributes that declare our work's id and default reference scheme. The values of these elements are not as important as their function. They are used to link to a <code>work</code> section that we will discuss a little later, that completely define two functions for our document. For now, we'll just set them to: "KJV" and "defaultReferenceScheme". Here is our <code>osisText</code> line, which also includes the default language of our document:
<osisText osisIDWork="KJV" osisRefWork="defaultReferenceScheme" xml:lang="en">

==The Header==
Each OSIS work must have a <code>header</code> section that defines information about the text. This will include copyright and cataloguing data, among other bibliographic information. The <code>header</code> not only contains information about our work, it also contains basic information about any works which we reference in our text. Below is our entire <code>header</code> for our text. We'll explain it in more detail, below.
<header>
<work osisWork="KJV">
<title>King James Version of 1611</title>
<identifier type="OSIS">KJV.TutorEncoding</identifier>
<refSystem>Bible.KJV</refSystem>
</work>
<work osisWork="defaultReferenceScheme">
<refSystem>Bible.KJV</refSystem>
</work>
</header>

Our <code>header</code> includes two <code>work</code> elements. Each <code>work</code> element is uniquely distinguished by its <code>osisWork</code> attribute.

The first <code>work</code> element defines ''our'' work. This is designated by matching the <code>osisWork</code> attribute value to the <code>osisIDWork</code> attribute value of our <code>osisText</code> element in the section above. This sounds confusing but simply notice they both have the value "KJV"-- that's all there is to it.

Inside this work, we have an element that defines our <code>title</code>. We also have a special <code>identifier</code> element with a <code>type</code> value of "OSIS". This <code>identifier</code> element must be present and is used for assigning a canonical name to our OSIS document. We're claiming the "KJV.TutorEncoding" identifier for
our document, in case anyone wants to refer to our text if, say, we're included in a large library of OSIS documents.

When marking up Biblical materials, we have a need to reference certain <u>portions</u> of our materials, and not just the entire document. To allow this, we must provide two sides of the same coin:
*I am referencing this portion;
*I ''am'' this portion

The two functions are facilitated in OSIS with the <code>osisRef</code> and <code>osisID</code> attributes, respectively, and are reviewed in more detail in the next section.

The <code>refSystem</code> element in our work states that whenever we markup a portion of our text as something like, "Genesis 1:1" ''(side 2 of the coin)'' we are using the Bible.KJV reference system.

Remember that we had a second attribute on <code>osisText</code>, in the section above. This attribute is used to state which reference scheme our document will use by default, when citing references ''(side 1 of the coin)'' in our text. The second work element above matches our reference scheme, and declares that we are using the Bible.KJV reference scheme as our default.

==Marking and Referencing==
Before going any further, we should talk about an OSIS concept that enables us to reference pieces of other works, and also label pieces of our own work as targets of references. These two concepts are represented by the OSIS attributes <code>osisRef</code> and <code>osisID</code>, respectively. The concepts are fairly straight forward, and in their simplest incarnation, easy to comprehend. As an example, let's say we have a commentary that wishes to reference James 1:19. OSIS includes a <code>reference</code> element for this purpose, and for our example, an instance may look something like:
Please see <reference osisRef="Jas.1.19">James 1:19</reference>

The counterpart, <code>osisID</code>, is very similar. Let's say a Bible wishes to mark a section as ''being'' James 1:19. OSIS provides a <code>verse</code> element for this, and our Bible may include something like:
<verse osisID="Jas.1.19">Wherefore, my beloved brethren, let every man be swift to hear, slow to speak, slow to wrath:</verse>

==Text Divisions==
OSIS works can be subdivided into arbitrary smaller sections, if desired. For Bibles, it usually makes sense to keep the traditional divisions that have been used for decades: Testament, Book, Chapter, Verse. We will use these for our text. OSIS provides a <code>div</code> element to facilitate some of these divisions; other divisions are more specifically supported. Here are our 3 divisions, at the beginning of our work to get us down to Genesis, chapter 1.
<div type="x-testament">
<div type="book" osisID="Gen">
<chapter osisID="Gen.1">

==Actual Text==
Now ''finally'' we're ready to start including our actual Bible text in the document. The first verse is Genesis 1:1. We'd like to let the world know the identification of this part of our document, so we'll include the text in a <code>verse</code> element with an appropriate <code>osisID</code> attribute. Here it is:
<verse osisID="Gen.1.1">In the beginning God created the Heauen and the Earth.</verse>

==Literal Translations==
The text that we've chosen to encode claims to be a special type of Bible translation, sometimes referred to as a ''literal'' translation. Translations of these type attempt to preserve --as best they can-- the wording of the text from their original language. These works all tend to use similar mechanisms to indicate where they have needed to deviate from what was presented in the original source, for the purpose of clear target language understanding. Our second verse includes one such anomaly-- the second instance of the word ''was''. Most printed editions of the KJV will ''italicize'' this word, indicating that there was no such Hebrew counterpart that was translated into the English ''"was"'', but without this word, the sentence would not represent correct English. Since OSIS is ''presentation-agnostic'', instead of delegating a display type like ''italic'' for this purpose, we will mark the anomaly and let the publisher choose how they would like it displayed. OSIS provides a <code>transChange</code> element to allow these translations to mark deviations such as these, and a <code>changeType</code> attribute on this element to indicate the type of change made. Here is our Genesis 1:2, which includes this markup.
<verse osisID="Gen.1.2">
And the earth was without forme , and voyd;and darkeneffe
<transChange changeType="added">was</transChange>
vpon the face of the deepe : And the Spirit of God mooued
vpon the face of the waters.
</verse>

==Quotes==
Our last verse that we will markup includes a quote by God, Himself! Let's be sure to get this one correct. In OSIS, quotes can be marked with a <code>q</code> element. A <code>speaker</code> attribute is also optionally allowed, which we will use to designate who is speaking in this portion of Scripture. Since the orthography of the KJV had no quotation marks, this is indicated with an empty <code>marker</code> attribute.
<verse osisID="Gen.1.3">
And God faid, *<q speaker="God" marker="">Let there be light</q> : and there was light.
</verse>

==Notes==
Genesis 1:3 has a note that still needs to be included. In OSIS, notes are inlined at the point of inclusion. Notes also have various types. In this instance, the note is a cross-reference. To retain the original orthography we use the <code>n</code> attribute to provide the original marker.
<note type="crossReference" n="*">
<reference osisRef="Ps.33.6">Pfal.33.6.</reference>
and
<reference osisRef="Ps.136.5">136.5.</reference>
<reference osisRef="Acts.14.15">acts.14.15.</reference>
and
<reference osisRef="acts.17.24">17.24.</reference>
<reference osisRef="Heb.11.3">hebr.11.3.</reference>
</note>

The entire verse would be:
<verse osisID="Gen.1.3">
And God faid,
<note type="crossReference" n="*">
<reference osisRef="Ps.33.6">Pfal.33.6.</reference>
and
<reference osisRef="Ps.136.5">136.5.</reference>
<reference osisRef="Acts.14.15">acts.14.15.</reference>
and
<reference osisRef="acts.17.24">17.24.</reference>
<reference osisRef="Heb.11.3">hebr.11.3.</reference>
</note>
<q speaker="God" marker="">Let there be light</q>
: and there was light.
</verse>

==Finishing up==
Remember, in XML, we must have closing marks for every opening mark of an element. Let's be sure to close all of our elements before finishing up our OSIS text. First we'll close our Chapter, then Book, then Testament.
</chapter>
</div>
</div>

Then we'll close our <code>osisText</code>.
</osisText>

and finally, our root <code>osis</code> element
</osis>

==Conclusion==
And that's it!!! Congratulations, you've just walked through your first entire OSIS document. With power comes complexity, so there is much more to learn if you wish to unlock the features of OSIS that will allow you to more richly markup your texts. But some people may prefer to keep the more intricate aspects of OSIS under lock and key, depending on their needs. With OSIS, the choice is yours, and you now know everything necessary to start encoding your own texts, making them usable by organization all around the world in a variety of presentation venues. Blessings in your endeavours.

OSIS Tutorial

2009-03-24T00:37:26Z

Wlerin: Replacing "f" with "ſ" to more faithfully represent the original. also a few other minor tweaks for the same purpose.

=Creating a Basic OSIS Document=
Creating a basic OSIS document can be an easy task with just a little direction, which this brief tutorial hopes to provide.

Throughout this tutorial, we will be marking up a Bible excerpt: Gen 1:1-3, from the King James Version of the Bible, 1611 edition. The excerpt reads as follows:
THE FIRST BOOKE OF MOSES, called GENESIS.
Chap.I.
The creation of the world.
1 The creation of Heauen and Earth, 3 of the
light, 6 of the firmament, 9 of the earth ſe-
parated from the waters, 11 and made fruit-
full, 14 of the Sunne, Moone and Starres,
20 of fiſh and fowle, 24 of beaſts and cat-
tell, 26 of Man in the Image of God. 29 Al-
ſo the appointment of food.
1. In the beginning
God created the
Heauen and the
Earth.
2. And the
earth was with=
out forme , and
voyd;and darken=
effe ''was'' vpon
the face of the deepe : And the Spirit
of God mooued vpon the face of the
waters.
3. And God ſaid, *Let there be light :
and there was light.
* Pſal.33.6. and 136.5. acts.14.15. and 17.24. hebr.11.3.

While this looks like a bunch of typos, it is a faithful representation of the original.<br/>
For an image of this see: http://dewey.library.upenn.edu/sceti/printedbooksNew/index.cfm?TextID=kjbible&PagePosition=77<br/>
For the entire first chapter of Genesis see: [[KJV 1611]]

==XML==
At the core, OSIS is an XML markup standard and must comply with rules for basic XML documents. This means that we will need a basic XML header to begin our document. This line should do just fine:
<?xml version="1.0" encoding="UTF-8" ?>

==The Root Node==
The root node for an OSIS document has the element name <code>osis</code>. Since OSIS uses XML Schema to define itself, we can place a link in the root node declaring our document's structure definition (we're an OSIS XML document, not just ''any'' XML document). Our complete root node will look like this:
<osis xmlns="http://www.bibletechnologies.net/2003/OSIS/namespace"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bibletechnologies.net/2003/OSIS/namespace osisCore.2.1.xsd">

==The Work Container==
OSIS documents can either be a corpus of multiple works, or merely a single text, like the KJV Bible. The latter will be our OSIS document type. We declare this by placing our entire work in an <code>osisText</code> element. This element will include attributes that declare our work's id and default reference scheme. The values of these elements are not as important as their function. They are used to link to a <code>work</code> section that we will discuss a little later, that completely define two functions for our document. For now, we'll just set them to: "KJV" and "defaultReferenceScheme". Here is our <code>osisText</code> line, which also includes the default language of our document:
<osisText osisIDWork="KJV" osisRefWork="defaultReferenceScheme" xml:lang="en">

==The Header==
Each OSIS work must have a <code>header</code> section that defines information about the text. This will include copyright and cataloguing data, among other bibliographic information. The <code>header</code> not only contains information about our work, it also contains basic information about any works which we reference in our text. Below is our entire <code>header</code> for our text. We'll explain it in more detail, below.
<header>
<work osisWork="KJV">
<title>King James Version of 1611</title>
<identifier type="OSIS">KJV.TutorEncoding</identifier>
<refSystem>Bible.KJV</refSystem>
</work>
<work osisWork="defaultReferenceScheme">
<refSystem>Bible.KJV</refSystem>
</work>
</header>

Our <code>header</code> includes two <code>work</code> elements. Each <code>work</code> element is uniquely distinguished by its <code>osisWork</code> attribute.

The first <code>work</code> element defines ''our'' work. This is designated by matching the <code>osisWork</code> attribute value to the <code>osisIDWork</code> attribute value of our <code>osisText</code> element in the section above. This sounds confusing but simply notice they both have the value "KJV"-- that's all there is to it.

Inside this work, we have an element that defines our <code>title</code>. We also have a special <code>identifier</code> element with a <code>type</code> value of "OSIS". This <code>identifier</code> element must be present and is used for assigning a canonical name to our OSIS document. We're claiming the "KJV.TutorEncoding" identifier for
our document, in case anyone wants to refer to our text if, say, we're included in a large library of OSIS documents.

When marking up Biblical materials, we have a need to reference certain <u>portions</u> of our materials, and not just the entire document. To allow this, we must provide two sides of the same coin:
*I am referencing this portion;
*I ''am'' this portion

The two functions are facilitated in OSIS with the <code>osisRef</code> and <code>osisID</code> attributes, respectively, and are reviewed in more detail in the next section.

The <code>refSystem</code> element in our work states that whenever we markup a portion of our text as something like, "Genesis 1:1" ''(side 2 of the coin)'' we are using the Bible.KJV reference system.

Remember that we had a second attribute on <code>osisText</code>, in the section above. This attribute is used to state which reference scheme our document will use by default, when citing references ''(side 1 of the coin)'' in our text. The second work element above matches our reference scheme, and declares that we are using the Bible.KJV reference scheme as our default.

==Marking and Referencing==
Before going any further, we should talk about an OSIS concept that enables us to reference pieces of other works, and also label pieces of our own work as targets of references. These two concepts are represented by the OSIS attributes <code>osisRef</code> and <code>osisID</code>, respectively. The concepts are fairly straight forward, and in their simplest incarnation, easy to comprehend. As an example, let's say we have a commentary that wishes to reference James 1:19. OSIS includes a <code>reference</code> element for this purpose, and for our example, an instance may look something like:
Please see <reference osisRef="Jas.1.19">James 1:19</reference>

The counterpart, <code>osisID</code>, is very similar. Let's say a Bible wishes to mark a section as ''being'' James 1:19. OSIS provides a <code>verse</code> element for this, and our Bible may include something like:
<verse osisID="Jas.1.19">Wherefore, my beloved brethren, let every man be swift to hear, slow to speak, slow to wrath:</verse>

==Text Divisions==
OSIS works can be subdivided into arbitrary smaller sections, if desired. For Bibles, it usually makes sense to keep the traditional divisions that have been used for decades: Testament, Book, Chapter, Verse. We will use these for our text. OSIS provides a <code>div</code> element to facilitate some of these divisions; other divisions are more specifically supported. Here are our 3 divisions, at the beginning of our work to get us down to Genesis, chapter 1.
<div type="x-testament">
<div type="book" osisID="Gen">
<chapter osisID="Gen.1">

==Actual Text==
Now ''finally'' we're ready to start including our actual Bible text in the document. The first verse is Genesis 1:1. We'd like to let the world know the identification of this part of our document, so we'll include the text in a <code>verse</code> element with an appropriate <code>osisID</code> attribute. Here it is:
<verse osisID="Gen.1.1">In the beginning God created the Heauen and the Earth.</verse>

==Literal Translations==
The text that we've chosen to encode claims to be a special type of Bible translation, sometimes referred to as a ''literal'' translation. Translations of these type attempt to preserve --as best they can-- the wording of the text from their original language. These works all tend to use similar mechanisms to indicate where they have needed to deviate from what was presented in the original source, for the purpose of clear target language understanding. Our second verse includes one such anomaly-- the second instance of the word ''was''. Most printed editions of the KJV will ''italicize'' this word, indicating that there was no such Hebrew counterpart that was translated into the English ''"was"'', but without this word, the sentence would not represent correct English. Since OSIS is ''presentation-agnostic'', instead of delegating a display type like ''italic'' for this purpose, we will mark the anomaly and let the publisher choose how they would like it displayed. OSIS provides a <code>transChange</code> element to allow these translations to mark deviations such as these, and a <code>changeType</code> attribute on this element to indicate the type of change made. Here is our Genesis 1:2, which includes this markup.
<verse osisID="Gen.1.2">
And the earth was without forme , and voyd;and darkeneffe
<transChange changeType="added">was</transChange>
vpon the face of the deepe : And the Spirit of God mooued
vpon the face of the waters.
</verse>

==Quotes==
Our last verse that we will markup includes a quote by God, Himself! Let's be sure to get this one correct. In OSIS, quotes can be marked with a <code>q</code> element. A <code>speaker</code> attribute is also optionally allowed, which we will use to designate who is speaking in this portion of Scripture. Since the orthography of the KJV had no quotation marks, this is indicated with an empty <code>marker</code> attribute.
<verse osisID="Gen.1.3">
And God faid, *<q speaker="God" marker="">Let there be light</q> : and there was light.
</verse>

==Notes==
Genesis 1:3 has a note that still needs to be included. In OSIS, notes are inlined at the point of inclusion. Notes also have various types. In this instance, the note is a cross-reference. To retain the original orthography we use the <code>n</code> attribute to provide the original marker.
<note type="crossReference" n="*">
<reference osisRef="Ps.33.6">Pfal.33.6.</reference>
and
<reference osisRef="Ps.136.5">136.5.</reference>
<reference osisRef="Acts.14.15">acts.14.15.</reference>
and
<reference osisRef="acts.17.24">17.24.</reference>
<reference osisRef="Heb.11.3">hebr.11.3.</reference>
</note>

The entire verse would be:
<verse osisID="Gen.1.3">
And God faid,
<note type="crossReference" n="*">
<reference osisRef="Ps.33.6">Pfal.33.6.</reference>
and
<reference osisRef="Ps.136.5">136.5.</reference>
<reference osisRef="Acts.14.15">acts.14.15.</reference>
and
<reference osisRef="acts.17.24">17.24.</reference>
<reference osisRef="Heb.11.3">hebr.11.3.</reference>
</note>
<q speaker="God" marker="">Let there be light</q>
: and there was light.
</verse>

==Finishing up==
Remember, in XML, we must have closing marks for every opening mark of an element. Let's be sure to close all of our elements before finishing up our OSIS text. First we'll close our Chapter, then Book, then Testament.
</chapter>
</div>
</div>

Then we'll close our <code>osisText</code>.
</osisText>

and finally, our root <code>osis</code> element
</osis>

==Conclusion==
And that's it!!! Congratulations, you've just walked through your first entire OSIS document. With power comes complexity, so there is much more to learn if you wish to unlock the features of OSIS that will allow you to more richly markup your texts. But some people may prefer to keep the more intricate aspects of OSIS under lock and key, depending on their needs. With OSIS, the choice is yours, and you now know everything necessary to start encoding your own texts, making them usable by organization all around the world in a variety of presentation venues. Blessings in your endeavours.