[x3d-public] Results from upgrading X3D JSON schema, replaced $ref occurences of character | with %7C (legal URI)

[John Carlson]

Replacing | with %7C in minimal places (only anchor URIs), proceeding to production validation on https://coderextreme.net/X3DJSONLD/src/main/html/validator.html (everit-org not used, Ajv used)
https://github.com/coderextreme/x3dschema/blob/master/javaresults.txt (everit-org results)
https://github.com/coderextreme/x3dschema/blob/master/results3.txt (Ajv results, autogenerated schema)
Results between two may vary by schema used.
https://github.com/coderextreme/x3dschema/blob/master/results6.txt (Ajv results, hand generated schema)
In an ideal world, everit-org and Ajv should match up. I don't see any bad effects of using %7C in Ajv, so I will go ahead permit this issue to be closed (if not already). The two Ajv results are done by running the hand-generated results against the autogenerated results and subtracting (both ways), so they should be very different.

Proceed with validating your JSON objects with validator.html or X3DJSONLD.  Autogenerated schemas should be present and functional.
NEW PROJECT:
https://github.com/coderextreme/json-schema preparations for using everit-org on massive scale (now just one file).  Modify arg value in build.xml and run ant.

DISCUSSION:
Should we use %7C in URI’s for JSON schema, or change X3DUOM to a non-escaped URI character? The autogenerator can go either way, it will just appear that the X3DUOM and X3D JSON schema are different if we choose to go with %7C in X3D JSON schema URIs (we can’t really use | in X3D JSON schema URIs).
Thanks,

John

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