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

[Patrick Durusau]

Troy,

Troy A. Griffitts wrote:

> OK guys.  I still don't get it.
>
> If I run across a <qEnd> in the text, how do I know what <qStart> it 
> goes with?

I am going through the latest release a line at a time today, mainly 
cleaning up prose and the like.

The linking between <qEnd> and <qStart> should be specified by use of 
the osisID. In other words, they share the same osisID value.

>
> If I run across a <milestoneEnd> how do I know what <milestoneStart> 
> it goes with?
>
> WHAT DOES PT AND SE stand for?!  Used for?  Does anybody really know?  
> I have no clue!  it could mean PizzaTime and SuperErnie for all I 
> know! :)

SE is used to specify the "type" of the milestone, which can be used 
along with the linking of a start/end pair for particular formatting.

PT is also a "type" of milestone, but gives us control over presentation 
features for the milestone. Note that it includes an enumeration of 
these types, such as screen, which allow software to insert a screen 
break at the milestone. Other types include column, page, etc. PT only 
occurs on the generic milestone since it marks a point in the text where 
some behavior is expected or desired. The reason for having this 
separate from "type" is to have a controlled list to suggest for use in 
marking such features.

Note that SE "types" report a type of pseudo-container and are different 
from the PT types.

Could rename if that would be helpful, say msStartEnd and msPoint if 
that would help remember the respective functions?

Patrick

>
> Please help me understand.
>
>
>     -Troy.
>
>
>
> Patrick Durusau wrote:
>
>> 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