Find qualifiers in search ranges + related updates for Req 23

[Tom Bellwood <bellwood@us.ibm.com>]

I'm not convinced we need the all of these, but I agree some control here is requiredl. IMO we should try to keep the behavior here consistent with default behaviors expressed elsewhere. "exactMatch" is the default matching behavior and it already covers keyName and keyValue data in keyedReferences. It should be enhanced to apply to the various members of the keyedReferenceRange structure, including lowerValue, upperValue, lowerInclusive, upperInclusive and inverted. Better yet, we should also consider defining keyedReferenceRange to contain a keyedReference plus these other new elements/attributes we added. This would simplify the spec and the changes we have to make to take this related structure into account.

While we're at it, all of the other FQ's which reference bag elements need to be updated to take keyedReferenceRange into accoung (for example, caseSensitiveMatch and caseInsensitiveMatch need to now also include lowerValue and upperValue, and so on).

As for the qualifiers you've identified, should we look at trying to extend the approximateMatch notation and rules to achieve most of what's desired and add any new FQ's needed after that?

Thanks,
Tom Bellwood Phone: (512) 838-9957 (external); TL: 678/9957 (internal)
Co-Chair, OASIS UDDI Specification TC
STSM - Emerging Technologies
IBM Corporation

To: <uddi-spec@lists.oasis-open.org>
cc:
Subject: [uddi-spec] Do ranges require more FindQualifiers?




It just struck me that if we will be storing ranges in the registry, and allowing them in queries, we'll need more FindQualifiers to deal with the possible range v range requests:

1. subset = the range in the find request is a subset of the range stored
2. I need this resource between 9 and 10, it is available between 8 and 12 - match
3. superset = the range in the find request includes all of the range stored
4. I need the resource range to fall between 10 and 100, it is 30 to 40 - match
5. intersect = the range in the find request overlaps with the range stored (perhaps by a minimum amount)
6. I need at least one hour of this resource between 9 and 12, it is available 8 to 10 - match

Those are the  obvious ones, and the last one requires an additional parameter (I wonder where  we can put that extra parameter?).
 
What do you  think?
 
Tony Rogers
Computer Associates
Senior Architect
tel +61 3 9727 8916
fax +61 3 9727 3491
tony.rogers@ca.com