[osis-core] osis.1.9.8 attached!

[Troy A. Griffitts]

 > I believe you may mean <note type="translation"> rather than
 > <note type="explanation">.

Why would you think this?


 > I propose that we NOT allow hyphens in osisGenRegex and require
 > that encoders replace the naturally occuring hypen with a substitute
 > character.

Not sure what you mean by this, but I am not willing to encode morph 
information without hypens.  IMO, we should not do this because I may 
not KNOW that an encoding was modified and I need to switch it back.  I 
don't think - would be the only problem.  What about []@?


Todd Tillinghast wrote:
> I think that we should be able to annotate any of the values that would
> conform to osisGenRegex.
> 
> <osisText>
>    <header>
>       <work osisWork="s">
>          <title>Strongs Numbers</title>
>          ...
>       </work>
>    </header>
>    <div annotationRef="s:12345">
>       ...
>    </div>
>    ...
> </osisText>
> 
> This is fine as long as the osisGenRegex value does not have a hyphen in
> it (as is the case for Strongs numbers).  However, if one the
> annotationRef values does have a hypen then it would not be possible
> disimbaguate an osisGenRegex with a hypen from an osisRefRegex with a
> range.
> 
> As Troy has pointed out there are cases where the identifier value for
> an osisGenRegex would naturally have a hypen.  Because we already have
> said that a hypen is reserved to indicate a range and both osisGenRegex
> and osisRefRegex should occure togeather in an annotateRef list of
> values, I propose that we NOT allow hyphens in osisGenRegex and require
> that encoders replace the naturally occuring hypen with a substitute
> character.
> 
> Is this an acceptable solution?
> 
> Todd
> 
> 
>>-----Original Message-----
>>From: osis-core-admin@bibletechnologieswg.org 
>>[mailto:osis-core-admin@bibletechnologieswg.org] On Behalf Of 
>>Patrick Durusau
>>Sent: Saturday, October 18, 2003 6:00 PM
>>To: osis-core@bibletechnologieswg.org
>>Subject: [osis-core] osis.1.9.8 attached!
>>
>>
>>Guys,
>>
>>Valid regex for osisGenRegex.
>>
>>Added cQuote to osisMilestonePt.
>>
>>Todd has some questions on the allowance of hyphens.
>>
>>Very interested in the self-documenting feature that Troy suggested. 
>>Todd and I discussed it and think it should be generalized but 
>>insufficient time remains to do that.
>>
>>Suggestion, let's go with the prefixes and do a generalized 
>>defaulting 
>>mechanism to answer Troy's point on the use of x-values for 
>>attributes. 
>>Would be a real change for 3.0.
>>
>>Hope everyone is having a great day!
>>
>>Patrick
>>
>>-- 
>>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