Issue 124 - WS-Discovery - xAddrs in ResolveMatches issue

[Ram Jeyaraman <Ram.Jeyaraman@microsoft.com>]

This issue is assigned the number 124. For further discussions on this issue, please refer to this issue number or use this thread.

 

From: Dan Driscoll
Sent: Monday, December 15, 2008 8:41 PM
To: Ram Jeyaraman
Subject: NEW issue: WS-D xAddrs in ResolveMatches issue

 

Physically addressed services that do not have distinct xAddrs are currently forced to generate an empty xAddrs element or produce no ResolveMatches at all in response to a Resolve for their EPR.

 

Since not all clients have the same understanding of physical addresses as services (some clients may know nothing about HTTP, for instance) Target Services need a way to generate meaningful ResolveMatches messages without including empty elements.  That way, they can inform clients that their EPR should be interpreted as a physical address.

 

Proposed change:

·         Make xAddrs optional in ResolveMatches schema (add ‘minOccurs=”0”’)

·         Craft some language that makes xAddrs mandatory in ResolveMatches if the service has xAddrs.  I’ll work with Vipul to build this.