[osis-core] <chapter> in <lg>

[Todd Tillinghast]

In the CEV Gen.50 starts in the middle of a paragraph.  Do you have the
CEV edition that Mike sent out?  If you don't I can scan the page and
email it to you.  There are a couple of other cases in the TEV, as well
as other translations.

It seems we are faced with one of three options.  1) Allow <chapter> to
exist everywhere <verse> does or 2) backtrack and make special provison
of chapter and verse milestones (make new and milestone only elements)
that do not follow the pattern of having the container element also act
as a milestone or 3) backtrack on the entire concept of containers and
milestones as the same elements.

I lean toward option 1, it is not purely an ANY model and we have
already stated that it is best practice that a <chapter> is ALWAYS
broken when other elemetns from the section/paragraph/list/lg heirarchy
overlap with the BCV heirarchy, so in practice it should not lead to
strange encodings.

I don't think it is really an option to tell people they have to
terminate an element so that the chapter marker can be inserted.

Todd

> -----Original Message-----
> From: osis-core-admin@bibletechnologieswg.org 
> [mailto:osis-core-admin@bibletechnologieswg.org] On Behalf Of 
> Patrick Durusau
> Sent: Saturday, May 31, 2003 7:57 PM
> To: osis-core@bibletechnologieswg.org
> Subject: Re: [osis-core] <chapter> in <lg>
> 
> 
> Troy,
> 
> Troy A. Griffitts wrote:
> 
> > Maybe I'm daft, but is the question can <chapter> contain <p> ?  If
> > so, I am very much in favour of this.  I can point out MANY 
> occurances 
> > of this if, indeed, this is the discussion topic.  Since 
> traditional 
> > chapter breaks are absolutely rediculous 20+% of the time, I would 
> > suggest that paragraphs would span traditional chapter division as 
> > least this much.
> 
> No, I understood the question to be a <p> containing a <chapter>.
> 
> Not sure how you can say that a <p> crosses a <chapter> 
> boundary since 
> in traditional printing you would have an end to the <p> just 
> before the 
> end of the <chapter> and then a new <chapter> followed by a 
> new <p>. Not 
> sure how else it would be represented in print.
> 
> Sorry, are we just completely missing each other?
> 
> Patrick
> 
> 
> 
> >
> >     -Troy.
> >
> >
> >
> > Patrick Durusau wrote:
> >
> >> Todd,
> >>
> >> Well, and we have the case with Rev. 12:17 (18? in newer versions)
> >> that Chris pointed out.
> >>
> >> Suspect that if content models to be meaningful that we 
> won't be able
> >> to accomodate every oddity in the text. Otherwise, we wind 
> up the the 
> >> OED *ANY* content model, which makes stylesheets and 
> processing all 
> >> but impossible.
> >>
> >> Since there are only two cases that have been pointed out, 
> one with a
> >> <lg> and Chris's report of what sounds like (I don't have 
> a version 
> >> to verify this observation) the split of a verse (I am 
> sure there are 
> >> others but also oddities and not regular occurrences), my first 
> >> reaction is to close the element in question and then close the 
> >> chapter. That at least preserves the book/chapter division for the 
> >> tradition you are encoding, although it then raises the 
> question of 
> >> linking the part you split.
> >>
> >> Comments, thoughts?
> >>
> >> Patrick
> >>
> >> Todd Tillinghast wrote:
> >>
> >>> Bible.CEV.Eccl.10 starts in the middle of a <lg>. This is a pretty
> >>> ugly case.
> >>>
> >>> Todd
> >>>
> >>>
> >>> _______________________________________________
> >>> osis-core mailing list
> >>> osis-core@bibletechnologieswg.org 
> >>> http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
> >>>
> >>>  
> >>>
> >>
> >
> >
> > _______________________________________________
> > osis-core mailing list
> > osis-core@bibletechnologieswg.org 
> > http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
> >
> 
> -- 
> Patrick Durusau
> Director of Research and Development
> Society of Biblical Literature
> Patrick.Durusau@sbl-site.org
> Co-Editor, ISO 13250, Topic Maps -- Reference Model
> 
> 
> 
> 
> _______________________________________________
> osis-core mailing list
> osis-core@bibletechnologieswg.org 
> http://www.bibletechnologieswg.org/mailman/lis> tinfo/osis-core
>