[osis-core] Syntax Check

Steve DeRose osis-core@bibletechnologieswg.org
Tue, 27 Aug 2002 11:47:48 -0400


At 10:23 AM -0400 08/26/02, Harry Plantinga wrote:
>  > Before I re-write the regex, is there general agreement on
>>  Steve's proposal:
>>
>>  work(refsys):canonical(split)@grain-canonical(split)@grain
>
>The work(refsys) is the reverse of what Todd proposed, refsys(work).
>The reason Todd proposed as he did, I suppose, is that he wanted to
>be able to omit the (work), but the refsys was supposed to be required.
>In the above proposal, presumably the (refsys) would be optional
>and the workID required.  I suppose that a refsys can be optional if
>the default refsys for the work is used.
>
>But what about the case where we don't have a specific work, only
>a reference system and class of works?

I think I had been (vaguely) assuming that a class of works would 
count as a (virtual?) work and be declared by a <work> element. Say, 
like leaving out the publication date if you don't care which edition 
of the NIV, or leaving out all but the "Bible" and "English" if you 
don't care which translation. Then any actual work that unifies with 
the header declaration is acceptable (presumably software would try 
your 'preferred' version first or some such).

>
>For example, suppose I want to get Ps. 20 out of the LXX using
>the KJV reference system.  I suppose I would
>
>- define a work element selecting the edition requested
>- use the optional (refsys)?
>
>--------------------------------------
><works>
>   <work workID="lxx">
>     <identifier type="OSIS">Bible.LXX.*.en.*</identifier>
>   </work>
></works>
>
>.....
>
>   osisRef="lxx(Bible.KJV):Ps.20"....
>
>-----------------------------------------
>
>I think the work(refsys) syntax works just fine.
>But we should be aware that in some ways it's a totally different
>approach from what we had previously discussed.  There would no
>longer be a "Bible.KJV:Matt.1.1" -- instead, you'd define a <work>
>element saying as much as you care to say about what edition of the
>KJV to use, give it a workID such as myKJV, and use "myKJV:Matt.1.1".
>
>-Harry


-- 

Steve DeRose -- http://www.stg.brown.edu/~sjd
Chair, Bible Technologies Group -- http://www.bibletechnologies.net
Email: sderose@speakeasy.net
Backup email: sjd@stg.brown.edu