[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Issue 063 - WS-Discovery - Clarify matching behavior for empty<d:Types>, <d:Scopes> element
|
This issue is assigned the number 063. For further
discussions on this issue, please refer to this issue number or use this
thread. From: Vipul Modi Please defer discussions on this issue until a time this
issue is accepted and is assigned a number. Description: The Probe matching algorithm described in Section 5.1 does
not describe the behavior when <d:Types> is empty element. Should the
behavior be same as d:Types missing, i.e. do not include types in the matching
criteria or should it be that match the services that do not have any Type? Proposed Resolution: Types are matched using set operations, and the empty set
(denoted by <d:Types />) is a subset of every set of Target Service
types. Thus, <d:Types /> should match all Target Services, same as
if Types was not present in the Probe. Furthermore, a Target Service without a
port type does not make sense. The description of Types and Scopes element in Section 5.2
Probe should be changed as follows. /s:Envelope/s:Body/d:Probe/d:Types If omitted or empty, implied value is any
Type. /s:Envelope/s:Body/d:Probe/d:Scopes If
included, MUST be a list of absolute URIs. If omitted or empty,
implied value is any Scope. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]