[osis-core] Overlapping Summary??

[Harry Plantinga]

If I remember correctly, Steve was suggesting using only containers 
(segments) for 1.1 to see how much of a pain it turns out to be.  
Then possibly add milestone containers in 2.0, with a clear 
explanation of semantics.

I mumbled something not-very-well-thought-out about using some 
start- and end-milestones in 1.1 that could later be interpreted
as containers in some other version or level of OSIS. However, I'd 
want to think that out carefully before taking that approach.  Can 
the same file always work for two different semantic systems?

Then again the majority of overlap problems identified so far have
to do with quotes. Maybe for quotes at least we could find some
way of representing quotes with milestones. This would be one compromise
we could make to minimize segmentation problems. What we'd be giving
up is the ability to treat quotes as containers in XSLT, DOM, etc.
We'd also be giving up the ability to use XSLT to find the correct kind
of quote for nesting -- <q><q><q>Thus says the Lord: --> "'"Thus...

Possibilties:
  1.  Pure segmentation in 1.1; look into milestone containers in 2.0
  2.  Pure segmentation with milestone quote start and quote end
  3.  Pure segmentation with the option of milestone quote start and end.

I lean a bit toward #1.  We can always use &rdquo; instead of 
milestones.

-Harry


> I actually like the Steve/Harry suggestion on defining the semantics 
> rather than my more back-door hack on the default syntax of XML. I think 
> I could make my solution work as is, but it might be more confusing in 
> the long run and that is a definite disadvantage.
> 
> Suggestion: Should I clean up the current schema to focus solely on 
> segmentation (with appropriate attributes) and work on an additional 
> module that has the most common crossing elements with the semantics of 
> milestones? Same attributes that they have now in fuller form (although 
> we need to proof those as well). The module could make it clear that 
> these carry the semantics of being empty elements but that they carry 
> attribute information (with proper use) that will allow that semantic to 
> change to containership in OSIS 2.0?
> 
> Suggestions for syntax or commentary?
> 
> Comments?
> 
> Patrick
> 
> -- 
> Patrick Durusau
> Director of Research and Development
> Society of Biblical Literature
> pdurusau@emory.edu
> 
>