Bill Doerrfeld

About Bill Doerrfeld

Bill Doerrfeld is an API specialist, focusing on API economy research and marketing strategy for developer programs. He is the Editor in Chief for Nordic APIs. He leads content direction and oversees the publishing schedule for the Nordic APIs blog. Bill personally reviews all submissions for the blog and is always on the hunt for API stories; you can pitch your article ideas on our Create With Us page. Follow him on Twitter, or visit his personal website.

  • László Miklósik

    Very nice article and presentation!

    The talk mentions “JSON schemas” and I was wondering if it’s in the roadmap of the IETF specification group (for SCIM 2.0 at least) to define the SCIM API more concretely (Schemas + Resources + Operations), for example using OpenAPI (formerly known as Swagger, details here: https://openapis.org/ )?

    This contract-first approach would be extremely useful, because it would allow generating both server-side stubs and working SCIM clients in multiple programming languages. This would definitely bring more widespread adoption. An example I found is here: https://github.com/APIs-guru/openapi-directory/blob/master/APIs/citrixonline.com/scim/NA/swagger.yaml

    I also wrote a similar yaml files for our case, and while doing so I discovered many points from the specification which leave room for interpretation. Probably writing such a descriptor is a very good way to the check the specification itself.