[oslc-core] Programmatic determination of what is supported

[Steve K Speicher]

I'm not aware of any way.

There are 2 different scenarios where you may want to discover this:
1. When you have the oslc:ServiceProvider resource and may be able to look 
into it.
2. When you don't have oslc:ServiceProvider and only have a URI

There also may be cases where a service provider only supports selective 
properties on certain resource types, for example on Requirement but not 
ServiceProvider.

So the best we have at the moment is to just try it and look for non-400.

Thanks,
Steve Speicher | IBM Rational Software | (919) 254-0645


> From: James Conallen/Philadelphia/IBM at IBMUS
> To: oslc-core at open-services.net
> Date: 07/20/2010 01:10 PM
> Subject: [oslc-core] Programmatic determination of what is supported
> Sent by: oslc-core-bounces at open-services.net
> 
> As we see various implementations of any given OSLC specification, 
> even Core 2.0 ones, do we have any means to determine which of the 
> optional features a given implementation supports?
> 
> For example suppose we have two different implementation the OSLC xM
> specification which is a core 2.0 derived spec; "Product A" and 
> "Product B". Each developed by a different vendor, hence they made 
> different decisions on which optional features they support. For 
> example Product A supports selective properties and Product B does not.
> 
> Is there any way for a client to determine if the product supports 
> selective properties or not, without actually trying it and then 
> looking for a non-400 response code?
> 
> 
> <jim/>
> 
> jim conallen
> jconallen at us.ibm.com
> Rational Software, IBM Software Group
> _______________________________________________
> Oslc-Core mailing list
> Oslc-Core at open-services.net
> http://open-services.net/mailman/listinfo/oslc-core_open-services.net