[osis-core] osisCore_Candidate.1.1_006!

[Patrick Durusau]

Harry,

Thanks for the quick response!

Note that 007 (this evening) will not have the "[ ]" in the regex.

Think I have found (in conversation with Steve) the constraint problem. 
<div> for example has two occurrence models, one where it is required 
<osisText> and one where it is optional <div>. Will make it optional in 
<osisText> which should not be a problem since it is the only container 
for its subelements and see if that fixes the problem. Works "as is" for 
editors today but someday conformant software will appear and I want the 
schema to work then as well. ;-)

Patrick

Harry Plantinga wrote:

>>Question: Do I need to rework the regex to allow the wildcard 
>>character 
>>"*" in the osisRef? (suspect I do since it only allows 
>>letters/numbers and underscore
>>
>
>According to the proposal, no.  You'd use the wildcard like this:
>
><work osisWork="lxx">
>  <identifier type="OSIS">Bible.LXX.*.en</identifier>
></work>
>
>We should officially decide if OSIS is the right string to use
>in type="OSIS".
>
>We should also decide on a name for things like this: Bible.LXX.*.en.
>That is, under this proposal, we are using "osisWork" for two different
>sorts of things -- the internal and the external work identifiers. 
>Maybe we could use "workID" for the internal identifier and "osisWork"
>for the external one.  So we'd have 
>
><osisText osisWork="Bible.NIV.Zondervan1992.en">
>
>and 
>
><work workID="NIV">
>  <identifier type="OSIS">Bible.NIV.Zondervan1992.en">
>
>>Question: Do I need to drop the "[ ]" in the namespace prefix for 
>>osisWork in osisRef? (This was a reference system specifier. 
>>That is how 
>>I interpret Harry's post but want to be sure.)
>>
>
>According to the proposal, yes, you'd drop the [] in the namespace
>prefix.
>
>-Harry
>

-- 
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
pdurusau@emory.edu