fix: content-type status and revoke request

docs/en/revocation-lists.rst

@@ -138,10 +138,10 @@ A Wallet Instance MUST request the revocation of a Digital Credential as defined
  
  POST /revoke HTTP/1.1
  Host: pid-provider.example.org
- Content-Type: application/x-www-form-urlencoded
-
- credential_pop=$CredentialPoPJWT
-
+ Content-Type: application/json
+ {
+  "credential_pop":"$CredentialPoPJWT"
+ }
 
 Below, is given a non-normative example of a Credential PoP with decoded JWT headers and payload and without signature for better readability:
 
@@ -180,7 +180,7 @@ Below, is given a non-normative example of a Credential PoP with decoded JWT hea
 Credential Revocation HTTP Request
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-The requests to the *Issuer Revocation endpoint* MUST be HTTP with method POST, using the mandatory parameters listed below within the HTTP request message body. These MUST be encoded in ``application/x-www-form-urlencoded`` format.
+The requests to the *Issuer Revocation endpoint* MUST be HTTP with method POST, using the mandatory parameters listed below within the HTTP request message body. These MUST be encoded in ``application/json`` format.
 
 .. _table_revocation_request_params: 
 .. list-table:: 
@@ -251,7 +251,7 @@ Below a non-normative example of an HTTP Response with an error.
 .. code::
 
  HTTP/1.1 400 Bad Request
- Content-Type: application/json;charset=UTF-8
+ Content-Type: application/json
 
  {
  "error": "invalid_request"
@@ -299,9 +299,10 @@ The following diagram shows how the Wallet Instance requests a Status Attestatio
 
  POST /status HTTP/1.1
  Host: pid-provider.example.org
- Content-Type: application/x-www-form-urlencoded
-
- credential_pop=$CredentialPoPJWT
+ Content-Type: application/json
+ {
+ "credential_pop":"$CredentialPoPJWT"
+ }
 
 A non-normative example of Credential Proof of Possession is provided :ref:`in the previous section <credential_pop_jwt_ex>`.
 
@@ -346,7 +347,7 @@ A non-normative example of Credential Proof of Possession is provided :ref:`in t
 Status Attestation HTTP Request
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-The requests to the *Credential status endpoint* of the Issuers MUST be HTTP with method POST, using the same mandatory parameters as in the :ref:`Table of Credential Request parameters <table_revocation_request_params>`. These MUST be encoded in ``application/x-www-form-urlencoded`` format. 
+The requests to the *Credential status endpoint* of the Issuers MUST be HTTP with method POST, using the same mandatory parameters as in the :ref:`Table of Credential Request parameters <table_revocation_request_params>`. These MUST be encoded in ``application/json`` format. 
 
 .. list-table:: 
  :widths: 20 60 20
@@ -432,7 +433,7 @@ Below a non-normative example of an HTTP Response with an error.
 .. code::
 
  HTTP/1.1 400 Bad Request
- Content-Type: application/json;charset=UTF-8
+ Content-Type: application/json
 
  {
  "error": "invalid_request"