[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OSLCCORE-153) Semantics of ">", ">=", "<", <=" with URI values
[ https://issues.oasis-open.org/browse/OSLCCORE-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=68519#comment-68519 ] James Amsden commented on OSLCCORE-153: --------------------------------------- Can we leverage XML semantics here? So in your example, > would would be based on lexical ordering of URIs - not something that would seem to be very useful unless the URIs were in some particular form. But not something it would see OSLC needs to worry about. > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]