RE: Web Service Description and stateful services

> 
> But whether WSD or WSCHOR eventually looks into this, I *do* think
that we
> need to have concepts/relationships that describe how a Web service
> maintains its state.  This is obviously tied up with the more abstract
> discussions we've had over the role of "statelessness" in the Web
> architecture.
> 

Surely, the way a Web service maintains its state must be an
implementation detail. How do we refer to/address that state and whether
there is value in providing a standard way for
creating/modifying/accessing it should be the topic of discussion, but
in the appropriate WGs.

.savas.