[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [search-ws-comment] searchRetrieve Accept Parameters
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" <williamstw@gmail.com> To: <search-ws-comment@lists.oasis-open.org> Cc: "Matthew Dovey" <m.dovey@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.dovey@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: search-ws-comment-subscribe@lists.oasis-open.org > Unsubscribe: search-ws-comment-unsubscribe@lists.oasis-open.org > List help: search-ws-comment-help@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/ >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]