> While this specification does not dictate the structure, or impose any requirements, on the shape, format, and content of the payload it does offer recommendations
Too loose to be a standard but better than nothing.
Yeah, we don't call it a standard for that reason, here's the tagline:
> Open source tools and guidelines for sending webhooks easily, securely and reliably
We have been going back and forth about this. Though we purposefully made Standard Webhooks more like guidelines than a formal specification (note there's no mention of RFC2119, for example) so that it's easier to conform to without forcing implementations to have breaking changes. Even if it means you don't get the full benefits.
I think people can get a lot of benefits even if they don't follow the whole thing, and it's our job to continue building tools to make it easier to build conforming implementations than non-conforming ones.
> Open source tools and guidelines for sending webhooks easily, securely and reliably
We have been going back and forth about this. Though we purposefully made Standard Webhooks more like guidelines than a formal specification (note there's no mention of RFC2119, for example) so that it's easier to conform to without forcing implementations to have breaking changes. Even if it means you don't get the full benefits.
I think people can get a lot of benefits even if they don't follow the whole thing, and it's our job to continue building tools to make it easier to build conforming implementations than non-conforming ones.