1240757 - Implement v1/v2 API

Status: RESOLVED WONTFIX

(developer.mozilla.org Graveyard :: BrowserCompat, defect)

Description

[John Whitlock [:jwhitlock]]

What problem would this feature solve?
======================================
The v1 API was designed and implemented when the JSON API specification was at Release Candidate 1. Since then, JSON API v1.0 was released, and third-party tools like Ember.js have adopted the specification. We should update to this new specification, to allow the use of shipping versions of third-party tools in the contribution and management (C&M) interface. Parallel support of the old API will allow other tools to continue working during a transition period.

Other API additions are needed, and will be targeted at the v2 API.

Who has this problem?
=====================
Staff contributors to MDN

How do you know that the users identified above have this problem?
==================================================================
shobson has asked for an API compatible with JSON API v1.0, since Ember.js officially supported ember-data in August 2015 [1], and ember-data picked JSON API as the native data representation in September 2015 [2]

[1] http://emberjs.com/blog/2015/08/13/ember-2-0-released.html
[2] http://emberjs.com/blog/2015/09/02/ember-data-2-0-released.html

How are the users identified above solving this problem now?
============================================================
In September 2015, a "spike" implementation of JSON API v1.0 was developed [3], and is running at http://bcnext.herokuapp.com. This allowed some C&M work, but since it was a read-only interface, C&M work has stopped.

[3] https://github.com/mdn/browsercompat/tree/spike_v2_api_1153288

Do you have any suggestions for solving the problem? Please explain in detail.
==============================================================================
Implement a v2 API supporting JSON API v1.0 that runs at the same time as a v1 API supporting JSON API RC1.  Prioritize blockers for the C&M interface. Retire or transition tools from the v1 API to the v2 API. When ready, drop the v1 API.

Is there anything else we should know?
======================================
This is a tracking bug for v1/v2 API issues

Comment 1

[Jeremie Patonnier :Jeremie]

Revert assignment as the project is currently on hold.

Comment 2

[John Whitlock [:jwhitlock]]

The BrowserCompat project is canceled.  See https://github.com/mdn/browsercompat for current effort. Bulk status change includes the random word TEMPOTHRONE.