{"action":"created","issue":{"url":"https://api.github.com/repos/oslc-op/oslc-specs/issues/153","repository_url":"https://api.github.com/repos/oslc-op/oslc-specs","labels_url":"https://api.github.com/repos/oslc-op/oslc-specs/issues/153/labels{/name}","comments_url":"https://api.github.com/repos/oslc-op/oslc-specs/issues/153/comments","events_url":"https://api.github.com/repos/oslc-op/oslc-specs/issues/153/events","html_url":"https://github.com/oslc-op/oslc-specs/issues/153","id":489454030,"node_id":"MDU6SXNzdWU0ODk0NTQwMzA=","number":153,"title":"OSLC query does not specify how oslc.orderBy affects the results","user":{"login":"oslc-bot","id":54863849,"node_id":"MDQ6VXNlcjU0ODYzODQ5","avatar_url":"https://avatars3.githubusercontent.com/u/54863849?v=4","gravatar_id":"","url":"https://api.github.com/users/oslc-bot","html_url":"https://github.com/oslc-bot","followers_url":"https://api.github.com/users/oslc-bot/followers","following_url":"https://api.github.com/users/oslc-bot/following{/other_user}","gists_url":"https://api.github.com/users/oslc-bot/gists{/gist_id}","starred_url":"https://api.github.com/users/oslc-bot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/oslc-bot/subscriptions","organizations_url":"https://api.github.com/users/oslc-bot/orgs","repos_url":"https://api.github.com/users/oslc-bot/repos","events_url":"https://api.github.com/users/oslc-bot/events{/privacy}","received_events_url":"https://api.github.com/users/oslc-bot/received_events","type":"User","site_admin":false},"labels":[{"id":1528509193,"node_id":"MDU6TGFiZWwxNTI4NTA5MTkz","url":"https://api.github.com/repos/oslc-op/oslc-specs/labels/Core:%20Query","name":"Core: Query","color":"c5def5","default":false},{"id":1492857788,"node_id":"MDU6TGFiZWwxNDkyODU3Nzg4","url":"https://api.github.com/repos/oslc-op/oslc-specs/labels/Priority:%20High","name":"Priority: High","color":"fbca04","default":false},{"id":1537530858,"node_id":"MDU6TGFiZWwxNTM3NTMwODU4","url":"https://api.github.com/repos/oslc-op/oslc-specs/labels/Xtra:%20Jira","name":"Xtra: Jira","color":"ededed","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2019-09-04T23:33:01Z","updated_at":"2019-09-04T23:33:07Z","closed_at":null,"author_association":"NONE","body":"OSLC Query 2.0 describes an oslc.orderBy query parameter. However, our returned results use unordered representations such as a list of statements with rdfs:member. If the query response is non-paged, then oslc.orderBy serves no purpose - a consumer cannot determine the order from the returned RDF.\n\nIt potentially serves a purpose for a paged response (either LDPC paging, or OSLC paging), where the first page should contain a subset of the sorted members starting at the beginning and so on. The OSLC Query 2.0 does not describe this usage pattern so it‘s unclear whether anything more was intended.\n\n---\n_Migrated from https://issues.oasis-open.org/browse/OSLCCORE-143 (opened by @DavidJHoney; previously assigned to @jamsden)_\n"},"comment":{"url":"https://api.github.com/repos/oslc-op/oslc-specs/issues/comments/528131869","html_url":"https://github.com/oslc-op/oslc-specs/issues/153#issuecomment-528131869","issue_url":"https://api.github.com/repos/oslc-op/oslc-specs/issues/153","id":528131869,"node_id":"MDEyOklzc3VlQ29tbWVudDUyODEzMTg2OQ==","user":{"login":"oslc-bot","id":54863849,"node_id":"MDQ6VXNlcjU0ODYzODQ5","avatar_url":"https://avatars3.githubusercontent.com/u/54863849?v=4","gravatar_id":"","url":"https://api.github.com/users/oslc-bot","html_url":"https://github.com/oslc-bot","followers_url":"https://api.github.com/users/oslc-bot/followers","following_url":"https://api.github.com/users/oslc-bot/following{/other_user}","gists_url":"https://api.github.com/users/oslc-bot/gists{/gist_id}","starred_url":"https://api.github.com/users/oslc-bot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/oslc-bot/subscriptions","organizations_url":"https://api.github.com/users/oslc-bot/orgs","repos_url":"https://api.github.com/users/oslc-bot/repos","events_url":"https://api.github.com/users/oslc-bot/events{/privacy}","received_events_url":"https://api.github.com/users/oslc-bot/received_events","type":"User","site_admin":false},"created_at":"2019-09-04T23:33:07Z","updated_at":"2019-09-04T23:33:07Z","author_association":"NONE","body":"@DavidJHoney: The spec is rather unclear on whether oslc.orderBy applies only to use of oslc.searchTerms or not.\n\nIn our last query working group meeting, there was a suggestion that we introduce a new property, perhaps oslc:order of type xsd:integer. This would represent the ordering of the returned members, analogous to oslc:score representing the full-text score ordering. There is a slight risk in doing so. If a domain has used oslc:order as a property, then the result of the query is that the additional oslc:order representing ordering may clash or conflict with real resource properties that might not even be an integer. However, if an implementation has done that, I think that‘s a defect in the implementation. It should not use a public namespace with vocabulary terms that are not defined as part of that public vocabulary, and instead use a private namespace.\n\nThe advantage of introducing oslc:order (as a MAY rather than a MUST) is that it provides clients with a sorted membership, even in cases where a paged response is not used. If that property is absent, then for the non-full-text-search use case, I think that spec needs to be clearer about inferring ordering.\n\nThe other point relates to oslc.select and [https://issues.oasis-open.org/browse/OSLCCORE-123](https://issues.oasis-open.org/browse/OSLCCORE-123). If we agree that proposal, that would have to exclude oslc:order. In other words, if oslc.select is omitted, return the query result container and only one statement for each member and its oslc:order value."}}
{"actor":{"display_login":"oslc-bot"}}