OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

search-ws message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [search-ws] queryn: A proposal for SRU to facilitate formsprocessing


> but am less convinced about your point b) which has to do
> with presentation. In my opinion presentation (or wire encoding) is purely an
> SRU function and has nothing to do with CQL. SRU is the protocol whose job
> is to get the query across. Whether the query travels wholesale through a
> single "query" parameter or is split up over mutiple querylets (can I use that
> word? :) as signalled by a "queryn" parameter does not affect the query
> itself.

Semantically the query is unchanged, syntactically it is.

In the same way in classical propositional logic we have the "standard" notation (e.g. a ^ b) but some use Lukasiewicz's notation (e.g. Kab). Whilst both notations express the same query, I would regard these as different queryTypes.

Similarly, if for some reason, I decided to write a variant of CQL which used polish (or reverse polish) notation instead of infix, that would be a different queryType.

I think, there may be a nomenclature problem, as I agree that these are the same type of query, but not the same queryType! To me the queryType parameter instructs the SRU server which parser it should use to read the incoming query. The SRU server will require a different parser depending on whether the CQL is encoded in the normal format, your form-based encoding or my mythical polish variant.

Matthew


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]