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

[Todd Tillinghast]

Todd

Does <qEnd> need globalAttributes?

Is there a reason that milestoneSe is required?  What good are start and
end milestones without a mechanism to find their partner?

Fortunately all the bears are in hibernation!  A good day for it since
there is a lot of snow falling out side.

I am not an expert on teiForm.  Is the fixed="milestone" because that is
the closest matching element TEI type?  No objection, just error
checking.
 
Otherwise looks good to me.  Troy any comments?

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 11:21 AM
> To: osis-core@bibletechnologieswg.org
> Subject: Re: Add new quote specific milestone attributes - RE:
[osis-core]
> milestone name inconsistencies
> 
> Todd,
> 
> So...
> 
> <xs:element name="qStart">
> 
>     <xs:complexType>
> 
>         <xs:attributeGroup ref="globalAttributes"/>
> 
>         <xs:attribute name="who" type="xs:string" use="optional"/>
> 
>         <xs:attribute name="level" type="xs:string" use="optional"/>
> 
>         <xs:attribute name="milestoneSe" type="milestoneSe"
> use="optional"/>
> 
>         <xs:attribute name="TEIform" fixed="milestone"/>
> 
>     </xs:complexT ype>
> 
> </xs:element>
> 
> 
> <xs:element name="qEnd">
> 
>     <xs:complexType>
> 
>         <xs:attributeGroup ref="globalAttributes"/>
> 
>         <xs:attribute name="milestoneSe" type="milestoneSe"
> use="optional"/>
> 
>         <xs:attribute name="TEIform" fixed="milestone"/>
> 
>     </xs:complexT ype>
> 
> </xs:element>
> 
> Add wherever <q> is now allowed.
> 
> Well, doesn't decrease milestone use since these are in fact
milestones.
> On the other hand, does give you attributes, who, level (still not
> comfortable but maybe somebody will find it useful), not  currently in
> milestone.
> 
> Is the foregoing a correct recitation?
> 
> Patrick
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 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')
> >>>>
> >>>
> >>>
> >
> 
> --
> Patrick Durusau
> Director of Research and Development
> Society of Biblical Literature
> pdurusau@emory.edu
> 
>