[osis-core] ccel texts and validation
Harry Plantinga
osis-core@bibletechnologieswg.org
Sat, 16 Nov 2002 12:40:35 -0500
But do we know that it will be named osisCore.1.1.1.xsd?
Patrick, what's the name going to be?
-Harry
> -----Original Message-----
> From: owner-osis-core@bibletechnologieswg.org
> [mailto:owner-osis-core@bibletechnologieswg.org] On Behalf Of
> Todd Tillinghast
> Sent: Saturday, November 16, 2002 12:32 PM
> To: osis-core@bibletechnologieswg.org
> Subject: RE: [osis-core] ccel texts and validation
>
>
> Harry,
>
> As a model to follow it would be better to refer to the
> http://www.bibletechnologies.net/osisCore.1.1.1.xsd rather
> than the version on you site.
>
> I don't think want every encoder to replicate the schema on
> their own web site. I understand that even now the current
> schema is not present on the web site.
>
> A trick I have used while waiting for the schema to be
> publicly posted, is to put the schema on my own site and then
> hard code the IP address of www.bibletechnologies.net on my
> machine in the hosts file to be the IP of my server.
>
> Todd
>
> > -----Original Message-----
> > From: owner-osis-core@bibletechnologieswg.org [mailto:owner-osis-
> > core@bibletechnologieswg.org] On Behalf Of Harry Plantinga
> > Sent: Saturday, November 16, 2002 6:01 AM
> > To: osis-core@bibletechnologieswg.org
> > Subject: [osis-core] ccel texts and validation
> >
> > The current version of the texts I'm submitting for the
> CD-Rom can be
> > found at http://www.ccel.org/ccel-osis/home.html. There are
> currently
> > 164 texts totalling about 230 MB. They have been converted
> to conform
> > to my own unofficial osisCore1.1.1.xsd which moves the <rights>
> > element into the <work> element, allows <milestone> in <title>,
> > doesn't require elements inside <item>, etc.
> >
> > The texts have been converted with the intention that they will be
> > valid against that schema, but only a handful have been tested, so
> > there are probably some well-formed but invalid documents in the
> > batch.
> >
> > I don't have a unix-based schema validator. I've been using
> XML Spy,
> > which means getting the document onto my laptop, loading
> them into XML
> > Spy, and the like. Does anyone know of a good Unix/Linux schema
> > validator?
> >
> > -Harry
> >
> >
> > > -----Original Message-----
> > > From: owner-osis-core@bibletechnologieswg.org
> > > [mailto:owner-osis-core@bibletechnologieswg.org] On
> Behalf Of Todd
> > > Tillinghast
> > > Sent: Friday, November 15, 2002 4:29 PM
> > > To: osis-core@bibletechnologieswg.org
> > > Subject: RE: Add new quote specific milestone attributes -
> > > RE: [osis-core] milestone name inconsistencies
> > >
> > >
> > > Troy,
> > >
> > > milestoneSe (or is it milestoneSE) is to match up a pair of
> > > milestones.
> > >
> > > <div>
> > > <verse osisID="X.1.2">kdkd <qStart milestoneSE="123"/> dkd
> > > kd</verse>
> > > <verse osisID="X.1.3"> dkjksdjf <qEnd
> milestoneSE="123"/> adkjf
> > > </verse> </div>
> > >
> > > splitID is to indicate that an element is a part of a set of
> > > elements that all have the same value for splitID when an element
> > > must be split into pieces because it is deferring to an other
> > > element from an overlapping hierarchy. As in the
> following.
> > >
> > > <q type="blockQuote">
> > > <lg>
> > > <l>
> > > <verse osisID="Ps.1.1" splitID="Ps.1.1">Happy
> > > are those</verse>
> > > </l>
> > > <l>
> > > <verse osisID="Ps.1.1" splitID="Ps.1.1">who
> > > reject the advice of evil people,</verse>
> > > </l>
> > > <l>
> > > <verse osisID="Ps.1.1" splitID="Ps.1.1">who do
> > > not follow the example of sinners</verse>
> > > </l>
> > > <l>
> > > <verse osisID="Ps.1.1" splitID="Ps.1.1">or join
> > > those who have no use for God.</verse>
> > > </l>
> > > <l>
> > > <verse osisID="Ps.1.2" splitID="Ps.1.2">Instead,
> > > they find joy in obeying the Law of the <divineName
> > > type="yhwh">LORD</divineName>,</verse>
> > > </l>
> > > <l>
> > > <verse osisID="Ps.1.2" splitID="Ps.1.2">and they
> > > study it day and night.</verse>
> > > </l>
> > > <l>
> > > <verse osisID="Ps.1.3" splitID="Ps.1.3">
> > > <note type="crossReference"
> > > osisRef="Ps.1.3-Ps.1.3">
> > > <note type="link">
> > > <reference
> > > osisRef="Jer.17.8"/>
> > > </note>
> > > </note> They are like trees that grow
> > > beside a stream,</verse>
> > > </l>
> > > <l>
> > > <verse osisID="Ps.1.3" splitID="Ps.1.3">that
> > > bear fruit at the right time,</verse>
> > > </l>
> > > <l>
> > > <verse osisID="Ps.1.3" splitID="Ps.1.3">and
> > > whose leaves do not dry up.</verse>
> > > </l>
> > > <l>
> > > <verse osisID="Ps.1.3" splitID="Ps.1.3">They
> > > succeed in everything they do.</verse>
> > > </l>
> > > </lg>
> > > </q>
> > >
> > > Todd
> > >
> > > > -----Original Message-----
> > > > From: owner-osis-core@bibletechnologieswg.org
> [mailto:owner-osis-
> > > > core@bibletechnologieswg.org] On Behalf Of Troy A. Griffitts
> > > > Sent: Friday, November 15, 2002 1:20 PM
> > > > To: osis-core@bibletechnologieswg.org
> > > > Subject: Re: Add new quote specific milestone attributes - RE:
> > > [osis-core]
> > > > milestone name inconsistencies
> > > >
> > > > I still don't know the difference/meaning of: milestoneSe as it
> > > relates
> > > > to splitID.
> > > >
> > > > Why is Se upper/lower and ID upper/upper?
> > > >
> > > > What does Se stand for? Pt?
> > > >
> > > > Start/End? Part/Time? :)
> > > >
> > > > if Se = StartEnd, then I think it should be milestoneSE
> > > (upper/upper).
> > > > as they are different words.
> > > >
> > > > BUT, ID by that rule would be Id (upper/lower), because
> > > it's the same
> > > > word. BUT I LIKE ID (upper/upper)! Maybe we could say
> > > 'abbreviations'
> > > > are always upper/upper, so we get ID and SE both.
> > > >
> > > > :) all in the purpose of consistency...
> > > >
> > > >
> > > >
> > > > Todd Tillinghast wrote:
> > > > > Patrick,
> > > > >
> > > > > <snip>
> > > > >
> > > > >>>Todd
> > > > >>>
> > > > >>>Does <qEnd> need globalAttributes?
> > > > >>>
> > > > >>
> > > > >>Yes, linked by osisID and splitID values according to the
> > > > >
> > > > > documentation.
> > > > >
> > > > > I don't see any purpose for splitID for a milestone since a
> > > milestone
> > > > > can not be segmented.
> > > > >
> > > > > Are you proposing that we "link" <qEnd> with <qStart>
> > > with osisID or
> > > are
> > > > > you refereeing to some other meaning of "link"?
> > > > >
> > > > >
> > > > >>>Is there a reason that milestoneSe is required?
> What good are
> > > start
> > > > >>
> > > > > and
> > > > >
> > > > >>>end milestones without a mechanism to find their partner?
> > > > >>>
> > > > >>
> > > > >>I don't read milestoneSe as being required? Reads
> use="optional"
> > > > >
> > > > >
> > > > > What I was trying to say and didn't was that I think
> > > "milestoneSe"
> > > > > should be required. (Sorry of the confusion.) Do you
> > > see any that
> > > > > milestoneSe should not be required?
> > > > >
> > > > >
> > > > > <snip>
> > > > >
> > > > > Todd
> > > >
> > >
> > >
>
>