[osis-core] osisCore_Candidate.1.1_006 - 5 - osisID should ONLY exist in <verse>, <p>, and <div>

[Todd Tillinghast]

I can't think of places other than <div>, <p>, and <verse> where an
osisID would be needed?  Exceptions being <l> and <item> and similar
elements.  If <l> were to have an osisID then encoding would be simpler
because at present a <verse> element MUST be contained in EVERY <l>
element if you are not using milestones to mark the verses.  (See the
Ps.1-Ps.3 I encoded a couple of days ago and posted.)

Previously we had decided that even elements like <l> and <item> would
not have osisIDs but would be contained by a <verse> or contain a
<verse> (now expanded to <p>)

The more elements that can contain an osisID the more places and types
of elements we have to handle when looking for a verse.

Do you think we should have osisID on <l> and <item>?

Are there other specific elements we should allow osisID on?  

I think you will agree that <work> does not need an osisID.  There are
many other similar cases.

Todd
> 
> I thought we were going to use osisID in LOTS of situations,
> e.g.
> 
> <p osisID="X.4">  to identify this paragraph of augustine's
> confessions as "X.4", etc.
> 
> -whp
> 
> > -----Original Message-----
> > From: owner-osis-core@bibletechnologieswg.org
> > [mailto:owner-osis-core@bibletechnologieswg.org] On Behalf Of
> > Todd Tillinghast
> > Sent: Friday, August 30, 2002 1:33 PM
> > To: osis-core@bibletechnologieswg.org
> > Subject: [osis-core] osisCore_Candidate.1.1_006 - 5 - osisID
> > should ONLY exist in <verse>, <p>, and <div>
> >
> >
> > osisID should ONLY exist in <verse>, <p>, and <div>.  It
> > should be optional with the exception of <verse>.
> >
> > Possibly in milestone_start and milestone_end?  Troy?
> >
> > Todd
> >