[oslc-core] Resources from a different service
Dragos Cojocari
dragos.cojocari at ro.ibm.com
Thu Oct 21 06:23:41 EDT 2010
Hey all,
as resources exposed by one provider can be linked to resources from
another provider some questions arise on how they can be retrieved:
1. can the Resource Shape for a resource refer the resource shapes of the
resources of the other domains in the oslc:valueShape property?
2. if the answer to (1) is yes, and there is no obvious reason why it
shouldn't be, can one query service aggregate resources from multiple
providers?
I believe the answer to (2) is NO and in this case a different question
arises: how can a query consumer determine what resources can be obtained
( aggregated/in-lined) from one query service? in other words, how can the
consumer determine how to build the queries to retrieve the data:
- referenced resources from the same domain could be obtained with
a single query crafted to in-line the properties of the referenced
resources
- referenced resources from other providers would have to be
requested using multiple queries sent to multiple query services.
Example:
- single provider: the details of a "QM V2 TestPlan" and its "QM V2
TestCases" linked by http://open-services.net/ns/qm#usesTestCase ( as
described by
http://open-services.net/bin/view/Main/QmSpecificationV2Shapes)
- multiple provider: the details of a "CM V2 Change Request" and the
details of the "QM V2 Test Case" linked through
http://open-services.net/ns/cm#testedByTestCase ( as described by
http://open-services.net/bin/view/Main/CmSpecificationV2Shapes )
In the above examples the consumer needs to know that the details for the
"QM V2 Test Case" cannot be obtained from the same query service as the
"CM V2 Change Request".
Thanks and regards,
Dragos
Exceptand situatiile in care partile au convenit in alt mod: / Unless
stated otherwise above:
IBM România S.R.L.
Bucharest Business Park, Corp A2, Şos. Bucureşti-Ploieşti Nr. 1A, 013681
Bucureşti 1, ROMANIA
CIF RO378660, RC J/40/5106/1991
Cap.Soc. 41.670 Lei
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20101021/e0ad4be1/attachment-0003.html>
More information about the Oslc-Core
mailing list