alternate request (GET>POST) syntax support fore "more" url

[RoboSparrow]

see issue adlnet/xAPI-Spec#1065, where i asked for clarification

In short I believe that more endpoints should fall under the alternative request syntax requirement.

I currently have no access to a 0.10.0 instance to test it.

0.9.1 rejects with status 400 and error messages for all post body params

• clarification is especially important for our LRS as we do include query params in our more endpoint.

[RoboSparrow]

0.10.0 returns 400, Bad request

POST /statements?method=GET&until_id=59b8cdd0a097fa60676f2295

request body, containing query and headers

since=2017-09-13T06:23:58.987Z&limit=2&registration=e01504fd-a786-4dd4-bcdf-642e60b9d82c&Content-Type=application/json&Authorization=Basic VVRKaGY3RmtGb2pDUnBRM0xLQmNKR1BZZWNPRmZnb2Z1VWJWanNFbjpXVXl0aHBaMGtlamR1azZmM1RGQmFhQ2ExdmdTRkdlOGU0U01OR2h5&X-Experience-API-Version=1.0.2

Response body (parsed)

{ code: 400,
     message: 'GET parameters do not validate.',
     data: 
      [ 'Object value found, but an array is required',
        'The property method is not defined and the definition does not allow additional properties',
        'Failed to match at least one schema' ] }