[x3d-public] dropped mail
John Carlson
yottzumm at gmail.com
Sun Nov 15 20:31:29 PST 2015
OMG! LOL!
It would be great to see them posted, but it may overwhelm people, and many of them are probably ancient. And maybe it’s a good thing that they didn’t get posted! There were some things on security tokens that probably should be posted. Essentially binding a sub-scenegraph (DEF node) to an operation (USE, append, insert, update, remove) into an unforgeable reference or authorization token, and then this reference can be shared to enable multiuser scene graph modification in a secure fashion.
John
> On Nov 15, 2015, at 3:32 PM, Don Brutzman <brutzman at nps.edu> wrote:
>
> John: while looking for a hypermail address, I just discovered that your yottzumm at gmail.com was not subscribed to the x3d-public mailing list, and so your mails were getting discarded. Argh.
>
> This is really unfortunate because you have had a lot of great posts and suggestions. Apparently only I was seeing them... 8(
>
> Anyway, I have subscribed that address for you. You are also subscribed (originally) as john.carlson3 at sbcglobal.net
>
> If you want to unsubscribe one or the other (to avoid duplicates) then the subscripiton/information page is
>
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
> I suppose we (or I) should send your dropped mail to the public list, piecewise or as a bunch... please advise what you think.
>
>
> On 11/13/2015 9:48 AM, John Carlson wrote:
>> Unicode is handled with \u followed by 4 hexadecimal digits, I believe.
>>
>> John
>>> On Nov 13, 2015, at 1:17 AM, Don Brutzman <brutzman at nps.edu <mailto:brutzman at nps.edu>> wrote:
>>>
>>> Thanks for the testing, this is a helpful complement that mostly matches the jslint results.
>>>
>>> http://www.web3d.org/x3d/content/examples/build.json.out
>>>
>>>
>>>
>>> On 11/12/2015 7:10 PM, John Carlson wrote:
>>>>
>>>>> On Nov 10, 2015, at 10:46 AM, Don Brutzman <brutzman at nps.edu <mailto:brutzman at nps.edu>> wrote:
>>>>>
>>>>> The X3dToJson.xslt stylesheet is an experimental effort to help create a JSON encoding for X3D Graphics.
>>>>>
>>>>> A new release of the experimental design page, supporting tools and examples is available:
>>>>>
>>>>> X3D to JSON Stylesheet Converter
>>>>> http://www.web3d.org/x3d/stylesheets/X3dToJson.html
>>>>>
>>>>> Status: developmental work, with design pattern being assessed by X3D community.
>>>>>
>>>>> We plan to discuss this draft JSON encoding during the weekly X3D Working Group teleconference tomorrow, Wednesday November 10, as usual 0800-0930 pacific.
>>>>>
>>>>> This is pretty detailed. We have found that certain JSON constraints do not map directly to XML. For example, so far,
>>>>> a. attributes are prefixed with @ symbol to facilitate context-free parsing.
>>>>> b. JSON objects require ordered collections of similar children according to field type as unique keys,
>>>>
>>>> JSON arrays are ordered. JSON object keys can be reordered.
>>>>> c. JSON arrays allow unordered collections of children.
>>>>> d. Comments can be included if a special key is used (#comment) but order is only partially preserved.
>>>>>
>>>>> This has meant that partial sorting of X3D scenes (documents) occurs. For the syntax of X3D, preserving exact XML node order appears to not be completely possible.
>>>>
>>>> I am having trouble with this statement, since I thought I showed you an encoding which did maintain XML node order. I can send you the Java code if you like. It’s basically very similar to XML, with an object for the attributes, and an array surrounding that and any other child elements. Comments get translated into strings (in arrays). Comments don’t appear in objects, just like XML).
>>>
>>> there is probably a better way to say things... am trying to get it phrased just right. am _not_ trying to imagine that JSON is something it is not.
>>>
>>> Shortest summary for current encoding pattern: perfect round trip is not possible without partial reordering of some X3D scenes. matching functionality is not changed.
>>>
>>>>> For the semantics of X3D, which has some order dependence (DEF IDs must be defined prior to utilizing USE IDREFs for load-time performance), functional equivalence appears to be possible.
>>>>>
>>>>> Important next steps include John Carlson's work on a loader, and examining the syntax of javascript code that authors might write when accessing X3D JSON scene graph structures.
>>>>
>>>> While I agree I can continue working on this and apply more effort to this (I need to make sure I handle the array on the outside removed), I think we still should provide people with an accurate stylesheet translation that passes a simple JSON parse.
>>>
>>> i think there are very few bugs at this point and the majority of 3800 scenes - certainly the majority of common use cases - are passing. so we should press on.
>>>
>>> but first, detailed scrutiny continues:
>>>
>>>> I downloaded the lasted JSON zip you provided, verified the MD5 checksum and ran the JSON files through jsonlint (jsonlint-lines). Here are the results below. I will work with you tomorrow to get this tool installed on your system. You do need node.js though. I will look for a Java version.
>>>
>>> i have installed node.js and am happy to try your way first - always good to learn more - then attempt automating further tests into the ant build scripts.
>>>
>>>> www.web3d.org/x3d/content/examples//Basic/development/QuadTreeExamples.json <http://www.web3d.org/x3d/content/examples//Basic/development/QuadTreeExamples.json>
>>>> [Error: Parse error on line 2:
>>>> "#comment":[ "ENTITY, ELEMEN
>>>> ----------^
>>>> Expecting 'EOF', '}', ',', ']', got ':']
>>>> www.web3d.org/x3d/content/examples//Basic/development/SchemaTest.json
>>>> [Error: Parse error on line 58:
>>>> ... at translation":[10000.e-1, 50, 0.5],
>>>> -----------------------^
>>>> Expecting 'EOF', '}', ',', ']', got 'undefined']
>>>> www.web3d.org/x3d/content/examples//Basic/development/ScriptSyntaxExample.json
>>>> [Error: Parse error on line 111:
>>>> ... "@value":["\"\"\" \"quote
>>>> -----------------------^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', ']', got 'undefined']
>>>> www.web3d.org/x3d/content/examples//Basic/development/SpinGroupInternalSubsetDeclaration.json
>>>> [Error: Parse error on line 2:
>>>> "#comment":[ "ENTITY, ELEMEN
>>>> ----------^
>>>> Expecting 'EOF', '}', ',', ']', got ':']
>>>> www.web3d.org/x3d/content/examples//Basic/development/TestDoctype.json
>>>> [Error: Parse error on line 2:
>>>> "#comment":[ "XML declaratio
>>>> ----------^
>>>> Expecting 'EOF', '}', ',', ']', got ':']
>>>> www.web3d.org/x3d/content/examples//Basic/development/TestRegularExpressionChecks.json
>>>> [Error: Parse error on line 91:
>>>> ... "@key":[0, 0.250.5, 0.75, 1],
>>>> -----------------------^
>>>> Expecting 'EOF', '}', ',', ']', got 'undefined']
>>>> www.web3d.org/x3d/content/examples//Basic/development/TestSchematronDiagnostics.json
>>>> [Error: Parse error on line 92:
>>>> ...}, "Scene": { { "@USE":"impr
>>>> ---------------------^
>>>> Expecting 'STRING', '}', got '{']
>>>> www.web3d.org/x3d/content/examples//Basic/development/X3dRetreatProtoExercise.json
>>>> [Error: Parse error on line 328:
>>>> ...t", } }
>>>> ----------------------^
>>>> Expecting 'STRING', got '}']
>>>
>>> the preceding are all either experimental DOCTYPE extensions (not recommended, archival) or intentional scene errors (for validation testing). thus can be ignored. all documented in the scene metadata tags.
>>>
>>>> www.web3d.org/x3d/content/examples//Basic/ExperimentalBinaryCompression/Lion.json <http://www.web3d.org/x3d/content/examples//Basic/ExperimentalBinaryCompression/Lion.json>
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Basic/ExperimentalBinaryCompression/LionCoded.json <http://www.web3d.org/x3d/content/examples//Basic/ExperimentalBinaryCompression/LionCoded.json>
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>
>>> apparently memory overruns. over 1MB numeric data for a 34-line scene.
>>>
>>>> www.web3d.org/x3d/content/examples//Basic/Followers/DoorDesired.json <http://www.web3d.org/x3d/content/examples//Basic/Followers/DoorDesired.json>
>>>> [Error: Parse error on line 69:
>>>> ... "@content":"http://www.web3d.or <http://www.web3d.or/>
>>>> ----------------------^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'undefined']
>>>
>>> erroneous backslash in source. fixed. conversion now passes.
>>>
>>>> www.web3d.org/x3d/content/examples//Basic/Geospatial/MarsLOD002.json <http://www.web3d.org/x3d/content/examples//Basic/Geospatial/MarsLOD002.json>
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Basic/Geospatial/MarsLOD005.json
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Basic/Geospatial/MarsLOD008.json
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Basic/Geospatial/MarsLOD011.json
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Basic/Geospatial/MarsLOD017.json
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Basic/Geospatial/MarsLOD020.json
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Basic/Geospatial/MarsLOD023.json
>>>
>>> these all have exceedingly long numeric arrays, suspect too big for memory. note most of the intervening scenes pass OK so the pattern is OK.
>>>
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Basic/Medical/BodySkinIndexedFaceSetNIST.json <http://www.web3d.org/x3d/content/examples//Basic/Medical/BodySkinIndexedFaceSetNIST.json>
>>>
>>> nearly 1MB of data in a Coordinate and IFS index array. memory exceeded.
>>>
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Basic/Medical/BonesAllSkeleton.json <http://www.web3d.org/x3d/content/examples//Basic/Medical/BonesAllSkeleton.json>
>>>
>>> 9 MB numeric data. will be interesting to compare size of JSON, .x3db and .x3de versions when we get them. a number of other H-Anim conversions OK.
>>>
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Basic/Medical/BonesHead.json <http://www.web3d.org/x3d/content/examples//Basic/Medical/BonesHead.json>
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Basic/Medical/BonesMandible.json
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Basic/Medical/SkeletonCompleteNoNormals.json
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Basic/Medical/SkeletonCompleteNormals.json
>>>
>>> those last two are 10MB and 20MB each!
>>>
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Basic/ScriptConformance/CreateNodesFromPrototypeECMAScript.json <http://www.web3d.org/x3d/content/examples//Basic/ScriptConformance/CreateNodesFromPrototypeECMAScript.json>
>>>> [Error: Parse error on line 104:
>>>> ... at DEF":"SC", } } ] }
>>>> ----------------------^
>>>> Expecting 'STRING', got '}']
>>>
>>> known conversion problem when a script contains a field that contains a USE to itself - will check recursive logic in translator, not a problem with pattern.
>>>
>>>> www.web3d.org/x3d/content/examples//Basic/ScriptConformance/PerFrameNotificationECMAScript.json <http://www.web3d.org/x3d/content/examples//Basic/ScriptConformance/PerFrameNotificationECMAScript.json>
>>>> [Error: Parse error on line 61:
>>>> ... at DEF":"SC", } } ] }
>>>> ----------------------^
>>>> Expecting 'STRING', got '}']
>>>
>>> similar
>>>
>>>> www.web3d.org/x3d/content/examples//Basic/Shaders/Flutter.json <http://www.web3d.org/x3d/content/examples//Basic/Shaders/Flutter.json>
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Basic/StudentProjects/AllenDutton.json
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Basic/Security/HelloWorldSigned.json
>>>> [Error: Parse error on line 225:
>>>> ...deFieldNameNotFound":[ { "Sign
>>>> -----------------------^
>>>> Expecting 'EOF', '}', ',', ']', got ':']
>>>> www.web3d.org/x3d/content/examples//Basic/Security/HelloWorldSignedDecrypted.json
>>>> [Error: Parse error on line 225:
>>>> ...deFieldNameNotFound":[ { "Sign
>>>> -----------------------^
>>>> Expecting 'EOF', '}', ',', ']', got ':']
>>>
>>> XML-encrypted scenes have characters that JSON doesn't like. can't re-encode encrypted versions without breaking them anyway, so this is not a test case.
>>>
>>>> www.web3d.org/x3d/content/examples//Basic/Shaders/SimpleShader.json <http://www.web3d.org/x3d/content/examples//Basic/Shaders/SimpleShader.json>
>>>> [Error: Parse error on line 144:
>>>> ... }
>>>> -----------------------^
>>>> Expecting 'STRING', got '}']
>>>
>>> stray commas, will check logic
>>>
>>>> www.web3d.org/x3d/content/examples//Basic/StudentProjects/LaetitiaSprints.json <http://www.web3d.org/x3d/content/examples//Basic/StudentProjects/LaetitiaSprints.json>
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>
>>> my copy is passing OK
>>>
>>>> www.web3d.org/x3d/content/examples//Basic/X3dSpecifications/ECMAScriptSaiCreateNodesFromPrototype.json <http://www.web3d.org/x3d/content/examples//Basic/X3dSpecifications/ECMAScriptSaiCreateNodesFromPrototype.json>
>>>> [Error: Parse error on line 100:
>>>> ... at DEF":"SC", } } ] }
>>>> ----------------------^
>>>> Expecting 'STRING', got '}']
>>>> www.web3d.org/x3d/content/examples//Basic/X3dSpecifications/ECMAScriptSaiPerFrameNotification.json <http://www.web3d.org/x3d/content/examples//Basic/X3dSpecifications/ECMAScriptSaiPerFrameNotification.json>
>>>> [Error: Parse error on line 53:
>>>> ... at DEF":"SC", } } ] }
>>>> ----------------------^
>>>> Expecting 'STRING', got '}']
>>>
>>> duplicate of prior SC bug
>>>
>>>> www.web3d.org/x3d/content/examples//Basic/X3dSpecifications/X3dHeaderPrototypeSyntaxExamples.json <http://www.web3d.org/x3d/content/examples//Basic/X3dSpecifications/X3dHeaderPrototypeSyntaxExamples.json>
>>>> [Error: Parse error on line 265:
>>>> ...[ "alternative: Text s
>>>> ----------------------^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', ']', got 'undefined']
>>>
>>> bug - trouble handling intentionally gnarly spec comment with double (or is it triple?) escaping:
>>>
>>> <Text string='"He said, \"Immel did it!\""'/>
>>>
>>> "#comment":[
>>> "alternative: Text string='\"He said, \"Immel did it!\"\"'"
>>> ]
>>>
>>>> www.web3d.org/x3d/content/examples//ConformanceNist/Appearance/PixelTexture/256PixelTexture.json <http://www.web3d.org/x3d/content/examples//ConformanceNist/Appearance/PixelTexture/256PixelTexture.json>
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>
>>> memory issue handling 600K single-line numeric string
>>>
>>> obtw json will want to insert commas throughout
>>>
>>>> www.web3d.org/x3d/content/examples//ConformanceNist/GeometricProperties/Coordinate/15000points_lineset.json <http://www.web3d.org/x3d/content/examples//ConformanceNist/GeometricProperties/Coordinate/15000points_lineset.json>
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//ConformanceNist/Geometry/IndexedLineSet/15000-polylines-defcolor.json
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//ConformanceNist/Geometry/IndexedLineSet/15000-Vertices.json
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Savage/AircraftFixedWing/B52H-StrategicBomber-UnitedStates/B52HStatic.json
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Savage/AircraftHelicopters/JhlHeavyLift-NPS/JointHeavyLiftHelicopter.json
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Savage/Locations/CampPendletonCalifornia/CampPendletonOperatingAreasExample.json
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Savage/Locations/FortLauderdaleFlorida/FortLauderdaleDepths10m.json
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Savage/Locations/FortLauderdaleFlorida/FortLauderdaleDepths20m.json
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Savage/Locations/MontereyBayCalifornia/MontereyBayLargeMesh.json
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Savage/Robots/UnmannedUnderwaterVehicles/Bluefin21BPAUV.json
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Savage/Scenarios/RemusMission10MAR2003/RemusMissionLineTrackPlayback.json
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Savage/Scenarios/UssColeTerroristAttack/AdenHarbor.json
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Savage/Scenarios/UssColeTerroristAttack/AdenHarborSmallScale.json
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Savage/ShipsCivilian/PersonalWaterCraft/JetskiWithRider.json
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Savage/ShipsCivilian/ResearchVessels/Endeavor.json
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//Savage/Tools/Authoring/GridsExamplePixelTexture.json
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>
>>> all memory exceeded
>>>
>>>> www.web3d.org/x3d/content/examples//Savage/Weapons/UnderwaterMines/ReportedContactPrototype.json <http://www.web3d.org/x3d/content/examples//Savage/Weapons/UnderwaterMines/ReportedContactPrototype.json>
>>>> [Error: Parse error on line 594:
>>>> ... "Mine code enumerati
>>>> -----------------------^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', ']', got 'undefined']
>>>
>>> backslashes in comment. fixed source.
>>>
>>>> www.web3d.org/x3d/content/examples//X3dForAdvancedModeling/GeometricShapes/IcosahedronSubdivisionLevel5.json <http://www.web3d.org/x3d/content/examples//X3dForAdvancedModeling/GeometricShapes/IcosahedronSubdivisionLevel5.json>
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>> www.web3d.org/x3d/content/examples//X3dForAdvancedModeling/Matlab/PhasedArrayBeamExample.json <http://www.web3d.org/x3d/content/examples//X3dForAdvancedModeling/Matlab/PhasedArrayBeamExample.json>
>>>> [Error: Parse error on line 1:
>>>>
>>>> ^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'EOF']
>>>
>>> memory exceded
>>>
>>>> www.web3d.org/x3d/content/examples//X3dForAdvancedModeling/Inspiration/ObliqueStrategiesText.json <http://www.web3d.org/x3d/content/examples//X3dForAdvancedModeling/Inspiration/ObliqueStrategiesText.json>
>>>> [Error: Parse error on line 1:
>>>> strategy[ 0]=['Remo
>>>> --^
>>>> Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'undefined']
>>>
>>> failure to capture embedded Javascript into JSON - probably a good thing, avoiding eval-style vulnerabilities? worth further scrutiny.
>>>
>>>> www.web3d.org/x3d/content/examples//X3dForWebAuthors/Chapter02-GeometryPrimitives/TextSpecialCharacters.json <http://www.web3d.org/x3d/content/examples//X3dForWebAuthors/Chapter02-GeometryPrimitives/TextSpecialCharacters.json>
>>>> [Error: Parse error on line 82:
>>>> ...s X3D backslash \\" \"Pi Π is Π XML
>>>> -----------------------^
>>>> Expecting 'EOF', '}', ':', ',', ']', got 'undefined']
>>>
>>> JSON does not seem to like non-ascii characters, similar problems with foreign-language files. perhaps there is a test switch to permit full unicode support.
>>>
>>> ... so thanks for identifying 2 flawed scenes and a few potential converter improvements.
>>>
>>> not seeing any problems with conversion pattern.
>>>
>>> all the best, Don
>>> --
>>> Don Brutzman Naval Postgraduate School, Code USW/Br brutzman at nps.edu <mailto:brutzman at nps.edu>
>>> Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149
>>> X3D graphics, virtual worlds, navy roboticshttp://faculty.nps.edu/brutzman
>>
>
>
> all the best, Don
> --
> Don Brutzman Naval Postgraduate School, Code USW/Br brutzman at nps.edu
> Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149
> X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman
More information about the x3d-public
mailing list