On Fri, 15 Feb 2008, Doug Tody wrote:
>> The ambiguous case that result in the same difficulty that Paul referred to is
>> if the two versions can be described with the same capability type but the
>> values of the capability metadata are different. At the moment, the best way
>> to handle this case is to register these as separate resources.
>
> Guess I still don't understand why this is so. These are two
> separate capability elements, hence if the query is really looking
> for capability elements (which are what is now a "service") it
> should work. Maybe the issue is that we need to query the registry
> for capability elements rather than resources, now that we can have
> multiple capabilities per resource?
Actually, now that the point this out, this is not a problem. That is, not only do capability metatadata differ to distinguish them (as opposed to just, perhaps, a human-oriented text description), but you can still use the version attribute as the distinguishing key.
cheers,
Ray
Received on 2008-02-15Z17:23:27