[x3d-public] X3D Agenda 19 June 2020: Mantis issues

John Carlson yottzumm at gmail.com
Thu Jun 18 19:54:56 PDT 2020


For 1302 geoSystem, I recommend looking at JSON schema as created by Roy
Walmsley and  copied into the automatically generated schemas wholesale.

If we can convert JSON Schema to XMLSchema, that might be a good solution.

Idk.   Maybe try it on a small scale first.

John

On Thu, Jun 18, 2020 at 9:42 PM Don Brutzman <brutzman at nps.edu> wrote:

> We meet at our regular time and Zoom coordinates, Friday 08-0930 pacific
> (your time zone may vary).
>
> ---
>
> 1. *Participation Information*
>
> [1] Web3D Teleconference Information
>      https://www.web3d.org/member/teleconference-information
>
> Please use the following link for all Web3D Consortium Meetings.
>
> Join URL:
> https://us02web.zoom.us/j/81634670698?pwd=a1VPeU5tN01rc21Oa3hScUlHK0Rxdz09
>
> Meeting ID: 81634670698      Meeting Password: 483805
>
> One tap mobile
>      US (New York) +1 929 205 6099,,(nine-digit number from Join URL
> above)#
>      US (San Jose)  +1 669 900 6833,,(nine-digit number from Join URL
> above)#
>
> ---
>
> 2. *Related work*
>
> We hope to review and accept Pull Request 8 next week to integrate
> Physically Based Rendering (PBR) and lighting with glTF support.
>
> Efi, Thanos, Dick and Don have nearly all node and node type architectural
> relationships defined for an upgraded Sound component that includes
> spatialized sound capabilities matching W3C Web Audio API.
>
> We plan to submit a draft specification for review to Web3D Consortium
> Board of Directors and membership on 30 June.  Following that review the
> draft document will be released publicly for comment in time for SIGGRAPH
> 2020.
>
> Implementations to date include X3DOM, X_ITE and Titania, Castle Game
> Engine view3dscene and FreeWRL, with possible implementation interest noted
> by at other major codebases.
>
> Ongoing releases include X3D4 XML Schema, X3D Unified Object Model
> (X3DUOM), X3D XML Schema and DOCTYPE, X3D Ontology, X3D JSON encoding,
> X3DJSAIL (Java), X3DPSAIL (Python x3d.py).
>
> Summary of current and planned X3D4 nodes and fields is available in
>
> [1] X3D4 Tooltips
>      https://www.web3d.org/x3d/content/X3dTooltips.html
>
> ---
>
> 3. *Mantis Issues*
>
> Dick and Don continue making steady progress applying approved changes to
> the X3D4 Specifications and related assets.
>
> [2] Mantis: View All Issues
>      https://www.web3d.org/member-only/mantis/view_all_bug_page.php
>      then select "X3D Project" in upper right corner.
>
> Reportedly each member and invited expert either has full access into
> these Mantis issues, or else is being assisted.  POC is Executive Director
> Anita Havele if difficulties persist.
>
> Draft specification available to members in Github version control:
>
> [3] Github Web3D Consortium
>      https://github.com/Web3dConsortium
>
> [4] Github Web3D Consortium: ISO-IEC 19775-1 - X3D Architecture and base
> components, Part 1
>
> https://github.com/Web3DConsortium/X3D/tree/master/ISO-IEC19775/ISO-IEC19775-1/ISO-IEC19775-1v4.0/ISO-IEC19775-1v4-WD1/Part01
>
> This week we are reviewing a large number of issues that are quite close
> to resolution.  Each issue has enjoyed scrutiny and dialog on the
> x3d-public mailing list and X3D Working Group reviews.  We seek to
> determine consensus on as many as possible in order to allow including the
> corresponding changes in the forthcoming X3D4 draftrelease.
>
> Issue list follows, full issue list attached.
>
> Id              Summary
>
> 1310            near and far clipping planes currently not directly
> specified
>
> 1309            NavigationInfo avatarSize parameters need to be split into
> separate fields
>
> 1308            creaseAngle support by Triangle nodes
>
> 1307            X3DParticleEmitterNode mass and surfaceArea accessType
> initializeOnly rather than inputOutput?
>
> 1304            allowing animation of Cone, Cylinder bottom/side/top:
> accessType inputOutput
>
> 1303            optional support for WebMercator datasets
>
> 1302            geoSystem is difficult to define and parse, consider
> alternative approach
>
> 1301            check geospatial navigation to see if NavigationInfo modes
> are sufficient
>
> 1300            Consistently unify metadata model for GeoMetadata and
> HAnimHumanoid info array
>
> 1299            Annotation Component deferral
>
> 1293            HypersurfaceSensor/MultiTouchSensor for multi-touch
> environments
>
> 1292            numbering of z order of layers in LayerSet
>
> 1283            XML encoding: change X3D4 MetadataSet default
> containerField='value' ?
>
> 1281            TwoSidedMaterial deprecation by adding Appearance
> backMaterial field
>
> 1277            Provide displayBBox field on X3DBoundedObject nodes to
> display bounding boxes, rename bboxDisplay for consistency
>
> 1276            name types: whitespace constraints, NMTOKEN and SFString
>
> 1275            whether CollisionCollection and RigidBody implement
> X3DBoundedObject node
>
> 1273            https level support requirements should match http level
> support
>
> 1272            glTF import needs to include metadata import
>
> 1271            add visible field to X3DBoundedObject
>
> 1269            glTF physically based rendering PBR, advanced material
> textures and lighting
>
> 1268            add height and width attributes to root X3D node
>
> 1267            Strategies to Improve X3Dv4 Audio and Sound Component
>
> 1266            Make RGB and grayscale textures treatment consistent
>
> 1265            Text size clarification, relative to baseline
>
> 1264            NavigationInfo type TURNTABLE HELICOPTER GAME FREEFLY
>
> 1263            Log capability to record event streams
>
> 1262            new field /refresh/ for Inline, ImageTexture etc.
>
> 1261            PointSet field for Normal node
>
> 1259            Scanning profile needed?
>
> 1258            Layout component needs to be consistently implemented
>
> 1257            Inline allowed to load additional model types
>
> 1255            Projective Texture Mapping Component (PTM)
>
> 1252            PointProperties node specification;
> PointSet/LineSet/IndexedLineSet can contain Normal
>
> Today Dick and I located a large number of editorial comments from an
> in-depth review by Roy Walmsley.  We are going through each one-by-one and
> will elevate any that are functional, rather than simply editorial.
>
> Thanks for all scrutiny, feedback and implementation efforts.  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/20200618/6a76d905/attachment.html>


More information about the x3d-public mailing list