[OASIS Issue Tracker] (OSLCCORE-140) OSLC Core 3.0 Discovery does not describe the results of GET on a QueryCapability queryBase URL.

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

James Amsden created OSLCCORE-140:
-------------------------------------

             Summary: OSLC Core 3.0 Discovery does not describe the results of GET on a QueryCapability queryBase URL.
                 Key: OSLCCORE-140
                 URL: https://issues.oasis-open.org/browse/OSLCCORE-140
             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
          Issue Type: Bug
          Components: Core, Query
            Reporter: James Amsden
            Assignee: James Amsden


OSLC Core 3.0 Discovery defines QueryCapability and oslc:queryBase: The base URI to use for queries. Queries are invoked via HTTP GET on a query URI formed by appending a key=value pair to the base URI, as described in Query Capabilities section. But there is no Query Capabilities section in the Discovery document that describes what the results of such a GET would be, or addresses the OSLC Core 2.0 use of rdfs:member vs. ldp:member. Since ldp:member is a subproperty of rdfs:member, OSLC Core 2.0 Query Capability's use of rdfs:member to list the members of a GET on a queryBase URL is compatible with the queryBase being an LDPC. However, this needs to be documented in the OSLC Core 3.0 Discovery specification and referenced in the updated OSLC Core 3.0 Query Capability specification.



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