This is a good point. Keep in mind that currently this discovery is built on the `/rest` discovery docs and I don't see REST going away anytime soon. But that being said, if we are positive that `resource` for the REST endpoint is a reserved parameter value then we can have it specified in the top level object. This does eliminate the possibility of expanding that object to include custom `headers` or things like that. Hopefully `media` is also a reserved word as well then or we will have to change things around a bit.

If you look at https://developers.google.com/drive/v2/reference/files/insert you will see they describe the parameters as "query parameters" but these docs are REST only it seems. I can't find RPC docs.

If you look at https://www.googleapis.com/discovery/v1/apis/drive/v2/rpc and specifically the `drive.files.insert` call, they have a `resource` in the parameters list, so if we want to be compatible with this, this might be a good possibility.

The other thing is we can change the top level object to something like `options` then have `parameters`, `body` OR `resource` and `media` like:

```javascript
// definition:
insert = function(options, callback) {
  // ... implementation
};

drive.files.insert({
  parameters: {
    convert: true
  },
  body: { /* ... */ },
  media: { /* ... */ }
});