OSIS 211 CR

2011-08-15T04:06:01Z

Westonruter: Allow shadow/virtual elements

This page is for recording potential change requests to the OSIS XML schema.

== OSIS 2.1.1 Change Requests ==
The [http://en.wikipedia.org/wiki/Society_of_Biblical_Literature Society of Biblical Literature] conference in November 2011 provides a potential opportunity for a decision making meeting. Therefore anyone with an outstanding OSIS bug report or feature proposal for consideration for inclusion into an updated OSIS schema, please write a very concise change request here in this page, including motivating use case.

== Bugs ==

=== osisGenRegex bug ===
Currently that regex looks like [1], but it should looks like [2]:

<pre>
[1] ((((\p{L}|\p{N}|_)+)(\.(\p{L}|\p{N}|_))*:)?([^:\s])+)
[2] ((((\p{L}|\p{N}|_)+)(\.(\p{L}|\p{N}|_)+)*:)?([^:\s])+)
(missing + right here ^)
</pre>

So our document with the following element isn't valid because the
string "Strong" cannot be more than 1 character long in the current schema:
<w morph="robinson:N-NSF" lemma="lemma.Strong:βίβλος">βίβλος</w> --[[User:Osk|Osk]] 19:48, 5 November 2010 (UTC)

== Feature requests ==

=== Allow <transChange> within <w> ===
An encoder ought to be ''allowed'' to put <transChange> on elements smaller than an orthographic word. If I'm translating an instance of "λόγος", but for some reason I believe that I should translate it as "words", I ought to be able to encode <w>word<transChange>s</transChange></w>. --[[User:Osk|Osk]] 19:48, 5 November 2010 (UTC)

=== Add an element for morphology within <w> ===
Necessary for encoding documents like MORPH (WLC + morphology), we need an element to embed within <w> to carry lexical information. I suggest calling it <m> and giving it all of the attributes found on <w>. --[[User:Osk|Osk]] 19:48, 5 November 2010 (UTC)

=== Allow <transChange> within <hi> ===
A highlighted sentence or part of a sentence is a unit, including any transChange parts of it.
At the moment a highlighted sentence with a transChange will look like this:
<hi type="bold"> Texttexttext </hi><transChange><hi type="bold"> moreText</hi></transChange><hi type="bold"> TextText</hi>
<hi type="bold"> Texttexttext <transChange>moreText</transChange> TextText</hi>

This would look cleaner and would be also closer to what is meant. [[User:Refdoc|refdoc]]:[[User_Talk:Refdoc|talk]] 16:02, 3 August 2011 (MDT)
[[Category:OSIS]]

=== Allow <transChange> within <note> ===
When translating an alternate Greek version of a passage, added words need to be indicated.

=== Allow remote header reference ===
When serving short passages via web services, as valid OSIS documents, a full header is obtrusive. Also, in a collection of related documents, for example separate book files for a Bible, one centralized header would be more maintainable. The simplest approach would probably be to allow @href on the header element, to abstract some or all of the header content. See Troy's [https://groups.google.com/d/topic/openscriptures/kygOM0yPHL8/discussion related post].

===Allow shadow/virtual elements===
A second requirement for distributing valid OSIS fragments through web services is a form of virtual, or shadow, element to supply the context of the given fragment. A new global attribute for indicating this virtual status is essential to distinguish them from the actual markup of the document. In the [http://www.esvapi.org/api ESV API], they have this construct via `virtual` attribute (see description for `include-virtual-attributes``). See Troy's [https://groups.google.com/d/topic/openscriptures/kygOM0yPHL8/discussion related post] (same as previous).

=== Improve Ketiv/Qere markup ===
A ketiv or qere can consist of one or more words, and so need to be grouped and related to one another. I propose adding <ketiv> with @id, and <qere> with @idref, to contain the content (<w> elements) and allow validation of the connection. A qere with no ketiv could be marked up without the @idref.

=== Milestonable <p> ===
For documents where the primary structure is book, chapter, verse, like the Authorized Version or the Hebrew Bible, we should be able to mark up paragraphs as milestones. This would allow for equality, rather than making book, section, paragraph a privileged system.

=== Quotation types ===
From the manual (p. 43): "The rendering for quotations marks after an interruption, for example, can be distinguished using the type attribute on this element, with values such as initial, medial, and final." Please make these @type values official: initial, medial, and final.

Talk:OSIS 211 CR

2011-08-10T06:23:59Z

Westonruter: /* Introduction */

== Introduction ==

Chris, please add an introductory description to the top of this page. [[User:David Haslam|David Haslam]] 17:56, 12 December 2010 (UTC)
:Done - based on Troy's post in the Google group for Open Scriptures. [[User:David Haslam|David Haslam]] 08:11, 4 August 2011 (MDT)

== New Features ==

Troy outlined a couple new features to handle OSIS fragments: https://groups.google.com/d/msg/openscriptures/kygOM0yPHL8/3232AYNQsSIJ
Including:
* Shadow/virtual elements
* Remotely referenceable header

David Troidl also had a list of suggestions: https://groups.google.com/d/topic/openscriptures/1lyqiBSUCh8/discussion

--[[User:Westonruter|Westonruter]] 00:23, 10 August 2011 (MDT)

CrossWire Bible Society - User contributions [en]

OSIS 211 CR

Talk:OSIS 211 CR