[osis-core] <verse> and <chapter> in <lg> and <list>

[Todd Tillinghast]

That is the sort of example I had in mind.

Todd

> -----Original Message-----
> From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
> admin@bibletechnologieswg.org] On Behalf Of Chris Little
> Sent: Tuesday, June 10, 2003 11:18 PM
> To: osis-core@bibletechnologieswg.org
> Subject: Re: [osis-core] <verse> and <chapter> in <lg> and <list>
> 
> 
> 
> Patrick Durusau wrote:
> 
> > Todd,
> >
> > Todd Tillinghast wrote:
> >
> >> In osisCore.1.1.1.xsd we had milestoneStart and milestoneEnd as
> children
> >> of <lg> and <list>.
> >>
> >> Since we have deprecated those elements AND PRESUMING the reasoning
for
> >> them to be there in the first place was so to support verse (and
> >> possibly chapter) milestone pairs, is there a stronger case to
insert
> >> <chapter> and <verse> as milestones and containers that contain
only
> <l>
> >> and <item in <lg> and <list> respectively?
> >>
> >> OR where <milestoneStart> and <milestoneEnd> as children of <lg>
and
> >> <list> a bad idea in the first place?
> >>
> >>
> > The second case, bad idea, probably overly enthusiastic fingers. ;-)
> >
> > Only things that have PCDATA content should have any sort of
> > milestone. What would you be breaking between two items in a list?
If
> > they are parts of separate lists, make them separate.
> 
> 
> What about something like,
> 
> <verse sID=""/>
> pcdata
> <lg>
> <l>pcdata</l>
> <l>pcdata</l>
> <verse eID=""/>
> <verse sID=""/>
> <l>pcdata</l>
> <l>pcdata</l>
> <verse eID=""/>
> </lg>
> 
> The same situation occurs with lists/tables that include an
introduction
> plus the first part of the list/table in the first verse with
subsequent
> parts in other verses.
> 
> --Chris
> 
> 
> 
> _______________________________________________
> osis-core mailing list
> osis-core@bibletechnologieswg.org
> http://www.bibletechnologieswg.org/mailman/listinfo/osis-core