[osis-core] osisWork, refSystem - Summary

[Harry Plantinga]

> 1. Should have attributes on osisText that are osisWork and refSystem.

> 2. The values of osisWork and refSystem are declared in separate 
> container elements, <works> and <refSystems> respectively, by 
> <work> and 
> <refSystem> elements, each of which has an attribute that acts as an 
> identifier for that entry.

OK, let's see if I have this right.  I'd do something like this?

------------------------------------------------------------
<header>
  <title>Augustine's Confessions</title>
  <creator role="Author">St. Augustine</creator>
  <creator role="translator">Pusey</creator>
  <publisher>S.P.C.K.</publisher>
  <date>1912</date>

  <works>
    <work osisWork="augustine.confessions.SPCK1912">
      <title>Augustine's Confessions</title>
      <creator role="author">St. Augustine</creator>
      <creator role="translator">Pusey</creator>
      <publisher>S.P.C.K.</publisher>
      <date>1912</date>
    </work>
  </works>

  <refSystem refSystem="augustine.confessions.pusey.1880>
    <title>Augustine's Confession</title>
    <creator role="author">St. Augustine</creator>
    <creator role="translator">Pusey</creator>
    <language>en</language>
    <date>1880</date>
  </refSystem>
</header>
    

<osisText osisWork="augustine.confessions.SPCK1912"
refSystem="agustine.confessions.pusey.1880">
 [doc here]
</osisText>
------------------------------------------------------------

At least, that's my take on #1 and #2 above.  

The obvious issue is that there is redundant information in the
<header> and in the <work> element. Do I really need a <work> element
to define augustine.confessions.SPCK1912, and if so, should we drop
the header elements?

-Harry