<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">I have not been following the details
enough for me to be able to run a conversion. I have created an
X3D file using X3D-Edit (probably an old version) and converted it
ClassicVRML using Xj3D. I also converted it to ClassicVRML using a
style sheet, but that produced only 1 line of content - the XML
header line.<br>
<br>
I would like to see what this file looks like in JSON encoding
(and ClassicVRML, but that is a really minor point).<br>
<br>
<br>
Thank you,<br>
<br>
Leonard Daly<br>
<br>
<br>
<br>
<br>
</div>
<blockquote cite="mid:565D4B68.4060606@realism.com" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Comments are not allowed in a JSON
file (I used <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://stackoverflow.com/questions/244777/can-i-use-comments-inside-a-json-file">http://stackoverflow.com/questions/244777/can-i-use-comments-inside-a-json-file</a>
and the references contained in the page, especially to
json.org, RFC 4627 and RFC 7159). <br>
<br>
Does this approach puts comments into JSON data elements? If so,
that means comments have been elevated from text in the file to
data in the file. If this approach is to capture comments
throughout the original non-JSON file, does that mean the data
model between a JSON-encoded scene and an XML-encoded scene is
significantly different?<br>
<br>
Out of curiosity, does the compressed binary encoding capture
comments from anyplace in the original scene file? If so, does
the data model that is stored in the CBE file match that of the
original file?<br>
<br>
<br>
Leonard Daly<br>
<br>
<br>
<br>
<br>
On 11/30/2015 9:27 PM, Don Brutzman wrote:<br>
</div>
<blockquote cite="mid:565D2FB3.1000606@nps.edu" type="cite">On
11/30/2015 4:23 PM, John Carlson wrote: <br>
<blockquote type="cite">There might be a comment before the
first x3d object. <br>
</blockquote>
<br>
very interesting observation! <br>
<br>
- since JSON does not support comments, and <br>
- since we have come up with an allowable approach for comments
inside an X3D scene graph that allows round-trip support with
other encodings, <br>
<br>
then <br>
<br>
- we probably ought to deliberately avoid capturing or including
any comments in the JSON encoding that might appear outside the
"X3D" object declaration. <br>
<br>
all the best, Don <br>
</blockquote>
<br>
<br>
<div class="moz-signature">-- <br>
<font class="tahoma,arial,helvetica san serif" color="#333366">
<font size="+1"><b>Leonard Daly</b></font><br>
X3D Co-Chair<br>
Cloud Consultant<br>
President, Daly Realism - <i>Creating the Future</i> </font></div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
x3d-public mailing list
<a class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>
<a class="moz-txt-link-freetext" href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a>
</pre>
</blockquote>
<br>
<br>
<br>
<div class="moz-signature">-- <br>
<font class="tahoma,arial,helvetica san serif" color="#333366">
<font size="+1"><b>Leonard Daly</b></font><br>
X3D Co-Chair<br>
Cloud Consultant<br>
President, Daly Realism - <i>Creating the Future</i>
</font></div>
</body>
</html>