tag:blogger.com,1999:blog-34454975.post4048523001362663624..comments2023-06-28T16:58:41.189+02:00Comments on Web Reflection: On JSON CommentsAndrea Giammarchihttp://www.blogger.com/profile/16277820774810688474noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-34454975.post-60903346158402027722011-12-08T21:07:28.170+01:002011-12-08T21:07:28.170+01:00The purists are going to hate commenting in this w...The purists are going to hate commenting in this way because it means a larger memory footprint when the corresponding structure is built.<br /><br />For those purists, there's nothing stopping an enterprising developer from using a SAX style parser to build the structure and ignore the comments while doing so.<br /><br />All that to say, I like this approach.Anonymoushttps://www.blogger.com/profile/04994552847390577941noreply@blogger.comtag:blogger.com,1999:blog-34454975.post-28623884696103116312011-12-08T11:57:29.356+01:002011-12-08T11:57:29.356+01:00If you post some multibyte characters then you exc...If you post some multibyte characters then you exceed 140 bytes. ;)Anonymoushttps://www.blogger.com/profile/04353842783341426429noreply@blogger.comtag:blogger.com,1999:blog-34454975.post-90349113451898703062011-12-07T18:52:29.854+01:002011-12-07T18:52:29.854+01:00I too like the @comment metatag. If parsers would ...I too like the @comment metatag. If parsers would just ignore those as part of data and you could check for them and pluck them out that would be fine. I really don't see the need for comments in JSON. If someone needs to describe it with verbage the file isn't the place for that. Providers and consumers should know what the nodes are for and if they don't, sticking comments in isn't the way to solve that problem. It's a process issue, not a technology one.Bil Simserhttp://weblogs.asp.net/bsimsernoreply@blogger.comtag:blogger.com,1999:blog-34454975.post-92209701735510514592011-12-06T13:02:33.130+01:002011-12-06T13:02:33.130+01:00the clean is not mandatory, is just a nice have.
T...the clean is not mandatory, is just a nice have.<br />The reason anyone would like to put comments are configuration files ... those we write manually, those always parsed with specific properties check.<br /><br />If the software that relies in a JSON config file does a for loop, is not a big deal to ignore keys that start with a common convention, e.g. the @<br /><br />For all other cases, like data transfer, the reason we all use JSON, this comments thing is a non problem, imhoAndrea Giammarchihttps://www.blogger.com/profile/16277820774810688474noreply@blogger.comtag:blogger.com,1999:blog-34454975.post-86222440729373072312011-12-06T10:14:14.149+01:002011-12-06T10:14:14.149+01:00I really like the idea of doing something like @co...I really like the idea of doing something like @comment:'This is my comment'.<br /><br />My only concern would be that if we started doing this and it only half took off, people would have to make the mental switch from JSON they have to clean to JSON they don't.Toby Osbournhttps://www.blogger.com/profile/12272318108145320922noreply@blogger.com