[oslc-core] Requests for unknown or unsupported properties

[Arthur Ryman]

John,

The semantics of the where clause is based on graph pattern matching. 
Therefore "property != X " should only succeed if there is at least one 
triple for property whose object is different than X.

Regards, 
___________________________________________________________________________ 

Arthur Ryman 

DE, Chief Architect, Reporting &
Portfolio Strategy and Management
IBM Software, Rational 

Toronto Lab | +1-905-413-3077 (office) | +1-416-939-5063 (mobile) 





From:
John Arwe <johnarwe at us.ibm.com>
To:
oslc-core at open-services.net
Date:
04/16/2012 08:20 AM
Subject:
Re: [oslc-core] Requests for unknown or unsupported properties
Sent by:
oslc-core-bounces at open-services.net



> > http://example.com/bugs?oslc.where=oslc_cm:approved!=true
> Same as previous.  Though it would be worth running a few tests to 
confirm 
> SPARQL behavior with some of these negative/edge cases.

Beware the negatives of multivalued properties. 
!= might be equivalent to ! ( = ) for single valued props, but not 
multivalued ones 
I had to referee some interesting "it's a bug!  no, it's a feechur!" 
arguments first time my implementers tried negating the = operator on the 
latter case. 
Best Regards, John

Voice US 845-435-9470  BluePages 
Tivoli OSLC Lead - Show me the Scenario 
_______________________________________________
Oslc-Core mailing list
Oslc-Core at open-services.net
http://open-services.net/mailman/listinfo/oslc-core_open-services.net