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

[Troy A. Griffitts]

I still don't know the difference/meaning of: milestoneSe as it relates 
to splitID.

Why is Se upper/lower and ID upper/upper?

What does Se stand for?  Pt?

Start/End?  Part/Time? :)

if Se = StartEnd, then I think it should be milestoneSE (upper/upper). 
as they are different words.

BUT, ID by that rule would be Id (upper/lower), because it's the same 
word.  BUT I LIKE ID (upper/upper)!  Maybe we could say 'abbreviations' 
are always upper/upper, so we get ID and SE both.

:)  all in the purpose of consistency...



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"?
> 
> 
>>>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?
> 
> 
> <snip>
> 
> Todd