[x3d-public] X3D minutes 17 MAR 2023: Web3D 2023 Conference Call for Participation CFP, X3D 4.0 editorial comments review
John Carlson
yottzumm at gmail.com
Fri Mar 17 16:36:44 PDT 2023
Here is a generated JSON file
https://www.web3d.org/x3d/content/examples/Basic/GeoSpatial/A5_GeoOrigin.json
That shows different encodings of 2 different MFString fields. See
NavigationInfo. at type and geoSystem.
I don’t believe there is any problem with XML or ClassicVRML.
So we can do all the work in the JSON encoding or in X3D4.1 or beyond. I
don’t mind kicking as far down the line as you like!
I’m not really concerned about this since I’ve implemented patches, I’m
just concerned about wording in an abstract encoding forcing a string
encoding instead of using arrays native to an encoding. That is, choosing
XML encoding of an array field instead of a non-XML encoding. We should
be consistent for all MFStrings in an encoding. One can be more liberal
with types when one is dealing with a binding.
But yeah, arrays in a string is fine with me, just seems like a lot of work.
John
On Fri, Mar 17, 2023 at 5:09 PM John Carlson <yottzumm at gmail.com> wrote:
> I note that geoSystem uses MFString, and I feel that MFString encoding
> syntax should be the same across all MFString fields in an encoding to
> insure consistency and reliability of browser and converter
> implementations. I’m less sure of the need to require consistency and
> reliability between different encodings.
>
> Thanks for your wordsmithing, Nicholas. Note that changing status quo
> will require changes to X3DOM, X_ITE and X3DJSONLD.
>
> X3DJSONLD may end up being a relic, but I’m guessing implementations in
> X3DOM and X_ITE will carry on.
>
> While we can work on these decisions one MFString at a time, wouldn’t it
> be better to group them together?
>
> Thanks!
>
> John
>
> On Fri, Mar 17, 2023 at 12:09 PM Brutzman, Donald (Don) (CIV) <
> brutzman at nps.edu> wrote:
>
>> Attendees: William Glascoe, Anita Havele, Vince Marchetti, Dick Puk, Doug
>> Sanden, Don Brutzman.
>>
>>
>>
>> The X3D Working Group meets weekly on Fridays 09-1000 Pacific on Web3D
>> Consortium zoom channel. Telcon information:
>>
>> -
>> https://us02web.zoom.us/j/81634670698?pwd=a1VPeU5tN01rc21Oa3hScUlHK0Rxdz09
>> - https://zoom.us/j/148206572 Password 483805
>> - https://www.web3d.org/member/teleconference-information
>>
>>
>>
>> 1. *X3D 2023 goals. *Our primary activities for X3D Working Group in
>> 2023 are focused on broad and correct deployment.
>>
>>
>>
>> 1. Encourage consistent rendering, interaction and usage for the many
>> tremendous capabilities in X3D4.
>> 2. Update ISO specifications and implementations for multiple
>> programming languages and file encodings to match X3D4.
>>
>>
>>
>>
>>
>> 1. *Web3D 2023 Conference*
>>
>>
>>
>> Call for papers now available. What a powerful program!
>>
>>
>>
>> - Web3D 2023, 9-11 October 2023, Vicomtech
>> - San Sebastian Spain, In-person and Online
>> - https://web3d.siggraph.org
>> - https://web3d.siggraph.org/cfp
>>
>>
>>
>> *Towards interconnectivity of Metaverses*
>>
>> The purpose of the 28th International ACM Conference on 3D Web Technology
>> (Web3D 2023) is to study and share the principles and the latest
>> advancements in connected 3D universes. Provide navigation metaphors that
>> allow users to move seamlessly from one virtual world to another.
>>
>> The goal of the conference and of the Web3D community, which has a rich
>> history of developing technologies that enable the creation, transmission,
>> access, interaction, sharing, and visualization of 3D universes. Bringing
>> together a diverse group of individuals to share innovative and influential
>> thoughts on how the metaverse can revolutionize the future of
>> communications. This includes topics such as 3D applications and services
>> accessible through a wide range of devices, from simple mobile phones to
>> more complex systems such as AR/VR headsets, and heavily populated virtual
>> worlds, especially those connected through high-speed, low-latency networks.
>>
>> The 28th International ACM Conference on 3D Web Technology (Web3D 2023)
>> is a major event for the Metaverse community. Sponsored by ACM SIGGRAPH, in
>> cooperation with Web3D Consortium and supported by Eurographics, this
>> conference is hosted by Vicomtech and brings together experts from around
>> the world to discuss the latest research, development, and practices
>> related to the Metaverse.
>>
>> It will be really interested if we can start collecting and disseminating
>> 3D models as part of the publication process. Anyone interested?
>>
>>
>>
>>
>>
>> 1. *X3D 4.0 editors-draft IS.review preparation now in progress*
>>
>>
>>
>> Have begun applying changes from editors review of DIS spec, in
>> preparation for final IS submission to ISO. Many changes are complete,
>> several pending ISO comments require lengthy double-checking. Marked-up
>> specification draft visible at
>>
>>
>>
>> -
>> https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-IS.review
>>
>>
>>
>> As before, each comment is being resolved in Mantis. Mantis issues are
>> not closed until reviewed together. Specification changes are checked into
>> GitHub.
>>
>>
>>
>> - Mantis issue resolution
>> - https://www.web3d.org/member-only/mantis/view_all_bug_page.php
>>
>>
>>
>> - Review draft
>> -
>> https://github.com/Web3DConsortium/X3D/tree/master/ISO-IEC19775/ISO-IEC19775-1/ISO-IEC19775-1v4.0/ISO-IEC19775-1v4-IS.review
>>
>>
>>
>> - Editors comments
>> -
>> https://github.com/Web3DConsortium/X3D/blob/master/ISO-IEC19775/ISO-IEC19775-1/ISO-IEC19775-1v4.0/ISO-IEC19775-1v4-DIS.ISO/Disposition%20of%20Comments%20on%20ISO_IEC_DIS_19775-1_(Ed_4).pdf
>>
>>
>>
>> When these changes are all complete and reviewed satisfactorily, I will
>> again fire up the build scripts to scrub all style markup appropriately, to
>> create a separate pristine version for ISO submission.
>>
>>
>>
>>
>>
>> 1. *X3D4 Sound Component review*
>>
>>
>>
>> - Minutes 3 MAR 2023: X3D4 Sound Component and W3C Audio API review
>> -
>> https://web3d.org/pipermail/x3d-public_web3d.org/2023-March/018574.html
>>
>>
>>
>> Dick Puk sent a message to Web3D member-only X3D list about only
>> accepting editorial/errata changes at this late date of X3D 4.0
>> finalization. Thanks for that.
>>
>>
>>
>> - [x3d] Recent discussions about changes to the X3D 4.0 Sound
>> Component
>>
>>
>>
>> Issues that will get resolved in this final editing phase:
>>
>>
>>
>> - clarifications needed in prose for 16.4.13 ListenerPointSource and
>> 16.4.18 SpatialSound nodes.
>> - https://www.web3d.org/member-only/mantis/view.php?id=1436
>> - “If the *dopplerEnabled* field is TRUE, then sound sources which
>> are moving spatially in the transformation hierarchy, relative to the
>> location of the ListenerPointSource node, shall be modified by applying
>> velocity-induced frequency shifts corresponding to Doppler effect.”
>>
>>
>>
>> - Correcting mistaken type, also for specification consistency: SFTime
>> - DynamicsCompressor : X3DSoundProcessingNode {
>>
>> SFFloat [in,out] attack 0.003 [0,∞)
>>
>> SFTime [in,out] release 0.25 [0,∞)
>>
>> - https://www.web3d.org/member-only/mantis/view.php?id=1436
>>
>>
>>
>> - Convolver buffer[] array is quite difficult to use, allowing
>> AudioClip as an alternative seems like an obvious (previously overlooked)
>> remedy.
>> - We decided to wait and fix it later, along with other likely
>> refinements to the Sound component, to best align with Web Audio API. It
>> is related to handling of multiple-channel sound sources.
>>
>>
>>
>> - SFInt32 number of channels to go with buffer in Convolver?
>> - This is not explicitly described in specification, but implicit in
>> handling of the child nodes (such as BufferAudioSource).
>> - Need for editorial clarification accepted.
>> - We will look in Web Audio API and see if there is useful prose to
>> paraphrase in Convolver that helps to clarify the handling of
>> number-of-channel questions. Otherwise we’ll create appropriate prose.
>> Doug has next crack at this.
>>
>>
>>
>> As described in previous meetings, I will be looking for one or two
>> co-chairs who can begin documenting Web3D Best Practices and suggested new
>> capabilities for X3D 4.0. As ever, discussion on x3d-public mailing list
>> and synopses in Mantis Issue Tracker will be the means for ensuring that
>> all good consensus approaches are captured and advanced.
>>
>>
>>
>>
>>
>> 1. *Comment reconciliation*
>>
>>
>>
>> Dick Puk and I will review correct completion and resolve each of the
>> following applied comments.
>>
>>
>>
>> Id
>>
>> Project
>>
>> Tags
>>
>> Status
>>
>> Severity
>>
>> Summary
>>
>> 1436
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> Sound component editorial clarifications
>>
>> 1435
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> cross-link AcousticProperties from Sound component to Shape component
>>
>> 1434
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> DIS editors disposition: annex citations
>>
>> 1433
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> DIS editors disposition: glossary, replace 'abbreviations' with
>> 'abbreviated terms'
>>
>> 1432
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> DIS editors disposition: clause 3, definitions introductory paragraph
>>
>> 1431
>>
>> X3D
>>
>> V4.0, V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> indicating references are required
>>
>> 1430
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> DIS editors disposition: general comment 10, references introductory
>> paragraph
>>
>> 1429
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> DIS editors disposition: general comment 9, foreward, additional note on
>> feedback
>>
>> 1428
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> DIS editors disposition: general comment 8, foreword list of changes
>>
>> 1427
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> DIS editors disposition: general comment 7 Foreword boilerplate
>>
>> 1426
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> DIS editors disposition: general comment 5, title structure
>>
>> 1425
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> DIS editors disposition: general comment 4, code font
>>
>> 1424
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> DIS editors disposition: general comment 3, Introduction and TOC
>>
>> 1423
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> DIS editors disposition: general comment 2, correct verbal forms
>>
>> 1422
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> DIS editors disposition: general comment 1 "this document"
>>
>> 1420
>>
>> X3D
>>
>> V4.0 Resolution, V4.1
>>
>> assigned
>>
>> major
>>
>> Missing 5 enumeration sets (and likely fields) from Web Audio interfaces
>>
>> 1419
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> rename “Texture Projector component” as “Texture Projection component”
>>
>> 1418
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> major
>>
>> Ambiguity about texture coordinate generation
>>
>> 1417
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> versionContent document-index table incomplete
>>
>> 1415
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> 26.3.4 HAnimMotion field issues: name, skeletalConfiguration,
>> totalNumberFrames
>>
>> 1414
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> 26.3.4 HAnimMotion node signatures
>>
>> 1413
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> text
>>
>> Misspelled node name: IndexedFanSet should be IndexedTriangleFanSet
>>
>> 1411
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> enumeration values for Web Audio nodes do not follow CAPITALIZATION
>> conventions
>>
>> 1410
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> major
>>
>> HAnimHumanoid skin definitions need to assign textures via Shape, Group,
>> Switch etc.
>>
>> 1408
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> feature
>>
>> CollisionCollection and HAnimMotion nodes are each missing description
>> field
>>
>> 1407
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> Collision element (and other elements) missing description field in
>> Version Content
>>
>> 1406
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> 25.3.6 GeoOrigin description is awkwardly phrased
>>
>> 1405
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> 39.3.2 X3DDamperNode has erroneous extra characters
>>
>> 1404
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> 39.4.6 OrientationDamper, incorrect word 'orientation' vice 'rotation'
>>
>> 1403
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> Insufficient description for HAnimJoint
>>
>> 1402
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> Insufficient description for HAnimSegment
>>
>> 1401
>>
>> X3D
>>
>> V4.0 Resolution, V4.1
>>
>> assigned
>>
>> minor
>>
>> formally adding values to align X3D4 LineProperties with Quality
>> Information Framework (QIF) specification
>>
>> 1398
>>
>> X3D
>>
>> V4.0 Resolution
>>
>> assigned
>>
>> minor
>>
>> OrthoViewpoint fieldOfView type needs to be SFVec4f, not MFFloat
>>
>>
>>
>>
>>
>>
>>
>> - Nicholas do you have a geosystem prose refinement for us?
>> - https://www.web3d.org/member-only/mantis/view.php?id=1437
>>
>>
>>
>> Great meeting, thanks everyone.
>>
>>
>>
>> Color note: don’t forget to wear green on Saint Patrick’s Day… your
>> avatar too. March the 17th – Sleep the 18th. [image: Shamrock]
>>
>>
>>
>> Have fun with X3D 4.0! 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, data
>> 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/20230317/c412b344/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1171 bytes
Desc: not available
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20230317/c412b344/attachment-0001.png>
More information about the x3d-public
mailing list