RE: Comment on Fragment Identifiers


This is a case of simplicity versus consistency with WSDL 2.0.

In WSDL 2.0, the MEPs are an extension point and that third parameter can 
have any value (as defined by a new MEP). It's the message label and not 
restricted to in and out. It defines a role.

I'm not advocating either way - just explaining the origin.

Arthur Ryman,
IBM Software Group, Rational Division

phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text:

"Ashok Malhotra" <> 
Sent by:
12/13/2006 05:08 PM

"" <>
"" <>
RE: Comment on Fragment Identifiers

Resending.  Last attempt was truncated.

As you may know, the WS-Policy WG has been doing some work on defining
element identifiers for WSDL 1.1 elements.  We are trying to align this
work with the WSDL 2.0 fragment identifiers described in Appendix A.2 of
the WSDL 2.0 Candidate Recommendation draft of 2006-03-27.

In looking at Appendix A.2 I came across two situations where I think the 
syntax can be improved.  Consider
this fragment identifier takes 3 parameters.  The first two take names as 
values while the third takes a message label whose value can only be 
"input" or "output".  Having a parameter that takes a keyword as value 
seems foreign to the general design in which parameters take names as 
values.  Thus, I suggest that the label be added to the name of the 
fragment identifier and it have only two parameters, thus:

The following row in the table can also be improved.
can be replaced by two identifiers

Similar suggestions apply to 

I hope you will consider these changes.

All the best, Ashok

Received on Wednesday, 13 December 2006 22:32:10 UTC