[x3d-public] Volunteer needed, X3D JSON to X3D XML, X3D Canonicalizer, comparison

[John Carlson]

We use X3dToJson.xslt stylesheet to convert the standard x3d xml to draft x3d json.  I doubt if a tool can meet our requirements without some modification.  But yeah, if you want to convert the XML to JSON you can, as long as you convert back to XML for verification. :)  In other words, compare XML, please.  Use the X3D Canonicalizer if necessary on both the XML files. https://svn.code.sf.net/p/x3d/code/www.web3d.org/x3d/tools/canonical/doc/x3dTools.htm <https://svn.code.sf.net/p/x3d/code/www.web3d.org/x3d/tools/canonical/doc/x3dTools.htm>
John
> On Mar 20, 2016, at 2:00 PM, clement at igonet.fr wrote:
> 
> https://www.npmjs.com/package/xmltojson <https://www.npmjs.com/package/xmltojson> should let me compare exclusively json files... ;-)
> 
> Le 20 mars 2016 18:51:09 UTC+01:00, "clement at igonet.fr" <clement at igonet.fr> a écrit :
> At the very moment (for Open Earth View - osm2x3d module), I only compare some (x3d) json files with nodejs mocha (unit test) framework. xml files comparison should not be a problem, either by comparing raw files, or by comparing json files generated from xml files.
> 
> I could suggest/provide you a nodejs framework quickly...
> 
> Clement.
> 
> 
> 
> Le 20 mars 2016 18:24:03 UTC+01:00, John Carlson <yottzumm at gmail.com> a écrit :
> Well first we have to develop the unit test for the report.  Do you have anything from your open map development comparing xml?  If you look at X3DJSONLD/json2x3d.js you will see how I generate xml for a single case.  This will need to be run through the canonicalizer, then compared to the original .x3d file from x3d resources examples.  Ideally the script would checkout the examples from SourceForge or download a zip, convert to json (don or I have a script for this), convert to xml etc.  Checking out might be faster than downloading a zip.
> 
> John
> 
> On Mar 20, 2016 1:13 PM, "clement at igonet.fr <mailto:clement at igonet.fr>" <clement at igonet.fr <mailto:clement at igonet.fr>> wrote:
> I thought about unit tests with text output in case of failure.
> 
> If you want mail report and so on in case of failure, I'm also confortable with generation of Junit xml report (from nodejs with mocha, or even from shell), confortable with Jenkins deployment (my main job is DevOps) and Dashboard report (also invested in Q.A. process).
> 
> Would you be ready to use and find founds for a server dedicated for this? A basic ssh access to a debian or centos server is enough. I know well a very good server provider in Canada, cheaper than AWS: https://www.ovh.com/ca/en <https://www.ovh.com/ca/en>/
> 
> Clément.
> 
> Le 20 mars 2016 17:44:52 UTC+01:00, John Carlson <yottzumm at gmail.com <mailto:yottzumm at gmail.com>> a écrit :
> It's more than just one unit test, there are around 3500 or so JSON files.  It needs to be robust and report errors in an actionable fashion, not just pass/fail.
> 
> On Mar 20, 2016 2:39 AM, "clement at igonet.fr <mailto:clement at igonet.fr>" <clement at igonet.fr <mailto:clement at igonet.fr>> wrote:
> Hi John.
> Well, it just looks like Unit Test to put in place.
> I could be your guy.
> 
> Clement.
> 
> Le 19 mars 2016 23:48:02 UTC+01:00, John Carlson <yottzumm at gmail.com <mailto:yottzumm at gmail.com>> a écrit :
> I am soliciting for a volunteer for X3D JSON to X3D XML conversion work.  This would entail:
> 
> * Using the X3D JSON Loader associated code to convert X3D Resources examples JSON to XML (and DOM).
> * Running the X3D Canonicalizer to convert to canonicalized X3D XML
> * Running a comparison between X3D Resources examples X3D XML and XML output from X3D Canonicalizer
> * Reporting any discrepancies to X3D JSON Working Group
> * Integrating any improvements into the X3D JSON Loader associated code, contributing to X3D JSON Loader development work in generating X3D XML.
> 
> Other activities may include:
> 
> * Integrating the X3D JSON Schema into the X3D JSON Loader
> 
> You must be a self-motivated self-starter.  JavaScript and Node.js (scripting) knowledge would be useful.  Limited knowledge of X3D desired.  Knowledge of XML entities, escaping, quoting, JSON desired, but may be learned.  Java knowledge might be useful in the
> future.
> 
> I’d do it myself, but I recently came out of retirement.
> 
> The purpose of this is to validate that the JSON loader can essentially produces equivalent XML to X3dToJson.xslt input (roundtripping).  A blissful side effect we hope is that the JSON loader will be able to handle the various quoting and escaping that is coming towards us.
> 
> Thanks,
> 
> John
> 
> 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>
> 
> clement at igonet.fr <mailto:clement at igonet.fr>
> clement at igonet.fr <mailto:clement at igonet.fr>
> clement at igonet.fr
> 
> clement at igonet.fr

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20160320/5ad15abd/attachment-0001.html>