<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 14 (filtered medium)"><style><!--
/* Font Definitions */
@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";
mso-fareast-language:EN-US;}
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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
.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>Minutes of X3D Schema and DTD Review, Refactoring meeting held 3<sup>rd</sup> August 2015 at 0800 PDT (1500 UTC).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Attendees: Roy Walmsley, Don Brutzman<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>1. <b><u>Siggraph review</u></b><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Don gave a summary review of the Siggraph conference, covering the following topic areas: X3DOM, high performance rendering, profiles, CAD, 3D printing, examples, Schema analysis work by Marc Petit, glTF and binary glTF, shaders and their usage.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>2. <b><u>ComposedCubeMapTexture</u></b><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black;background:white;mso-highlight:white'><a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/env_texture.html#ComposedCubeMapTexture">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/env_texture.html#ComposedCubeMapTexture</a></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It was noted that Don had already agreed and implemented the suggested change, i.e. the failure of the DTD to permit prototypes. Furthermore, he had also fixed similar issues with TextureBackground and ComposedTexture3D. For full details see:<o:p></o:p></p><p class=MsoNormal><a href="http://web3d.org/mailman/private/x3d_web3d.org/2015-August/003467.html">http://web3d.org/mailman/private/x3d_web3d.org/2015-August/003467.html</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>3. <b><u>ComposedShader</u></b><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black;background:white;mso-highlight:white'><a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/shaders.html#ComposedShader">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/shaders.html#ComposedShader</a></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>For full details of comment see:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><a href="http://web3d.org/mailman/private/x3d_web3d.org/2015-August/003465.html">http://web3d.org/mailman/private/x3d_web3d.org/2015-August/003465.html</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>It was agreed that there was a lack of examples to understand the usage of the ComposedShader node, particularly with respect as to how any user defined fields are accessed by child ShaderPart nodes.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>There was also some discussion as to the usage of shader nodes in general. Suggestions arose during Siggraph that shader nodes might be more browser based rather than appearance based. Roy commented that he had used shader nodes in VRML, where shader nodes were inserted into the scene graph before and other geometry or material nodes and then applied to all subsequent geometry. He agreed to post an example to the lists.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Don noted that the ComposedShader node had a <i>language</i> field which would apply to all child ShaderPart nodes. He updated the tooltips to clarify this.<o:p></o:p></span></p><p class=MsoPlainText><a href="http://www.web3d.org/x3d/content/X3dTooltips.html#ComposedShader">http://www.web3d.org/x3d/content/X3dTooltips.html#ComposedShader</a><o:p></o:p></p><p class=MsoPlainText><a href="http://www.web3d.org/x3d/content/X3dTooltips.html#ShaderPart">http://www.web3d.org/x3d/content/X3dTooltips.html#ShaderPart</a><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>It was also noted that the node names were confusing, and some of the text in the specifications not entirely clear. Don raised a specification comment for text in the ShaderPart node, for which Mantis issue 842 was raised.<o:p></o:p></span></p><p class=MsoNormal><a href="http://web3d.org/mailman/private/x3d_web3d.org/2015-August/003469.html">http://web3d.org/mailman/private/x3d_web3d.org/2015-August/003469.html</a><o:p></o:p></p><p class=MsoNormal><a href="http://www.web3d.org/member-only/mantis/view.php?id=842">http://www.web3d.org/member-only/mantis/view.php?id=842</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It was agreed that the definition of the ComposedShader node in the Schema is missing <i>field</i> in the child content model.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It was agreed that in each of the three cases where user defined fields were permitted, i.e. ComposedShader, PackagedShader and ShaderProgram, the <i>field</i> children must come before the standard IS and ChildContentModelCore defined for <i>X3DNode</i>.<o:p></o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black;background:white;mso-highlight:white'><a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/shaders.html#PackagedShader">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/shaders.html#PackagedShader</a></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black;background:white;mso-highlight:white'><a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/shaders.html#ShaderProgram">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/shaders.html#ShaderProgram</a></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The question arose whether these three nodes should be mixed content or not.<o:p></o:p></p><p class=MsoNormal style='text-indent:36.0pt'>ComposedShader definitely is not as it does not have a <i>url</i> field.<o:p></o:p></p><p class=MsoNormal style='text-indent:36.0pt'>PackagedShader has a <i>url</i> field but, in the Schema, is stated to not allow mixed content (i.e. source code instead of a URL).<o:p></o:p></p><p class=MsoNormal style='text-indent:36.0pt'>ProgramShader has a <i>url</i> field, and the Schema states it is allowed mixed content (i.e. source code instead of a URL).<o:p></o:p></p><p class=MsoNormal style='text-indent:36.0pt'><o:p> </o:p></p><p class=MsoNormal>The specification does not comment on this.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It was agreed that further review was required on this topic. Don added a TODO comment to the Schema for each of these three nodes.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Next meeting: No meeting next week due to attendance at ISO SC24 meeting. Next meeting 7<sup>th</sup> September 2015 at 0800 PDT (1500 UTC).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The meeting closed at 1030 PDT (1730 UTC).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Roy<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>PS Subsequent to the meeting it was noted that there is a relevant Mantis issue 432.<o:p></o:p></p><p class=MsoNormal><a href="http://www.web3d.org/member-only/mantis/view.php?id=432">http://www.web3d.org/member-only/mantis/view.php?id=432</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>