Supplemental: Re: [osis-core] 1.9.5 (no errors) -- Strong's numbers
Troy A. Griffitts
osis-core@bibletechnologieswg.org
Fri, 17 Oct 2003 11:30:41 -0700
Actually,
I'd like to be a rebel and say that ALL lists should use '|' instead of
' ' for consistency. Maybe other other groups will follow, and maybe
Steve can get it changed in the next specification anyway, or at least a
<element xml:listdelim="|"> mechanism :)
Anyway, the osisRef list is a nice idea, but I'm quite sure our morph
information contains characters not valid in osisRef, like: V-AMI-1S
Maybe lemma does, as well, but even if not, I'd not wish to use ' ' to
delimit lemma and '|' used to delimit morph.
I'm a little confused about why we changed <identifier type="OSIS">
I realize Chris asked to have it kept in, but what is the other
mechanism? and why are we confusing the issue by adding 2 mechanisms to
convey the same thing? :)
-Troy.
Troy A. Griffitts wrote:
> My comment about a 'cleaner solution' for lists was directed at XML in
> general. Spaces are not an acceptable delimiter for me. We agreed to
> standardize on '|' for everything in OSIS that couldn't use ' ' for a
> list. As far as I'm aware, there is no XPath mechanism that
> specifically deals with elements of a list anyway. We've written code
> that handles these types of lists in our engine, and they are still
> necessary.
>
> Many attributes cannot use ' ' as it's delimiter. e.g.,
>
> <w gloss="en:I loose">Luw</w>
>
> And yes, we have texts with multiple lemmatizations in them, so
> sometimes the lemma will be given with a strongs code, sometimes the
> morph will be given with an extended strongs code, sometimes the morph
> will be given with a robinsons code.
>
>
> -Troy.
>
>
> Todd Tillinghast wrote:
>
>> Patrick,
>>
>> If you meant that the prefix "strongs" in lemma="strongs:1234" would not
>> be in a regex, that is fine with me.
>>
>> The question is do Troy and Chris have a problem with NOT having a
>> standardized prefix for strongs numbers and having to dereference the
>> prefix to the <work> element to determine the type of value they are
>> handling.
>>
>> The following would be equivalent:
>> Case 1:
>> <osisText ...>
>> <work osisWork="strongs">
>> ...
>> <identifier type="OSIS">the proper identifier including version of
>> strongs numbers</identifier>
>> ...
>> </work>
>> <div>
>> <w lemma="stongs:1234 strongs:4553">text</w>
>> </div>
>> </osisText>
>>
>> Case 2:
>> <osisText ...>
>> <work osisWork="s">
>> ...
>> <identifier type="OSIS">the proper identifier including version of
>> strongs numbers</identifier>
>> ...
>> </work>
>> <div>
>> <w lemma="s:1234 s:4553">text</w>
>> </div>
>> </osisText>
>>
>> Troy, Chris?
>>
>> Todd
>>
>>
>>
>>> -----Original Message-----
>>> From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
>>> admin@bibletechnologieswg.org] On Behalf Of Patrick Durusau
>>> Sent: Friday, October 17, 2003 11:31 AM
>>> To: osis-core@bibletechnologieswg.org
>>> Subject: Supplemental: Re: [osis-core] 1.9.5 (no errors) -- Strong's
>>> numbers
>>>
>>> Todd,
>>>
>>> BTW, the result of that action would be to not enumerate Strongs, GK,
>>
>>
>> etc.
>>
>>> Can live with that. Would be better to have those systems documented
>>
>>
>> in
>>
>>> work anyway and there are some advantages to using that regex.
>>>
>>> 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
>>>>
>>>
>>>
>>> --
>>> 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
>
>
> _______________________________________________
> osis-core mailing list
> osis-core@bibletechnologieswg.org
> http://www.bibletechnologieswg.org/mailman/listinfo/osis-core