[osis-core] Proposed works syntax

[Harry Plantinga]

What's the purpose of the <work> entry -- is it more or less a bibliography
entry, so you can identify the desired work, edition, language? If so, some
of the dublin core elements don't seem to be relevant. It doesn't seem to
help in identifying a work to give its <contributor>, <subject>,
<description>, <type>, <format>, <source>, <relation>, <coverage>, <rights>.

I'm not even sure it makes sense to specify something like <subject> --
would we be saying, perhaps, that we don't know a work's title or author --
we just want any work on a particular subject?

On the other hand, some of the dublin core elements would have to be
overloaded with custom types.  For example,

<identifier type="URL">
<identifier type="ISBN">
<identifier type="ISSN">
<identifier type="osisWork">

<work refWork="LXX"><osisWork>bible.lxx</osisWork></work> would give us a
way of saying "I want to use the osisID scheme of bible.lxx" without
identifying a title, author, publisher, etc.

What about using elements more closely tied to traditional bibliography
entries, the ways that were discussed in Rome for selecting bible versions
(version, language, ???), and URL, ISBN, ISSN?

I'm thinking <title> <author> <publisher> <date> <edition> <version>
<language> <url> <isbn> <issn> <osisWork> ... any others?

-Harry

----- Original Message -----
From: "Patrick Durusau" <pdurusau@emory.edu>
To: "osis-core" <osis-core@bibletechnologieswg.org>
Sent: Wednesday, July 03, 2002 7:20 AM
Subject: [osis-core] Proposed works syntax


> Greetings,
>
> Is the following a step in the right direction for Steve's
> works-referenced syntax?
>
> Add to header:
>
> <references> contains only <work>*
>
> <xs:element name="work">
>           <xs:annotation>
>             <xs:documentation>
>                 <p>The &lt;work&gt; element is used to allow easy
reference to any work from within the OSIS
>  document instance. It is most commonly used in connection with osisID to
specify a particular work that
> is being referenced by the osisID in question.</p>
> <xs:complexType>
> <xs:sequence>
> <xs:element ref="title" minOccurs="0"/>
> <xs:element ref="contributor" minOccurs="0" maxOccurs="unbounded"/>
> <xs:element ref="creator" minOccurs="0" maxOccurs="unbounded"/>
> <xs:element ref="subject" minOccurs="0" maxOccurs="unbounded"/>
> <xs:element ref="date" minOccurs="0" maxOccurs="unbounded"/>
> <xs:element ref="description" minOccurs="0" maxOccurs="unbounded"/>
> <xs:element ref="publisher" minOccurs="0" maxOccurs="unbounded"/>
> <xs:element ref="type" minOccurs="0" maxOccurs="unbounded"/>
> <xs:element ref="format" minOccurs="0" maxOccurs="unbounded"/>
> <xs:element ref="identifier" minOccurs="0" maxOccurs="unbounded"/>
> <xs:element ref="source" minOccurs="0" maxOccurs="unbounded"/>
> <xs:element ref="language" minOccurs="0" maxOccurs="unbounded"/>
> <xs:element ref="relation" minOccurs="0" maxOccurs="unbounded"/>
> <xs:element ref="coverage" minOccurs="0" maxOccurs="unbounded"/>
> </xs:sequence>
> <xs:attribute name="refWork" type="xs:string" use="required"/>
> </xs:complexType>
> </xs:element>
>
> I just put the work attribute in as xs:string but that is just a place
> holder. Please suggest how we could enumerate values for use with our
> "x-" extension.
>
> Reasoning being that by specifying the work attribute on osisID, there
> is a reference back to the <work> element(s) held in references. Note
> that this is not ID/IDREF so we can avoid the name restrictions in XML.
> So, would have to be enforced by application.
>
> This does not solve the versification problem but does at least clear
> part of the way to that problem.
>
> Comments, suggestions?
>
> Patrick
>
>
>
> --
> Patrick Durusau
> Director of Research and Development
> Society of Biblical Literature
> pdurusau@emory.edu
>