[oslc-core] Better name for OSLC indexing profile

[Frank Budinsky]

Hi Benjamin,

> A question for my own understanding...if a service provider
> annotates more than 1 of its Query Capabilities via the oslc:usage
> parameter, then how does a consumer know which of the (possibly
> many) Query Capabilities is exposing the "total set of resources"?

If there is more than 1, then the union of the resources returned by all of
them is the total set.

Normally, I would expect multiple Query Capabilities to be used when a
service provider wants to return different types of resources in separate
lists. In that case it might have one "published" Query Capability per
resource type, in which case there would be no overlap between the
resources in the multiple lists. More generally, however, there could
conceivably be some overlap between the resources returned by multiple
"published" Query Capabilities. My feeling is that, although this isn't the
most efficient way to do it (so we should recommend no overlap), but it
shouldn't be disallowed since it may be the easiest way for a service
provider to implement the "Resource Publishing" capability by reusing other
existing Query Capabilities.

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