RE: WSD Requirements: add a requirement about safe and idempotent characteristics

Mark,

>If it were resolved
>such that HTTP methods, including GET, were given their rightful status
>as WSDL operations, then that's all a developer has to know, and they
>can write software that uses GET as it's defined in RFC 2616; any "safe"
>or "idempotent" flag would be superfluous.

I have the impression that Hugo wanted to also address cases where POST is used instead of GET (because, for example, headers are to be specified), but still the operation is idempotent. So just looking at the method would not sufficient to tell whether the operation is idempotent or not.

Ugo