[OASIS Issue Tracker] (OSLCCORE-153) Semantics of ">", ">=", "<", <=" with URI values

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/OSLCCORE-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=68534#comment-68534 ] 

David Honey commented on OSLCCORE-153:
--------------------------------------

https://www.w3.org/TR/rdf-sparql-query/#OperatorMapping doesn't appear to describe any use of comparing resource URIs. All the values for <, <=, >, >= are literals and not IRIs. If we're using SPARQL as our guide here (one that has issues - see https://issues.oasis-open.org/browse/OSLCCORE-134), then it would have been better if the syntax didn't allow it. If we don't change the syntax to disallow it, I think the spec should at least indicate that it might not supported and that a 501 Not Implelmented MAY be returned. Even if an implementation supports it, the semantics are not covered by SPARQL, and hence are likely to be implementation-dependent.

> Semantics of ">", ">=", "<", <=" with URI values
> ------------------------------------------------
>
>                 Key: OSLCCORE-153
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-153
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>          Components: Query
>            Reporter: David Honey
>            Assignee: James Amsden
>
> The query syntax for oslc.where supports a query term that uses ">", ">=", "<", or "<=" with a URI value. However, the semantics are undefined.
> For example, what does the following mean, if anything?
>     oslc.where=dcterms:creator > <http://example.com/user/David>
> The only use case I can think of where this might add value is where the value is a URI of an enumeration member. If an enumeration has members defined with rdf:value denoting ordering, then a query such as:
>     oslc.where=cm:severity > cm:Medium
> might be useful. However, the spec does not define how enumeration members might be compared.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)