OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (OSLCCORE-105) Query spec does not define behaviour of oslc.where or oslc.searchTerms if not implemented

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

James Amsden commented on OSLCCORE-105:

A client could easily discover this by attempting the query and seeing if there are any results. That is, when a client executes a query that is properly expressed (no syntax errors or invalid references), then the would naturally expect the server to provide a result. If the server doesn't implement the particular query feature, then it could return an empty result. This would not allow the client to distinguish between an actual empty result or an unsupported feature. Its not clear the client would do much different in either case because the result is the same - no data from the query. 

However, defining an oslc:Error that indicates the server doesn't provide the feature would be useful. 

> Query spec does not define behaviour of oslc.where or oslc.searchTerms if not implemented
> -----------------------------------------------------------------------------------------
>                 Key: OSLCCORE-105
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-105
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Task
>          Components: Query
>            Reporter: David Honey
>            Assignee: James Amsden
> https://open-services.net/bin/view/Main/OSLCCoreSpecQuery describes two differenty types of query:
> 1) A text search query specified by oslc.searchTerms
> 2) A property graph based query specified by oslc.where
> In order to ease the implementation buden of the spec, we should allow servers to implement one but not necessarily both. Currently a client has no means of discovering whether either or both are supported before issuing a query request.
> The spec should define the behaviour if oslc.searchTerms or oslc.where is specified but the server does not support that capability.

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]