charset not needed for application/json media type

[Brian Campbell]

According to https://www.iana.org/assignments/media-types/application/json no "charset" parameter is defined for “application/json” and adding one really has no effect on compliant recipients.

FAPI probably shouldn’t be requiring it then.

However, 6.2.1. Protected resources provisions in part one https://openid.net/specs/openid-financial-api-part-1-ID2.html#rfc.section.6.2.1 has “shall send the Content-type HTTP header Content-Type: application/json; charset=UTF-8 if applicable;”

Which is arguably harmless because it is UTF-8 anyway but there are currently conformance test suite tests which are requiring that the charset parameter be present and pointing to that FAPI clause.

FAILURE

EnsureResourceResponseContentTypeIsJsonUTF8

FAPI-R-6.2.1-10 FAPI-R-6.2.1-9

Response charset not declared

content_type

‌ application/json

[Joseph Heenan]

Discussed on today’s WG call; Brian commented that it’s really not required to specify the charset explicitly as it’s already the default. Stuart commented that the Australian spec probably explicitly says to exclude the charset; the OB spec often doesn’t include it too.

‌

Brian agreed to propose a pull request (thanks Brian!).

[Brian Campbell]

pull request #145 removes the charset=UTF-8 from part 1 sec 6.2.1

[Stuart Low]

Aligns with current CDS and I support. https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/27

[Nat Sakimura]

Resolved by pull request #145