[osis-core] RE: Work Issue
Patrick Durusau
osis-core@bibletechnologieswg.org
Thu, 30 Jan 2003 17:57:26 -0500
--------------010908080702000700030301
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Todd,
Before you jump off into another issue, let me see if I have the old one
at least partially understood:
We have a KJV Bible that for whatever reason, also has Hebrew Bible
versification marked in the text itself, for example: Gen:1.1/Gen:1.1
and so on.
And you want to have a single work element that has both reference
systems inside the work element, so you can use either one? Sorta like
the editions of Augustine that have multiple reference systems in a
single edition so you can go find stuff in other editions?
So as we are now, with the text having only one attribute to point at a
single work element (which is every thing inside it) you don't know
which reference system is meant if both are recorded inside the work
element? And this is a problem for osisID only?
Just making sure I understand the use case first.
Breaking for dinner now, back in a while.
Patrick
Todd Tillinghast wrote:
>Troy,
>
>I can agree. In fact it sounds like an improvement since the other
>sub-elements would seem to be less "precise". Example if I were the
>author then I could be identified as "Daniel Todd Tillinghast", "Todd
>Tillinghast", "Daniel T. Tillinghast", or "Daniel T Tillinghast". Any
>variation causing a mismatch.
>
>However, I don't know what the opinion of the rest of the group would
>be.
>
>Todd
>
>-----Original Message-----
>From: osis-core-admin@bibletechnologieswg.org
>[mailto:osis-core-admin@bibletechnologieswg.org] On Behalf Of Troy A.
>Griffitts
>Sent: Thursday, January 30, 2003 3:13 PM
>To: osis-core@bibletechnologieswg.org
>Subject: Re: [osis-core] RE: Work Issue
>
>
>
>>You are correct. I the statement should be all of the sub-elements
>>except the <refSystem> element.
>>
>>
>
>Might we further limit this resolution rule to ONLY the <identifier>
>subelements?
>
> -Troy.
>
>_______________________________________________
>osis-core mailing list
>osis-core@bibletechnologieswg.org
>http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
>
>_______________________________________________
>osis-core mailing list
>osis-core@bibletechnologieswg.org
>http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
>
>
--
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
pdurusau@emory.edu
Co-Editor, ISO Reference Model for Topic Maps
--------------010908080702000700030301
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body>
Todd,<br>
<br>
Before you jump off into another issue, let me see if I have the old one
at least partially understood:<br>
<br>
We have a KJV Bible that for whatever reason, also has Hebrew Bible versification
marked in the text itself, for example: Gen:1.1/Gen:1.1 and so on.<br>
<br>
And you want to have a single work element that has both reference systems
inside the work element, so you can use either one? Sorta like the editions
of Augustine that have multiple reference systems in a single edition so
you can go find stuff in other editions?<br>
<br>
So as we are now, with the text having only one attribute to point at a single
work element (which is every thing inside it) you don't know which reference
system is meant if both are recorded inside the work element? And this is
a problem for osisID only? <br>
<br>
Just making sure I understand the use case first.<br>
<br>
Breaking for dinner now, back in a while.<br>
<br>
Patrick<br>
<br>
Todd Tillinghast wrote:<br>
<blockquote type="cite"
cite="mid000001c2c8b0$c32c60e0$8100a8c0@halogenlight">
<pre wrap="">Troy,
I can agree. In fact it sounds like an improvement since the other
sub-elements would seem to be less "precise". Example if I were the
author then I could be identified as "Daniel Todd Tillinghast", "Todd
Tillinghast", "Daniel T. Tillinghast", or "Daniel T Tillinghast". Any
variation causing a mismatch.
However, I don't know what the opinion of the rest of the group would
be.
Todd
-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:osis-core-admin@bibletechnologieswg.org">osis-core-admin@bibletechnologieswg.org</a>
[<a class="moz-txt-link-freetext" href="mailto:osis-core-admin@bibletechnologieswg.org">mailto:osis-core-admin@bibletechnologieswg.org</a>] On Behalf Of Troy A.
Griffitts
Sent: Thursday, January 30, 2003 3:13 PM
To: <a class="moz-txt-link-abbreviated" href="mailto:osis-core@bibletechnologieswg.org">osis-core@bibletechnologieswg.org</a>
Subject: Re: [osis-core] RE: Work Issue
</pre>
<blockquote type="cite">
<pre wrap="">You are correct. I the statement should be all of the sub-elements
except the <refSystem> element.
</pre>
</blockquote>
<pre wrap=""><!---->
Might we further limit this resolution rule to ONLY the <identifier>
subelements?
-Troy.
_______________________________________________
osis-core mailing list
<a class="moz-txt-link-abbreviated" href="mailto:osis-core@bibletechnologieswg.org">osis-core@bibletechnologieswg.org</a>
<a class="moz-txt-link-freetext" href="http://www.bibletechnologieswg.org/mailman/listinfo/osis-core">http://www.bibletechnologieswg.org/mailman/listinfo/osis-core</a>
_______________________________________________
osis-core mailing list
<a class="moz-txt-link-abbreviated" href="mailto:osis-core@bibletechnologieswg.org">osis-core@bibletechnologieswg.org</a>
<a class="moz-txt-link-freetext" href="http://www.bibletechnologieswg.org/mailman/listinfo/osis-core">http://www.bibletechnologieswg.org/mailman/listinfo/osis-core</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="$mailwrapcol">--
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
<a class="moz-txt-link-abbreviated" href="mailto:pdurusau@emory.edu">pdurusau@emory.edu</a>
Co-Editor, ISO Reference Model for Topic Maps
</pre>
<br>
</body>
</html>
--------------010908080702000700030301--