<html><head></head><body>Hi John.<br>
Well, it just looks like Unit Test to put in place.<br>
I could be your guy.<br>
<br>
Clement.<br><br><div class="gmail_quote">Le 19 mars 2016 23:48:02 UTC+01:00, John Carlson <yottzumm@gmail.com> a écrit :<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">I am soliciting for a volunteer for X3D JSON to X3D XML conversion work. This would entail:<br /><br />* Using the X3D JSON Loader associated code to convert X3D Resources examples JSON to XML (and DOM).<br />* Running the X3D Canonicalizer to convert to canonicalized X3D XML<br />* Running a comparison between X3D Resources examples X3D XML and XML output from X3D Canonicalizer<br />* Reporting any discrepancies to X3D JSON Working Group<br />* Integrating any improvements into the X3D JSON Loader associated code, contributing to X3D JSON Loader development work in generating X3D XML.<br /><br />Other activities may include:<br /><br />* Integrating the X3D JSON Schema into the X3D JSON Loader<br /><br />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.<br /><br />I’d do it myself, but I recently came out of retirement.<br /><br />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.<br /><br />Thanks,<br /><br />John<br /><hr /><br />x3d-public mailing list<br />x3d-public@web3d.org<br /><a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br /></pre></blockquote></div><br>
clement@igonet.fr</body></html>