Context Navigation

Changes between Initial Version and Version 1 of Ticket #32646, comment 5

initial	v1
1	1	I can see the case for content negotiation.
2	2
3		My two ~~sense~~: In browsers, there's a standard `.json()` method for http responses [0], and the Python `requests` library also has `.json()` method, so a simple `.json()` method is becoming more of the norm for a lot of simple use cases.
	3	My two cents: In browsers, there's a standard `.json()` method for http responses [0], and the Python `requests` library also has `.json()` method, so a simple `.json()` method is becoming more of the norm for a lot of simple use cases.
4	4
5	5	I don't think I'd be wrong if I said most apis only need to speak json. Content negotiation, while needed for some use cases, is probably overkill for many people's. Some people aren't going to want their endpoint to accept xml and yaml.