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:Ray Denenberg, Library of Congress (rd@loc.gov)
Date:Sep 14, 2009 11:59:33 am
List:org.oasis-open.lists.search-ws-chair

Is everyone on the TC comfortable with the conclusion of this discussion?

And what was the conclusion? I assume the conclusion is that we will keep the parameter - both in the APD and SRU 2.0. However we need to be able to write up our reasoning coherently since this was a public comment from someone outside the TC.

Need a volunteer to write it up.

--Ray

----- Original Message ----- From: "Tim Williams" <will@gmail.com> To: <sear@lists.oasis-open.org> Cc: "Matthew Dovey" <m.do@jisc.ac.uk> Sent: Wednesday, August 12, 2009 12:13 PM Subject: Re: [search-ws-comment] searchRetrieve Accept Parameters

On Wed, Aug 12, 2009 at 11:29 AM, Matthew Dovey<m.do@jisc.ac.uk> wrote:

Don't get me wrong, I'm supportive of urls that give some indication of the format - and most implementors will likely expose different formats via different URI patterns (its a little easier to dispatch on anyway), the question is only whether that should be a part of the spec or not - and I suggest not.

Some of the client applications built using SRU have been very thin clients consisting of little more than client side XSLT generating a HTML interface. It is because of these use cases, that there was pressure to ensure that there was a mechanism within the spec to achieve all the functionality via URLs

In such a case, it seems the guidance should be to generate your HTML interface from a transform of the Explain descriptor. Doing so, one would simply parse the descriptor looking and target a URL with a 'type' attribute they understood (e.g. select="url[@type='text/html']/@href) - same as Firefox does with an OpenSearch descriptor.

--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/