How does the universal resolver support application/did+json

@peacekeeper wondering about the profile.... should it be `https://w3id.org/did-resolution` ?

Can you provide your thoughts on what happens when I request `application/did+json` ?

I assume based on your comments on the DID WG call that the universal resolver will throw an error if the did method does not support `application/did+json` but does `application/did+ld+json`....

I would prefer that `application/did+json` be compatible with `application/did+ld+json`... so that JSON-LD can be returned when JSON is requested and the DID Method has chosen not to support JSON...

Obviously thats for the DID WG to decide.

I would like to know how you plan to handle the following cases:

1. `application/did+json` is requested but did method only supports `application/did+ld+json`.

2. `application/did+ld+json` is requested but did method only supports `application/did+json`.

3. `*/*` is requested but did method only supports `application/did+ld+json`.

4. `*/*` is requested and did method supports `application/did+ld+json` and `application/did+json`.

5. `application/did+ld+json, application/did+json` is requested and did method supports `application/did+ld+json`.

6. `application/did+json, application/did+ld+json` is requested and did method supports `application/did+ld+json`.

Review the six content-negotiation cases in the issue and the referenced DID WG discussion. Establish the intended behavior for each requested media type, including wildcard and ordering cases, then document the agreed resolution; the issue is done when the behavior is decided and recorded.

Written by the indexing model from the issue text.