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

[Troy A. Griffitts]

Agree with Todd that we need a <q> milestone element.  I'd rather have 
<q mStart="uid123" /> and <q mEnd="uid123" /> (using my attribute group 
suggestion-- actually, it wasn't mine originally), so that we might 
apply it to other elements consistently (besides just <q>) in the future.

BUT, the demand for a <q> milestone is such that I'd be willing to 
support a compromise of Todd's suggestion of just having 2 special new 
elements, if that's what it takes to get others to agree.

We actually haven't heard from Patrick on the addition of the 'level' 
attribute to <q>, which I think me and Todd both feel is valuable.

	-Troy.



Todd Tillinghast wrote:
> Patrick,
> 
> I think that it does make sense to use milestones for quotes.  It just
> makes encoding drastically easier to accomplish and the result is easier
> to read.
> 
> The reason the current milestone elements are not sufficient are because
> there are specialized attributes present on <q> that are not available
> with the current milestone elements.  There are several attributes of
> <q> that are not present in the generic milestone element (level and
> who).  The type attribute needs to be reserved for its intended purpose.
> 
> I propose that we add a pair of quote specific milestone elements.  By
> adding these two elements the need to use milestones in most documents
> will drop dramatically.
> 
> New quote milestone elements.
> <qs> for quote start (or <qStart>
> <qe> for quote end (or <qEnd>)
> 
> Insert the normal milestone matching attributes and put the attributes
> that are currently in <q> in <qStart>.
> 
> Allow the two new elements where ever <q> is allowed.
> 
> Todd
> 
> 
> 
> 
> 
>>-----Original Message-----
>>From: owner-osis-core@bibletechnologieswg.org [mailto:owner-osis-
>>core@bibletechnologieswg.org] On Behalf Of Troy A. Griffitts
>>Sent: Friday, November 15, 2002 10:33 AM
>>To: osis-core@bibletechnologieswg.org
>>Subject: Re: [osis-core] milestone name inconsistencies
>>
>>I guess these are fine with me, but I would RATHER have something
>>smaller.  I couldn't tell you what Pt, or Se mean right now.  If we're
>>going to be unintuitive already, we might as well save space and make
> 
> it
> 
>>msPt msSe msStart msEnd
>>
>>What do msPt and msSe mean?
>>
>>And what do you use 'type' for on the milestone?
>>
>>I guess I've been wrong on my usage of these tags since the beginning.
>>
>>	-Troy.
>>
>>STILL DON'T LIKE THE MILESTONE ELEMENT.  THINK IT SHOULD BE REMOVED IN
>>FAVOUR OF A MILESTONE ATTRIBUTE GROUP THAT CONTAINS mStart and mEnd
>>
>>AT LEAST FOR <q>
>>
>>(Have to keep voicing this until Steve says NO or 3 out of 5 say yes)
> 
> :)
> 
>>
>>
>>
>>Patrick Durusau wrote:
>>
>>>Troy,
>>>
>>>Proposed changes (original -> change): Breaks anyone?
>>>
>>>Element:
>>>
>>>milestone (same)
>>>
>>>Attributes:
>>>
>>>Milestone_Pt -> milestonePt
>>>
>>>type: Milestone_Pt -> milestonePt
>>>
>>>
>>>Element:
>>>
>>>milestone_Start -> milestoneStart
>>>
>>>Attributes:
>>>
>>>Milestone_SE -> milestoneSe
>>>
>>>type: Milestone_SE -> milestoneSe
>>>
>>>
>>>Element:
>>>
>>>milestone_End -> milestoneEnd
>>>
>>>Attributes:
>>>
>>>milestone_SE -> milestoneSe
>>>
>>>type: Miletonse_SE -> milestoneSe
>>>
>>>
>>>Patrick
>>>
>>>
>>>Troy A. Griffitts wrote:
>>>
>>>
>>>>a quick examination of the milestone_Start element and it's
>>>
> attributes
> 
>>>>will reveal strange naming, including, but not limited to, '_'
>>>>characters, non-camelCase theme, same attributes for both start/end
>>>>with different case.
>>>>
>>>>(I know Patrick has already conceded to change these, but just
>>>
> wanted
> 
>>>>to be sure they are on 'the list')
>>>
>>>
>>>
>