[x3d-public] X3D4 updates: MultiTexture validation, X3DUOM, Java, Python, Turtle

[John Carlson]

Thanks, Don!

I’m hoping I can adjust the synonyms in ComposedCubeMapTexture soon,
adopting something that will interoperate across the entire tool chain for
X3D4.

Probably more results will appear out of my personal portfolio soon, as I
continue to improve it.

 Note that I believe I have surprising results for writing out intermediate
results from X3DJSONLD.java instead of passing DOM directly to
X3DLoaderDOM.java.  All warnings, etc disappear!

It may be worth comparing DOM trees in that case.

At some point, I hope to transfer my X3D JSON Schemas back to sourceforge.
  Konstantin, note that there is a python JSON validator under X3DJSONLD,
so you have many choices for validation of JSON files.   I primarily use a
modified Ajv output for debugging.

On Mon, Sep 27, 2021 at 4:09 PM Brutzman, Donald (Don) (CIV) <
brutzman at nps.edu> wrote:

> Extensible 3D (X3D) Graphics is the royalty-free open standard for
> publishing, viewing, printing and archiving interactive 3D models on the
> Web.
>
>
>
> Here are recent updates.  Had some good refinements related to
> MultiTexture, now rippled out through all of the open-source autogenerated
> software builds.
>
>
>
>    1. X3D XML Schema update activity, addressing some scene validation
>    issues:
>
> https://www.web3d.org/specifications/x3d-schema-changelog.txt
>
>
>
> 25 SEP 2021, brutzman
>
> - (v3.1-v4.0) MultiTexture texture field has type X3DSingleTextureNode and
> can include
>
>   ComposedCubeMapTexture, GeneratedCubeMapTexture, ImageCubeMapTexture,
>
>   ComposedTexture3D, ImageTexture3D, PixelTexture3D
>
> - (v3.1-v4.0) MultiTextureCoordinate is part of
> ComposedGeometryContentModel
>
> - (v4.0) allow X3DComposedGeometryNode texCoord field to include
>
>   X3DSingleTextureCoordinateNode|MultiTextureCoordinate
>
> - (v4.0) allow watchlist containerField for backwards compatibility of X3D
> models in
>
>   containerFieldChoicesAudioClip
>
>
>
> Corresponding changes added to X3D XML DOCTYPE as appropriate.  All
> details found at
>
>
>
>    - X3D Specifications: Schema and DOCTYPE Validation
>    - https://www.web3d.org/specifications
>
>
>
>    1. X3D XML Schema changes are applied to the X3DUOM, which then in
>    turn is applied via XSLT conversion stylesheets to create multiple coding
>    projects.
>
>
>
>    - X3D Unified Object Model (X3DUOM)
>    - https://www.web3d.org/specifications/X3DUOM.html
>    - https://www.web3d.org/specifications/X3dUnifiedObjectModel-4.0.xml
>
>
>
> “The X3D Unified Object Model (X3DUOM) is a full set of object-oriented
> interfaces for all nodes, fields and statements in the X3D Architecture
> Specification.”
>
>
>
> Each of the following codebase updates passed respective sets of unit
> tests and conversions using the test scenes (nearly 4000 total).
>
>
>
>    - X3D Resources, Examples: Scene Archives for X3D
>    - https://www.web3d.org/x3d/content/examples/X3dResources.html#Examples
>
>
>
>    1. JAVA X3DJSAIL API
>
>
>
>    - X3D Java Scene Access Interface Library (X3DJSAIL)
>    - http://www.web3d.org/specifications/java/X3DJSAIL.html
>
>
>
> “X3D Java Scene Access Interface Library (X3DJSAIL) supports programmers
> with standards-based X3D Java interfaces and objects, all as open source.”
>
>
>
>    1. Python X3DPSAIL API
>
>
>
>    - X3D Python Scene Access Interface Library (X3DPSAIL)
>    - https://www.web3d.org/x3d/stylesheets/python/python.html
>
>
>
>    - Python x3d.py package
>    - https://pypi.org/project/x3d
>
>
>
> “The x3d.py Python X3D Package supports programmers with Python interfaces
> and objects for standards-based X3D programming, all as open source.”
>
>
>
> Design Features
>
>
>
>    - The current implementation strives to follow first principles of
>    python package design, being as "pythonic" as possible. Creating a
>    native-Python implementation for X3D data structures appears to provide the
>    greatest possible portability.
>    - Python is exceedingly rigorous regarding design and implementation,
>    demands crisp readability, and often leads to a single best approach for
>    each programming task. These are valuable features that lead to ease of
>    programming and greatly reduced debugging. A single well-constructed
>    open-source Python X3D implementation has the potential to serve all Python
>    distributions and programmers well.
>
>
>
>    1. X3D Ontology
>
>
>
>    - X3D Ontology for Semantic Web
>    - https://www.web3d.org/x3d/content/semantics
>
>
>
> “The X3D Ontology for Semantic Web provides terms of reference for
> semantic query of X3D models.”
>
>
>
> Steady work continues.  All feedback welcome.  Have fun with X3D4!   8)
>
>
>
> 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
>
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20210927/ddd320e1/attachment.html>