I think it depends on your intent behind the API. Are you trying to create something that makes the developer/user/world easier and better or are you trying to

I think it depends on your intent behind the API. Are you trying to create something that makes the developer/user/world easier and better or are you trying to keep your system perfect, clean, and done the right way? If it's about opening up to the larger world so that more things can be built and accomplished, you want to make it as easy as possible to use and understand across the board. You can be as strict and stern about RFC specks and rules as you want when building your thing...however, the more rigid you are, they more you'll need to be operating from a position of power from the start or the more you'll struggle to get real adoption (and to be realistic, most of us are not really releasing things from a position of power)