[x3d-public] How to tell if a file is JSON

[John Carlson]

Leonard, you can go into X3D-Edit, select an X3D file and hit the moebius circle.

John
> On Dec 1, 2015, at 2:00 PM, Leonard Daly <web3d at realism.com> wrote:
> 
> 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.
> 
> I would like to see what this file looks like in JSON encoding (and ClassicVRML, but that is a really minor point).
> 
> 
> Thank you,
> 
> Leonard Daly
> 
> 
> 
> 
>> Comments are not allowed in a JSON file (I used 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> and the references contained in the page, especially to json.org, RFC 4627 and RFC 7159). 
>> 
>> 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?
>> 
>> 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?
>> 
>> 
>> Leonard Daly
>> 
>> 
>> 
>> 
>> On 11/30/2015 9:27 PM, Don Brutzman wrote:
>>> On 11/30/2015 4:23 PM, John Carlson wrote: 
>>>> There might be a comment before the first x3d object. 
>>> 
>>> very interesting observation! 
>>> 
>>> - since JSON does not support comments, and 
>>> - since we have come up with an allowable approach for comments inside an X3D scene graph that allows round-trip support with other encodings, 
>>> 
>>> then 
>>> 
>>> - we probably ought to deliberately avoid capturing or including any comments in the JSON encoding that might appear outside the "X3D" object declaration. 
>>> 
>>> all the best, Don 
>> 
>> 
>> -- 
>> Leonard Daly
>> X3D Co-Chair
>> Cloud Consultant
>> President, Daly Realism - Creating the Future
>> 
>> 
>> _______________________________________________
>> x3d-public mailing list
>> x3d-public at web3d.org <mailto:x3d-public at web3d.org>
>> http://web3d.org/mailman/listinfo/x3d-public_web3d.org <http://web3d.org/mailman/listinfo/x3d-public_web3d.org>
> 
> 
> 
> -- 
> Leonard Daly
> X3D Co-Chair
> Cloud Consultant
> President, Daly Realism - Creating the Future
> <commentTest.x3d><commentTest.x3dv>_______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20151201/deedb1de/attachment.html>