Add new quote specific milestone attributes - RE: [osis-core] milestone name inconsistencies

[Patrick Durusau]

Todd,

Todd Tillinghast wrote:

>Patrick,
>
>I have to strongly disagree with the use of osisID to match up start and
>end milestones.  
>
On what basis? The only reason TEI does not use ID for that purpose is 
that it has to be unique in the document.

Any mechanism is going to have to involve either pointing, whether 
expressed as a ref or not, or have some sort of matching tokens.

>
>If PT if for presentation type and SE is for Something Else AND neither
>is to help us match up starting and ending milestones then we need
>ANOTHER attribute for the purpose of matching up milestones.
>
>We must NOT use osisID to match up milestones starting and endings
>because we would force the inclusion of arbitrary trash in the
>identifier namespace whose sole purpose is to match up milestones.  
>
>If the encoder wants to create an osisID for a milestone let them but it
>should not be required so that a pair can be matched up.
>
>We should have some thing like:
><p>
>	<qStart end="xyz"/> text <qEnd start="xyz"/>
></p>
>
>If the "end" and "start" attributes are not required what good are start
>and end milestones.
>
What good are the paired milestones anyway? As I recall there were many 
calls for pseudo-containment milestones, which I personally disagree 
with but now we have those and paired <qStart>, <qEnd> milestones.

I am really at a loss to explain why we should require end/start on 
matching milestones. I have no problem with adding the attributes but 
see no reason to require their use.

Waiting on a good reason for requiring end/start attributes (willing to 
add but why require)?

Patrick



>
>
>We do not have an attribute to indicate "PresentationType" in any other
>element and it could be determined to be useful there as well.  I think
>we should remove milestonePT and force people to use type and subtype to
>describe the type of data the element is and figure out the
>"Presentation Type" their style sheet based on the data type.  
>
>I still don't know what milestoneSE is for.  Until this morning I
>thought it was for matching up the "S"tart and "E"nd of a pair of
>milestones.  If no one can explain what it is for we should remove it.
>
>Todd
>
>>-----Original Message-----
>>From: owner-osis-core@bibletechnologieswg.org [mailto:owner-osis-
>>core@bibletechnologieswg.org] On Behalf Of Patrick Durusau
>>Sent: Friday, November 15, 2002 12:42 PM
>>To: osis-core@bibletechnologieswg.org
>>Subject: Re: Add new quote specific milestone attributes - RE:
>>
>[osis-core]
>
>>milestone name inconsistencies
>>
>>Todd,
>>
>>Todd Tillinghast wrote:
>>
>>>Patrick,
>>>
>>><snip>
>>>
>>>>>Todd
>>>>>
>>>>>Does <qEnd> need globalAttributes?
>>>>>
>>>>Yes, linked by osisID and splitID values according to the
>>>>
>>>documentation.
>>>
>>>I don't see any purpose for splitID for a milestone since a milestone
>>>can not be segmented.
>>>
>>>Are you proposing that we "link" <qEnd> with <qStart> with osisID or
>>>
>are
>
>>>you refereeing to some other meaning of "link"?
>>>
>>Linking with osisID. Present due to globalAttributes.
>>
>>
>>>>>Is there a reason that milestoneSe is required?  What good are
>>>>>
>start
>
>>>and
>>>
>>>>>end milestones without a mechanism to find their partner?
>>>>>
>>>>I don't read milestoneSe as being required? Reads use="optional"
>>>>
>>>What I was trying to say and didn't was that I think "milestoneSe"
>>>should be required.  (Sorry of the confusion.)  Do you see any that
>>>milestoneSe should not be required?
>>>
>>Sorry, don't see why it should be required. I could simply want to use
>>milestoneStart and milestoneEnd without the milestoneSe. (This
>>attribute, like milestonePt, was added at Bob's request for pointing
>>purposes.)
>>
>>Patrick
>>
>>
>>><snip>
>>>
>>>Todd
>>>
>>--
>>Patrick Durusau
>>Director of Research and Development
>>Society of Biblical Literature
>>pdurusau@emory.edu
>>
>>
>

-- 
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
pdurusau@emory.edu