<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:Cambria;
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-top:0cm;
margin-right:0cm;
margin-bottom:10.0pt;
margin-left:0cm;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
h1
{mso-style-priority:9;
mso-style-link:"Heading 1 Char";
margin-top:24.0pt;
margin-right:0cm;
margin-bottom:0cm;
margin-left:0cm;
margin-bottom:.0001pt;
line-height:115%;
page-break-after:avoid;
font-size:14.0pt;
font-family:"Cambria","serif";
color:#365F91;
mso-fareast-language:EN-US;}
h2
{mso-style-priority:9;
mso-style-link:"Heading 2 Char";
margin-top:13.5pt;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:15.5pt;
font-family:"Times New Roman","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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-priority:9;
mso-style-link:"Heading 1";
font-family:"Cambria","serif";
color:#365F91;
font-weight:bold;}
span.Heading2Char
{mso-style-name:"Heading 2 Char";
mso-style-priority:9;
mso-style-link:"Heading 2";
font-family:"Times New Roman","serif";
mso-fareast-language:EN-GB;
font-weight:bold;}
.MsoChpDefault
{mso-style-type:export-only;
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><h2 align=center style='text-align:center'>SUBSTANTIVE CHANGES<o:p></o:p></h2><h1><span lang=EN style='mso-fareast-language:EN-GB'>1. X3DMetadataNode<o:p></o:p></span></h1><p class=MsoNormal style='text-align:justify'><span lang=EN style='mso-fareast-language:EN-GB'>There is a single instance of the term X3DMetadataNode in the existing specification in paragraph 7.2.4.3 Integration with X3D worlds.<o:p></o:p></span></p><p class=MsoNormal style='text-align:justify'><span lang=EN style='mso-fareast-language:EN-GB'>The abstract interface X3DMetadataObject is defined as simply being two fields. Note that it has no nodal content as it is not a type derived from X3DNode. It cannot, therefore, be used as the value for a SFNode or MFNode field because these fields are defined, in section 5.3.12, to specify an X3D node.<o:p></o:p></span></p><p class=MsoNormal style='text-align:justify'><span lang=EN style='mso-fareast-language:EN-GB'>The <i>metadata</i> field in all nodes derived from X3DNode is defined as a SFNode field. Thus X3DMetadataObject cannot be the type required. Thus all node definitions throughout the specification are incorrect.<o:p></o:p></span></p><p class=MsoNormal style='text-align:justify'><span lang=EN style='mso-fareast-language:EN-GB'>The solution for this is to define the X3DMetadataNode. This is derived from X3DNode and X3DMetadataObject.<o:p></o:p></span></p><p class=MsoNormal style='text-align:justify'><span lang=EN style='mso-fareast-language:EN-GB'>My changes therefore include the definition of the X3DMetadataNode, references to it in all appropriate places in section 7 and setting it as the required type for the value of all <i>metadata</i> fields.<o:p></o:p></span></p><h1><span lang=EN style='mso-fareast-language:EN-GB'>2. X3DUrlObject<o:p></o:p></span></h1><p class=MsoNormal style='text-align:justify'><span lang=EN style='mso-fareast-language:EN-GB'>This abstract interface is not defined in this section. It is in 9 Networking component. All references have been removed.<o:p></o:p></span></p><h1><span lang=EN style='mso-fareast-language:EN-GB'>3. X3DBindableNode<o:p></o:p></span></h1><p class=MsoNormal style='text-align:justify'><span lang=EN style='mso-fareast-language:EN-GB'>In the list of constructs in 7.2.1 the X3DbindableNode is included as a commonly used interface. It is, however, a base abstract node type. Thus it is more appropriate to include it in the line above.<o:p></o:p></span></p><p class=MsoNormal style='text-align:justify'><span lang=EN style='mso-fareast-language:EN-GB'>In section 7.2.2 the terminology ‘multiply instanced’ has been essentially replaced with ‘multiply referenced instance’ when referring to the DEF/USE syntax in accordance with Comment 01 of mine.<o:p></o:p></span></p><h1><span lang=EN style='mso-fareast-language:EN-GB'>3. Header statement<o:p></o:p></span></h1><p class=MsoNormal style='text-align:justify'><span lang=EN style='mso-fareast-language:EN-GB'>The version number of the standard supported is shown as 3.2. It should be 3.3.<o:p></o:p></span></p><h1><span lang=EN style='mso-fareast-language:EN-GB'>4. PROFILE statement<o:p></o:p></span></h1><p class=MsoNormal style='text-align:justify'><span lang=EN style='mso-fareast-language:EN-GB'>The list of profiles defined in the standard did not include the Medical Interchange profile. This has been added.<o:p></o:p></span></p><h1><span lang=EN style='mso-fareast-language:EN-GB'>5. UNIT statement<o:p></o:p></span></h1><p class=MsoNormal style='text-align:justify'><span lang=EN style='mso-fareast-language:EN-GB'>The unit statement, 7.2.5.5 included discussion of the <conversion_factor> for converting from user defined units to standard base units. There was no definition of how this conversion factor is to be applied. I have added, therefore, an equation to cover this. Does this equation represent the intended method?<o:p></o:p></span></p><h1><span lang=EN style='mso-fareast-language:EN-GB'>6. Support levels<o:p></o:p></span></h1><p class=MsoNormal style='text-align:justify'><span lang=EN style='mso-fareast-language:EN-GB'>The MetadataBoolean node is missing from Table 7.2 – Core component support levels.<o:p></o:p></span></p><h2 align=center style='text-align:center'>TEXTUAL CORRECTIONS<o:p></o:p></h2><h2 style='text-align:justify'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";font-weight:normal'>There were quite a number of simple typographic and grammatical errors that I have corrected. They included some erroneous links. There were also some layout amendments. None of these are substantive.<o:p></o:p></span></h2><h2 align=center style='text-align:center'>ATTACHMENT<o:p></o:p></h2><p class=MsoNormal>Attached to this document is the suggested updated HTML file for the core component.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>