[OASIS Issue Tracker] (OSLCCORE-145) Resource shape for use with oslc.query and oslc.select

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

     [ https://issues.oasis-open.org/browse/OSLCCORE-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Honey updated OSLCCORE-145:
---------------------------------

        Summary: Resource shape for use with oslc.query and oslc.select  (was: Resource shape for use with oslc.select)
    Description: 
Currently, the only resource shape available for a query user is the maximum of one specified by oslc:resourceShape in the oslc:queryCapability. That resource shape relates to the properties of the query base URI and provides the properties that may be referenced in any oslc.properties query parameter value. It does <b>not</b> describe the properties of members.

How does a client discover what properties may be used with oslc.select or with oslc.where?

Not all member properties might be queryable. A resource shape for use with oslc.select might describe more OSLC properties than a resource shape for properties specified in oslc.where.

This seems like a major omission from the OSLC Core 2.0 and 3.0.


  was:
Currently, the only resource shape available for a query user is the maximum of one specified by oslc:resourceShape in the oslc:queryCapability. That resource shape provides the properties that are queryable for use with oslc.where. Curiously, this cardinality is inconsistent with oslc:creationFactory that supports Zero-or-many resource shapes.

How does a client discover what properties may be used with oslc.select?
The query resource shape is a starting point, but is likely to omit properties that would be available but are not queryable.

       Proposal:   (was: Allow a query capability to define a resource shape specific to use of oslc.select using a new predicate.)

> Resource shape for use with oslc.query and oslc.select
> ------------------------------------------------------
>
>                 Key: OSLCCORE-145
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-145
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>          Components: Query
>            Reporter: David Honey
>            Assignee: James Amsden
>
> Currently, the only resource shape available for a query user is the maximum of one specified by oslc:resourceShape in the oslc:queryCapability. That resource shape relates to the properties of the query base URI and provides the properties that may be referenced in any oslc.properties query parameter value. It does <b>not</b> describe the properties of members.
> How does a client discover what properties may be used with oslc.select or with oslc.where?
> Not all member properties might be queryable. A resource shape for use with oslc.select might describe more OSLC properties than a resource shape for properties specified in oslc.where.
> This seems like a major omission from the OSLC Core 2.0 and 3.0.



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