[osis-core] Reference encoding

[Patrick Durusau]

Todd,

Doesn't this introduce confusion with osisID?

In other words, on a <q> element, the osisID (if present) should 
indicate what is being contained by the <q> element. It sounds like that 
is what you want to do with scope.

Note that scope works on <div> since it is (should be) a large container 
that the osisID may not be sufficient to identify it contents so you get 
a range with osisRefType.

Patrick

Todd Tillinghast wrote:

>Patrick,
>
>I think we resolved by saying that the <q> does not use either osisID or
>osisRef and that a <reference> element is place within the <q> contain
>where the text would be presented.  
>
>Question, how can we differentiate between cases where the reference is
>to presented and cases where the reference information about the quote
>is encoded but not to be presented.  I know this tends toward the
>presentation side of things, but does encourage the use of a "scope"
>attribute to identify what is contained.  If the encoder also wants to
>also place a <reference> element within the <q> element that would still
>be allowed.
>
>Should we add "scope" to <q>?
>
>Todd
>
>  
>
>>-----Original Message-----
>>From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
>>admin@bibletechnologieswg.org] On Behalf Of Patrick Durusau
>>Sent: Thursday, June 12, 2003 3:47 PM
>>To: osis-core@bibletechnologieswg.org
>>Subject: [osis-core] Reference encoding
>>
>>Guys,
>>
>>    
>>
>>>In OSIS documents that are not Bibles, it is a common to see a quote
>>>of scripture text followed by the reference.
>>>
>>>Does it make sense to add an optional osisRef attribute to <q> and
>>><milestoneStart> to accommodate this frequent issue?
>>>
>>>Example: <q osisRef="Matt.20.28">The Son of Man did not come to be
>>>served, but to serve . . . </q>
>>>
>>>rather than <q>The Son of Man did not come to be served, but to
>>>      
>>>
>serve
>  
>
>>>. . .<reference osisRef="Matt.20.28">Matthew 20:28</reference></q>
>>>      
>>>
>>(Todd)
>>    
>>
>>Assumption: The string "Matthew 20:28" actually appears inline in the
>>text. That should be marked as an osisRef.
>>
>>The <q> element should use an osisID to indicate "what" text is being
>>quoted.
>>
>>Patrick
>>
>>--
>>Patrick Durusau
>>Director of Research and Development
>>Society of Biblical Literature
>>Patrick.Durusau@sbl-site.org
>>Co-Editor, ISO 13250, Topic Maps -- Reference Model
>>
>>Topic Maps: Human, not artificial, intelligence at work!
>>
>>
>>
>>_______________________________________________
>>osis-core mailing list
>>osis-core@bibletechnologieswg.org
>>http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
>>    
>>
>
>_______________________________________________
>osis-core mailing list
>osis-core@bibletechnologieswg.org
>http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
>
>  
>

-- 
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
Patrick.Durusau@sbl-site.org
Co-Editor, ISO 13250, Topic Maps -- Reference Model

Topic Maps: Human, not artificial, intelligence at work!