[DOCS-8162] Clarify if MongoDB Extended JSON needs its own associated MIME Type Created: 23/Jun/16 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dissatisfied Former User | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Location: https://docs.mongodb.com/manual/reference/mongodb-extended-json/ |
||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 2 days ago |
| Epic Link: | DOCSP-1769 |
| Description |
|
JSON encoded data generally has the associated mime type "application/json", however this format is "generic" and contains no structural specification beyond the basic types. MongoDB Extended JSON is a flavour that adds semantic meaning to specific underlying structures (specifically, predominantly single-key nested mappings whose key is $-prefixed), which is way more meaning than expected for just "application/json". It is customary to use an annotation on the mime type to denote the structure or format used within, but none is currently documented on the MongoDB Extended JSON page. Please consider what an appropriate value might be ("application/json+mongo"?) and include it in the documentation. Thank you! |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |
| Comment by Kay Kim (Inactive) [ 24/Sep/16 ] |
|
bulk assigning tickets in backlog to team members to groom. |