<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=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@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:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></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-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Hi Andreas,<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>I have checked and can tell you that this issue has already been noted. For reference it is Mantis issue 916. This comment was:<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>-------------------------------------<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Subject: misnamed nodes and incorrect field in support table<br><br>1. "X3DVolumeNode" needs to corrected as "X3DVolumeDataNode"<br><br>2. "CompositeVolumeStyle" (entry in level 3) needs to corrected as "ComposedVolumeStyle".<br><br>3. ComposedVolumeStyle entry at level 3 indicates: "ordered field is always treated as FALSE. All other fields fully supported."<br><br>However there is no "ordered" field, and so this line should be rewritten as "All fields fully supported."<span style='mso-fareast-language:EN-US'><o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>-------------------------------------<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>All three of the points noted will be corrected as submitted.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>There are no current plans to introduce an ‘ordered’ field. If you think that is desirable, then it would be appropriate to raise a specification comment.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>All the best,<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Roy<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><b><span lang=EN-US>From:</span></b><span lang=EN-US> x3d-public [mailto:x3d-public-bounces@web3d.org] <b>On Behalf Of </b>Andreas Plesch<br><b>Sent:</b> 10 January 2018 18:01<br><b>To:</b> X3D Graphics public mailing list <x3d-public@web3d.org><br><b>Subject:</b> [x3d-public] Volume rendering spec.<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><div><p style='margin:0cm;margin-bottom:.0001pt'><span style='font-family:"Arial",sans-serif'>Before I submit a spec. comment I would like to explore if there are more appropriate resolutions to the following issues:</span><o:p></o:p></p><p style='margin:0cm;margin-bottom:.0001pt'><o:p> </o:p></p><p style='margin:0cm;margin-bottom:.0001pt'><span style='font-family:"Arial",sans-serif'>Table 41.7 ( <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/volume.html#t-supportlevels">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/volume.html#t-supportlevels</a> ) lists CompositeVolumeStyle in level 3. However, a style with this name is not defined in the Volume Rendering component. There is a ComposedVolumeStyle but this style is a level 2 style in the table.</span><o:p></o:p></p><p style='margin:0cm;margin-bottom:.0001pt'><o:p> </o:p></p><p style='margin:0cm;margin-bottom:.0001pt'><span style='font-family:"Arial",sans-serif'>A proposed resolution is to remove the row which lists CompositeVolumeStyle from Table 41.7</span><o:p></o:p></p><p class=MsoNormal><br><span style='font-family:"Arial",sans-serif'>Table 41.7 refers to an ordered field in the support column for ComposedVolumeStyle. However, the node signature at section 41.4.4 ( <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/volume.html#ComposedVolumeStyle">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/volume.html#ComposedVolumeStyle</a> ) does not have an ordered field.</span><o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='font-family:"Arial",sans-serif'>A proposed resolution is to replace the comment in the support column for ComposedVolumeStyle with 'All fields fully supported'.</span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='font-family:"Arial",sans-serif'>Alternatively, it is possible that there used to be an ordered field and that it should be reintroduced. Then level 3 would support this field.</span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='font-family:"Arial",sans-serif'>Andreas</span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div></div></body></html>