Comments are being removed from JSON. I think that this will have
minimal impact because existing decoders can continue to recognize and
ignore comments.
No known encoders use comments. This is not surprising because
comments are not very useful in data interchange.
This change will more closely align JSON with YAML and Python, and
will simplify the standard.
I wish to thank everyone for their comments, suggestions, and emails.
Comments are being removed from JSON. I think that this will have minimal impact because existing decoders can continue to recognize and ignore comments. No...
... If you like. There is no harm in leaving it in. The current Java decoder recognizes comments in the slashslash, slashstar, and hash forms. I am leaving it...
... I would think that the fact that a parse is successful no longer means that the input was valid JSON would be a pretty good reason to take it out... -- ...
Are comments officially out of the specification? It seems so looking at the current state of the spec http://www.json.org/. ... existing decoders can continue...
JSON does not have comments. A JSON encoder MUST NOT output comments. A JSON decoder MAY accept and ignore comments. Comments should never be used to transmit...
... Not now, but it used to have comments. I believe it's time to start versioning the spec. Several things have changed, and people have different ...
As Martin already said, JSON used to have comments. I don't know what led to the stringent opinion (perhaps from field experience) that they are so harmful as...
I had posted in the original thread talking about comments and wanted to follow up here as well. While meta data, like comments, might be useful, the only way...
These were the reasons for removing comments: First, comments turned out to not be very useful. Second, comments were the most difficult feature to support in...
I am assuming the order of reasons list was not significant. ... This is always rather subjective. When you consider that all text formats strive for and boast...
... I would like to understand your intentions. Where commentary is important, it can be encoded directly in JSON, where the outermost object resembles a COBOL...
... It can be useful to comment-out sections of hand-coded JSON for development/testing, and to have inline human-readable comments about what is going on. A...
... I don't really consider comments as meta-data, unless you mean in the style of javadocs. I see comments as much a presentation aspect of the syntax as...
Jim has said it sweetly what pretty much everyone has been saying on this thread (perhaps just in too many words). He's also hit my points right on. ... If...
... It's a shame that neither the previous version nor the current version aren't versioned... ;-) -- Martin Cooper (luckily I have a copy on disk) or that the...
I think the real crux of this is simply, you cannot create a json format string through encoding from existing data that would contain comments (IIRC). It is...
... Huh? If I'm writing an encoder that takes a Java data structure and encodes it into JSON, it would make perfect sense to me to generate comments (in ...
I'll jump in here and say that even a draconian syntax like XML (arguably the most used data stream format on the planet) supports comments. The whole point of...
... encodes ... encoded. So, ... encoding ... Why would you do that? What expectation do you have of the receiver? Why waste the bandwidth? What, specifically,...
... debug information is *IN*valuable , for us weak-minded developers that cant guess whats being passed back and forth, i use html comments in lots of...
... In this specific example, I might choose to do this because multiple Java types map to the same JSON type, and it could help me a lot with identifying ...
I am completely stumped. Did the rest of my message not present the cases? Do HTML, XML and YAML or just about any text format not acknowledge the utility of...
I think Martin's response (#177 [1]) has addressed most points so I just want to add one thing simply. Given any text format, comments are just about as useful...
... As I said, I have a sneaking hunch that the real issue stems from tying JSON to YAML. With the comments debate generating some traffic, I feel less daring...
I do have to say, unless I've missed something big in the thread, the only thing I see keeping comment support *out* of the new version is "because". As in...
Funny thing is, YAML was designed for human consumption as much as a language-neutral serializing format. And JSON's ancestry (JavaScript) is more in the LISP...
Offline 
Send Email
