Method Namespaces: implicit creation can be harmful, request new API methods to create/delete

In another thread I posted that today we learned that method repo namespaces seem to be implicitly created

http://gatkforums.broadinstitute.org/firecloud/discussion/9294/method-namespaces-docs-do-not-make-clear-that-namespaces-are-implicitly-created#latest

This strikes me as dangerous, especially in light of the fact that one cannot delete namespaces at present. So, the smallest typo (or a miscoded loop, etc) leaves junk that persists for a long time (cluttering the UI, etc).

So I'd like to ask that the Method Repository section of the API (https://api.firecloud.org/#!/Method_Repository) be extended to include endpoints for creating and deleting namespaces. When a namespace is not empty the delete request would not be honored, unless a force option/parameter is passed in with the call.

Thanks, Mike