[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [search-ws] 2.0 features (draft message to SRU implementors)
>> deprecate the PROX BOOLEAN operator and instead represent proximity by two methods: 1. >> adding a relation, 'window'. examples: >> * dc.title window/distance<5/unit=word "fries salt vinegar" >> (fries, salt, and vinegar all within a span of 5 words) >> *dc.title window/distance<5/unit=word ((fish and fries) and (salt or >> vinegar)) >> (fish and chips and one of salt or vinegar, in a 5 word window) >> * dc.title window/distance=2/unit=word/ordered "fries salt " >> (fries followed by salt with 2 words between) and 2. Adding a boolean modifier 'prox' which acts the same as the current boolean, however can be attached to either AND (the current style of proximity) or NOT for negative proximity -- eg: * "fish and" not/prox chips (fish and followed by anything other than chips) Hope that helps! Rob >> >> 3. Faceted Searching ("scan" a result set) >> One might search a library database for books about a particular > topic, >> and >> then see how many records there are in different time period >> >> 4. Result Set Size >> Allow the client to indicate how much effort the server should take to >> determine or estimate the number of records in the result set. >> Similarly, >> allow the response to estimate accuracy of the result-set-size >> reported. >> The server may be able to determine the exact number of records, or >> provide >> a realistic estimate, but it may be an expensive process. The server >> might >> prefer not go through that process unless the client requests that it >> do so. >> Or the client might want to explicitly request that the server go >> through, >> or not go through, that process. (The client might want the first 10 >> records, or any 10 records, regardless of how many records there are. >> In >> that case if the server goes through the process of determining how >> many >> records there are, it may go through an expensive process for nothing. >> There >> is also the special case where the server cannot determine or estimate >> the >> number of records in the result set. In that case it might be useful > to >> have >> a special value or some way to indicate this condition.) >> >> 5. Multiple Query Types >> CQL is currently the only query type used by SRU but there could be >> other >> query types as well, for example, Parameterized Query and XQuery. >> >> 6. Eliminate the Version and Operation Parameters >> These two parameters are based on the assumption that the same base >> URL >> might be used for different operations and versions. Instead, > different >> base >> URLs should be used. >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this mail list, you must leave the OASIS TC that >> generates this mail. Follow this link to all your TCs in OASIS at: >> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >> > > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]