[osis-core] osisCore.1.9

[Chris Little]

Troy,

When you convert between schemata, you need to make certain judgements 
about what was intended by the designers of each.  The Lockman DTD uses a 
paragraph division marker to indicate paragraph breaks.  They probably 
based that on the less correct usage of the HTML <P> element that you see 
floating around in so many badly encoded documents, but any decent editor 
or program like HTML Tidy will thankfully correct for you.

We do provide a mechanism for correctly marking paragraphs; it's the <p> 
element, and it's not a milestone unless you give it start & end IDs.  If 
you find Lockman's paragraph division marker, that indicates you're 
between two paragraphs.  Every one of them should be turned into 
"</p><p>".  Then just add a <p> at the start of the chapter and a </p> at 
the end.  (This is not a general purpose solution, since paragraphs could 
conceivably cross chapter boundaries, but it does not occur in the NASB.)

Lockman and OSIS have a different manner of marking paragraphs, but the 
essential fact is that they identify what constitutes a paragraph.  If you 
can identify what constitutes a paragraph according to Lockman's DTD, then 
you put it inside a <p> element in OSIS.  Marking it with <milestone 
type="x-p"/> isn't very useful since it will never be handled by any 
stylesheet or OSIS application that you don't implement yourself.  
Likewise, setting down <p/> elements at breakpoints as you suggested we 
allow, is a violation not only of the schema but of the semantics of the 
<p> element.

--Chris


On Sat, 11 Oct 2003, Troy A. Griffitts wrote:

> >> I can encode, but think it is against the OSIS 1.0 goal of PROVIDING 
> >> mechanisms to allow at least mainstream Bible publishers (of which 
> >> Lockman is probably in the top 3) to encode their Bible, using:
> >>
> >> <milestone type="x-p" />
> >>
> > 
> > Why is this contrary to allowing them to encode their Bible? I have not 
> > seen the underlying code but assume that from the manner in which you 
> > describe your encoding, they have chosen another hierarchy other than 
> > book/chapter/paragraph. That is a legitimate choice but is at variance 
> > with our decision to make other hierarchies give way to that one.
> 
> Patrick,
> 	I did not say that this was 'contrary to allowing them to encode their 
> Bible'.  I said that it was 'against the OSIS 1.0 goal of PROVIDING 
> mechanisms' for them to encode their Bible.
> 
> 	However, this is the worst case that I said I could accept for now. 
> So, if this is indeed the will of the group, I will use the 'punt' 
> mechanism of 'milestone' and 'x-' for this regular occurrence in my Bibles.
> 
> 	-Troy.
> 
> 
> _______________________________________________
> osis-core mailing list
> osis-core@bibletechnologieswg.org
> http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
>