<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle22
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
span.proposed
{mso-style-name:proposed;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1302425246;
mso-list-type:hybrid;
mso-list-template-ids:-253188192 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:1.25in;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.75in;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:2.75in;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.25in;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.75in;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:4.25in;
text-indent:-9.0pt;}
@list l1
{mso-list-id:1635476494;
mso-list-type:hybrid;
mso-list-template-ids:-2023208714 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Attendees: Anita Havele, Nicholas Polys, Don Brutzman. Regrets: Dick Puk. We worked together for 2 hours today, minutes follow.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><ol style='margin-top:0in' start=1 type=1><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l0 level1 lfo2'>Web3D 2022 Call for Papers<o:p></o:p></li></ol><p class=MsoNormal><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'>https://www.web3d.org/news-story/web3d-2022-call-papers<o:p></o:p></li></ul><p class=MsoListParagraph style='margin-left:.25in'><o:p> </o:p></p><ol style='margin-top:0in' start=2 type=1><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l0 level1 lfo2'>We discussed upcoming conference this fall.<o:p></o:p></li></ol><p class=MsoListParagraph><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'>13<sup>th</sup> 3DBODY.TECH Conference & Expo<o:p></o:p></li><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'>https://www.3dbody.tech<o:p></o:p></li><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'>The Premier Multidisciplinary International Conference and Exhibition on 3D Human Body Scanning and Processing Technologies<o:p></o:p></li><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'>3DBODY.TECH Conference & Expo provides a platform of eminent professionals, entrepreneurs, academicians and researchers across the globe to present, learn and discuss the latest in 3D human body scanning and processing technologies. The multidisciplinary character of 3DBODY.TECH makes it unique and not comparable to any other meeting related to 3D body technologies.<o:p></o:p></li></ul><p class=MsoListParagraph><o:p> </o:p></p><p class=MsoNormal>Of interest is that this immediately precedes Web3D Conference.<o:p></o:p></p><div style='mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal style='border:none;padding:0in'><o:p> </o:p></p></div><p class=MsoNormal><o:p> </o:p></p><ol style='margin-top:0in' start=3 type=1><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l0 level1 lfo2'>ISO, INCITS H3 and W3C liaison: weekly issues check.<o:p></o:p></li></ol><p class=MsoListParagraph style='margin-left:0in'><o:p> </o:p></p><p class=MsoListParagraph style='margin-left:0in'>Interesting draft work is proceeding on Guidelines for Representation and Visualization of Smart Cities.<o:p></o:p></p><p class=MsoListParagraph style='margin-left:0in'><o:p> </o:p></p><p class=MsoListParagraph style='margin-left:0in'>We are engaged in this effort and encouraging use of structured data and X3D visualization across several dozen ISO standards, motivated so that Smart Cities might have a coherent basis for information presentation and interaction. Much lead-in work was performed at workshops and in papers at the past two Web3D Conferences.<o:p></o:p></p><p class=MsoListParagraph style='margin-left:0in'><o:p> </o:p></p><p class=MsoListParagraph style='margin-left:0in'>Abstract. “Developers and users of any smart city will need tools to evaluate and examine options and trade-offs, and predict outcomes. Parts or all of a smart city would need to be modelled, and smart city functions need to be simulated to evaluate possible results. The modelling and simulation of smart city functions relies on representation and visualization of the data. Representation and visualization of smart cities will enable prototyping, demonstration, and analysis of smart city concepts for further development. Both physical/geometric and semantic data will need to be represented and visualized.”<o:p></o:p></p><p class=MsoListParagraph style='margin-left:0in'><o:p> </o:p></p><p class=MsoListParagraph style='margin-left:0in'>“Representation and visualization of smart cities is a prime application for an integrated approach to leverage standardization since no single standard will address all requirements. This document provides guidelines as to what needs to be represented for smart cities and how this can be achieved. This technical specification will define categories of data associated with smart cities, and the requirements for their representation and visualization. It will describe how ISO/IEC JTC 1/SC 24 standards including SEDRIS and X3D can be applied to represent and visualize urban infrastructure, services, and features. Use cases are presented that explore how these standards could be applied in smart city analysis and visualization applications.”<o:p></o:p></p><div style='mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in'><p class=MsoListParagraph style='margin-left:0in;border:none;padding:0in'><o:p> </o:p></p></div><p class=MsoListParagraph style='margin-left:0in'><o:p> </o:p></p><p class=MsoListParagraph style='margin-left:0in'>Web3D Consortium members can request a copy of this document and comment, if they like. We will be voting prior to May 11.<o:p></o:p></p><p class=MsoListParagraph style='margin-left:0in'><o:p> </o:p></p><p class=MsoListParagraph style='margin-left:0in'>Web3D membership has value! Please join, if you haven’t already.<o:p></o:p></p><p class=MsoListParagraph style='margin-left:0in'><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'>https://www.web3d.org/join<o:p></o:p></li></ul><div style='mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal style='border:none;padding:0in'><o:p> </o:p></p></div><p class=MsoNormal><o:p> </o:p></p><ol style='margin-top:0in' start=4 type=1><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l0 level1 lfo2'>Dick and I had a big 2-week review, resolving or improving over 60 Mantis issues. Change list for 19-28 April is attached.<o:p></o:p></li></ol><p class=MsoListParagraph><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'>Web3D Mantis Issue List<o:p></o:p></li><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'>https://www.web3d.org/member-only/mantis/view_all_bug_page.php<o:p></o:p></li></ul><p class=MsoListParagraph><o:p> </o:p></p><p class=MsoNormal>Several issues have been pushed to the list requesting comment. About 50 additional issues remain… the finish line is almost visible!<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>During the call, we will work towards achieving consensus on a handful of lingering discussion issues. All inputs are welcome.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'>X3D4 Architecture, latest<o:p></o:p></li><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'>https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/Architecture.html<o:p></o:p></li></ul><div style='mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal style='border:none;padding:0in'><o:p> </o:p></p></div><p class=MsoNormal><o:p> </o:p></p><ol style='margin-top:0in' start=4 type=1><ol style='margin-top:0in' start=1 type=a><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l0 level2 lfo2'>We reviewed Michalis Kamburelis message<o:p></o:p></li></ol></ol><p class=MsoNormal><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'>[x3d-public] ambientIntensity [0, 1] or unbounded [0, infinity) ?<o:p></o:p></li><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'>http://web3d.org/pipermail/x3d-public_web3d.org/2022-April/017278.html<o:p></o:p></li></ul><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>regarding<o:p></o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'>Mantis 130: 17.2.2: Lighting Max Values<o:p></o:p></li><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'>https://www.web3d.org/member-only/mantis/view.php?id=130<o:p></o:p></li></ul><p class=MsoNormal><o:p> </o:p></p><pre><span style='font-family:"Calibri",sans-serif'>We agreed on rationale for his first proposed solution:<o:p></o:p></span></pre><pre><span style='font-family:"Calibri",sans-serif'>“</span>1. Ignore, i.e. leave ambientIntensity in [0,1]. Just because <o:p></o:p></pre><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'> there's no practical reason to change it.”<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks for another great response Michalis.<o:p></o:p></p><div style='mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal style='border:none;padding:0in'><o:p> </o:p></p></div><p class=MsoListParagraph style='margin-left:.75in'><o:p> </o:p></p><ol style='margin-top:0in' start=4 type=1><ol style='margin-top:0in' start=2 type=a><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l0 level2 lfo2'>We worked to ensure that authors rendering points, lines or UnlitMaterial geometry include emissive values.<o:p></o:p></li></ol></ol><p class=MsoNormal><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'>1347: UnlitMaterial emissiveColor has incorrect default value? no, must remain 1 1 1, modify X3DOneSidedMaterialNode<o:p></o:p></li><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'>https://www.web3d.org/member-only/mantis/view.php?id=1347<o:p></o:p></li></ul><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Confirmed reasonableness of removing emissiveColor from X3DOneSidedMaterialNode so that no overrides are necessary for differing default values. This is a common X3D design practice.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Some wording improvements for clarity:<o:p></o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'>12.3.4 X3DOneSidedMaterialNode<o:p></o:p></li><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'>https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/shape.html#X3DOneSidedMaterialNode<o:p></o:p></li><li style='mso-list:l1 level1 lfo1'><span class=proposed><span style='background:yellow;mso-highlight:yellow'>The <i>emissiveColor</i> field is defined in implementing nodes (albeit with differing default values).</span></span> The <i>emissiveColor</i> <span class=proposed><span style='background:yellow;mso-highlight:yellow'>and <i>emissiveTexture</i> fields enable an author</span></span> to model "glowing" objects. This can be useful for displaying unlit (pre-lit) models (where the light energy of the room is computed explicitly), or for displaying scientific data. <span class=proposed><span style='background:yellow;mso-highlight:yellow'>Application of emissive color values has an essential role when rendering points (PointSet), lines (LineSet and IndexedLineSet), and geometry rendered with unlit materi</span>als.</span> To display an "unlit" object (whose visible color should not be modified by any light in the scene), <span class=proposed><span style='background:yellow;mso-highlight:yellow'>an</span></span> author can use <span class=proposed><span style='background:yellow;mso-highlight:yellow'>an</span></span> UnlitMaterial node.<o:p></o:p></li><li style='mso-list:l1 level1 lfo1'>The <i>emissiveTexture</i> RGB channel is multiplied with the <i>emissiveColor</i> to yield the <i>emissiveParameter</i> in the lighting equations. <span class=proposed><span style='background:yellow;mso-highlight:yellow'>Further information is provided in 11.2.2.5 Points and lines rendering.</span></span> <o:p></o:p></li></ul><p class=MsoNormal>Also included improvements to <o:p></o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'>X3D4 Architecture, 11.2.2.5 Points and lines rendering<o:p></o:p></li><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'>https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/rendering.html#PointsLinesRendering<o:p></o:p></li><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'><span class=proposed><span style='background:yellow;mso-highlight:yellow'>Emissive colors are primary means of rendering these nodes. The <i>emissiveColor</i> and fields typically control these "glowing" effects. Failure to include emissive colors may result in these geometry nodes not being rendered.</span></span><span style='background:yellow;mso-highlight:yellow'><o:p></o:p></span></li></ul><div style='mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal style='border:none;padding:0in'><o:p> </o:p></p></div><p class=MsoNormal><o:p> </o:p></p><ol style='margin-top:0in' start=4 type=1><ol style='margin-top:0in' start=3 type=a><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l0 level2 lfo2'>We discussed inclusion of markerType providing symbology for point displays, deciding against.<o:p></o:p></li></ol></ol><p class=MsoNormal><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'>Mantis 1393: 12.4.7 PointProperties missing markerType field<o:p></o:p></li><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'>https://www.web3d.org/member-only/mantis/view.php?id=1393<o:p></o:p></li></ul><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-left:.25in'><span style='background:silver;mso-highlight:silver'>Nicholas thinks that old markerType values are pretty ancient and not useful, further that browser builders are unlikely to implement them. Modelers want their own icon/glyph/splat for visualization and interaction.<br><br>Of further note is that markerType values do not have any existing implementations, not meeting our "2 implementations" requirement. There is a risk of it being counterproductive and distracting efforts in this direction.<br><br></span><o:p></o:p></p><p class=MsoNormal style='margin-left:.25in'><span style='background:silver;mso-highlight:silver'>Downside to removal is small: if markerType not added, then no such mechanism exists until X3D4.1 (when it is likely to get resolved fully). Meanwhile experimentation is welcome, the "X" in X3D is Extensible.<br><br>Dick please confirm: we are removing.<br><br>Nicholas please get 1-2 Mantis issues added describing how to proceed, there may be one partial issue on glyphs already.</span><o:p></o:p></p><div style='mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal style='border:none;padding:0in'><o:p> </o:p></p></div><p class=MsoNormal><o:p> </o:p></p><ol style='margin-top:0in' start=4 type=1><ol style='margin-top:0in' start=4 type=a><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l0 level2 lfo2'>We worked further on improvements to Switch and LOD when a descendant node is bound. Currently such behavior is undefined.<o:p></o:p></li></ol></ol><p class=MsoNormal><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'>Mantis 1192: 07.2.2 Bindable children nodes - Undefined results if bindable node is under Switch or LOD is problematic<o:p></o:p></li><li class=MsoListParagraph style='margin-left:0in;mso-list:l1 level1 lfo1'>https://www.web3d.org/member-only/mantis/view.php?id=1192<o:p></o:p></li></ul><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='background:silver;mso-highlight:silver'>Analysis during X3D Working Group call:<br><br>a. Switch would keep each binding stack aligned with whichever child was active, thereby binding and unbinding nodes whenever the Switch level is modified.<br><br>b. LOD would have all of its child bindable nodes on the binding stack throughout, so that user experience was consistent. For example, it would make no sense for Viewpoints to get arbitrarily unbound and bound, based on range to viewer, as a user independently navigated through a scene.<br><br>c. LOD attempting to maintain author intent has access to all Viewpoint nodes on binding stack, and range-to-viewer LOD transitions are either flexible suggestions (browser-optimization control) or rigidly enforced (forceTransitions field is TRUE). Thus if a node is subsequently bound by user in a different inactive LOD child branch, then that binding event is honored and that LOD child branch becomes the active child branch. This binding event (and changed LOD child branch selection) takes precedence over browser range/performance considerations, and also takes precedence over whatever value is provided in forceTransitions field. (Example: selecting a room Viewpoint while in a large building model).<br><br>d. NavigationInfo, Background and Fog binding stacks and responses to binding events should behave identically to Viewpoint. Variations would be exceedingly complex and not understandable. Consistency means that author intent and user action always take precedence, for Switch and LOD response.<br><br>Spec editors work on integrating these principles as specification prose (we are close already) and report back recommended changes to X3D working group</span>.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>IMO this will significantly help user-sensible scalability of huge (perhaps Metaverse-scale) models using many Inline and prototype nodes, enabling predictable and performant navigation and traversal throughout.<o:p></o:p></p><div style='mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal style='border:none;padding:0in'><o:p> </o:p></p></div><p class=MsoNormal><o:p> </o:p></p><ol style='margin-top:0in' start=5 type=1><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l0 level1 lfo2'>Endgame plan for X3D4 Architecture specification.:<o:p></o:p></li></ol><p class=MsoNormal><o:p> </o:p></p><ol style='margin-top:0in' start=5 type=1><ol style='margin-top:0in' start=1 type=a><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l0 level2 lfo2'>The next few weeks are good for final member + public review.<o:p></o:p></li><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l0 level2 lfo2'>We will continue resolving editorial Mantis issues, deliberately at best speed.<o:p></o:p></li><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l0 level2 lfo2'>Unfinished/undemonstrated functional issues are marked as X3D4.1 for future work.<o:p></o:p></li><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l0 level2 lfo2'>We expect to submit Draft International Specification (DIS) during last half of May, around 2-3 weeks from now.<o:p></o:p></li></ol></ol><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Vince, please confirm this plan aligns with our Consortium bylaws and practices documents. Thanks in advance for making sure we don’t overlook any steps.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Anita please supervise any formal ascertainment by Board and Membership, as needed.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks for all contributions and all progress, getting Extensible 3D (X3D) Graphics version 4 finally ready to ship.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Have fun with X3D! 8)<o:p></o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>all the best, Don<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>-- <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>Don Brutzman Naval Postgraduate School, Code USW/Br <a href="mailto:brutzman@nps.edu">brutzman@nps.edu</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>X3D graphics, virtual worlds, Navy robotics https://</span> <span style='font-size:10.0pt;font-family:"Courier New"'>faculty.nps.edu/brutzman<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>