[oslc-core] Oslc-Core Digest, Vol 14, Issue 30

[John Arwe]

Forgive me, but I'm confused.

> The current version of the proposal does a better job at meeting goal #2
> than #1. It says this:

Which #1 and #2.  I see nothing labeled with those strings earlier in your 
message, nor the word "goal" or any spelling variant.

> In the simplest case, a service provider can provide exactly one Query
> Capability (i.e., queryBase URI) which includes all of its contained
> resources. On the other hand, it may instead provide several Query
> Capabilities, each exposing only a subset of the indexable resources. 
This
> is convenient if different types are most easily returned using custom
> member properties.

This set of alternatives appears to ignore a third case, i.e. multiple 
Query Capabilities are exposed and their set of enumerated resources 
overlap.  Or is that not relevant for some reason?

Best Regards, John

Voice US 845-435-9470  BluePages
Tivoli Component Technologies



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20110328/31c20d94/attachment-0003.html>