RE: Issue 17: support for SOAP role attribute

Can a role attribute contain a relative URI?  xs:anyURI allows this,
unless we add a restriction in prose.  If relative URIs are allowed, can
we support the empty value case without stepping on the infoset [base
URI] property?

> -----Original Message-----
> From: Martin Gudgin [mailto:mgudgin@microsoft.com]
> Sent: Wednesday, June 26, 2002 9:12 AM
> To: Jean-Jacques Moreau
> Cc: Web Service Description
> Subject: RE: Issue 17: support for SOAP role attribute
> 
> 
> Well, I think it sould probably just be 'role', as it appears on a
> soap:header element there is no need to qualify the attribute.
> 
> Gudge
> 
> -----Original Message-----
> From: Jean-Jacques Moreau [mailto:moreau@crf.canon.fr]
> Sent: 26 June 2002 16:25
> To: Martin Gudgin
> Cc: Web Service Description
> Subject: Re: Issue 17: support for SOAP role attribute
> 
> 
> This is much better, thanks. Actually, I think we should also change
> 'SOAP role' to 'soap:role'.
> 
> Jean-Jacques.
> 
> Martin Gudgin wrote:
> 
> > Also suggest you merge the following two sentences;
> >
> > 'Omitting the SOAP role attribute information item is equivalent to
> > indicating value of
> > "http://www.w3.org/2001/12/soap-envelope/role/ultimateReceiver".
> > An empty value is equivalent to omitting the attribute completely,
> > i.e. targeting the SOAP header block to an ultimate SOAP receiver.'
> >
> > To read
> >
> > 'A SOAP role attribute information item that is either absent or has
> > an empty value is equivalent to indicating a value of
> > "http://www.w3.org/2001/12/soap-envelope/role/ultimateReceiver" i.e.
> > targeting the SOAP header block to an ultimate SOAP receiver.'

Received on Wednesday, 26 June 2002 15:03:29 UTC