If you look at the text on HTTP GET/POST binding, you see that the in the case of a GET request, there is no payload and in the case of the POST request, the payload is not SOAP. The GET requests look more like they could be requests to a RESTful web service. Perhaps a future version of the Basic Profile will issue some recommendations for RESTful web services, but for now, I guess we have to settle for recommendations regarding SOAP web services.
With SOAP, HTTP GET requests cannot be used to issue a request to a web service, since they do not allow a payload to be enclosed, like the POST and PUT requests do.
Thank you Ivan! You see, I was under the impression that HTTP POST should be used to send a SOAP request. If HTTP GET/POST are not allowed (in Basic Profile Version 1.0), what did they expect us to use?