6399 2009-01-14 00:03:39 +0000 Enumeration-EnumerationEnd violate WS-I BP 2009-04-21 21:33:45 +0000 1 1 1 Unclassified WS-Resource Access Enumeration FPWD PC Windows XP CLOSED REMIND http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jan/0007.html hasProposal P2 normal --- 1 dug dug bob public-ws-resource-access-notifications oldest_to_newest 23045 0 dug 2009-01-14 00:03:39 +0000 WS-Enumeration defines an output-only (ie. solicit-response) operation as follows: <wsdl:portType name="DataSource"> ... <wsdl:operation name="EnumerationEndOp" > <wsdl:output message="wsen:EnumerationEndMessage" wsa:Action=" http://schemas.xmlsoap.org/ws/2004/09/enumeration/EnumerationEnd"/> </wsdl:operation> </wsdl:portType> WS-I Basic Profile R2303 says the following: 4.5.2 Allowed Operations Solicit-Response and Notification operations are not well defined by WSDL 1.1; furthermore, WSDL 1.1 does not define bindings for them. R2303 A DESCRIPTION MUST NOT use Solicit-Response and Notification type operations in a wsdl:portType definition. A solicit-response message reverses the interact between the service and the client. Typically, the client is responsible for initiating the interaction, but with solicit-response the service is sending an unsolicited message to the client. BP determined that there wasn't any consensus on how to implement this (what would be the trigger mechanism for this message exchange, or how does the service initiate a connection with a client that might not allow incoming connections), thus BP banned it. Proposal: Remove this operation. 24151 1 bob 2009-03-11 09:55:58 +0000 proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Mar/0054.html 24168 2 bob 2009-03-11 17:28:08 +0000 resolved 2009-03-1 with the following change: change EnumEndPort to EnumEndPortType