Problem/Motivation
This issue tracks child issues relating to JSON:API 1.1 spec compliance. The announced tag date for 1.1 is September 30, 2022.
Reference: Changelist
Remaining tasks
Areas where Drupal is not 1.0 compliant but we were ahead of 1.1; ensure tagged spec compliance.
- #3279366: [PP-1] Implement json:api 1.1 server-required profile error handling/signaling
- #3279364: [PP-1] Implement json:api 1.1 `error.source.missing.key` data to compliment `error.source.pointer`
Areas where Drupal is incompatible and there is no existing PP on JSON:API 1.1; that is, we're just plain out of spec.
New features/options in 1.1 that Drupal can support
Changelog for releases after 1.0
RC 1
- New features include: profiles, ”@-Members”, and error object
typelinks. - There are editorial clarifications around: query parameters (their parsing/serialization, and reserved parameter names), the appropriate status code for specificresponses, and the presence of the
includedkey even when its value is an empty array. - JSON:API switched to recommending camelCased names.
RC 2
- Extensions were added and the scope of profiles were reduced since their introduction in RC1.
- Links can be represented as RFC 8288-style web links.
- A new
describedbylinks member was added so that implementors can incorporate description documents (e.g. OpenAPI or JSON Schema) directly into their APIs. - Local IDs were introduced so that a client can create a relationship to a resource yet-to-be created by the same request.
RC 3
- Refined links objects. The link object
paramsmember was removed to better align with other JSON link serializations. Theanchortarget attribute was also removed. It may be restored in a future minor release.
RC 4
- Formalized the definition of specification and implementation semantics.
- Refined the definitions of extensions and profiles.
- Clarified details regarding expected and allowed responses, query parameters, and more.
