Deprecating vs completely specifying JsonAdapter

Nobody has claimed this yet.

The JSON-B specification lacks several details about the use of JsonAdapter. As a result, the existing implementations behave differently. As a consequence, existing applications need to apply workarounds to work on all implementations unchanged.

There are two proposals currently how to fix that in a future version of the specification:

* @mkarg proposes to completely specify JsonAdapter, so both implementations behave the same.
The effect would be that all existing applications can either keep the existing workarounds or remove them, at their exclusive discretion.
* @rmannibucau proposes to deprecate and eventually drop JsonAdapter.

To get broad input from the community, everybody (users and vendors) are invited to discuss the pros and cons of these proposals.

To come to a final decision, committers are invited to vote for / agains these proposals.

Start by reading the issue's two proposals for handling JsonAdapter and the existing discussion in the 19 comments. A decision would require resolving the competing specification approaches through community input and committer voting; no implementation files or tests are identified in the issue.

Written by the indexing model from the issue text.