RE: [search-ws] class name for new class of query

["Ray Denenberg, Library of Congress" <rden@loc.gov>]

Ralph, that's a valid point, but it's irrelevant to the issue I'm raising.

To your point: 

let's say you want to define "XQuery" for SRU. You write up a definition, in
that definition you say "and you put your XQuery string in a parameter named
'XQuery' in the request.  And you say the value of queryType in the request
should be 'XQuery'. And you say to omit the query parameter.  And you assign
that definition a URI.

Then I want to define "XQuery for SRU, but my definition is a bit different
from yours (I've profiled the W3C spec a bit differently) and in my
definition I say "and you put your XQuery string in the query parameter in
the request".  And I say the value of queryType in the request should be
'XQuery'.  And I assign that definition a URI.

And all this should work fine right?


Now to my point.   I'm trying to write procedures for all this; the
"classical" procedures (query parameter present) are all there already; the
new procedures (query parameter omitted, new parameters present) differ
considerably.  You might not consider there to be a considerable difference
in the class of queries, but it would help to have a name to reference the
new class, just for ease of describing the proceduures. 

--Ray




> -----Original Message-----
> From: LeVan,Ralph [mailto:levan@oclc.org]
> Sent: Monday, January 10, 2011 2:55 PM
> To: Denenberg, Ray; OASIS SWS TC
> Subject: RE: [search-ws] class name for new class of query
> 
> Or you have a community that expects it to be in a particular.  In the
> case of XQuery, I wouldn't be astonished if they wanted a parameter
> named "xquery".  It's not up to us to tell them how to send their
> queries.
> 
> Ralph
> 
> > -----Original Message-----
> > From: Ray Denenberg, Library of Congress [mailto:rden@loc.gov]
> > Sent: Monday, January 10, 2011 2:51 PM
> > To: 'OASIS SWS TC'
> > Subject: RE: [search-ws] class name for new class of query
> >
> > But not all non-cql query types are in this class. W3C XQuery, for
> example.
> > You would set queryType to XQuery and put the XQuery query in the
> query
> > parameter.
> >
> > (Somewhere there would be a definition of the XQuery query, and it
> would say
> > so, that the query goes in the query parameter.  I don't see any
> point
> in
> > having it create a new parameter just because it is different from
> cql. I
> > think the only time this whole feature would be useful is when you
> need to
> > have multiple parameters, so you can't fit the whole query in a
> single
> > parameter.)
> >
> > --Ray
> >
> > > -----Original Message-----
> > > From: LeVan,Ralph [mailto:levan@oclc.org]
> > > Sent: Monday, January 10, 2011 2:38 PM
> > > To: Denenberg, Ray; OASIS SWS TC
> > > Subject: RE: [search-ws] class name for new class of query
> > >
> > > non-cql queries.
> > >
> > > Ralph
> > >
> > > > -----Original Message-----
> > > > From: Ray Denenberg, Library of Congress [mailto:rden@loc.gov]
> > > > Sent: Monday, January 10, 2011 2:29 PM
> > > > To: LeVan,Ralph; 'OASIS SWS TC'
> > > > Subject: RE: [search-ws] class name for new class of query
> > > >
> > > > Because it's much easier to write procedures with a name to refer
> to.
> > > --Ray
> > > >
> > > > > -----Original Message-----
> > > > > From: LeVan,Ralph [mailto:levan@oclc.org]
> > > > > Sent: Monday, January 10, 2011 2:17 PM
> > > > > To: OASIS SWS TC
> > > > > Subject: RE: [search-ws] class name for new class of query
> > > > >
> > > > > What new class of queries are we talking about?  QueryTypes
> that
> > > choose
> > > > > not to use the "query" parameter?  Why should they be
> distinguished
> > > > > from those that do use the query parameter?
> > > > >
> > > > > Ralph
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Denenberg, Ray [mailto:rden@loc.gov]
> > > > > > Sent: Monday, January 10, 2011 2:12 PM
> > > > > > To: 'OASIS SWS TC'
> > > > > > Subject: [search-ws] class name for new class of query
> > > > > >
> > > > > > In describing this new class of query SRU will be
> accomodating,
> > > it
> > > is
> > > > > > difficult/awkward without having a name to call this class.
> Can
> > > we
> > > > > call these
> > > > > > "parameterized queries", parameter-bases queries", "component
> > > > > queries"? I'm
> > > > > > not thrilled with any of these though I could live with any
> of
> > > them
> > > > > and can't think
> > > > > > of anything I think is perfect.  Any other suggestions?
> > > > > >
> > > > > > --Ray
> > > > > >
> > > > > >
> > >
> ---------------------------------------------------------------------
> > > > > > To unsubscribe from this mail list, you must leave the OASIS
> TC
> > > that
> > > > > > generates this mail.  Follow this link to all your TCs in
> OASIS
> > > at:
> > > > > > https://www.oasis-
> > > > > open.org/apps/org/workgroup/portal/my_workgroups.php
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe from this mail list, you must leave the OASIS TC
> > > that
> > > > > generates this mail.  Follow this link to all your TCs in OASIS
> at:
> > > > >
> > >
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> > > >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this mail list, you must leave the OASIS TC that
> > generates this mail.  Follow this link to all your TCs in OASIS at:
> > https://www.oasis-
> open.org/apps/org/workgroup/portal/my_workgroups.php
> >
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php