[osis-core] Ambiguity regarding <work> and when to use <identifier type="OSIS"> and <referenceSystem> and which is required.
Fri, 15 Nov 2002 12:40:18 -0700
Are any of you documents to the point where we could use a couple of
them as examples regarding the issue with <identifier type="OSIS"> and
If you have a text that uses values in osisID and osisRef attributes
that use both the defaults and other works, then we would not need to
construct an example.
I attempted to access you OSIS library online but it seems to be down.
Sorry for the possible complication regarding the release of your
documents, if I know that you had a deadline of today I would have
worked harder to get with Troy earlier this week and bring this beast to
the forefront. (We started the attempt to call each other a week ago an
finally connected yesterday.)
I believe that whatever the resolution, that if you ALWAYS include BOTH
a <identifier type="OSIS"> and a <referenceSystem> element with
IDENTICAL values for ALL works then your encodings will be correct
regardless of the final interpretation. This however presumes that it
is correct for the two values to be identical. Given you position on
such things I doubt that it will be a problem. (Troy, do you agree?)
> -----Original Message-----
> From: firstname.lastname@example.org [mailto:owner-osis-
> email@example.com] On Behalf Of Todd Tillinghast
> Sent: Friday, November 15, 2002 12:10 PM
> To: firstname.lastname@example.org
> Subject: RE: [osis-core] Ambiguity regarding <work> and when to use
> <identifier type="OSIS"> and <referenceSystem> and which is required.
> Yes there is no change needed for the schema, but there could be
> implications regarding how you encode the child elements of <work>
> > -----Original Message-----
> > From: email@example.com [mailto:owner-osis-
> > firstname.lastname@example.org] On Behalf Of Troy A. Griffitts
> > Sent: Friday, November 15, 2002 12:05 PM
> > To: email@example.com
> > Subject: Re: [osis-core] Ambiguity regarding <work> and when to use
> > <identifier type="OSIS"> and <referenceSystem> and which is
> > Concerning Todd's comments... Our conversation was more concerning
> > INTERPRETATION of the markup, than syntax. Don't be concerned about
> > syntax changes for the schema.
> > Concerning:
> > <identifier type="OSIS">
> > I thought we had unofficially agree to use things like:
> > Bible.KJV.MyEdition.
> > Or at least keep things in a 'class'-like structure.
> > Harry, I would think if you want to have hard links to your docs,
> > are more than welcome to include:
> > <identifier type="CCEL">
> > But I wouldn't use type="OSIS" for the URLs that Todd has pointed
> > that you are using.
> > -Troy.
> > Todd Tillinghast wrote:
> > > All,
> > >
> > > Troy and I spoke on the phone yesterday afternoon regarding the
> > > the values in <identifier type="OSIS"> and <referenceSystem> with
> > > He and I had differing understandings about which are required in
> > > cases, and how they are used to resolve the full meaning of values
> > > osisID and osisRef attributes.
> > >
> > > Troy is composing a set of examples to make clear what seems not
> > > clear, and hopefully for us as a group to come to a common
> > > understanding.
> > >
> > > Harry, two concerns regarding releasing the CD for distribution at
> > > meeting next week.
> > > 1) If the way you have encoded <work> elements is inconsistent
> > > standard. Then there will be a large number of documents in
> > > with encoding that is inconsistent with the standard. (This is of
> > > course no reflection on your encoding but upon the ambiguity that
> > > currently exists.)
> > > 2) I noticed in past encodings that you have put a value like
> > > http://www.ccel..... for the value of <identifier type="OSIS">.
> > > Although the standard does not specify the form of this value, it
> > > leave the door open for the future to encode things without the
> > > http://www.ccel.org and simply create an identifier that does not
> > > a transport or website.
> > > 3) The use of a reference to
> > > http://www.bibletechnologies.net/osisCore.1.1.1.xsd to specify the
> > > schema rather than a reference to a local copy.
> > >
> > > I don't think any of these issues will cause significant effort to
> > > correct but will make for examples that we would want people to
> > >
> > > Based on today's email I understand you are under a deadline and I
> > > that there is still time to make necessary adjustments. I think
> > > would all agree that it would be preferred for the sample CD to be
> > > consistent with what the standard.
> > >
> > > Todd
> > >
> > >
> > >