On behalf of the spec editors, I'd like to solicit general feedback on the v1.1 release candidate to understand how things are going in the community.

We are currently in an awkward state, unable to finalize v1.1 due to the caveat described in the status section:

This version is expected to be finalized and released on January 31, 2019 (provided there are two compliant implementations by that date; if not the release will wait until such implementations exist to prove its viability).

It's inarguably a bad sign that we're now more than five months past this date without yet being aware of multiple compliant server and client implementations of the v1.1 RC. Now it's possible that we're simply out of the loop, and v1.1 has been fully implemented by several libraries that we (the editors) don't happen to be using. However, it's also possible that the new-to-1.1 profiles feature has proven too onerous, impractical, or undesirable to be implemented widely (and this is of course the precise reason that we added that caveat in the first place).

With that in mind, we're reaching out with a few questions to JSON:API implementors:

• Have you attempted to implement any part of v1.1? If so, what part?
• Which parts of v1.1 do you find useful?
• Which parts of v1.1 do you not find useful?
• Have any parts of v1.1 proven to be too onerous or impractical to implement?

For reference, the major deltas introduced in 1.1 are listed in the update history section of the home page and copied below:

• New features include: profiles, "@-Members", and error object type links.
• There are editorial clarifications around: query parameters (their parsing/serialization, and reserved parameter names), the appropriate status code for specific responses, and the presence of the included key even when its value is an empty array.
• JSON:API switched to recommending camelCased names.

Please feel free to speak openly in comments below. We are trying to revitalize the spec and push forward on some much needed initiatives. However, we're also willing to re-examine and change some aspects of v1.1 first, because it has definitely become a blocker.

Thanks for any feedback you can provide.