Prateek
> (2) I am troubled by prescriptive advice given on lines 184-186 that
> describes a specific technique for identifying a security token.
> As we have discussed before, the requirement to connect a specific
> security token to a specific message is a general requirement
> extending beyond RX. It would be much better if this text were to
> make reference to Section 8 of WS-SC which describes this technique
> versus inventing it from scratch,
As I stated on the call the other day, I am strongly opposed to the RX
committee tying itself to the timetable of SX. If we have to have 2
lines of text that repeat something that may or may not be in the final
WS-SC that is a small price to pay to get our spec standardized and
usable. Once SC is standardized we can certainly revisit this section.
Alternatively the RSP profile can refer users to SC instead of our spec.
However it is not in the best interests of this specification to add a
dependency on "work-in-progress" at this late stage of our lifecycle.
Paul
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://feeds.feedburner.com/bloglines/pzf
"Oxygenating the Web Service Platform", www.wso2.com
