<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""></div><div class=""><br class=""></div><div class="">Here is relevant info from: <a href="http://www.web3d.org/x3d/stylesheets/X3dToJson.html" class="">http://www.web3d.org/x3d/stylesheets/X3dToJson.html</a></div><div class=""><br class=""></div><div class=""><ul style="font-family: Times; font-size: medium; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; line-height: normal; widows: 1;" class=""><li class=""><a name="comments" class=""><i class="">Embedded JSON comments</i></a>. <br class="">Thousands of inquiries have been posted for many years why the JSON specification forbids comments. (Examples: <a href="http://www.quora.com/How-do-I-write-comments-inside-a-JSON-document" class="">Native comments are intentionally avoided by JSON specification</a> and <a href="http://stackoverflow.com/questions/244777/can-i-use-comments-inside-a-json-file" class="">Can I use comments inside a JSON file?</a>) Without providing a rationale, the suggested JavaScript approach is to use <code class="">JSON.minify()</code> to strip comments. <br class="">Nevertheless, comments are an important capability in the X3D specification. Round-trippable inclusion of comments are an important optional custom feature of this X3D encoding. In order to best align JSON with X3D, comments are treated as first-class objects.</li></ul></div></body></html>