[oslc-core] Example of a self-subject query capability representation?
ryman at ca.ibm.com
Wed Apr 28 17:23:40 EDT 2010
Thx for the clarification on Resource Shapes. I now understand that they
are first class resources and have URLs. That is exactly what we need so
that a common Resource Shape resource can be referenced by any
oslc:Property that has the described resource as its range.
For queries, we only need to know the Resource Shape of the query base
URL. That tells us what properties it has so we can write queries. We do
NOT need the shape of the query response since that can be inferred from
the query parameters, i.e. oslc.properties, oslc.from, and oslc.select
tell us the properties that come back.
Arthur Ryman, PhD, DE
Chief Architect, Project and Portfolio Management
IBM Software, Rational
Markham, ON, Canada | Office: 905-413-3077, Cell: 416-939-5063
Twitter | Facebook | YouTube
Dave <snoopdave at gmail.com>
oslc-core <oslc-core at open-services.net>
04/28/2010 11:33 AM
Re: [oslc-core] Example of a self-subject query capability representation?
oslc-core-bounces at open-services.net
On Wed, Apr 28, 2010 at 10:03 AM, Arthur Ryman <ryman at ca.ibm.com> wrote:
> 3. * If you define a single-subject query must you also define the
> "shape" of the resulting response And specifically, how did we know,
> in Tack's example, that the root element would be <ems:ProjectList>?
> In the definition of a query capability, the oslc:shape property SHOULD
> give the Resource Shape of the subject resources.
A query capability can have zero-or-more shapes which reflect the
different types of resources that can be queried via the capability,
not the shape of the resulting query response.
Based on what I understand about single-subject queries so far, it
appears that we need to use shapes in two different ways in a query
1) One shape defines the query response that comes back from a query
2) Another set of shapes define the shapes of resource that you query over
Is that correct? If so, that's not what we cover in the spec.
Seems like the shape for use #1 above should be defined in the Core
spec and the shapes used in #2 should be defined by various domain
> I think the current design does not allow top-level Resource Shape
> resources. It would make more sense if we could define top-level
> Shape and then refer to them via URLs for the other resources.
Actually, it does. Resource Shapes each exist at a URI.
Oslc-Core mailing list
Oslc-Core at open-services.net
More information about the Oslc-Core