[OASIS Issue Tracker] (OSLCCORE-176) Describing the difference between HyperGraphQL and OSLC Query

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

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

James Amsden commented on OSLCCORE-176:
---------------------------------------

I agree with David. Clearly there is a lot of fragmentation and incompatibilities in the persistence and query domain. The goal of OSLC query is to provide a minimal query capability that enables tool integration without limiting tool technical architectures. 

As we develop OSLC Query 3.0, we should keep this goal in mind and resist the temptation to add a lot of query facilities to OSLC Query that would make it more difficult to implement, harder to use for simple things, and more coupled to any particular persistence technology. All of those things limit rather than enable integration.

Any query facilities beyond those required to enable simple integration should be handled by the individual tools, and will likely introduce implementation specific query facilities.

 

> Describing the difference between HyperGraphQL and OSLC Query
> -------------------------------------------------------------
>
>                 Key: OSLCCORE-176
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-176
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Task
>          Components: Query
>            Reporter: Axel Reichwein
>            Assignee: James Amsden
>            Priority: Major
>
> HyperGraphQL ([http://hypergraphql.org/] ) looks very similar in functionality to OSLC Query. HyperGraphQL seems to have reached a relevant level of significance in the broad Linked Data community, as it is based on the popular GraphQL standard. At some point, developers will want to know the difference between HyperGraphQL and OSLC Query. Understanding these differences may also shape future OSLC Query standardization efforts.  



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)