RE: Using attributes to mark RefProp's and RefParam's

Hi dims:

One thing I haven't seen mentioned so far in this thread is the
following.  If indeed we assume that marking refp's is useful, we need
to ask if the marking is solely intended for those nodes which already
understand how to process WSA, or if it's also going to be useful in
order to protect against the kinds of security/speech-act issues that
have been discussed by myself, yourself, Rich, and others.  If the
former, an attribute is fine.  

If the latter, there will also have to be some kind of mechanism to
ensure that the attribute is understood by all nodes - in other words,
having a wsa:type attribute won't prevent your
<somens:DoSomethingInappropriate wsa:type="property"/> header from being
processed if the wsa:type attribute isn't understood, and since there's
no mustUnderstand for attributes, you would likely want something like a
<wsa:RefPs soap:mustUnderstand="true"/> header as well.

There is also a potential issue here of schema validation, and the fact
that although an element may have been scoped out for SOAP header use
(by putting the right attributeGroup in its schema), inserting a
wsa:type or other attribute may not be easy to process on some systems
which do explicit validation.  This probably won't be a huge issue, and
many such elements will simply allow arbitrary attributes, but it's
something to consider.

--Glen

> -----Original Message-----
> From: public-ws-addressing-request@w3.org 
> [mailto:public-ws-addressing-request@w3.org] On Behalf Of 
> Srinivas, Davanum M
> Sent: Wednesday, November 24, 2004 12:56 PM
> To: public-ws-addressing@w3.org
> Subject: Using attributes to mark RefProp's and RefParam's
> 
> Team, 
> 
> Me and Igor were chatting about how to mark RefProp's and 
> RefParam's on the way back AND still not "lose the ability to 
> leverage the SOAP processing model", here's the outcome.....Comments?
> 
> Suppose we have an EPR which says this: 
> <wsa:EndpointReference>
>    <wsa:Address>
>         http://www.example.com/services/someService 
> <http://www.example.com/services/someService> 
>    </wsa:Address>
>    <wsa:ReferenceProperties>
>         <tns:resourceID>DataChunk42</tns:resourceID>
>    </wsa:ReferenceProperties>
>    <wsa:ReferenceParameters>
>         <tns:expires>32000</tns:expires>
>    </wsa:ReferenceParameters>
> </wsa:EndpointReference> 
> 
> Can we have it come back as this? 
> <SOAP-ENV:Envelope>
>      <SOAP-ENV:Header>
>          <wsa:MessageID>msgid:1234567902282223</wsa:MessageID>
>          <wsa:To>http://www.example.com/services/someService</wsa:To>
>          <wsa:Action>http://www.example.com/someAction</wsa:Action>
>          
> <wsa:From>http://www.example.com/clients/someClient</wsa:From>
>          
> <wsa:ReplyTo><wsa:Address>http://www.example.com/clients/someO
therClient</wsa:Address></wsa:ReplyTo>
>          
> <wsa:FaultTo><wsa:Address>http://www.example.com/clients/yetAn
otherClient</wsa:Address></wsa:FaultTo>
>          <tns:resourceID 
> wsa:type="property">DataChunk42</tns:resourceID>
>          <tns:expires wsa:type="parameter">32000</tns:expires>
>      </SOAP-ENV:Header>
>      <SOAP-ENV:Body>
>         ...
>      </SOAP-ENV:Body>
> </SOAP-ENV:Envelope> 
> 
> Davanum Srinivas 
> Computer Associates 
> Senior Architect, Web Services Group 
> Tel: +1 508 628 8251 
> davanum.srinivas@ca.com 
> http://ws.apache.org/~dims/ <http://ws.apache.org/~dims/>  
> 
> Davanum Srinivas 
> Computer Associates 
> Senior Architect, Web Services Group 
> Tel: +1 508 628 8251 
> davanum.srinivas@ca.com 
> http://ws.apache.org/~dims/ <http://ws.apache.org/~dims/>  
> 
>

Received on Monday, 29 November 2004 16:31:02 UTC