[osis-core] OSIS_0105:2 non-Bible References?

[Todd Tillinghast]

This is really a reply to OSIS_0105:2, OSIS_0105:3, AND OSIS_0105:18.

We seem to be uncomfortable or at least not completely settled on the
issue of "work", "reference", "ID", "IDREF", identifying who-am-I, and
i-point-at.

I am starting to come over to the Patrick camp on the use of IDs and
IDREFs (with a few caveats).

Problems I see that we want to solve and haven't cleanly solved:
1) We want to use IDs for the who-am-I case.
2) There are cases where two (or more) elements could legitimately claim
the same ID.
3) We want to have a "generic" reference structure, but also want to
validate references to the Bible (and possibly other works) for a more
restrictive structure.
4) We want to use the behavior of IDREF when use a reference to point at
an element either in the same document or a different document.
5) We are struggling with the "work" structure both because it
represents the work and in some (but not all cases) the reference
system.
6) Our reference structure has no way of requiring "work" be indicated.

Solutions:
1) Derive a ReferenceType from both xs:ID and xs:IDREF.  This will give
us the two building blocks that we want to work with.
2) Declare that start milestones are the elements that use the ID for
references and that end milestones use IDREFs
Eg: <p reference="John.1.1"><verseStart marker="John.1.1"/> verse text
<verseEnd marker="John.1.1"/> 
Where the marker attribute in <verseStart is derived from
IDReferenceType which is derived from ID AND
The marker attribute in <verseEnd> is derived from IDREFReferenceType
which is derived from IDREF AND
The reference attribute in <p> is derived from IDREFReferenceType which
is still derived from IDREF.

(marker in <referenceStart>, <chapterStart> and <bookStart> would also
derive from IDReferenceType)
(encoders would have to decide between using <referenceStart> and
[<chapterStart>, <bookStart>, and <verseStart>] strategies for
milestones.)

3) In order to solve the problems with work, reference system, AND ID
ambiguity, "work" would be abolished.  If the IDREFReferenceType points
to an ID in the same document then let it simply say
(reference="John.1.1") if the IDREFReferenceType points to an ID in a
different document the (reference="Bible_TEV.xml#John.1.1").
4) Allow the marker in a start milestone to either be an
IDREFReferenceType OR IDReferenceType so that the milestone can point to
an externally defined reference system. 
5) Have documents outside the documents being encoded define the set of
IDs that are the reference system being used within the documents.  The
Bible_TEV.xml file in #3 above is an example of a file that defines the
set of reference IDs.  This way ALL IDs are validateable AND this
solution works for all types of references and does not leave us with
one strategy for Bible related references and another one for "other"
references.  Further the "id defining" external documents can also allow
for "centeralized"/standard reference naming and strategies as well AND
also provides the mechanism for mapping between reference systems when
desired but does not force it when not needed/wanted.

I hope this makes some sense.  I think a complete example would make
this really clear.  I can possibly to that Monday night but more likely
Tuesday.  I have to get to bed now because I will likely be awoken by
the youngest in about 4 hours.

Thoughts?

Todd

> -----Original Message-----
> From: owner-osis-core@bibletechnologieswg.org [mailto:owner-osis-
> core@bibletechnologieswg.org] On Behalf Of Patrick Durusau
> Sent: Saturday, April 06, 2002 10:35 AM
> To: osis-core@bibletechnologieswg.org
> Subject: [osis-core] OSIS_0105:2 non-Bible References?
> 
> Troy,
> 
> Troy A. Griffitts wrote:
> 
> >I'll try to tackle commenting on a few...
> >
> >>Separate the notion of Bible references from other references more
> >>generally. For non-Bible references, simply defer by declaring
non-Bible
> >>references to be "x-" and to be treated at some later point with a
> >>validation mechanism like we have for Bible references.
> >>
> >
> >Why are Bible references treated differently than non-Bible
references?
> >Per a previous email from Todd, we have a work= attribute that
dictates
> >schema (should it be a separate schema= attribute?), if we want to
> >enforce a schema.  Am I not following your thread of thought on this
> >one?
> >
> Sorry, confusion on my part. Did not interpret work (pointing to
> WorkType) as requiring validation to another (as yet proposed schema).
> 
> Seems to be pointing to a regex? No?
> 
> Help me here, what am I missing?
> 
> Patrick
> 
> 
> --
> Patrick Durusau
> Director of Research and Development
> Society of Biblical Literature
> pdurusau@emory.edu
> 
>