If i understand correctly, the current RAML Spec supports only “http” and “https” for the protocols field. I believe it might be useful to also add “coap” (RFC7252) as a supported protocol in raml. CoAP is very closely mapped to http for constrained environments. The payloads and api’s are pretty much restful except for the fact that they are coap formatted (e.g. response codes).
RAML seems to be fairly generic and the IoT world may benefit from using RAML for their API definition.