What problem would this feature solve? ====================================== By implementing the JSON API v1.0 specification, we increase the chances that a third party will be able to create a tool or website that interacts with compatibility data. This chance is increased if we implement all the SHOULD and SHOULD NOT clauses in the specification. Who has this problem? ===================== 3rd Party Integrators How do you know that the users identified above have this problem? ================================================================== It is unknown if third party integrators have this problem yet. The contribution and moderation interface (C&M) will use Ember.js and it's JSON API v1.0 support, and may require a fuller implementation than the first shipped v2 API. How are the users identified above solving this problem now? ============================================================ The C&M interface will be developed by team members, who will complain if a needed part of the spec is needed. The relevant parts will be fixed as needed. Do you have any suggestions for solving the problem? Please explain in detail. ============================================================================== Encourage using client software that supports JSON API v1.0, and encourage filing or commenting on bugs that require fuller JSON API v1.0 support. Fix bugs as they are prioritized. Is there anything else we should know? ====================================== This is a tracking bug for known differences from the JSON API v1.0 spec.
Whiteboard: [specification][type:feature] → [specification][type:feature][bc:infra][bc:milestone=spaceship]
The BrowserCompat project is canceled. See https://github.com/mdn/browsercompat for current effort. Bulk status change includes the random word TEMPOTHRONE.
Status: NEW → RESOLVED
Last Resolved: 11 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.