[osis-core] 1.9.5 (no errors) -- Strong's numbers

Chris Little osis-core@bibletechnologieswg.org
Sun, 19 Oct 2003 10:28:25 -0700 (MST)


Todd & Patrick,

There are some good reasons why this won't work, mostly cited by Troy in 
his responses.  Essentially I think the regex needs to convey |-separated 
values consisting of a namespace followed by [^\|].

Specifically dealing with lemmata, it would be reasonable for someone to 
put the actual lemma (rather than a code identifying it) into the lemma 
attribute, and that lemma could conceivably consist of multiple words 
separated by whitespace.

I think it would be very convenient not to have to do look up the work for 
really common thinks like a Strong: prefix, so having a single standard 
prefix for everyone to use is definitely something I would prefer.  
Smaller file sizes are nice, but pretty far down on my list of priorities, 
along with whether to use single or double quotes.

The lemma should, IMO, be capable of containing useful information on its 
own that doesn't need to be looked up in an external document to have any 
relevence.  I have no problem with adding an osisRef: prefix along with 
Strong: and GK:, for those who have data that can use such a mechanism.  
The same goes for the values of morph, POS, etc.

--Chris

On Fri, 17 Oct 2003, Patrick Durusau wrote:

> Todd,
> 
> So you are saying that the type on lemma should be:
> 
> <xs:attribute name="lemma" type="osisRefType"/>
> 
> Which is a call to:
> 
> <xs:simpleType name="osisRefType">
> 		       <xs:list itemType="osisRefRegex"/>
> 	</xs:simpleType>
> 
> And in the docs we say to use the work element?
> 
> Works for me.
> 
> Chris?
> 
> Hope you are having a great day!
> 
> Patrick
> 
> Todd Tillinghast wrote:
> > Chris and Patrick,
> > 
> > I believe that Chris' solution will not give him what he is looking for
> > without making the attribute an xsd:list the same way osisID and
> > annotateRef are.  We have an opportunity to make the attributes in <w>
> > more robust by adopting the same regex form as osisID.  This way the
> > prefix could be defined clearly with a <work> element.  
> > 
> > Ex:
> > <osisText ...>
> >    <work osisWork="strongs">
> >       ...
> >       <identifier type="OSIS">the proper identifier including version of
> > strongs numbers</identifier>
> >       ...
> >    </work>
> >    <work osisWork="x">
> >       ...
> >       <identifier type="OSIS">the proper identifier</identifier>
> >       ...
> >    </work>
> >    <div>
> >       <w lemma="stongs:1234 strongs:4553 x:Text>text</w>
> >    </div>
> > </osisText>
> > 
> > This eliminates the need for the "|" character to separate values AND
> > provides for the file size to be greatly reduced by using "s" rather
> > than "strongs".
> > 
> > Todd
> > 
> > 
> >>-----Original Message-----
> >>From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
> >>admin@bibletechnologieswg.org] On Behalf Of Patrick Durusau
> >>Sent: Thursday, October 16, 2003 9:31 AM
> >>To: osis-core@bibletechnologieswg.org
> >>Subject: Re: [osis-core] 1.9.5 (no errors) -- Strong's numbers
> >>
> >>Chris,
> >>
> >>Unlike some issues, ;-), there has not been a hugh chorus on this one.
> >>
> >>I will post something directly to Kirk Lowery as he would be more
> > 
> > likely
> > 
> >>to know if there are any other common lemma designations
> > 
> > (Westminster?)
> > 
> >>that we need to include on the OT side anyway.
> >>
> >>Assuming no show stoppers, look for it as you outline in 1.9.6 (coming
> >>later today).
> >>
> >>Hope you are having a great day!
> >>
> >>Patrick
> >>
> >>Chris Little wrote:
> >>
> >>>
> >>>Patrick Durusau wrote:
> >>>
> >>>
> >>>>Any thing else that looks like a critical issue?
> >>>>
> >>>>BTW, since we are getting close to a major and hopefully stable
> >>>>release, please let me know when I can call tomorrow or Friday
> >>>
> > (Chris,
> > 
> >>>>please send a phone number off list) to make one final round of the
> >>>>group before we close the blast doors and fire our weapons. ;-)
> >>>
> >>>
> >>>Patrick,
> >>>
> >>>I'm quite hesitant to mention this, especially so near release, but
> >>
> > your
> > 
> >>>mention of moving into a stable major release suggests maybe we
> >>
> > should
> > 
> >>>address this now, especially since the solution is fairly obvious
> >>
> > and
> > 
> >>>painless to implement.
> >>>
> >>>Moving towards 1.0, we added the lemma attribute to the <w> element
> >>
> > as a
> > 
> >>>way to contain data such as Strong's number.  The attribute has the
> >>
> > type
> > 
> >>>attributeExtension since we didn't want to deal with the issues
> >>>surrounding it at that point.
> >>>
> >>>Now heading into 2.0, Strong's numbers are one of the few instances
> >>>where I still find I need to use attributeExtension, though it is a
> >>>fairly pedestrian need.
> >>>
> >>>I would recommend (unless we just decide to put it off a while
> >>>longer--which I could certainly understand):
> >>>
> >>>1) create a simple type, "osisLemma" that contains a single
> >>
> > enumerated
> > 
> >>>value: "Strong"
> >>>2) create a simple type, "wLemma" that is the union "osisLemma" and
> >>>"attributeExtension"
> >>>3) change the type of lemma to "wLemma"
> >>>
> >>>Documentation should indicate that valid values would match the
> >>
> > regex
> > 
> >>>[HG][1-9][0-9]{,3}  (H = Hebrew, G = Greek, 1-4 digit Strong's
> >>
> > numbers
> > 
> >>>without leading zeroes; this is the standard format used in most
> >>
> > print &
> > 
> >>>software versions.)
> >>>
> >>>--Chris
> >>>
> >>>
> >>>
> >>>_______________________________________________
> >>>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
> > 
> > 
> > _______________________________________________
> > osis-core mailing list
> > osis-core@bibletechnologieswg.org
> > http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
> > 
> 
> 
>