[osis-core] dataFormat: Attribute for header elements

Patrick Durusau osis-core@bibletechnologieswg.org
Mon, 01 Jul 2002 11:26:41 -0400


Greetings,

After an almost conversation-by-email discussion with Harry, I think we 
can answer his concerns with the following attribute declaration for all 
header elements:

<xs:attribute name="dataFormat" type="xs:string" use="optional"/>

Examples of its use:

<subject type="keyword" dataFormat="ccel-subjects">Christian Life;
   Sanctification</subject>
<subject type="keyword" dataFormat="LCSH">Practical Theology</subject>

and,

<creator type="Author" dataFormat="short-form">Alexander Whyte</creator>
 <creator type="Author" dataFormat="file-as">Whyte, Alexander
(1836-1921)</creator>

Note that it would be available on all header elements, which are:

<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:element ref="rights" minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="revisionDesc" minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="teiHeader" minOccurs="0" maxOccurs="1"/>

I was wondering about including it on teiHeader but then recalled the 
various versions of TEI and it would be possible that you might want to 
make so record of that information as well.

Action: Propose to include in the next release (hopefully later today or 
early tomorrow depending on how much progress we are making by later 
today.).

Patrick

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