We've had a couple of scenarios that don't seem to be addressable using the OSLC core 2.0 query syntax:
1. Finding all resources that don't have a particular value for a property. The != operator won't work for this, because in the case of multi-valued properties, records will be returned as long as there is a value that is not equal, even if there is also a value that is equal. This would require a unary "not" logical operator. 2. Finding all resources that have any value for a particular property (matching on predicate, regardless of value). This is probably would probably be best handled by a unary "exists" operator, or support for wildcard as the value in oslc.where clauses. Currently the grammar seems to only allow for wildcard for the predicate. So, am I correct in this assessment? If so, was this omission intentional (and if so what was the reason), or an oversight? ================================================ Joe Ross/Austin/IBM, [email protected] Tivoli Autonomic Computing & Component Technologies 512-286-8311, T/L 363-8311
