[osis-core] Question on: General Defaulting Mechanism

[Todd Tillinghast]

Patrick,

//*[@osisID] differs from //*/@osisID in that the first would be all
elements that have an osisID attribute and the second would be all
osisID attributes who have a parent element.

Because all attributes must be a child of an element //*/@osisID is the
same as //@osisID.

The argument for //@osisID is that it is simpler while //*/@osisID is
the same form as //GI/@osisID (//div/@osisID) and would be less
confusing from that perspective.

We could just allow both forms but I think we should stay away from
predicates if we can.

(Yes I meant element name not attribute name below.)

Todd

> -----Original Message-----
> From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
> admin@bibletechnologieswg.org] On Behalf Of Patrick Durusau
> Sent: Wednesday, March 17, 2004 11:28 AM
> To: osis-core@bibletechnologieswg.org
> Subject: Re: [osis-core] Question on: General Defaulting Mechanism
> 
> Todd,
> 
> About to reach that section of the users manual.
> 
> Todd Tillinghast wrote:
> > Patrick,
> >
> > Is there a better name for this attribute?
> > This is two word element name with an action.  What about something
like
> > <defaultWork>?
> >
> You mean element?
> 
> My rough draft has:
> 
> <xs:element name="workPrefix" type="workPrefixCT"
maxOccurs="unbounded"/>
> 
> with the model:
> 
> 	<xs:complexType name="workPrefixCT">
> 	<!-- path must be: //GI/@attributeName -->
> 		<xs:attribute name="path" type="xs:string"
use="required"/>
> 		<xs:attribute name="osisWork" type="osisWorkType"
> use="required"/>
> 		<xs:attributeGroup ref="globalWithoutType"/>
> 	</xs:complexType>
> 
> Agreed (at least I do) that we should strike the globals, so it would
> become:
> 
> <xs:complexType name="workPrefixCT">
> <!-- path must be: //GI/@attributeName -->
> <xs:attribute name="path" type="xs:string" use="required"/>
> <xs:attribute name="osisWork" type="osisWorkType" use="required"/>
> </xs:complexType>
> 
> 
> > Do we allow * for GI?  <defaultWork path="//*@osisID"
> > prefix="osisWork"/> (This would seem to be equivalent to <osisText
> > osisWorkID="osisWork">.)
> >
> Do I need the "*"?
> 
> Thought I could do (in XPATH):
> 
> //@osisID
> 
> McKay in his second edition (page 357) says you an do
> 
> //@osisID (well, he did not use an OSIS example, maybe in the next
> edition), but does report that:
> 
> //*[@width] is more "natural."
> 
> Not sure what "natural" would mean to someone who writes tomes on XSLT
> but there you have it. ;-)
> 
> 
> 
> > What about for the attribute? <defaultWork path="//w@*"
> > prefix="osisWork"/>
> >
> 
> See comment above on the path syntax.
> 
> > Do we leave the attributes on <osisText> for now but discourage
their
> > use?
> >
> Personally I think we should leave the attributes on <osisText> and
note
> this new mechanism as a refinement of it. If all I have is one work,
> typical in a single translation, would not make much sense to have to
> enumerate osisID, osisRef, etc. for the work prefix.
> 
> On the other hand, where I have a portion, perhaps repetitive, where I
> want to use another work prefix, such as a commentary, I think this
> would work quite well.
> 
> Comments?
> 
> Hope you are having a great day!
> 
> Patrick
> 
> 
> 
> > I agree with there ONLY being the two attributes and having this as
the
> > third element child of <header>.
> >
> > Todd
> >
> >
> >>Guys,
> >>
> >>Some time ago I started a thread on a general defaulting mechanism.
> >>
> >>Current thinking is that it would go in the header and would have
the
> >
> > form:
> >
> >><setDefault path="//GI@AttributeName" prefix="osisWork">
> >>
> >>header currently has <revisionDesc> and <work> in that order.
> >>
> >>This would add <setDefault> as the third element in that list.
> >>
> >>I read the proposed syntax to mean"
> >>
> >><setDefault : GI for this element
> >>
> >>path="//GI@AttributeName" : note the use of "//" means that
attribute
> >>name anywhere in the document. So, probably most useful for elements
> >>where having the same work prefix everywhere is acceptable.
> >>
> >>prefix="osisWork"> : means that the prefix is established by the
value
> >>of the osisWork attribute on a work element.
> >>
> >>Note that the users manual will say that use of a prefix will
override
> >>the defaulting provided by this mechanism.
> >>
> >>I don't see any reason to add attributes to this element.
> >>
> >>Comments or questions?
> >>
> >>--
> >>Patrick Durusau
> >>Director of Research and Development
> >>Society of Biblical Literature
> >>Patrick.Durusau@sbl-site.org
> >>Chair, V1 - Text Processing: Office and Publishing Systems Interface
> >>Co-Editor, ISO 13250, Topic Maps -- Reference Model
> >>
> >>Topic Maps: Human, not artificial, intelligence at work!
> >>
> >>
> >>_______________________________________________
> >>osis-core mailing list
> >>osis-core@bibletechnologieswg.org
> >>http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
> >
> >
> > _______________________________________________
> > osis-core mailing list
> > osis-core@bibletechnologieswg.org
> > http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
> >
> 
> 
> --
> Patrick Durusau
> Director of Research and Development
> Society of Biblical Literature
> Patrick.Durusau@sbl-site.org
> Chair, V1 - Text Processing: Office and Publishing Systems Interface
> Co-Editor, ISO 13250, Topic Maps -- Reference Model
> 
> Topic Maps: Human, not artificial, intelligence at work!
> 
> 
> _______________________________________________
> osis-core mailing list
> osis-core@bibletechnologieswg.org
> http://www.bibletechnologieswg.org/mailman/listinfo/osis-core