No.
It'd probably take 5 minutes to do, if you think anyone was interested.
They index names pretty much say it all.
I think I based it on some indexing suggestions from Kerry Blinco in
Australia.
Ralph
> -----Original Message-----
> From: Matthew J. Dovey [mailto:[log in to unmask]]
> Sent: Tuesday, September 14, 2004 3:55 PM
> To: [log in to unmask]
> Subject: Re: LOM
>
> Ralph,
>
> Have you written up the lom context set that you've used?
>
> Matthew
>
> > -----Original Message-----
> > From: Z39.50 Next-Generation Initiative [mailto:[log in to unmask]]
> > On Behalf Of LeVan,Ralph
> > Sent: Tuesday, September 14, 2004 6:03 PM
> > To: [log in to unmask]
> > Subject: Re: LOM
> >
> > And then I've been serving up and searching LOM records for
> > nearly 2 years
> > at this site: http://alcme.oclc.org/srw/search/SOAR
> >
> > Ralph
> >
> > > -----Original Message-----
> > > From: Matthew J. Dovey [mailto:[log in to unmask]]
> > > Sent: Tuesday, September 14, 2004 12:56 PM
> > > To: [log in to unmask]
> > > Subject: Re: LOM
> > >
> > > I don't think one exists - however this experimental server
> > > (http://adlibx.athabascau.ca/ADLib/SRU/) has basically
> > taken the LOM XML
> > > element names and substituted . For /
> > >
> > > Matthew
> > >
> > > > -----Original Message-----
> > > > From: Z39.50 Next-Generation Initiative [mailto:[log in to unmask]]
> > > > On Behalf Of Ray Denenberg, Library of Congress
> > > > Sent: 14 September 2004 16:57
> > > > To: [log in to unmask]
> > > > Subject: Re: LOM
> > > >
> > > > Can you point me to the lom context set?
> > > > --Ray
> > > >
> > > > ----- Original Message -----
> > > > From: "Robert Sanderson" <[log in to unmask]>
> > > > To: <[log in to unmask]>
> > > > Sent: Tuesday, September 14, 2004 6:34 AM
> > > > Subject: LOM
> > > >
> > > >
> > > > > On Tue, 14 Sep 2004, Matthew J. Dovey wrote:
> > > > > > I think that this might be worth considering in Eliot's
> > > > ISO 11179 call?
> > > > >
> > > > > As a great example of why we need ISO11179 rules and a clear and
> > > > > concise set of index name components, rather than blindly
> > > > copying xml
> > > > > element names out of schemas? :)
> > > > >
> > > > > ----------
> > > > > Date: Tue, 14 Sep 2004 03:09:06 +0100
> > > > > From: Scott Wilson <[log in to unmask]>
> > > > > To: [log in to unmask]
> > > > > Subject: Re: ADLib interface (was Re: Repository exposure)
> > > > >
> > > > > I strongly disagree; it isn't that CQL is a poor query
> > > > language - its
> > > > > that LOM is NOT a search vocabulary.
> > > > >
> > > > > The answer is to build a proper context set for LOM that can be
> > > > > queried efficiently. (An example I believe made it into the
> > > > appendices
> > > > > for the IMS DRI specification, but I may be wrong!)
> > > > >
> > > > > Xquery is not the answer as it request that the physical
> > > > encoding of
> > > > > the metadata must be XML, which will break federated
> > search across
> > > > > other repositories with different physical storage -
> > > > something the CQL
> > > > > was designed to abstract away from in the first place.
> > > > > -----------
> > > > >
> > > > >
> > > > > Scott is perfectly correct, in my opinion. The LOM context
> > > > set is a
> > > > > great example of how -not- to construct a context set, and
> > > > the trouble
> > > > > that you get into ("downright *broken*") if you do.
> > > > >
> > > > >
> > > > > ----------
> > > > > [a.b.c.d.role = contributor and a.b.c.d.name = XXXX]
> > > > >
> > > > > This will match on any record that 'XXXX' contributed
> > to, no matter
> > > > > what their role was in that particular contribution!!
> > > > > [...]
> > > > > There is no way I can see this problem easily rectified
> > > > within the CQL
> > > > > query syntax. It was just not designed to query
> > hierarchical data
> > > > > such as LOM. The real/ideal solution is to use a more
> > > > powerful query
> > > > > language such as XPath/XQuery.
> > > > > ----------
> > > > >
> > > > > Yes, CQL does not allow for relational queries using simple
> > > > booleans.
> > > > > However there are definitely ways to represent it. Consider the
> > > > > following possible queries, all of which could be used instead:
> > > > >
> > > > > dc.contributor = XXXX
> > > > > foo.name =/foo.role=contributor XXXX
> > > > > foo.name = XXXX and/foo.relatesTo foo.role = contributor
> > > > >
> > > > >
> > > > > Rob
> > > > >
> > > > >
> > > > > ,'/:. Dr Robert Sanderson
> > ([log in to unmask])
> > > > > ,'-/::::. http://www.o-r-g.org/~azaroth/
> > > > > ,'--/::(@)::. Special Collections and Archives,
> > > > extension 3142
> > > > > ,'---/::::::::::. University of Liverpool
> > > > > ____/:::::::::::::. L5R Shop:
> > > > http://www.cardsnotwords.com/ I L L U M
> > > > > I N A T I
> > > >
> >
|