[x3d-public] Fixed! Re: Gotcha in JSON schema (current deployed in X3DJSONLD, x3dvalidate)

[John Carlson]

AFAICT, after testing files that failed in the archive:

$ npx x3dvalidate at 8.7.0 C:/x3d-code/
www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/Animation/PongGame.json

$ npx x3dvalidate at 8.7.0 C:/x3d-code/
www.web3d.org/x3d/content/examples/X3dForWebAuthors/Chapter05AppearanceMaterialTextures/FillPropertiesExample.json

$ npx x3dvalidate at 8.7.0 C:/x3d-code/
www.web3d.org/x3d/content/examples/X3dForWebAuthors/Chapter05AppearanceMaterialTextures/LinePropertiesExample.json

I am releasing x3dvalidate 8.7.0 (validate X3D JSON) for production use.

Please check your archive files mentioned above with existing versions, and
then update!

Let me know if anyone has problems with previously mentioned

x3dvalidate is released under the BSD-2 license, and has copies of X3D JSON
schema generated in X3DJSONLD.  X3DJSONLD schemas and schema generator for
2020-12 JSON schema has been updated for integer enums.

John




On Sat, Mar 2, 2024 at 8:34 PM John Carlson <yottzumm at gmail.com> wrote:

> Apparently, some @names are treated as arrays of numbers?
>
> I think this has something to do with the xs:NMTOKEN previously mentioned
> for the X3DVertexAttributeNode and subtypes in X3D Schema and X3DUOM.
>
> I am converting these to strings until we can reach some kind of
> resolution with regards to X3DUOM.  I am pretty sure that arrays of
> numbers are not desired for @name!
>
> I am also working on numerical enumerations until some X3D schema/X3DUOM
> min/max is achieved for @hatchStyle and @lineType
>
> Thanks!
>
> John
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20240302/5a519e27/attachment.html>