I'm seriously contemplating the "Les Wibberly" option here! I've implemented the code to use http:accept already!

http://viaf.org/search?query=cql.any+all+"dempsey"+&version=1.1&maximumR ecords=100&sortKeys=holdingscount&http:accept=application/rss%2bxml <http://viaf.org/search?query=cql.any+all+%22dempsey%22+&version=1.1&max imumRecords=100&sortKeys=holdingscount&http:accept=application/rss%2bxml

This proposed change might end up costing me 10 minutes of reimplementation!

Otherwise, I don't care.

Ralph

From: Ray Denenberg, Library of Congress [mailto:rd...@loc.gov] Sent: Monday, June 08, 2009 2:57 PM To: sear...@lists.oasis-open.org Cc: Hammond,Tony Subject: [search-ws] http:accept

Quick feedback requested on this.

I've been having discussions with Tony Hammond on several topics. Following is an excerpt from one of his notes, note in particular the question in parenthesis at the bottom.

------------------------------------------------------------------------

--------------------

<!-- 2. queryType="cql" --> <Url type="application/xml" template="http://www.nature.com/opensearch? query={searchTerms} &amp;queryType={sru:queryType} &amp;http:accept={sru:httpAccept} " /> ===

(And btw, the parameter name 'http:accept' is awkward and out of step with other naming. What's wrong e.g. with 'httpAccept' or similar?)

------------------------------------------------------------------------

--------------------

I agree, the problem I see is that "http:" looks too much like a namespace prefix when it occurs in the context of Tony's example above.

I propose that we change these http: parameter names as suggested, i.e. change

http:accept to httpAccept, etc.

--Ray