- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 17 Jan 2007 18:51:21 +0000
- To: public-ws-policy-qa@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4251 Summary: Change syntax for some WSDL 1.1 identifiers Product: WS-Policy Version: LC Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Attachment AssignedTo: fsasaki@w3.org ReportedBy: ashok.malhotra@oracle.com QAContact: public-ws-policy-qa@w3.org 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.
Received on Wednesday, 17 January 2007 18:51:28 UTC