While the needs for comments in JSON are well understood, little discussions were made about which comment syntax and semantics should be used. It is not even c

While the needs for comments in JSON are well understood, little discussions were made about which comment syntax and semantics should be used. It is not even clear that implementations should return comments as a part of data model! Almost all JSON alternatives, which number at least hundreds I believe, are either unclear or haven't given much thought about this. And those who do care about them are unpopular. sigh Given its importance, we should take this into the standard body. Namely, the IETF should be pressurized enough to update RFC 8259 for every nitty-gritty about comments. It is clear that this new version of JSON needs to address multiple use cases which are often mutually exclusive, so we probably need to introduce some short indicator for profiles at the very beginning of the document. (Yes, that means you should declare in advance that you want comments and other humane syntaxes. I don't think that's very hard when you do want comments.)