Overloaded term 'method'

[MattSANU]

It seems confusing to have two meanings of the term 'method' - SPORE methods and HTTP methods. For example, a SPORE specification has a 'methods' object, each of whose members is a SPORE method, and each of these SPORE methods has an HTTP method attribute named 'method'. Phew.
Since a SPORE method has a URL and an HTTP method, I would find it more natural to call it an 'API operation', or maybe 'operation' for short.
I realise you can't break backward compatibility, but perhaps you could consider permitting some alias for SPORE methods that doesn't include the word 'method'?