Jim, Thx. That's a perfect example of using a member property other than rdfs:member.
Regards, ___________________________________________________________________________ Arthur Ryman DE, PPM & Reporting Chief Architect IBM Software, Rational Toronto Lab | +1-905-413-3077 (office) | +1-416-939-5063 (mobile) From: James Conallen/Philadelphia/IBM@IBMUS To: Arthur Ryman <[email protected]> Cc: Denilson Nastacio/Raleigh/IBM@IBMUS, Joe Ross/Austin/IBM@IBMUS, [email protected], [email protected] Date: 09/22/2011 12:07 PM Subject: Re: [oslc-core] Resource shapes in query capability A good example of this can be found here: http://open-services.net/bin/view/Main/OSLCCoreSpecRDFXMLExamples#Specify_a_query_resource_shape This query base shape indicates that there is only one 'kind' of resource, a http://example.com/blogs/commentshape that can be members of this query base. Thanks, jim conallen Rational Design Management (DM) Lead Architect, OSLC AM Lead [email protected] Rational Software, IBM Software Group From: Arthur Ryman <[email protected]> To: Joe Ross/Austin/IBM@IBMUS Cc: [email protected], [email protected], Denilson Nastacio/Raleigh/IBM@IBMUS Date: 09/19/2011 03:41 PM Subject: Re: [oslc-core] Resource shapes in query capability Sent by: [email protected] Joe, The query base is itself a resource so the link to the resource shape describes the properties of the query base. You could GET the query base and receive back a resource with those properties (maybe a title or description, and lots of members). At least one of those properties should be a membership property, and the values (objects) of this member property are the resources that belong to the query capability. Below is a SPARQL graph pattern that I hope helps. There are a few resources involved here, but they are all linked to each other. You start from the oslc:QueryCapability (?queryCapability) resource and get its oslc:ResourceShape (?queryBaseShape). You look at its oslc:Property resources and find the one that describes membership (?memberProperty). Then you look at its value to get the oslc:ResourceShape of the member resources (?memberShape). # this triple comes from the oslc:QueryCapability resource ?queryCapability oslc:resourceShape ?queryBaseShape . # these triples come from the oslc:ResourceShape resource of the query base ?queryBaseShape a oslc:ResourceShape . ?queryBaseShape oslc:property ?memberProperty . # these triples come from the oslc:Property resource for the member property of the query base ?memberProperty a oslc:Property . ?memberProperty oslc:isMemberProperty true . ?memberProperty oslc:valueShape ?memberShape . # ?memberShape is the oslc:ResourceShape of the member resources Regards, ___________________________________________________________________________ Arthur Ryman DE, PPM & Reporting Chief Architect IBM Software, Rational Toronto Lab | +1-905-413-3077 (office) | +1-416-939-5063 (mobile) From: Joe Ross <[email protected]> To: [email protected] Cc: Denilson Nastacio <[email protected]> Date: 09/18/2011 07:14 PM Subject: [oslc-core] Resource shapes in query capability Sent by: [email protected] We are trying to use resource shapes to advertise metadata about resources types that can be queried by OSLC clients. However, the description in the table in the OSLC Core spec seems to indicate a different usage, which is not clear: "oslc:resourceShape zero-or-one ... The Query Capability SHOULD provide a Resource Shape that describes the query base URI. " Is the intent that a query capability can only be used to query for instances of a single type of resource, since "occurs" is zero-or-one? Also, not clear what is meant by "a Resource Shape that describes the query base URI." We thought that the Resource Shape would be used to describe the resources that are managed by the provider and can be searched/retrieved using the query URL. If not, then it's not clear where we can expose that metadata to clients. This other paragraph later on in the specification seems to describe the use that we intended: "An OSLC Service may provide one or more Query Capabilities to enable query of resources. A Query Capability provides a base URI for forming Query Resource URIs and MAY provide Resource Shapes that describe the property values that may be expected in the resources that are queryable via the query capability. Thus, Query Capabilities provide a way to discover the resources managed by an OSLC Service. " This seems to indicate that there can be multiple resource shapes for a query capability and that they describe properties of the resources being managed by the provider. Which of these is correct? Thanks, ================================================ Joe Ross/Austin/IBM, [email protected] Tivoli Autonomic Computing & Component Technologies 512-286-8311, T/L 363-8311_______________________________________________ Oslc-Core mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-core_open-services.net _______________________________________________ Oslc-Core mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-core_open-services.net
