Re: Collection paging section usefulness

If we define a collection to contain a query endpoint, it can contain an 
<accept>query-language</accept> which is simply listing what query languages 
the server is programmed to respond to (standardization of the names, or MIME 
types, or even file extensions would help but oh well) and leaves 
interoperability up to the implementor entirely.  Like so:

http://example.com/2006/query?q={...}&query-language='opensearch'

It's an act of faith on the part of the user that if (s)he uses valid 
OpenSearch syntax the server will respond with a document in the defined 
markup language for OpenSearch.  With XQUERY, the results are by default XML 
documents, whereas XPATH can return either markup or plain text.  Maybe the 
APP spec can IANA-register query-language values sorta like @rel, along with 
allowable response MIME types.  Or something.

-EJB

>-----Original Message-----
>From: Eric J. Bowman [mailto:eric-MkmoNbc1SAncr/OS1auqaA@xxxxxxxxxxxxxxxx]
>Sent: Thursday, August 17, 2006 06:08 AM
>To: 'Henry Story'
>Cc: atom-protocol-O6w3ZxSwtmQ@xxxxxxxxxxxxxxxx
>Subject: Re:  Collection paging section usefulness
>
>
>>
>>writing general purpose search endpoints is really complex. There is  
>>one being developed by the W3C called SPARQL. Combine Atom, AtomOwl  
>>and SPARQL and you get
>>
>>http://intertwingly.net/wiki/pie/PaceSparqlLink
>>
>
>Why does it have to be complex?  Let's not call it a "search endpoint", come 
>to think of it, let's call it a "query endpoint".  Whatever language you wish 
>to define as supported, becomes supported at whatever locations you choose to 
>define (somehow).  Like so:
>
>http://example.com/query?q={whatever-floats-yer-boat}&query-language='sparql'
>http://example.com/2006/jul/query?q={...}&query-language='xquery'
>
>And so on and so forth.  Because the one thing REST interfaces to query 
>languages all seem to have in common, is the query goes between the curly 
>braces.  All a client needs is a service document to tell them what the query 
>URI is for a collection (somehow).
>
>-EJB
>
>>
>>Henry
>>
>>Foaf name: http://bblfish.net/people/henry/card#me
>>
>>
>>> -EJB
>>>
>>>>
>>>> - Sylvain
>>
>>
>
>
>