[x3d-public] X3D Working Group minutes 20 JAN 2023: HAnim issues, browser coverage X3D4 comment review for C, C++, C# draft specifications

John Carlson yottzumm at gmail.com
Fri Jan 20 20:40:38 PST 2023


I can look into creating C/C++ SAI test apps once i get help setting up the
SAI in VS Code or Visual Studio.   I have heard that the SAI was developed
with MSVC++ 2012…not going there.  There’s no current need for apps that i
know of, so I’ll be focusing on compiling rather than completely linking an
exe.

But there’s already tons to do.   I plan on visiting a nephrologist to
“optimize” my life.

Ccmake for c++ would work too, I’m already doing JSON to XML with it.

I’ll probably be adding/finding missing coordinates in HAnim tonight.

Thanks!

John

On Fri, Jan 20, 2023 at 8:19 PM Brutzman, Donald (Don) (CIV) <
brutzman at nps.edu> wrote:

> We met today for regular weekly meeting.
>
>
>
> Attendees: John Carlson, William Glascoe, Dick Puk, Doug Sanden, Don
> Brutzman.  Regrets Anita Havele.
>
>
>
> Still hoping to get a volunteer to help list missing nodes and fields in
> the X3D4 cross-reference table. Great learning opportunity, pretty easy –
> simply compare spec to index and note what is missing.
>
>
>
>    - X3D4 Annex Z, version content
>    -
>    https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-DIS/Part01/versionContent.html
>
>
>
>    1. We discussed recent plethora of comments by John regarding HAnim.
>    Color me overloaded… Thanks Joe for support and insights.
>
>
>
> Suggested next steps:
>
>    1. Baseball strategy: ”small ball.“ Focus on pairwise Joint-Segment
>       problems, simple, one at a time.
>       2. Likely culprits are incorrect/misplaced names in example scenes.
>       3. If there is a mistake in content, or misdiagnosis of a correct
>       pairing, that small effort is now isolated and fixable.
>
>
>
> Team sport, “art of the possible too.”  Thanks for all efforts.
>
>
>
>    1. Doug has shared interesting guidelines for Web browser developers.
>    Thank for super emerging resource for developers working on addition of
>    X3D4 capabiltiites.
>
>
>
> Some possible improvements for tooltips:  should we add component links?
> Most tabs are organized by nodes.
>
>    - X3D Node Inventory Comparison
>    <https://www.web3d.org/specifications/X3dNodeInventoryComparison.xlsx>
>     (.pdf
>    <https://www.web3d.org/specifications/X3dNodeInventoryComparison.pdf>)
>    shows node-by-node implementation coverage of the
>    X3D Abstract Specification: validation using X3D Schema, X3D DOCTYPE, and
>    X3D Schematron; X3D Tooltips and VRML97 node sets; plus selected
>    open-source implementations: FreeWrl, X3DOM, X_ITE, view3dscene (Castle
>    Game Engine), X3D-Edit, Xj3D.
>    - https://www.web3d.org/specifications/X3dNodeInventoryComparison.xlsx
>    - https://www.web3d.org/specifications/X3dNodeInventoryComparison.pdf
>
>
>
> Clarification to Javascript column:
>
>    - Can existing open-source JavaScript library exemplars (such as
>    X3DJSONLD, X3DOM and X_ITE) be considered in creation of a X3D JavaScript
>    SAI?  Yes, conceptually, also good for comparison.
>    - Following our existing successes, common-denominator patterns can be
>    regularized to guide our autogeneration capabilities and exactly match
>    JavaScript SAI standard?  Yes, someday…
>    - The X3D JavaScript SAI implementation need to be designed
>    consistently with the draft X3D JSON encoding. Despite delays in JSON
>    Schema standard, our encoding rules seem quite workable and stable.
>
>
>
>    - X3D to JSON Stylesheet Converter
>    - The X3D to JSON stylesheet converts .x3d XML to .json, supporting
>    the forthcoming JSON Encoding for X3D Graphics.
>    - https://www.web3d.org/x3d/stylesheets/X3dToJson.html
>
>
>
> We explored different techniques for sorting, labeling and updating
> spreadsheet rows and columns.  Probably best approach is to simply sort
> rows on the last tab and compare.
>
>
>
> Congratulations again Doug on FreeWRL browser having greatest reported
> coverage of X3D4 specification!
>
>
>
> We will continue to address guidance for browser and tool implementers
> next week.  Thank you Doug for your excellent start on guidelines!
>
>
>
>    1. We briefly discussed C, C++, C# comments.  We will address these
>    further next week.
>
>
>
>    1. Special thanks to Doug Sanden for quick-turn review of comments on
>       these specifications, also to Vince Marchetti.
>       2. Still TODO: entering concise summaries of all recent C C++ C#
>       comments in Web3D Mantis Issue Tracker.
>       3. Since ISO Draft International Status (DIS) ballot comments are
>       now at editorial stage, all of these comments can be consideredin next
>       round of specification editors’ review.
>       4. Since these drafts are X3D version 3.3,  three New Work Item
>       Proposal (NWIP) documents for 4.0 versions of the C, C++, C# specifications
>       is appropriate for revisions of each.  Those drafts might be prepared after
>       the current revision is complete.
>       5. The Web3D Board of Directors endorsed this effort, and looks
>       forward to continuing progress with X3D 4.0.
>       6. A signficant omission and deficency of the current
>       specifications is that they do not have two or more implementations
>       available.
>       7. Please note that all new specifications must follow Web3D
>       process.  We do not expect further deviations from that policy to be
>       approved, so renewed efforts are needed to build those implementations.
>       TODO add link)
>
>
>
> No Web3D member-confidential information is included in these minutes.
>
>
>
> Thanks everyone for steady progress… another great week for X3D4!  Yes we
> are having fun now.  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 https://
> faculty.nps.edu/brutzman
>
>
>
> *From:* Brutzman, Donald (Don) (CIV)
> *Sent:* Thursday, January 19, 2023 7:25 AM
> *To:* X3D Public Mailing List (x3d-public at web3d.org) <x3d-public at web3d.org
> >
> *Cc:* brutzman at nps.edu
> *Subject:* X3D Working Group agenda 20 JAN 2023: comment review for C,
> C++, C# draft specifications
>
>
>
> We meet at our regular time tomorrow, 0900-1000 pacific Friday 20 JAN.
>
>
>
> First we will briefly review updates to the following important status
> resource, discussing next steps.
>
>    - *Updated.* X3D Node Inventory Comparison
>    <https://www.web3d.org/specifications/X3dNodeInventoryComparison.xlsx>
>     (.pdf
>    <https://www.web3d.org/specifications/X3dNodeInventoryComparison.pdf>)
>    shows node-by-node implementation coverage of the
>    X3D Abstract Specification: validation using X3D Schema, X3D DOCTYPE, and
>    X3D Schematron; X3D Tooltips and VRML97 node sets; plus selected
>    open-source implementations: FreeWrl, X3DOM, X_ITE, view3dscene (Castle
>    Game Engine), X3D-Edit, Xj3D.
>    - https://www.web3d.org/specifications/X3dNodeInventoryComparison.xlsx
>    - https://www.web3d.org/specifications/X3dNodeInventoryComparison.pdf
>
>
>
> Our primary goal is to review all comments on the C, C++, C# draft
> specifications and ensure they are captured appropriately in the Web3D
> Consortium Mantis Issue Tracker. Results will be submitted to ISO.
>
>
>
> All participation is welcome.  Last week’s minutes attached for
> convenience.  Have fun with X3D! 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 https://
> faculty.nps.edu/brutzman
>
>
>
> *From:* Brutzman, Donald (Don) (CIV) brutzman at nps.edu
> *Sent:* Friday, January 13, 2023 10:40 AM
> *To:* X3D Public Mailing List (x3d-public at web3d.org) x3d-public at web3d.org
> *Cc:* Brutzman, Donald (Don) (CIV) brutzman at nps.edu
> *Subject:* X3D Working Group minutes 13 JAN 2023: refined goals, ISO
> specification updates, X3D4 implementation upgrade guidelines?
>
>
>
> Happy Friday 13th everyone!  (bwa ha ha…)
>
>
>
> Today we held our regular weekly meeting of X3D Working Group, Friday 13
> January 2023 at 09-10 pacific.  Connection information and topics follow.
>
>
>
>    -
>    https://us02web.zoom.us/j/81634670698?pwd=a1VPeU5tN01rc21Oa3hScUlHK0Rxdz09
>    - https://zoom.us/j/148206572  Password 483805
>    - https://www.web3d.org/member/teleconference-information
>
>
>
> Attendees: Anita Havele, Nicholas Polys, Dick Puk, Doug Sanden, Don
> Brutzman.
>
>
>
>
>
>    1. *Goal statement review*.  Our primary activities for X3D Working
>    Group in 2023 are focused on broad and correct deployment.  Refined:
>
>
>
>    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.
>
>
>
> The dozen corresponding standards to receive these updates are illustrated
> as follows:
>
>
>
>    - X3D Graphics Standards Relationships
>    -
>    https://web3d.org/specifications/X3dGraphicsStandardsRelationships.png
>
>
>
>
>
>    1. *Milestone: X3D4 Architecture Finalization*.
>
>
>
> Last Tuesday we held a totally successful ISO Editors meeting for X3D4
> Architecture Draft International Specification (DIS).  ISO review and
> approval deliberations continue.
>
>
>
> Today we reviewed progress, changes and next steps following.  Almost
> finally, finally done locking in all details…
>
>
>
>    - X3D4: Extensible 3D (X3D) Part 1: Architecture and base components,
>    ISO/IEC 19775-1:2022
>    -
>    https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-DIS/Part01/Architecture.html
>
>
>
>    - Mantis Issue Tracker
>    - https://www.web3d.org/member-only/mantis/view_all_bug_page.php
>
>
>
> Mantis issues are being updated to track all of the agreed-upon ISO
> changes correctly.
>
>
>
> Given the formally approved list of X3D4 Architecture changes, we can
> finally proceed with document editing.  Next step is to apply CSS-markup
> highlighted changes to the current DIS source for group review.
>
>
>
> Proposed github location for that draft:
>
>
>
>    - Web3D Consortium GitHub Archive
>    - https://github.com/Web3dConsortium
>    -
>    https://github.com/Web3DConsortium/X3D/tree/master/ISO-IEC19775/ISO-IEC19775-1/ISO-IEC19775-1v4.0/ISO-IEC19775-1v4-DIS
>    - ISO-IEC19775-1v4-ProposedIS will be new directory location, eventual
>    rename to “IS” once accepted by ISO
>
>
>
> X3D schema, DTD, X3DUOM, X3DJSAIL updates in progress, so far so good.
> Have applied most validation-related changes.  Initial
> recapitalization/dehyphenization of Web Audio-related enumerations to
> follow.
>
>
>
> Forward thinkers can rest assured that no good ideas regarding X3D
> evolution that didn’t “make the final ISO cut” are getting lost.  All
> future possibilities will continue to be tracked in Mantis and designated
> as future X3D 4.1.
>
>
>
>
>
>    1. *Web3D Review of C, C++, C# draft standards for X3D 3.3.*
>
>
>
> Deadline is imminent, we intend to review all comments next week.  Based
> on that review, X3D Working Group will make a recommendation to Web3D Board
> of Directors regarding Consortium and community inputs on specification
> readiness.
>
>
>
>
>
>    1. *Preparing for Outreach*.
>
>
>
> We discussed how to communicate the soon-to-happen approval of X3D 4.0 by
> ISO, including possible testimonials by members, implementers, authors,
> users, Standards Development Organization (SDO) partners, et al.
>
>
>
> *All testimonial statements are welcome.*  Web3D Consortium Executive
> Director Anita Havele to participate.
>
>
>
>
>
>    1. *X3D Node Inventory Comparison*.
>
>
>
> We took another look at this spreadsheet, let’s prepare to regularly
> update.  Multiple other assets can also be used by implementers to support
> upgrading to X3D4.
>
>
>
>    - X3D Specifications: Schema and DOCTYPE Validation
>    - https://www.web3d.org/specifications
>    - These assets are commonly used for XML validation of X3D scenes, and
>    in-depth documentation is also provided here.
>
>
>
>    - X3D Node Inventory Comparison (.pdf) shows node-by-node
>    implementation coverage of the X3D Abstract Specification: validation using
>    X3D Schema, X3D DOCTYPE, and X3D Schematron; X3D Tooltips and VRML97 node
>    sets; plus selected open-source implementations: FreeWrl, X3DOM, X_ITE,
>    view3dscene (Castle Game Engine), X3D-Edit, Xj3D.
>    - https://www.web3d.org/specifications/X3dNodeInventoryComparison.xslx
>    (master in version control)
>    - https://www.web3d.org/specifications/X3dNodeInventoryComparison.pdf
>    - This will be updated to X3D 4.0 latest, with changes highlighted in
>    yellow
>
>
>
>    - X3D Tooltips 4.0 also highlights all changes in yellow
>    - https://www.web3d.org/x3d/tooltips/X3dTooltips.html
>    - For example, Anchor tooltips:
>    - https://www.web3d.org/x3d/tooltips/X3dTooltips.html#Anchor
>
>
>
>    - The X3D4 Architecture specification itself also reveals specific
>    changes to nodes and fields, from versions 3.0, 3.1, 3.2, 3.3 and 4.0:
>    - X3D4 Architecture, Annex Z, Version Content
>    -
>    https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-DIS/Part01/versionContent.html
>    - For example, looking at Anchor node, you can see in rightmost column
>    that v4.0 adds load, bboxDisplay, autoRefreshTimeLimit etc.
>
>
>
> Suggested: should we create an X3D4 Migration Guide to help implementers?
> Seems like an excellent idea, also “rings true” with our initial goal
> statements today.
>
>
>
> *Volunteers please?  *Creating some form of X3D4 Migration Guide
> checklist to assist implementers might be quite useful.  Also an excellent
> professional opportunity for experts and consultants to demonstrate (and
> upgrade) their expertise.
>
>
>
>
>
>    1. *All other business*.
>
>
>
> Good discussions on download statistics (X3D-Edit, FreeWrl) and a variety
> of other topics... we’re having fun now!
>
>
>
> As ever, many thanks for the work of many contributors.  Deep breath… wow.
>
>
>
> No Web3D member-only information is included in these minutes… but please
> do note: several valuable items documented here have Web3D member-only
> access.
>
>
>
> Consortium membership has value!  *Please consider joining*.
>
>
>
>    - Join the Web3D Consortium
>    - https://www.web3d.org/join
>
>
>
> 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 https://
> faculty.nps.edu/brutzman
>
>
>
>
>
>
>
>
>
> 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 https://
> 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/20230120/5fb7468c/attachment-0001.html>


More information about the x3d-public mailing list