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

[Don Brutzman]

Continued improvement of the X3D JSON Loader sounds great!

Meanwhile, much of what you are looking for is also present in the Java/Ant-based build scripts already.  Hopefully this is helping with loader development as well.

Missing parts for this alternate Java/Ant approach to work:

a. Java-based conversion from FileName.json to FileNameRoundTrip.xml

b. Ant- or Java-based invocation of xmlunit testing to compare original FileName.x3d to FileNameRoundTrip.xml

Also creeping up my task list is the goal to

c. add X3D JSON Schema validation to the build scripts.

Depending on how forgiving the xmlunit package is, X3D Canonicalization (C14N) may or may not be needed.  In any case, Java-based C14N is available.

Outputs for each scene would be in the build log.  So scene error reporting is in the eye of any beholder too.

Quality Assurance (QA) is good!  This is all part of how we are ensuring that the X3D infrastructure provides a rock-solid basis for server-side/cloud/enterprise graphics.

http://www.web3d.org/x3d/content/examples/X3dResources.html#QualityAssurance

btw apologies that our intermittent server problems are not resolved yet.  Meanwhile the full set of X3D Validator checks are also available as part of X3D-Edit and testable locally when you have that installed.

==========================================

On 3/19/2016 3:48 PM, John Carlson wrote:
> 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

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