[osis-core] open issues

[Todd Tillinghast]

Gets to contents of verse 2 in what sense?

If creating a pure book->chapter->verse transformation if would put an
if condition testing for the presence of a next attribute.  If present I
would call a match based on an element with an attribute verseID that
matches the value of the next attribute.

This sort of thing would be about the same regardless of the approach
for the markup.  

The alternative that was rejected months ago is the approach of having
the basic text held in a single simple hierarchy.  Then have alternate
hierarchies exist that point to places in the central hierarchy.

The alternate hierarchies could be held near to top of the tree or in a
separate document.

This is no more complicated than milestones to navigate and is easier to
create.

Todd

> -----Original Message-----
> From: owner-osis-core@bibletechnologieswg.org [mailto:owner-osis-
> core@bibletechnologieswg.org] On Behalf Of Troy A. Griffitts
> Sent: Wednesday, June 05, 2002 4:12 PM
> To: osis-core@bibletechnologieswg.org
> Subject: Re: [osis-core] open issues
> 
> Todd,
> 	Couple issues:
> 		1) quotes in this example where the problem tag.  What
if
> phrase
> linquistic annotation or critical markup are the problem in the
future.
>   You solution to make the problem tag a milestone is good, and is, in
> theory, exactly what I'm suggesting, only allow any tag to become a
> milestone, if necessary.
> 
> 	2)  Write me something that easily gives me the contents of
verse 2.
> Segmentation seems complex to achieve a goal I've yet to understand.
> 
> 
> SIDENOTE: why do we have next/prev?  Are we assuming that segments may
> be out of order?
> 
> 
> 
> Todd Tillinghast wrote:
> > Is there an end to the quote that starts with "Thus".
> >
> > If I got your example correctly how about the following seem to you.
> > <p>
> > 	<verse verseID="1">Then God said, <qStart qID="1" level="1"/>Say
to
> my
> > people: <qStart qID="1" level="2"/>Thus says the LORD, <qStart
qID="1"
> > level="3"/>Repent! </verse>
> > 	<verse verseID="2" next="2@word:5(How)">You backsliding markup
> > authors.<qEnd qID="1" level="3"/></verse>
> > <p>
> > 	<verse verseID="2@word:5(How)" prev="2">How often have I desired
to
> give
> > you a good markup. </verse>
> > 	<verse verseID="3">But you were unwilling.</verse>
> > </p>
> >
> > The example you give seems to support the notion that if quotes are
> treated
> > using milestones that other overlapping hierarchies are fairly easy
to
> > support with segmentation assuming you do the trick with the "role"
for
> > verse like behavior.  (Still no milestones for verses.)
> >
> > Thoughts?
> >
> > Todd
> >
> >
> >>-----Original Message-----
> >>From: owner-osis-core@bibletechnologieswg.org
> >>[mailto:owner-osis-core@bibletechnologieswg.org]On Behalf Of Troy A.
> >>Griffitts
> >>Sent: Wednesday, June 05, 2002 3:30 PM
> >>To: osis-core@bibletechnologieswg.org
> >>Subject: [osis-core] open issues
> >>
> >>
> >>Not sure if anyone knows or cares, but most all of my issues brought
up
> >>in my last messages are still on the table:
> >>
> >>archive, if anyone needs the old messages:
> >>
> >>http://www.bibletechnologieswg.org/cgi-bin/lwgate/OSIS-CORE%40BIBL
> >
> > ETECHNOLOGIESWG.ORG/archives/
> >
> >>Not wanting to be a wrench in the works, but I still feel our gears
are
> >>turning fast down a wrong path.
> >>
> >>Specifically: segmentation isn't elegant and we can't anticipate all
> >>overlapping cases.  Try a few verses from a Prophetic text (e.g. Ez
> >>39:1-) e.g (not from Ez).
> >>
> >>1. Then God said, "Say to my people: 'Thus says the LORD, "Repent!
2.
> >>You backsliding markup authors."
> >>	How often have I desired to give you a good markup. 3. But you
were
> >>unwilling.
> >>
> >>
> >>Try to add phrase level annotation, critical markup and other tags
to
> >>that and you have no hope of a human understanding or getting it
right,
> >>muchless our schema to allow such things.  Anything can be forced to
> >>work.  I just don't see why our milestone approach wasn't about
3000x
> >>more elegant.
> >>
> >>Or even my unanswered suggestion of a having all tags allowed to be
used
> >>2 ways with a global 'milestone' attribute (kindof like Todd is
> >>suggesting with roles, but not exactly).
> >>
> >>global attributes mStart and mEnd
> >>
> >>That would allow 2 types of markup.  All tags to either be used as:
> >>
> >>XML Container:
> >><verse ID="Gen.1.1">In the beginning</verse>
> >>
> >>or
> >>
> >>XML Milestone / Logical Container
> >><verse ID="Gen.1.1" mStart="uniqueID1" />In the beginning<verse
> >>mEnd="uniqueID1" />
> >>
> >>
> >>
> >>
> 
>