OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

search-ws message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Groups - Search WS TC Call (Conference Call) modified

Minutes added.

 -- Ray Denenberg

Search WS TC Call (Conference Call) has been modified by Ray Denenberg

Date:  Monday, 22 September 2008
Time:  09:30am - 10:30am ET

Event Description:
Toll-free number: 888-448-7101
International Dial-In: See http://www.intercall.com/sprintservices/SPCIntlAccessNumber.pdf

Participant code:7646073 (initiator add 8984)

Host: Ralph

1. Roll Call

2. LOM Requirements

3. Querying structured data  

4. Proximity 
    window operator, proximity as a boolean modifier, exclusion
     element proximity (see ://www.oasis-open.org/apps/org/workgroup/search-ws/email/archives/200809/msg00034.html)

5. query type(s)
   query type indication;  query types: CQL, XQuery, SPARQL, PQ, etc.

6. Faceted search

7. Description Document

8. Element Set Names

9. Proposed Charter for OASIS Content Management Interoperability Services (CMIS) TC

10. Other business

11. Next meeting.

Voting Members Present:  Kerry, Janifer, Ray
Absent: Ralph, Larry, Ashley, Rob, Matthew

NO QUORUM:   These notes are unofficial. Agreements reached by the participants are not official decisions and will be proposed for approval next meeting (if there is a quorum).

Guests: David Massart, Nigel Ward, Daniel Rehak

Structured Querying.

We discussed the classic example: "find 'A' and 'B' within the same container element  'C' "

A suggested approach is to introduce a new context set, 'element' which defines a prox modifier: element.unit, with a value of 'parentElement' and a modifier 'element.parentElementName'. Thus:

A   PROX/element.unit=parentElement/distance=0/element.parentElementName=C  B 

Or even simpler, dispense with unit and distance:

A   PROX/element.container=C  B 

This seems to be a promising approach. 

In general, the LOM data, though it appears to be highly structured, for searching, the access points can be flattened out to a large degree.   So an 'element' context set might not be overly complex. 

Multiple query types and the QueryType parameter.

Everyone agrees that SRU 2.0 should support multiple query types.  There are two basic approaches: 

(1) use the query parameter to carry queries of all types and add a queryType parameter to specify how the query is to be interpreted.  

(2) No 'query' parameter, no queryType parameter.  Use the query type as the parameter name.   For instance,  if the query is a CQL query, theparameter might be CQLQuery; if it is a lucene query the parameter might be luceneQuery.

The first approach seems to be favored over the second.   There also seems to be general consensus that the queryType parameter should be optional.  If omitted, there would be a default. There does not seem to be complete consensus on what that default should be.   Should there be a standard-wide (static) defalt, i.e. "cql"? Or should the default be server-specific (specified by Explain)?

Response Format

The issue of response format was raised.  Will there be a request parameter to request a response format?  

An alternative approach would be that the response format is bound to a binding. Thus for SRU 2.0, the response format would always be the SRU 2.0 response format defined in the protocol.  There could be a different binding For RSS, etc.

This needs further discussion. 


A draft TC charter has been submitted to establish the OASIS Content Management Interoperability Services (CMIS) Technical Committee.  The charter mentions  
* To assess the relationship of CMIS to other related standards and industry
efforts.  These include JCR (JSR-170, JSR-283), WebDAV, and other relevant
Kerry had brought up the suggestion that the relationship to our activity might also be relevant. 

Comments are due September 24.    Kerry will submit a comment on our behalf.

Next Meeting

As this call has no quorum and is missing several key members, it has not been as productive as we had hoped.  The next scheduled meeting (two weeks) will likely be cancelled, and the following Monday is a US holiday.  

We should not wait four weeks for the next call, so we will try to schedule a call next Monday, September 29.

This event is one in a list of recurring events.
Other event dates in this series:

Monday, 19 May 2008, 09:30am to 10:30am ET
Monday, 02 June 2008, 09:30am to 10:30am ET
Monday, 16 June 2008, 09:30am to 10:30am ET
Monday, 30 June 2008, 09:30am to 10:30am ET
Monday, 14 July 2008, 09:30am to 10:30am ET
Monday, 28 July 2008, 09:30am to 10:30am ET
Monday, 11 August 2008, 09:30am to 10:30am ET
Monday, 25 August 2008, 09:30am to 10:30am ET
Monday, 08 September 2008, 09:30am to 10:30am ET
Monday, 06 October 2008, 09:30am to 10:30am ET
Monday, 20 October 2008, 09:30am to 10:30am ET
Monday, 03 November 2008, 09:30am to 10:30am ET
Monday, 17 November 2008, 09:30am to 10:30am ET
Monday, 01 December 2008, 09:30am to 10:30am ET
Monday, 15 December 2008, 09:30am to 10:30am ET

View event details:

PLEASE NOTE:  If the above link does not work for you, your email
application may be breaking the link into two pieces.  You may be able to
copy and paste the entire link address into the address field of your web

PRODID:-//Kavi Corporation//NONSGML Kavi Groups//EN
X-WR-CALNAME:My Calendar
SUMMARY:Search WS TC Call (Conference Call)
DESCRIPTION:Toll-free number: 888-448-7101\nInternational Dial-In: See
  code:7646073 (initiator add 8984)\n\nHost: Ralph\n\nGroup: OASIS
  Search Web Services TC\nCreator: Ray Denenberg

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]