Dave, The example query response in the core spec is a mult-subject response since it begins with <rdf:RDF>.
A "container" resource or a "collection" resource is a plain old resource that has some multi-valued property that we regard as a membership property. The values of this property are the members of the container/collection/list/... We can filter, sort, etc. this set of members using "member list pattern" queries. The core spec links to examples of self-subject query responses [1]. For example, the resource http://braintwistors.example.com/ems10/Project is a container resource that contains the list of all project resources. It has a multi-valued property ems:memberProject that refers to the member projects. <ems:ProjectList xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"; xmlns:dc="http://purl.org/dc/terms/"; xmlns:ems=" http://open-services.net/software-metrics/"; rdf:about="http://braintwistors.example.com/ems10/Project";> <dc:title>BrainTwistors Corp. Project List</dc:title> <dc:description> This is the list of all Project resources contained in BrainTwistors Corp. MetricServer web application. </dc:description> <ems:service rdf:resource="http://braintwistors.example.com/ems10"; /> <ems:memberProject rdf:resource=" http://braintwistors.example.com/ems10/Project/2009"; /> <ems:memberProject rdf:resource=" http://braintwistors.example.com/ems10/Project/3707"; /> <ems:memberProject rdf:resource=" http://braintwistors.example.com/ems10/Project/3998"; /> <!-- Other members of this ProjectList resource have been omitted for brevity. --> </ems:ProjectList> The following query filters the project list: http://braintwistors.example.com/ems10/Project?oslc.where=dc:identifier= "2009" The query response is: <ems:ProjectList xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"; xmlns:dc="http://purl.org/dc/terms/"; xmlns:ems=" http://open-services.net/software-metrics/"; rdf:about="http://braintwistors.example.com/ems10/Project";> <ems:memberProject rdf:resource=" http://braintwistors.example.com/ems10/Project/2009"; /> </ems:ProjectList> [1] http://open-services.net/bin/view/Main/OslcSimpleQuerySemanticsV1#Examples Regards, ___________________________________________________________________________ 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 From: Dave <[email protected]> To: oslc-core <[email protected]> Date: 04/26/2010 12:45 PM Subject: [oslc-core] Example of a self-subject query capability representation? Sent by: [email protected] I need a little help understanding the most recent changes in the Query Capabilities section of the spec. We now have two types of query capabilities, multi-subject and self-subject but we only illustrate multi-subject queries in our examples. I'm trying to understand what a self-subject query response would look like. Here's how it is described in the Core spec: "The RDF/XML representation of the query result begins with a node element whose rdf:about attribute value is equal to the base URI. Typically, the base URI is a container resource that may have a long list of members, e.g. the list of all defects in a bug tracking system. Since the list may contains hundreds of thousands of members, queries are used to filter the list for members that satisfy certain conditions, e.g. the bugs that have high priority and were created this week." I don't know what "the base URI is a container resource that may have a long list of members" means. Are we using a multi-valued property here to hold the resources that match the query? Tack or Arthur, would one of you please provide a simple example of a self-subject query response? Thanks, - Dave _______________________________________________ Oslc-Core mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-core_open-services.net
