[osis-core] osisWorkType

Patrick Durusau osis-core@bibletechnologieswg.org
Tue, 23 Sep 2003 11:07:47 -0400


Guys,

The users manual currently says:

Every osisText also needs to specify what reference or versification
scheme any osisRefs within it refer to. This may or may not be the
same work. Depending on how finely you distinguish things, there are
several major versification traditions, and countless fine-grained
variations. For the present, we identify and reserve names for these
major traditional reference systems:

<p>
     r-NA27 -- as used in most English Bibles, with slight variations.
</p>

<p>
     r-Hebrew -- Hebrew tradition varies in several respects, the best
known being that it number the proscriptions above Psalms as verse 1,
and the beginning of the psalm proper as verse 2.
</p>

<p>
     r-SamPent -- the Samaritan Pentateuch used a quite different
numbering system.
</p>

<p>
     r-Loeb -- This system is used for most classical literature,
though many major works have other systems as well.
</p>


Note that this is inconsistent with the current regex for work type:

<xs:simpleType name="osisWorkType">
		<xs:restriction base="xs:string">
			<xs:pattern value="((\p{L}|\p{N}|_)+)((\.(\p{L}|\p{N}|_)+)*)?"/>
		</xs:restriction>
</xs:simpleType>

And also note that osisText currently has the following attribute:

<xs:attribute name="osisRefWork" type="osisWorkType" use="optional" 
default="Bible"/>

Steve has suggested either just reserving them in the manual or possibly 
changing the regex to force the "x-" before user defined works.

While I am sympathetic to the convention of using the "x-" for user 
defined works, it would break backwards compatibility.

Any thoughts on texts that would break if this is enforced?

Can always just say these names are reserved and let it go at that. 
(without the leading "r-" of course)

Comments?

Hope everyone is having a great day!

Patrick


-- 
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
Patrick.Durusau@sbl-site.org
Chair, V1 - Text Processing: Office and Publishing Systems Interface
Co-Editor, ISO 13250, Topic Maps -- Reference Model

Topic Maps: Human, not artificial, intelligence at work!