OSIS Bibles - CrossWire Bible Society. From CrossWire Bible Society OSIS is an XML Schema definition for Bibles and other Biblical research texts, which enables ministries and other organizations to collaborate more easily. Traditionally, these organizations have stored their documents in disparate, proprietary markups, making it difficult when they wish to share in service with each other. OSIS provides a common markup for multiple visions. CrossWire is committed to supporting the OSIS initiative. We have developed OSIS import and export tools which work with our SWORD engine, making OSIS documents available to all of our SWORD software. The latest OSIS Schema definition and supporting information is available at: [1] ↑ Link broken.
Introduction This page is for practical examples of how to encode a Bible in OSIS 2.1.1 for building a SWORD module with osis2mod. Every OSIS SWORD module must be created from a well-formed and valid OSIS 2.1.1 document. See also OSIS Book Name Abbreviations. Body For: Home - The OSIS Website. XML Schema Documentation. About DocFlex Technology. 1. Introduction DocFlex is a new technology for rapid development of template-based documentation/report generators built into Java™ applications.
It is based on an idea that most of the data a typical application operate have a tree or network structure and generally can be represented in the form similar to Document Object Model (DOM) of XML files. (In fact, that's why XML is widely used to export/import those data and exchange between applications.) Following that idea, it is possible to imagine that if we had some abstract interface that represents most of the practically used data sources in a from similar to DOM, we could process such data using a single tool, which is based only on the concepts of XML (possibly with a few enhancements) and employs available standards and approaches developed around it.
The natural way to achieve all those goals would be to introduce a new programming medium in the form of a scripting language or templates. 2. A designer GUI can visualize everything. HTML, XML, OSIS, XSEM, ThML, USFM...: What a biblical scholar sh. If the title to this post hasn't already caused your eyes to glaze over, this post is intended to provide a brief overview of what is happening with biblical encoding systems.
This is a really simplified description with all sorts of caveats associated with such generalizations, but this should at least familiarize a biblical scholar with the field of biblical text encoding and equip him/her to name-drop acronyms with the geekiest of them. We have all become quite accustomed to reading digital versions of texts related to biblical studies, but there is considerable attention being paid to how that text is presented and how it may be enhanced. For viewing on the web (and in some programs), the system used is HTML=HyperText Markup Language. HTML only describes how the data looks on a page: paragraphs, lists, bold, italic, etc.
These codes are consistent, are established by a worldwide consortium, and they are important so that different browsers know how to display the data.