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

Sat, 31 Aug 2002 11:30:13 -0700

Actually, I was planning on using osisID in the same manner:

Naves Topical:

<div osisID="Faith">Faith is the...</div>

Matthew Henry's Commentary:

<div osisID="Matt.1.1">This geneology points out...</div>

Spurgeon's Morning and Evening:

<div osisID="0831">August 31: Today's reading will be in...</div>

This is OUR (OSIS') way to describe a target in a document for an osisRef.

eg.

See Nave's on <reference osisRef="naves:Faith">Faith</reference>

If I'm wrong, please let me know, because I have a number of unresolved 
issues if I am.

	-Troy.

Todd Tillinghast wrote:
> This is a different purpose that what I believe that osisID should be
> used for.  I think that osisID should be used for things that are a part
> of a canonical reference system.
> 
> If there is a need create an id for every element and mark every element
> with an identifier then we have the ID attribute for that purpose.  
> 
> Todd
> 
> 
>>I am thinking of osisID as a way of identifying and referencing
>>_anything_ in a document, and the document could be a sermon,
>>commentary, poem, whatever.
>>
>>I don't want to make assumptions about the granularity of osisIDs
>>that people will use.  Maybe people will want to put osisIDs on
>>every <w>, <l>, <figure>, <head>, <milestone>, <note>, ... In short,
>>it's hard to anticipate what people might want to put osisIDs on,
>>and it seems simpler and cleaner to me to put it in "globalAttributes"
>>so it goes on all non-header elements.
>>
>>Remember that if an element doesn't have an osisID attribute, there
>>will be no way of referencing that element using the osisRef system.
>>
>>-Harry
>>
>>
>>>-----Original Message-----
>>>From: owner-osis-core@bibletechnologieswg.org
>>>[mailto:owner-osis-core@bibletechnologieswg.org] On Behalf Of
>>>Todd Tillinghast
>>>Sent: Friday, August 30, 2002 2:43 PM
>>>To: osis-core@bibletechnologieswg.org
>>>Subject: RE: [osis-core] osisCore_Candidate.1.1_006 - 5 -
>>>osisID should ONLY exist in <verse>, <p>, and <div>
>>>
>>>
>>>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
>>>>>
>>>>
>>>
> 