This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
This issue was first discussed in my note http://lists.w3.org/Archives/Public/public-ws-policy/2006Nov/0128.html It recommended that the syntax of the identifiers - wsdl11.portTypeMessageReference(portType/operation/message) - wsdl11.portTypeOperationFault(portType/operation/fault) be changed to - wsdl11.portTypeMessageInput(portType/operation) - wsdl11.portTypeMessageOutput(portType/operation) - wsdl11.portTypeMessageFault(portType/operation) Similar changes were recommended for the corresponding identifiers for the binding element. David Orchard argued that the syntax was designed to allign with the WSDL 2.0 syntax. So, I asked the WSDL 2.0 WG for their opinion. They explained their rationale in http://lists.w3.org/Archives/Public/public-ws-policy/2006Dec/0092.html Jonathan Marsh expressed their opinion succintly as "The WG expressed no preference on whether your suggested redesign was a benefit for WSDL 1.1 component designators, where there isn't support for MEP extensibility. We note that if consistency with WSDL 2.0 component designators is paramount, keeping this redundant information in the format would be desirable. Yet if simplicity is paramount, removing the redundant information as you suggest would be natural." Thus, we need to answer Jonathan question above and take the appropriate decision.
During F2F, WG agreed to change "In" to "input" and "Out" to "output" as per Dave O's email. Bug is still open to see whether WG will move these outside of parenthesis.
RESOLUTION: 4251 closed with proposal from daveO http://lists.w3.org/Archives/Public/public-ws-policy/2007Jan/0180.html See http://www.w3.org/2007/02/14-ws-policy-irc#T17-57-45