I've noticed that if the client sends a resource creation request with an invalid schema, it reaches the HTTP handler:

{
    "schemas":["urn:ietf:params:scim:invalid:schema"],
    "userName":"[email protected]"
}

Considering that schema and its extensions are attached to the resource on server creation, should any schema name validation be present? If so, then I'll be happy to implement this validation.