[osis-core] <rights> in <titlePage>

[Todd Tillinghast]

For the next release:
I think expressing copyright which falls under <rights> within <work> is
a natural thing to see on a title page, currently there is not <rights>
as a child of <titlePage>.

Is this something that makes sense to add?

Todd

> -----Original Message-----
> From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
> admin@bibletechnologieswg.org] On Behalf Of Patrick Durusau
> Sent: Sunday, December 07, 2003 9:26 AM
> To: osis-core@bibletechnologieswg.org
> Subject: Re: [osis-core] morph regex error
> 
> Troy,
> 
> I think the regex is correct, no hyphens are allowed. This does not
mean
> that you should use a range in any of these, although that is
possible.
> It does allow these to be used as osisRefs so that they can refer to
> other sources of information.
> 
> Perhaps we should revisit at the January OSIS meeting but I don't
think
> we will reach a different conclusion.
> 
> Hope you are having a great day!
> 
> Patrick
> 
> Troy A. Griffitts wrote:
> > :)
> >
> > Unless I'm going senile-- which I've been suspecting for some time
now--
> > I believe that the last discussion on this subject, before release
of
> > 2.0, concluded that lemma, xlit, gloss, and morph WOULD NOT be
> > restricted by osisRef syntax.  We would make a separate complexType
for
> > them, which basically would allow: prefix:any_string
> >
> > I think I wanted to allow spaces (expecially for gloss), Patrick
found
> > real world occurances of other systems that used prohibiting
characters,
> > as well.
> >
> > So the conclusion was either:
> >
> > prefix:any_string
> >
> > or
> >
> > prefix:any string
> >
> > I think Steve may have made some push for replacing the 'space' but
> > don't remember the conclusion on that one.
> >
> > But regardless, there are no spaces in my offending line that I
quoted
> > earlier, and yet I still get an error.
> >
> > If I have to remove the cobwebs to defend this again, I will try,
but
> > think it's just a mis-sight in the .xsd.
> >
> >     -Troy.
> >
> >
> >
> >
> > Chris Little wrote:
> >
> >> Okay, okay.  No need to shout.  Don't kill the messenger.  Etc. :)
> >>
> >> The problem with changing the format is that we can no longer use
> >> morph, lemma, etc. values as osisRefs.  As it stands, any of these
> >> attributes could double as an osisRef/osisID.  So your lexicon,
> >> organized by lemma, could have divisions with osisIDs that are the
> >> same as their lemma values.  Likewise, if you organize the Robinson
> >> morphology scheme as a sort of lexicon, you can look up entries and
> >> tag them with osisIDs that are identical to your morph value.
> >>
> >> --Chris
> >>
> >> Troy A. Griffitts wrote:
> >>
> >>> NO!
> >>>
> >>>
> >>> Chris Little wrote:
> >>>
> >>>> Troy A. Griffitts wrote:
> >>>>
> >>>>> Hey guys.  It seems we may have messed up the regex on the morph
> >>>>> attribute of <w>.
> >>>>>
> >>>>> Here my line:
> >>>>>
> >>>>> <w xml:lang="grc" lemma="strongs:15" morph="robinsons:V-PAM-2P"
> >>>>> xlit="la:agaqopoieite">GREEK UTF8 TEXT HERE</w>
> >>>>>
> >>>>>
> >>>>>
> >>>>> Here's the MSV error output:
> >>>>>
> >>>>> Error at line:279, column:117 of
> >>>>> file:///space/home/scribe/msv/./lexcounts
> >>>>>   attribute "morph" has a bad value: the value does not match
the
> >>>>> regular expression
> >>>>>
>
"((((\p{L}|\p{N}|_)+)(\.(\p{L}|\p{N}|_))*:)((((\p{L})|(\p{N})|_)+)(((\.(
\p
> {L}|\p{N}|_)+)*))?))".
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> The value you give has never been valid.  Hyphens have never been
> >>>> allowed in morph or lemma attributes (nor have spaces and various
> >>>> other characters).  I think the decision we made before releasing
> >>>> 2.0 was to force folks to transcode these as '_'.
> >>>>
> >>>> Does that work for you?
> >>>>
> >>>> --Chris
> >>>
> >>
> >>
> >>
> >> _______________________________________________
> >> 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
> 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