[osis-core] Reference Syntax Proposal - Suggestion

[Kees F. de Blois]

Dear friends,

Now that we are ready to start marking up larger chunks of text, I would
like to ask some questions and make a couple of observations re. the
Matthew 13 sample text. Please forgive my ignorance...

While verses are elements that can be segmented, chapters are marked up
as attributes of <div> elements. In the earlier (pre-Rome) approach both
of them were treated in the same way (as milestones). I take it that the
new system allows us to have divs that cross chapter boundaries.

In the parallel references following the section heading "The Purpose of
the Parables" the reference to Luke 8.9-10 is split into two. You did
not do this for the Mark 4.10-12 parallel, why?

How do we handle discourse that goes beyond section and chapter
boundaries. Shoudn't there be a <div> that encompasses vs 11-23? Right
now our div structure only partly corresponds with the way TEV organizes
the text. However, the TEV translators make it clear that Jesus'
reported speech continues after the section heading at vs 18 by using
only opening quotation marks at major breaks (vs 16, 18) and only
closing the discourse at the end of vs 23. Shouldn't we have a div for
the entire speech with nested divs and p's?

Another thing is the embedded quote from vs 14b to 15, marked by TEV by
way of single quotation marks following common practice . Right now this
is handled as a second blockquote with an embedded linegroup. Is that
good enough?

Your comments will be appreciated.

Thanks for all the good work.

Kees

> -----Original Message-----
> From: owner-osis-core@bibletechnologieswg.org
> [mailto:owner-osis-core@bibletechnologieswg.org] On Behalf Of 
> Todd Tillinghast
> Sent: 02 August 2002 20:10
> To: osis-core@bibletechnologieswg.org
> Subject: [osis-core] Reference Syntax Proposal - Suggestion
> 
> 
> Attached is an example from Bible.TEV:Matt.13 that
> demonstrates segmentation not using the osisID.
> 
> Note that the segmentation is not only of <verse> elements
> but also <q> elements.
> 
> The purpose is to demonstrate that the osisID is not needed
> to for segmentation.  And to demonstrate the consistency 
> between segmented elements of different types (verse and q in 
> this case) by using segID rather than osisID in conjunction 
> with prev and next.
> 
> Todd
> 
> 
> 
>