[OASIS Issue Tracker] (OSLCCORE-100) Reference in old query spec does not exist in core 3.0

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

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

Jad El-khoury commented on OSLCCORE-100:
----------------------------------------

I also found section "4.10 Query" (https://tools.oasis-open.org/version-control/svn/oslc-core/trunk/specs/oslc-core.html#query) in Part1 of Core 3.0.

4.10.1 specifies that "OSLC Servers MAY support a Query Capability as defined in [OSLCQuery3]"

[OSLCQuery3] refers to Part8. But Part8 (as it stands) does not talk so much about the "Query Cabability" itself, with focus instead on the Query language/pattern.

So yes, a section on Query Capability is missing. If we add to Core section, we need to fix the reference in 4.10. 
Alternatively, extend Part 8, to define Query Capability?

> Reference in old query spec does not exist in core 3.0
> ------------------------------------------------------
>
>                 Key: OSLCCORE-100
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-100
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Task
>          Components: Query
>            Reporter: David Honey
>            Assignee: James Amsden
>
> In https://open-services.net/bin/view/Main/OSLCCoreSpecQuery under Graph Patterns:
> A Query Capability defines a starting subject resource, namely the base URI itself (see oslc:queryBase in the OSLC Core Specification - Query Capability). 
> However, there is no corresponding section in core 3.0 to reference. The link was to https://open-services.net/bin/view/Main/OslcCoreSpecification#Query_Capabilities. 
> However, there is https://tools.oasis-open.org/version-control/svn/oslc-core/trunk/specs/discovery.html#queryCapabilityShape. Should we reference that instead, or as well as some new core section?



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