This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Past experience has shown that state tables are a useful tool for describing how to manage shared resources such as the "session/cursor" defined in WS-Enumeration. There should be two tables in the specification; one that describes the client's point of view and the other that describes the point of view of the data source. Each table should enumerate all the possible states of a session/cursor and list the acceptable request or response messages for that state and the resulting state transition(s) (if any). The addition of these tables will improve our chances of detecting interoperability issues.
Created attachment 779 [details] Proposal Proposal.
Created attachment 806 [details] version 3 of the WS-Enumeration state tables
Created attachment 811 [details] version 4 of the WS-Enumeration state tables * took out "generate fault" defaults on unspecified cells * changed Expiration/Renewing cell to transition to [End] * change RenewResponse/End cell to transition back to [Active] if there had been an outstanding Renew request
Created attachment 818 [details] f2f agreed draft to be enhanced by editor
Resolved with comment #4