atom feed20 messages in org.oasis-open.lists.search-ws-chairRE: [search-ws-comment] searchRetriev...
FromSent OnAttachments
Tim WilliamsAug 11, 2009 5:02 am 
LeVan,RalphAug 11, 2009 6:24 am 
Tim WilliamsAug 11, 2009 7:56 am 
LeVan,RalphAug 11, 2009 8:00 am 
Tim WilliamsAug 11, 2009 10:02 am 
Hammond, TonyAug 12, 2009 12:36 am 
Tim WilliamsAug 12, 2009 4:32 am 
Hammond, TonyAug 12, 2009 7:40 am 
Tim WilliamsAug 12, 2009 8:09 am 
Matthew DoveyAug 12, 2009 8:28 am 
Matthew DoveyAug 12, 2009 8:30 am 
Tim WilliamsAug 12, 2009 9:12 am 
Hammond, TonyAug 14, 2009 5:54 am 
Hammond, TonyAug 14, 2009 6:16 am 
Ray Denenberg, Library of CongressAug 14, 2009 7:05 am 
LeVan,RalphAug 14, 2009 7:42 am 
LeVan,RalphAug 14, 2009 7:51 am 
Ray Denenberg, Library of CongressAug 14, 2009 11:44 am 
Hammond, TonyAug 20, 2009 6:27 am 
Ray Denenberg, Library of CongressSep 14, 2009 11:59 am 
Subject:RE: [search-ws-comment] searchRetrieve Accept Parameters
From:LeVan,Ralph (lev@oclc.org)
Date:Aug 11, 2009 8:00:33 am
List:org.oasis-open.lists.search-ws-chair

There is nothing about URL templates that stop content negotiation. But, the
applications that are using OpenSearch description documents do not typically do
that. They rely on the URL to do the right thing for them.

Take a look at some of those description documents. You'll see plenty of
examples of parameters that look like "&r=rss". That's embedded content
negotiation.

Ralph

-----Original Message----- From: Tim Williams [mailto:will@gmail.com] Sent: Tuesday, August 11, 2009 10:57 AM To: LeVan,Ralph Cc: sear@lists.oasis-open.org Subject: Re: [search-ws-comment] searchRetrieve Accept Parameters

Really? URLTemplates don't preclude you from regular HTTP content negotiation - it's ultimately just a URL. I've implemented opensearch and relied on regular HTTP conneg, is there something I'm missing here?

On Tue, Aug 11, 2009 at 9:25 AM, LeVan,Ralph<lev@oclc.org> wrote:

The need comes from the OpenSearch community.  They communicate with servers using URL templates and have no way of specifying the format of the response, other than through parameters in the URL.  So, they, and hence we, must embed content negotiation in our URLs.

-----Original Message----- From: Tim Williams [mailto:will@gmail.com] Sent: Tuesday, August 11, 2009 8:03 AM To: sear@lists.oasis-open.org Subject: [search-ws-comment] searchRetrieve Accept Parameters

I'm reading the sru-2-0-draft dated July 22, 2009.  Is there discussion somewhere that explains the rationale/need for supplying custom http-style parameters (sec 4.9) that duplicate the HTTP Headers themselves?

Thanks, --tim

-- This publicly archived list offers a means to provide input to the OASIS Search Web Services TC.

In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting.

Subscribe: sear@lists.oasis-open.org Unsubscribe: sear@lists.oasis-open.org List help: sear@lists.oasis-open.org List archive: http://lists.oasis-open.org/archives/search-ws-comment/ Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: http://www.oasis-open.org/maillists/guidelines.php Committee: http://www.oasis- open.org/committees/tc_home.php?wg_abbrev=search-ws Join OASIS: http://www.oasis-open.org/join/

-- This publicly archived list offers a means to provide input to the OASIS Search Web Services TC.

In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting.

Subscribe: sear@lists.oasis-open.org Unsubscribe: sear@lists.oasis-open.org List help: sear@lists.oasis-open.org List archive: http://lists.oasis-open.org/archives/search-ws-comment/ Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: http://www.oasis-open.org/maillists/guidelines.php Committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=search-ws Join OASIS: http://www.oasis-open.org/join/