[oslc-core] Fw: Questions on Query in Core Spec.
Tack Tong
tacktong at ca.ibm.com
Mon Apr 26 12:33:50 EDT 2010
Arthur,
Thanks for the response.
1. "GET the service provider and look for the shape resources. Find the one
for the rdf:type of the initial resource." In the Core Spec., oslc:shape
only got defined within the context of Creation Factory and Query
Capability. There is no way to relate a rdf:type of the initial resource
with a Creation Factory. Just looking at a Creation Factory, there is no
way to tell which resource type it is for. One have to look into the
oslc:shape it refers to find out the type of the resource. It is not
practical to get all resource shapes in all Creation Factory and figure out
which one matches. Also, we should not assume a shape for creation is the
same as the shape for query. Similar situation for oslc:shape in Query
Capability. It looks like we need either 1) be able to specify resource
shape of all resources (outside context of Creation Factory and Query
Capability) in the Service Provider Resource, or 2) specify the shape in
the original resource itself.
2. So, oslc.properties=*{*{*}} would get me all properties to 2 level deep
nested, right?
Tack Tong
IBM Rational software
tacktong at ca.ibm.com
905-413-3232
tie line 313-3232
----- Forwarded by Tack Tong/Toronto/IBM on 04/26/2010 12:19 PM -----
|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Arthur Ryman/Toronto/IBM |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Tack Tong/Toronto/IBM at IBMCA |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Cc: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|oslc-core at open-services.net, oslc-core-bounces at open-services.net |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|04/26/2010 10:25 AM |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Re: [oslc-core] Questions on Query in Core Spec. |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
Tack,
1. Correct - you don't create a Query Capability for every resource since
there are an unbounded number of them. You'd only create Query Capabilities
for a few "root" resources. You'd query those to find other resources. To
discover the shape of a resource do the following:
GET the resource and look at its rdf:type and other properties. One of
them should link back to the service provider, directly e.g.
oslc:serviceProvider, or indirectly.
GET the service provider and look for the shape resources. Find the one
for the rdf:type of the initial resource.
2. Correct, oslc.properties=*{*} matches all the properties of a resource,
and all of its nested properties (to depth 1).
Regards,
___________________________________________________________________________
Arthur Ryman, PhD, DE
Chief Architect, Project and Portfolio Management
IBM Software, Rational
Markham, ON, Canada | Office: 905-413-3077, Cell: Twitter | Facebook |
416-939-5063 YouTube
|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Tack Tong/Toronto/IBM at IBMCA |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|oslc-core at open-services.net |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|04/25/2010 10:15 PM |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|[oslc-core] Questions on Query in Core Spec. |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Sent by: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|oslc-core-bounces at open-services.net |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
1. One can use oslc.properties to query on an OSLC resource. e.g.
http://example.com/bugs/4242?oslc.properties=dc:title,dc:creator
{foaf:givenName,foaf:familyName}
If I was given the URL of a resource (such as http://example.com/bugs/4242
), how do I find out its Resource Shape so that I know what are the
properties to query on. I don't think I can create a self subject Query
Capability of every individual resource.
2. The wildcard oslc.properties=* and oslc.select=* should return all
properties of the resource and all properties of the members in the list.
How do I specify to return all properties including properties of all
nested properties? Do I use oslc.properties=*{*} or something similar?
Tack Tong
IBM Rational software
tacktong at ca.ibm.com
905-413-3232
tie line 313-3232_______________________________________________
Oslc-Core mailing list
Oslc-Core at open-services.net
http://open-services.net/mailman/listinfo/oslc-core_open-services.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20100426/f5864bf0/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ecblank.gif
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20100426/f5864bf0/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 11587942.gif
Type: image/gif
Size: 360 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20100426/f5864bf0/attachment-0001.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 11589837.gif
Type: image/gif
Size: 7568 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20100426/f5864bf0/attachment-0002.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20100426/f5864bf0/attachment-0003.gif>
More information about the Oslc-Core
mailing list