<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<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 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;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 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:blue;
text-decoration:underline;}
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.EmailStyle23
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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:415128076;
mso-list-template-ids:1860091288;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:534580192;
mso-list-template-ids:8580492;}
@list l1:level1
{mso-level-start-at:3;
mso-level-number-format:alpha-lower;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level4
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level7
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2
{mso-list-id:670379251;
mso-list-template-ids:846218332;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3
{mso-list-id:766000848;
mso-list-template-ids:-771064056;}
@list l3:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level2
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level3
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level5
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level6
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level8
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level9
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l4
{mso-list-id:1239512147;
mso-list-type:hybrid;
mso-list-template-ids:1074551500 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l4:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;}
@list l4:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;}
@list l4: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 l4:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.75in;
text-indent:-.25in;}
@list l4: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 l4: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 l4:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.25in;
text-indent:-.25in;}
@list l4: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 l4: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 l5
{mso-list-id:1583030120;
mso-list-type:hybrid;
mso-list-template-ids:-2050193478 1578647318 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l5:level1
{mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:Calibri;}
@list l5: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 l5: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 l5: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 l5: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 l5: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 l5: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 l5: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 l5: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;}
@list l6
{mso-list-id:1751927918;
mso-list-template-ids:8580492;}
@list l6:level1
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level3
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level4
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level6
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level7
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level9
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7
{mso-list-id:1876308344;
mso-list-type:hybrid;
mso-list-template-ids:1909258698 2011868096 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l7:level1
{mso-level-start-at:9;
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;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l7: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 l7: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 l7: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 l7: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 l7: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 l7: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 l7: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 l7: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;}
@list l8
{mso-list-id:1887451558;
mso-list-type:hybrid;
mso-list-template-ids:-1595759168 -1325788528 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l8: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;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l8: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 l8: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 l8: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 l8: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 l8: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 l8: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 l8: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 l8: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;}
@list l9
{mso-list-id:2126074499;
mso-list-template-ids:8580492;}
@list l9:level1
{mso-level-start-at:2;
mso-level-number-format:alpha-lower;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9:level3
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9:level4
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9:level6
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9:level7
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9:level9
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
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=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Helpful feedback, again thanks Christoph. Responses:<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:l4 level1 lfo8'>Definitely not trying to introduce new concepts. Describing the art of the possible, emphasizing standards for repeatability wherever possible.<o:p></o:p></li><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l4 level1 lfo8'>Concepts used in Stack Layers Alternatives diagram<o:p></o:p></li></ol><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l5 level1 lfo9'>X3D scene is an X3D model that may inline other internal models/media and interact with external resources.<o:p></o:p></li><li class=MsoListParagraph style='margin-left:0in;mso-list:l5 level1 lfo9'>X3D Application is whatever application you might put together that includes X3D model(s).<o:p></o:p></li></ul><p class=MsoNormal style='text-indent:.25in'>This seems like a good match to your expression of the same ideas.<o:p></o:p></p><ol style='margin-top:0in' start=3 type=1><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l4 level1 lfo8'>Agreed with your point; not trying to define a best-practice approach with this, rather trying to illustrate possibilities.<o:p></o:p></li><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l4 level1 lfo8'>Actually, server can provide any of the content identified and is especially useful for production/dissemination of Web-based content (HTML5 CSS JavaScript X3D) in any combination. Such deployment can add server-side mediation or shared state provided via HTML or X3D url calls. So server-side activities might lay behind several of the blocks shown, adding richness.<o:p></o:p></li><li class=MsoListParagraph style='margin-left:-.25in;mso-list:l4 level1 lfo8'>Yes these diagrams are both shared… the working group Stack Layers Alternatives diagram is attempting to show typical design choices available in this fairly complex domain.<o:p></o:p></li></ol><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>These combinations are all so rich and laden with information-driven potential that User Experience (UX) concepts seem appropriate for the most expressive layer at top… am hoping this will also someday inform efforts by Web3D User Experience (Web3DUX) Working Group.<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:l8 level1 lfo10'>Web3D User Experience (Web3DUX) Working Group<o:p></o:p></li><li class=MsoListParagraph style='margin-left:0in;mso-list:l8 level1 lfo10'>https://www.web3d.org/working-groups/web3d-user-experience<o:p></o:p></li><li class=MsoListParagraph style='margin-left:0in;mso-list:l8 level1 lfo10'><i><span style='font-family:"Arial",sans-serif;color:black;background:white'>The Web3DUX working group develops and demonstrates best practices for X3D support of rich user experiences using a variety of Web3D technologies and content-delivery platforms.</span></i><o:p></o:p></li></ul><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Onward we go – have fun with X3D! 8)<o:p></o:p></p><div><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 brutzman@nps.edu<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></div><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> Christoph Valentin <christoph.valentin@gmx.at> <br><b>Sent:</b> Sunday, September 25, 2022 2:05 AM<br><b>To:</b> John Carlson <yottzumm@gmail.com>; Brutzman, Donald (Don) (CIV) <brutzman@nps.edu><br><b>Cc:</b> X3D Public Mailing List (x3d-public@web3d.org) <x3d-public@web3d.org>; Brutzman, Donald (Don) (CIV) <brutzman@nps.edu>; Kevin <klw71@yahoo.com><br><b>Subject:</b> Re: RE: Re: [x3d-public] X3D Working Group meeting 23 SEP 2022: X3D Application Stack Layers Alternatives diagram refinement<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>Good morning,<br><br>Thank you for your feed back.<br><br>Yes, I agree, while "your"*) diagram is a thoroughly compiled list of technologies that are used together with X3D, "my"*) diagram is a rough overview about the possibilities we have at the client implementation of X3D applications.<br><br>May I add a few notes?<br><br>1) I tried to introduce the term "Web3D Browser", which is not (yet) commonly accepted<br><br>2) we should really make a difference between "X3D Scene" and "X3D Application". While X3D scenes should be completely independent of underlying technologies, the X3D application may be "native", "portable" or "web based" (or any combination, depending on which type(s) of Web3D Browsers is/are used/supported by the X3D application)<br><br>3) "My" diagram is a "potential" stack. As far as I know, we don't yet have Web3D Browsers that are (partially) implemented in WASM or based on <a href="https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fnode.js%2F&data=05%7C01%7Cbrutzman%40nps.edu%7C9af7f0ec179b4de705a408da9ed50a20%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637996935216623040%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=VUSk0M6mWE9j6eiKRenFztk0wkMLVxZuAYhyaxsm3%2BM%3D&reserved=0">Node.js</a>.<br><br>4) Neither "your" nor "my" diagram tackles server implementations. Only clients are considered.<br><br>All the best<br>Christoph<br><br>*) i put quotation marks around "your" and "my", because from a philosophical point of view, everything happening on the public list are actually "our" efforts :-)<br><br>--<br>Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.<o:p></o:p></p></div><div><p class=MsoNormal>Am 25.09.22, 01:54 schrieb "Brutzman, Donald (Don) (CIV)" <<a href="mailto:brutzman@nps.edu">brutzman@nps.edu</a>>: <o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:4.8pt;margin-right:0in'><p class=MsoNormal>Christoph, thanks for your efforts and your work on this diagram.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Since there are many ways to put together an application stack that utilizes X3D, we are striving for flexibility.<o:p></o:p></p><p class=MsoNormal><br>Not a goal: mandating a best or recommended practice. That is unhelpful.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Regarding purpose statement, our best phrasing suggested so far is <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:l7 level1 lfo1'>“X3D is interoperable with diverse technologies, providing multiple choices to developers.”<o:p></o:p></li></ul><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Am avoiding a layer for programming languages – there are many, sometimes with several used together, and with different configurations between developers and servers and clients. So including such a layer in a general diagram seems like an unnecessary complication/confusion.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>I hope you think that your diagram has many similarities with this more-general attempt. Vive la difference…<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Hope this helps, have fun with X3D! 8)<o:p></o:p></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>all the best, Don</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>-- </span><o:p></o:p></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></span><o:p></o:p></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</span><o:p></o:p></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</span><o:p></o:p></p></div><p class=MsoNormal> <o:p></o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> Christoph Valentin <<a href="mailto:christoph.valentin@gmx.at">christoph.valentin@gmx.at</a>> <br><b>Sent:</b> Saturday, September 24, 2022 11:16 AM<br><b>To:</b> John Carlson <<a href="mailto:yottzumm@gmail.com">yottzumm@gmail.com</a>>; Brutzman, Donald (Don) (CIV) <<a href="mailto:brutzman@nps.edu">brutzman@nps.edu</a>><br><b>Cc:</b> X3D Public Mailing List (<a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>) <<a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>><br><b>Subject:</b> Aw: Re: [x3d-public] X3D Working Group meeting 23 SEP 2022: X3D Application Stack Layers Alternatives diagram refinement<o:p></o:p></p></div></div><p class=MsoNormal> <span style='font-size:10.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>Hi all together,</span><o:p></o:p></p><div><div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>May I ask one question?</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>What is the purpose of the diagram?</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>I understood the diagram as a help for decision, if someone likes to implement an "X3D Application" and wants to know, which kind of expertise they will need.</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>True?</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>Kr,</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>CP/V</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>P.S.: on the other hand, the diagram I suggested earlier this week, was just a "rough overview for starters", about how X3D fits into any computer system.</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p><div style='border:none;border-left:solid #C3D9E5 1.5pt;padding:0in 0in 0in 8.0pt;margin-left:7.5pt;margin-top:7.5pt;margin-right:3.75pt;margin-bottom:3.75pt;-webkit-nbsp-mode: space;-webkit-line-break: after-white-space'><div style='margin-bottom:7.5pt'><p class=MsoNormal><b><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>Gesendet:</span></b><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> Samstag, 24. September 2022 um 20:05 Uhr<br><b>Von:</b> "John Carlson" <<a href="mailto:yottzumm@gmail.com">yottzumm@gmail.com</a>><br><b>An:</b> "Brutzman, Donald (Don) (CIV)" <<a href="mailto:brutzman@nps.edu">brutzman@nps.edu</a>><br><b>Cc:</b> "X3D Public Mailing List (<a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>)" <<a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>><br><b>Betreff:</b> Re: [x3d-public] X3D Working Group meeting 23 SEP 2022: X3D Application Stack Layers Alternatives diagram refinement</span><o:p></o:p></p></div><div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>More verbs:</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>Require, Design, Implement, Release/Produce/Emit, Consume/Collect.</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>More nouns:</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>Source, Sink</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p><div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>On Sat, Sep 24, 2022 at 1:00 PM John Carlson <<a href="mailto:yottzumm@gmail.com">yottzumm@gmail.com</a>> wrote:</span><o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><div><div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>Perhaps we should focus on Author/Creator, Read/View, Manipulate/Update/Edit/Transform/Convert, Debug/Test, Secure, Compress/Decompress, Publish/Evangelize, Buy/Browse, Sell/Purvey, more verbs. … Archive</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>On all our main classes:</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>Standards, Object Models, Conversion Programs, Worlds, Scenes, Models, Examples, Renderings, Bindings, Encodings, Schemas, Files, Tools/Browsers/Apps/Libraries</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>So on one axis we put verbs, and on other axis we put nouns/classes.</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>I’m not really pushing my way. I think it better demonstrates where work needs to be done.</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>In particular, our standards don’t refer to monetization at all. GNU at least advocates selling support, there’s Patreon, Odysee and 3D model stores.</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>Thanks, Don, for helping get beyond simple CRUD-GR!</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>Woohoo!</span><o:p></o:p></p></div></div></div></div><div><div><div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>John</span><o:p></o:p></p></div></div></div></div><div><div><div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p><div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>On Sat, Sep 24, 2022 at 10:12 AM Brutzman, Donald (Don) (CIV) <<a href="mailto:brutzman@nps.edu">brutzman@nps.edu</a>> wrote:</span><o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>John wrote:</span><o:p></o:p></p><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3 level1 lfo2'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>“Looked at layers and alternative attachment. I’m wondering why there’s two boxes for converting?“</span><o:p></o:p></li></ul><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>Good point. There are two similar concepts I’m trying to distinguish:</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-indent:.5in'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>(a) 3D models can be converted for reuse offline,</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-indent:.5in'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>(b) translator libraries offer programming-library options for applications.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>Attached please find this morning’s update. Added a caption for further explanation:</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2 level1 lfo3'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>“X3D is interoperable with diverse technologies, providing multiple choices to developers.”</span><o:p></o:p></li></ul><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>Complicated territory – does this help describe the many options available with X3D? Am striving for clarity and simplicity, if possible. Hopefully this diagram continues to improve, and might help us show the X3D value propositions more widely, including to Metaverse Standards Forum participants.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>Further review and comment by all is welcome.</span><o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Courier New"'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Courier New"'>all the best, Don</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Courier New"'>-- </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><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></span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Courier New"'>Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Courier New"'>X3D graphics, virtual worlds, Navy robotics https://</span><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><span style='font-size:10.0pt;font-family:"Courier New"'><a href="http://faculty.nps.edu/brutzman">faculty.nps.edu/brutzman</a></span><o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>From:</span></b><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> Brutzman, Donald (Don) (CIV)<br><b>Sent:</b> Friday, September 23, 2022 11:43 AM<br><b>To:</b> X3D Public Mailing List (<a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>) <<a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>><br><b>Cc:</b> <a href="mailto:brutzman@nps.edu">brutzman@nps.edu</a><br><b>Subject:</b> X3D Working Group meeting 23 SEP 2022: Mantis issues review, ballot deadlines, X3D Application Stack Layer Examples diagram</span><o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p><div style='border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>Attendees: Dick Puk, Don Brutzman</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>1. We first reviewed the two recently posted Mantis issues regarding SVG and QIF. We also looked at a Mantis issue posted earlier this year relating to scalable composition of really large X3D worlds. Selected details follow.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p><ol start=1 type=a><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l6 level1 lfo4'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>Mantis </span><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black;background:#F3F3F3'>1400: add Scalable Vector Graphics (SVG) to recommended image formats for ImageTexture</span><o:p></o:p></li></ol><p><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'><a href="https://www.web3d.org/member-only/mantis/view.php?id=1400">https://www.web3d.org/member-only/mantis/view.php?id=1400</a></span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.25in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black;background:#F3F3F3'>SVG references:</span><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'><br><br></span><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black;background:#F3F3F3'>* </span><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'><a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FGraphics%2FSVG&data=05%7C01%7Cbrutzman%40nps.edu%7C9af7f0ec179b4de705a408da9ed50a20%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637996935216623040%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=prkC1PUfDEHZ1b%2BcfuvLU8B%2BOB28FBDhR493xUhuEJ4%3D&reserved=0"><span style='font-size:10.0pt;text-decoration:none'>https://www.w3.org/Graphics/SVG</span></a><br></span><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black;background:#F3F3F3'>* "SVG is a markup language for describing two-dimensional graphics applications and images, and a set of related graphics script interfaces."</span><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'><br><br><span style='background:#F3F3F3'>Dick estimation: thinks SVG is a 2D scene-graph definition language. It can result as an image, though so can X3D.</span><br><br><span style='background:#F3F3F3'>This issue suggests that SVG be listed as a recommended (optional) format that can be rendered as an ImageTexture, using the default presentation settings of the SVG model.</span><br><br><span style='background:#F3F3F3'>Of note is that browsers are not forbidden from implementing SVG as an ImageTexture format, and also that SVG-to-PNG converters are commonplace.</span><br><br><span style='background:#F3F3F3'>Of further note is that the DPS minutes already showed a use case for SVG as ImageTexture, namely conversion of metadata information as a carefully laid-out annotation image that is billboarded in context. Having direct SVG rendering would eliminate the offscreen conversion step, permitting direct integration of X3D models with other HTML/SVG web graphics.</span><br><br><span style='background:#F3F3F3'>Concern: don't want to overcomplicate the existing ImageTexture functionality as a 2D array of pixels. Once generation of pixels becomes a computational process, this is different functionality for the ImageTexture node. This might raise further concerns about impact of ImageTexture computational complexity in various profiles (such as Interchange Profile).</span><br><br><span style='background:#F3F3F3'>Possible alternate: define SvgTexture node? What fields would it have?</span></span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.25in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black;background:#F3F3F3'>Suggested possible resolution:</span><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'><br><br></span><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black;background:#F3F3F3'>a. Browsers are welcome to implement ImageTexture as an allowed url format if they see fit,</span><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'><br><span style='background:#F3F3F3'>b. SvgTexture ought to be designed and considered as a possible new node,</span><br><span style='background:#F3F3F3'>c. ComposedImageTexture (or somesuch) might be designed and considered as an even-more general possibility for comuputational 2D imagery,</span><br><span style='background:#F3F3F3'>d. Following further practical experience, defer any specification-change recommendations to future X3D4.1.</span></span><o:p></o:p></p><div style='border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black;background:#F3F3F3'> </span><o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p><ol start=2 type=a><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l9 level1 lfo5'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>Mantis </span><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black;background:#F3F3F3'>1401: aligning X3D4 LineProperties with Quality Information Framework (QIF) specification</span><o:p></o:p></li></ol><p><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'><a href="https://www.web3d.org/member-only/mantis/view.php?id=1401">https://www.web3d.org/member-only/mantis/view.php?id=1401</a></span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.25in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black;background:#F3F3F3'>Suggested resolution:</span><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'><br><br></span><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black;background:#F3F3F3'>a. The concepts are directly aligned and overlapping, with some additions by QIF.</span><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'><br><span style='background:#F3F3F3'>b. This ISO standard does not appear to have been considered by SC24 or JTC1.</span><br><span style='background:#F3F3F3'>c. Close scrutiny of both terms and definitions needs to be performed before any changes might be recommended.</span><br><span style='background:#F3F3F3'>d. If changes are indeed warranted and acceptable, then they likely need to first considered as part of the Registry of Items, specifically entries for linestyle and hatchstyle.</span><br><span style='background:#F3F3F3'>e. At that point, amendment of X3D to stay aligned with Registry of Items (or possibly add further styles independently) can be considered.</span><br><span style='background:#F3F3F3'>f. Defer to X3D 4.1.</span><br><br><span style='background:#F3F3F3'>Meanwhile note in Web3D current ballot comments the need to fix the table erratum previously noted.</span></span><o:p></o:p></p><div style='border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p><ol start=3 type=a><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo6'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>Mantis </span><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black;background:#F3F3F3'>1192: 07.2.2 Bindable children nodes - Undefined results if bindable node is under Switch or LOD is problematic</span><o:p></o:p></li></ol><p><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'><a href="https://www.web3d.org/member-only/mantis/view.php?id=1192#bugnotes">https://www.web3d.org/member-only/mantis/view.php?id=1192#bugnotes</a></span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p><div style='border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black;background:#EBEBEB'>Comment on 19775-1: Abstract X3D Definitions - V3.3</span><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'><br></span><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black;background:#EBEBEB'>7.2.2 Bindable children nodes</span><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'><br><a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/core.html#BindableChildrenNodes"><span style='font-size:10.0pt;background:#EBEBEB;text-decoration:none'>http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/core.html#BindableChildrenNodes</span></a><br><br></span><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black;background:#EBEBEB'>-----------------</span><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'><br><span style='background:#EBEBEB'>Subject: Undefined results if bindable node is under Switch or LOD is problematic</span><br><br><span style='background:#EBEBEB'>Spec sayeth:</span><br><span style='background:#EBEBEB'>"The results are undefined if a bindable node is bound and is the child of an LOD, Switch, or any node or prototype that disables its children."</span><br><br><span style='background:#EBEBEB'>This leads to all manner of inconsistent problems among scenes. It also means that Inline node (which may or may not include bindable nodes) has undefined behavior under LOD/Switch/etc.</span><br><br><span style='background:#EBEBEB'>As a result, in addition to indeterminate X3D browser behavior, it means that X3D scenes are not fully composable. That is contrary to X3D design objectives.</span><br><br><span style='background:#EBEBEB'>Different prose and deterministic guidelines is needed in this section that provides clear rules for binding/unbinding nodes when they become active within LOD/Switch/etc. Small adaptations to current binding rules can likely address this problem satisfactorily.</span><br><br><span style='background:#EBEBEB'>Related: Mantis issue 749</span></span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black;background:#EBEBEB'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black;background:#EBEBEB'>April 29:</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black;background:#F3F3F3'>Analysis during X3D Working Group call:</span><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'><br><br></span><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black;background:#F3F3F3'>a. Switch would keep each binding stack aligned with whichever child was active, thereby binding and unbinding nodes whenever the Switch level is modified.</span><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'><br><br><span style='background:#F3F3F3'>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.</span><br><br><span style='background:#F3F3F3'>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).</span><br><br><span style='background:#F3F3F3'>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.</span><br><br><span style='background:#F3F3F3'>Spec editors work on integrating these principles as specification prose (we are close already) and report back recommended changes to X3D working group.</span><br><br><span style='background:#F3F3F3'>Don's opinion: 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.</span></span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black;background:#EBEBEB'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black;background:#EBEBEB'>Today’s session.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black;background:#EBEBEB'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black;background:#F3F3F3'>Alternatives deserving working-review consensus:</span><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'><br><br></span><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black;background:#F3F3F3'>a. Recommending this clarification of undefined prior specification prose might add important value, or might be construed as a technical change to X3D4.0 that possibly requires future re-balloting as another X3D 4.0 DIS (which is not an acceptable outcome).</span><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'><br><br><span style='background:#F3F3F3'>b. If not balloted then this becomes an X3D4.1 issue.</span><br><br><span style='background:#F3F3F3'>c. Web3D might consider some alternative approach to strongly encourage adoption of this clarified approach in order to further encourage greater scalability of multi-world environments, and better alignment with shared Metaverse design imperatives. For example, are we creating a Best Practices Pending X3D 4.1 Approval document of some sort?</span></span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>2. We only have 4 total issues to review as planned Web3D comments. This will occur during a single working-group meeting, 7 OCT.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>Deadline for X3D Ballot comments:</span><o:p></o:p></p><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo7'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>OCT, Web3D comments to INCITS (U.S. National Standards Body</span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo7'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>TBD OCT, INCITS comments to SC24</span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo7'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>4 NOV, SC24 comments to ISO</span><o:p></o:p></li></ul><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>No meeting currently planned for 30 SEP.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>3. Bonus round: we worked on the “layer” diagram from recent meetings a bit more. Latest X3dApplicationStackLayerExamples is attached, all comments welcome.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>Have fun with X3D!</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Courier New"'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Courier New"'>all the best, Don</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Courier New"'>-- </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><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></span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Courier New"'>Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Courier New"'>X3D graphics, virtual worlds, Navy robotics https://</span><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><span style='font-size:10.0pt;font-family:"Courier New"'><a href="http://faculty.nps.edu/brutzman">faculty.nps.edu/brutzman</a></span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'> </span><o:p></o:p></p></div></div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>_______________________________________________<br>x3d-public mailing list<br><a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a><br><a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a></span><o:p></o:p></p></blockquote></div></div></div></div></div></blockquote></div></div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana",sans-serif'>_______________________________________________ x3d-public mailing list <a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a> <a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a></span><o:p></o:p></p></div></div></div></div></div></div></blockquote></div></div></div></body></html>