[osis-core] scope attribute on <p>, <lg>, <list>, and <table>

[Todd Tillinghast]

> -----Original Message-----
> From: osis-core-bounces at bibletechnologieswg.org [mailto:osis-core-
> bounces at bibletechnologieswg.org] On Behalf Of Steven J. DeRose
> Sent: Friday, July 09, 2004 9:15 AM
> To: osis-core at bibletechnologieswg.org
> Subject: Re: [osis-core] scope attribute on <p>, <lg>, <list>, and
<table>
> 
> At 10:30 -0600 2004-05-25, Todd Tillinghast wrote:
> >In talking with a group attempting to use OSIS documents within
> >Documentum they are struggling with the fact that Bibles and thus
OSIS
> >documents have multiple overlapping hierarchies which is a problem
with
> >Documentum's architecture that requires that documents be broken in
to
> >"chunks".
> >
> >The best solution will like be for them to "chunk" OSIS documents at
the
> ><p>, <lg>, <list>, <table> level.  Because the common access pattern
is
> >likely to be based on Book/Chapter/Verse reference it would be handy
if
> >the "scope" attribute were available on these elements in the same
way
> >it is with <div>.
> >
> >Any objections to or reasons why we should not add "scope" to "large"
> >containers (<p>, <lg>, <list>, <table>, <speech> and possibly
<signed>
> >and <salute>)?
> >
> 
> I guess I have no objection to that, though accommodating
> Documentum's prehistoric "chunking" doctrine tastes bad. 

I share the same distaste.

> Why don't they just chunk however they want, but keep track of the
> applicable osisIDs for each chunk as they load, so they can search on
them?
> Doesn't sound too tough to me.

This may make sense because they won't be guaranteed that all text will
make use of the "scope" attribute even if it is provided.

At the same time there is no real harm in providing the scope attribute.
I could go either way.

Todd