[osis-core] osisWorkType

[Todd Tillinghast]

Patrick,

Reserving a fixed set has its advantages.  As has been discussed in the
past but has not been agreed upon.  I would like see a hierarchical
naming system that indicates the class of reference system and the
specific instance of reference system within that class.
For example:
Bible.NA27 (we might find a better name other than NA27, because NA27
means nothing to almost everyone, except scholars.)
Bible.Hebrew
Bible.SamPent
Bible.Loeb

Personally I would like to see Bible represent the Bible.NA27 as the
standard/default reference system.

I think the Bible.??? structure allows us to create reserved classes of
reference systems as time goes by.

If someone wants to create their own reference system then they would
have to use Bible.x-ThierOwnSystem or x-ThierOwnNonBiblicalSystem.

Is one of the above reference systems the one used but the French
Segond, if not we should add it in as well?

Todd

> -----Original Message-----
> From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
> admin@bibletechnologieswg.org] On Behalf Of Patrick Durusau
> Sent: Tuesday, September 23, 2003 9:08 AM
> To: osis-core@bibletechnologieswg.org
> Subject: [osis-core] osisWorkType
> 
> 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!
> 
> 
> _______________________________________________
> osis-core mailing list
> osis-core@bibletechnologieswg.org
> http://www.bibletechnologieswg.org/mailman/listinfo/osis-core