[x3d-public] X3D minutes19 June 2020: Mantis issues ongoing resolution - closer to draft X3D4 release
Don Brutzman
brutzman at nps.edu
Fri Jun 19 15:37:50 PDT 2020
We meet at our regular time and Zoom coordinates, Friday 08-0930 pacific (your time zone may vary).
Attendees: Anita Havele, Vince Marchetti, Doug Sanden, Don Brutzman.
No member-only information information is included in these minutes.
Thanks for patience with some Mantis challenges today. We persevered and got a lot done.
------------------------------
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 2020. Following that review the draft document will be released publicly for comment in time for SIGGRAPH 2020.
Implementation efforts 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 publicly at
[1] X3D4 Tooltips
https://www.web3d.org/x3d/content/X3dTooltips.html
------------------------------
3. *Mantis Access*
Reportedly each member and invited expert either has full access into these Mantis issues, or else is being assisted. POCs are Vince Marchetti and Anita Havele if difficulties persist.
We will renew our list of invited every 6 months. Next renewal request scheduled for 8 DEC 2020.
Confirmation has been sent to all individuals concerned by Anita and Vince. Thanks for all participation.
------------------------------
4. *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.
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
Thanks for help by Vince, Doug and Dick 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 draft release.
Issue list follows, full issue list attached.
Id Summary
=======================
1310 near and far clipping planes currently not directly specified
[5] Viewing frustum
https://en.wikipedia.org/wiki/Viewing_frustum
We expect that most render engines include ability to set near/far clipping planes. For example,
* OpenGL Rendering Pipeline, Clipping
https://www.khronos.org/opengl/wiki/Rendering_Pipeline_Overview
https://www.khronos.org/opengl/wiki/Vertex_Post-Processing#Clipping
* Setting near plane in OpenGL
https://stackoverflow.com/questions/3410096/setting-near-plane-in-opengl
* OpenGL glFrustum
https://www.khronos.org/registry/OpenGL-Refpages/gl2.1/xhtml/glFrustum.xml
* gluPerspective
https://www.khronos.org/registry/OpenGL-Refpages/gl2.1/xhtml/gluPerspective.xml
* WebGL Frustum Diagram
https://webglfundamentals.org/webgl/frustum-diagram.html
Confirmed as deserving further work. Adding this functionality to X3DViewpointNode will help when transitioning near-to-far in scenes with terrain.
-----
1309 NavigationInfo avatarSize parameters need to be split into separate fields
Suggested names for three respective avatarSize parameters follow. Using the prefix 'avatar' for each emphasizes that consistent backwards compatibility.
a. view-to-object collision distance: avatarRadius
b. avatar height above ground plane: avatarHeight
c. step-over height: avatarStepHeight
No changes to already defined functionality in avatarSize field. Given that it defines user (avatar) height and distance to collision, this is a cylindrical definition.
TODO: experiment with these names in X3DUOM and example content.
-----
1308 creaseAngle support by Triangle nodes
Rejected, see email thread. Computational concerns indeed are important.
[6] [x3d-public] Feedbacks related to x3d.py: creaseAngle support by Triangle nodes
http://web3d.org/pipermail/x3d-public_web3d.org/2020-June/012971.html
-----
1307 X3DParticleEmitterNode mass and surfaceArea accessType initializeOnly rather than inputOutput?
Deferred.
-----
1304 allowing animation of Cone, Cylinder bottom/side/top: accessType inputOutput
All changes applied, issue resolved.
-----
1303 optional support for WebMercator datasets
Thanks for email dialog!
Need to determine and review the authoritative reference in order to integrate with the spec. Since it is widely implemented with a lot of data available, so (despite some fidelity issues) we intend to support.
* Web Mercator projection
https://en.wikipedia.org/wiki/Web_Mercator_projection
Official reference appears to be EPSG:3857
* EPSG Geodetic Parameter Dataset
https://en.wikipedia.org/wiki/EPSG_Geodetic_Parameter_Dataset
We will track down master specification, and also determine if it has any standing in ISO already.
-----
1302 geoSystem is difficult to define and parse, consider alternative approach
Dick and Don will work further on this one.
-----
1301 check geospatial navigation to see if NavigationInfo modes are sufficient
Mike McCann, any thought to this?
-----
1300 Consistently unify metadata model for GeoMetadata and HAnimHumanoid info array
The expected approach will retain all existing metadata names and values without change, simply allowing a more consistent metadata alternative.
Expected demonstration will be mapping and translating existing structures to a consistent MetadataSet pattern, making this information less idiosyncratic. At that point we can consider deprecating or deleting the old fields.
-----
1299 Annotation Component deferral
Editorial work for Dick and Don - accomplished during the call, thanks Doug for being our safety spotter!
Resolved.
-----
1293 HypersurfaceSensor/MultiTouchSensor for multi-touch environments
Active topic on x3d-public list. Deferred to future date.
-----
1292 numbering of z order of layers in LayerSet
Deferred. Simply reccommends alignment of initial indexing (0 or 1) with HTML5.
-----
1283 XML encoding: change X3D4 MetadataSet default containerField='value' ?
Nearly complete but XML encoding related, and not necessary for SIGGRAPH 2020 release, deferred.
-----
1281 TwoSidedMaterial deprecation by adding Appearance backMaterial field
pending 1269 PBR, review next week!
-----
1277 Provide displayBBox field on X3DBoundedObject nodes to display bounding boxes, rename bboxDisplay for consistency
All work complete. Resolved.
-----
1276 name types: whitespace constraints, NMTOKEN and SFString
Everything is implemented in validation suite. Further review of X3D Architecture prose deferred.
-----
1275 whether CollisionCollection, RigidBody, RigidBodyCollection implement X3DBoundedObject interface (as does NurbsSet)
Pending implementation, as agreed by X3D Working Group.
Implemented for CollisionCollection, needed for RigidBody and RigidBodyCollection.
Need to confirm consistent specification prose in all relevant locations.
-----
1273 https level support requirements should match http level support
Deferred.
-----
1272 glTF import needs to include metadata import
pending 1269 PBR, review next week!
-----
1271 add visible field to X3DBoundedObject
All work complete. Resolved.
-----
1269 glTF physically based rendering PBR, advanced material textures and lighting
next week!
-----
1268 add height and width attributes to root X3D node
Deferred.
-----
1267 Strategies to Improve X3Dv4 Audio and Sound Component
In progress, weekly meeting minutes posted to x3d-public list.
-----
1266 Make RGB and grayscale textures treatment consistent
next week!
-----
1265 Text size clarification, relative to baseline
Deferred.
-----
1264 NavigationInfo type TURNTABLE HELICOPTER GAME FREEFLY
Web3DUX discussion in progress.
-----
1263 Log capability to record event streams
Deferred.
-----
1262 new field /refresh/ for Inline, ImageTexture etc.
Discussion deferred. Appears noncontroversial, recommend implementation and testing.
-----
1261 PointSet field for Normal node
Entered in Schema, DTD, X3DUOM and specification.
http://svn.code.sf.net/p/x3d/code/www.web3d.org/specifications/x3d-schema-changelog.txt
Example model:
https://x3dgraphics.com/examples/X3dForAdvancedModeling/Scanning/X3dMeshDesignPatternIndex.html
Simple conformance issue at this point. Resolved.
-----
1259 Scanning profile needed?
Added explanation that might be considered in the future. Resolved.
-----
1258 Layout component needs to be consistently implemented
Deferred.
-----
1257 Inline allowed to load additional model types
Next week! glTF loading implemented in view3dscene.
-----
1255 Projective Texture Mapping Component (PTM)
Review deferred.
-----
1252 PointProperties node specification; PointSet/LineSet/IndexedLineSet can contain Normal
Mostly complete. Sole remaining issue is whether PBR might affect rendering prose.
Need to do a final review when Physically Based rendering (Mantis 1269) is finalized. The current opinion is that PointSet are considered unlit so the rendering will not be affected by PBR.
-----
Thursday 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. They are well written and likely will not require further group attention.
Attached: updated issues list in Comma Separated Value (csv) text format, including today's updates.
------------------------------
5. *X3DUOM changes expected*
Based on today's progress and expected resolutions that are ready and nearly approved, am hoping to apply the following additions to X3D XML Schema, X3DUOM and related tools. These additions will facilitate experimentation, implementation and evaluation without breaking anything else.
Mantis 1310: X3DViewpointNode, nearClippingPlane farClippingPlane
Mantis 1309: NavigationInfo, avatarRadius avatarHeight avatarStepHeight (then later determine if avatarSize deprecated)
Mantis 1262: Inline, SFTime /refresh/
Mantis 1267: Sound component changes (abstract interfaces, nodes, fields once well defined)
Mantis 1264: add NavigationInfo /type/ optional enumerations for TURNTABLE HELICOPTER GAME FREEFLY
Mantis 1275: add /displayBBox/, /visible/ to RigidBody, RigidBodyCollection
Stand by for ongoing action! Absent any objections, I plan to add and deploy these so that we are prepared to apply multiple changes for X3D PBR next week. Downstream changes are still allowed.
-----
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: X3dMantisIssues19JUN2020.csv
Type: application/vnd.ms-excel
Size: 113287 bytes
Desc: not available
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20200619/d2ac78b0/attachment-0001.xlb>
More information about the x3d-public
mailing list