<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;}
@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;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
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;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@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:1194075258;
mso-list-type:hybrid;
mso-list-template-ids:1175780860 -354094934 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
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 l0: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 l0: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 l0: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 l0: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 l0: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 l0: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 l0: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 l0: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">
<div class="WordSection1">
<p class="MsoNormal">We are considering Mantis 1173 to add a number of definitions and clarifications to the X3D Architecture specification. This was first proposed in September 2017.<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:l0 level1 lfo1"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:black;background:#F3F3F3">Mantis 1173: Clause 3 Terms, definitions, acronyms, and abbreviations - Definition of
node and statement are insufficient</span><o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1"><a href="https://www.web3d.org/member-only/mantis/view.php?id=1173">https://www.web3d.org/member-only/mantis/view.php?id=1173</a>
<o:p></o:p></li></ul>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Review and any suggested wording improvements are welcome. Absent objects or improvements, we will apply these nonfunctional editorial changes.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><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 clear="all">
<span style="background:#EBEBEB">Subject: Abstract specification definitions of node and statement are insufficient.</span><br clear="all">
<br clear="all">
<span style="background:#EBEBEB">Problem: the abstract specification does not provide clear definitions for nodes and statements, resulting in ambiguous distinctions throughout other sections.</span><br clear="all">
<br clear="all">
<span style="background:#EBEBEB">The current definition for node is vague:</span><br clear="all">
<span style="background:#EBEBEB">"3.1.47 node, fundamental component of a scene graph"</span><br clear="all">
<br clear="all">
<span style="background:#EBEBEB">Suggested definition, improvements welcome:</span><br clear="all">
<span style="background:#EBEBEB">"3.1.47 node, fundamental component of a scene graph that defines information regarding animation, display, geometry, graph structure, interaction, object metadata, or rendering. Nodes are not statements.</span><br clear="all">
<br clear="all">
<span style="background:#EBEBEB">No definition for statement is provided. Suggested:</span><br clear="all">
<span style="background:#EBEBEB">"3.1.70.5, statement, fundamental component of a scene graph that defines document information, version/profile/component support, routing, and other scene-related information. Statements are not nodes.</span><br clear="all">
<br clear="all">
<span style="background:#EBEBEB">Existing usage of note:</span><br clear="all">
<span style="background:#EBEBEB">"3.1.87 X3D file, set of X3D nodes and statements as defined in this part of ISO/IEC 19775"</span><br clear="all">
<br clear="all">
<span style="background:#EBEBEB">Further action needed: Core component defines multiple capabilities requiring X3D statement support. Recommend that support for all X3D statements is included as a requirement in Core component, both in prose and in support
table. For example: "All X3D statements are defined as part of Core component level 1."</span><br clear="all">
<br clear="all">
<span style="background:#EBEBEB">Table 7.2 — Core component support levels</span><br clear="all">
</span><a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/core.html#t-Coresupportlevels"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:royalblue;background:#EBEBEB;text-decoration:none">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/core.html#t-Coresupportlevels</span></a><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:black"><br clear="all">
<span style="background:#EBEBEB">Can add similar table entry "All X3D statements are defined as part of Core component level 1."</span><br clear="all">
<br clear="all">
<span style="background:#EBEBEB">Correction needed:</span><br clear="all">
<span style="background:#EBEBEB">Figure 4.1 — X3D architecture</span><br clear="all">
</span><a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/concepts.html#f-X3DArchitecture"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:royalblue;background:#EBEBEB;text-decoration:none">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/concepts.html#f-X3DArchitecture</span></a><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:black"><br clear="all">
<span style="background:#EBEBEB">"The abstract structure of the sequence of statements that form an X3D world is specified in 7.2.5 Abstract X3D structure."</span><br clear="all">
<span style="background:#EBEBEB">should be modified to read "sequence of nodes and statements that form an X3D world"</span><br clear="all">
<br clear="all">
<span style="background:#EBEBEB">7.2.5 Abstract X3D structure</span><br clear="all">
</span><a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/core.html#AbstractX3DStructure"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:royalblue;background:#EBEBEB;text-decoration:none">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/core.html#AbstractX3DStructure</span></a><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:black"><br clear="all">
<span style="background:#EBEBEB">7.2.5.1 Organization</span><br clear="all">
<span style="background:#EBEBEB">should similarly modify</span><br clear="all">
<span style="background:#EBEBEB">"An X3D world is conceptually defined as a sequence of statements organized conceptually as a file."</span><br clear="all">
<span style="background:#EBEBEB">to say "as a sequence of nodes and statements"</span><br clear="all">
<br clear="all">
<span style="background:#EBEBEB">Needed:</span><br clear="all">
<span style="background:#EBEBEB">"PROTO instances are nodes."</span><br clear="all">
<br clear="all">
<span style="background:#EBEBEB">Suggested:</span><br clear="all">
<span style="background:#EBEBEB">"Comments are neither nodes nor statements."</span><br clear="all">
<br clear="all">
<span style="background:#EBEBEB">This section should also include a paragraph that lists X3D statements, such as</span><br clear="all">
<span style="background:#EBEBEB">"X3D statements include X3D, HEAD, PROFILE, COMPONENT, META, UNIT, Scene, ROUTE, PROTO declare, EXTERNPROTO delare, PROTO interface, PROTO body, field, fieldValue, IS, connect, IMPORT, EXPORT. Syntax and explicit/implicit definition
for these statements can vary among various encodings and language bindings."</span><br clear="all">
<br clear="all">
<span style="background:#EBEBEB">Further review of the abstract specification is warranted to see if other clarifications and corrections are needed.</span><br clear="all">
<br clear="all">
<span style="background:#EBEBEB">Of note is that clear distinction of nodes and statements is also necessary for proper specification of the X3D Unified Object Model.</span><br clear="all">
<br clear="all">
<span style="background:#EBEBEB">These clarifications are not expected to break any existing X3D model content because the existing legacy specification makes no relevant restrictions on use of X3D statements. Similarly, these clarifications do not require
changes (but may inspire improvements) to existing X3D implementations.</span><br clear="all">
<span style="background:#EBEBEB">-----------------</span></span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">all the best, Don<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"">Don Brutzman Naval Postgraduate School, Code USW/Br
<a href="mailto:brutzman@nps.edu"><span style="color:#0563C1">brutzman@nps.edu</span></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
<a href="http://faculty.nps.edu/brutzman"><span style="color:#0563C1">http://faculty.nps.edu/brutzman</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>