<HTML><HEAD>
<META content="MSHTML 6.00.6000.16939" name=GENERATOR>
<STYLE>P {
MARGIN: 5px 0px
}
</STYLE>
<META content=NPIKPYWHEE name=SKYPE_FRAMEID></HEAD>
<BODY style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 250">
<P>Dear Alan,</P>
<P> </P>
<P>>Myeong Won Lee wrote: <BR>>> 3. Physical units specification (Myeong Won Lee, The University of Suwon) <BR>>> <BR>>> The unit browser is being modified from the previous Physical node definition to <BR>>> the UNIT statements. There were contradictions in the email discussion of the <BR>>> X3D WG. We must decide amongst the following when determining which criteria <BR>>> should be applied in the implementation of the length units: <BR>>> <BR>>> (1) Length units are defined but do not affect the visual scene at all where <BR>>> there is no scaling. They transfer length units information only. In this case, <BR>>> we cannot compare differences in real length when two X3D objects designed <BR>>> separately are read into a scene using an inline node or by reading two X3D <BR>>> files together in a scene. There is no difference at all in the scene compared <BR>>> with no unit definition. <BR>>> <BR>>this makes no sense, whats the purpose of length units then. </P>
<P> </P>
<P>I agree with some of your statement, but there does exist some difference. For example, consider two X3D files. One is referencing a 1 cm X3D object. The other is referencing a 1 meter X3D object. In the display, 1 cm and 1 m objects may appear to be the same size when only one of them is displayed at a time, or if they are imported into the same scene one after the other. In this case, applications know their real sizes from the units-specified file although their relative scaling cannot be estimated in the display. </P>
<P>We may, however, avoid this misinterpretation depending on a way to recognize units. </P>
<P>In other words, this case does not have merit for browsers per se, but does have merit when transferring real-sized 3D objects between applications.</P>
<P> </P>
<P>>> (2) Length units are defined and do not scale objects when reading an X3D file, <BR>>> but relative scales are used when reading two units-specified X3D files together <BR>>> in a scene using inline nodes or by importing another unit X3D file. We must not <BR>>> scale objects when reading an X3D file because we cannot see the scaled objects <BR>>> of very large and small objects such as those of astronomical and microorganism <BR>>> size. It is desirable to use the same units in X3D files when it is necessary to <BR>>> have relative scales. <BR>>> <BR>>the easiest implementation of units would be a transform that changes <BR>>any non meter speced files into meters with an implicit transform that <BR>>the top of the file. </P>
<P> </P>
<P>If we transform any unit into meter every time, we may get scenes with invisible objects. For example, if we try to display a 1 km X3D object, the browser may transform it into 1000 m one, 1000 multiplication and we cannot see the object in the scene. This is inappropriate. Rather, it is better that the browser displays it as the same, i.e. 1000, but knows its unit is km.</P>
<P> </P>
<P>>Are you suggesting thats not a legal implementation? A browser can do <BR>>better if it detects that all files are the same units or that all files <BR>>are really small(ie then everything might get transformed to millimeters). <BR>><BR>> But you can't force that type of smart implementation on a browser. <BR>>Just converting everything to meters must be legal. <BR>><BR>>You language about "do no scale units when reading an x3d file" makes no <BR>>sense to me. Its one valid implementation. </P>
<P> </P>
<P>Here is another example that converting everything to meters may result in scenes with invisible objects. Consider that a designer created a bacteria using the micrometer unit. The designer may use 1 1 1 coordinates for the bacteria. If converting to meters, then we have 0.000001 0.000001 0.000001 coordinates and we cannot see the bacteria in the display. </P>
<P>Therefore, I would like to suggest "do not scale units when reading an x3d file in a scene". However, relative scaling is convenient if two or more x3d files are imported in a scene because<BR>then we can easily see the size difference between objects in the scene.</P>
<P>In summary, by putting units in an x3d file, browsers recognize coordinates defined by the units (1 1 1 coordinates and cm together, not converted to meter) browsers do not transform scaling for the units when reading the x3d file.</P>
<P>Does this make sense?</P>
<P><BR>Sincerely,</P>
<P> </P>
<P>Myeong Won Lee<BR></P>
<DIV> </DIV>
<BLOCKQUOTE style="PADDING-LEFT: 8px; MARGIN: 0px; BORDER-LEFT: black 2px solid">
<DIV style="COLOR: black; LINE-HEIGHT: 140%">---- Original Message ----<BR></DIV>
<DIV style="COLOR: black"><B>From : </B>Alan Hudson(giles@yumetech.com)<BR></DIV>
<DIV style="COLOR: black; LINE-HEIGHT: 140%"><B>To : </B>Myeong Won Lee(mwlee@suwon.ac.kr)<BR></DIV>
<DIV style="COLOR: black; LINE-HEIGHT: 140%"><B>Cc : </B>korea-chapter@web3d.org; x3d@web3d.org<BR></DIV>
<DIV style="COLOR: black; LINE-HEIGHT: 140%"><B>Sent : </B>Thursday, Nov 12, 2009 01:47 AM<BR></DIV>
<DIV style="COLOR: black; LINE-HEIGHT: 140%"><B>Subject : </B>Re: [X3D] Agenda items for the Korea chapter meeting (Wed. 5:10pm PST / Thu 10:10am Korea)<BR></DIV><BR>Myeong Won Lee wrote: <BR><BR>> 3. Physical units specification (Myeong Won Lee, The University of Suwon) <BR><BR>> <BR><BR>> The unit browser is being modified from the previous Physical node definition to <BR><BR>> the UNIT statements. There were contradictions in the email discussion of the <BR><BR>> X3D WG. We must decide amongst the following when determining which criteria <BR><BR>> should be applied in the implementation of the length units: <BR><BR>> <BR><BR>> (1) Length units are defined but do not affect the visual scene at all where <BR><BR>> there is no scaling. They transfer length units information only. In this case, <BR><BR>> we cannot compare differences in real length when two X3D objects designed <BR><BR>> separately are read into a scene using an inline node or by reading two X3D <BR><BR>> files together in a scene. There is no difference at all in the scene compared <BR><BR>> with no unit definition. <BR><BR>> <BR><BR>this makes no sense, whats the purpose of length units then. <BR><BR><BR><BR>> (2) Length units are defined and do not scale objects when reading an X3D file, <BR><BR>> but relative scales are used when reading two units-specified X3D files together <BR><BR>> in a scene using inline nodes or by importing another unit X3D file. We must not <BR><BR>> scale objects when reading an X3D file because we cannot see the scaled objects <BR><BR>> of very large and small objects such as those of astronomical and microorganism <BR><BR>> size. It is desirable to use the same units in X3D files when it is necessary to <BR><BR>> have relative scales. <BR><BR>> <BR><BR>the easiest implementation of units would be a transform that changes <BR><BR>any non meter speced files into meters with an implicit transform that <BR><BR>the top of the file. <BR><BR><BR><BR>Are you suggesting thats not a legal implementation? A browser can do <BR><BR>better if it detects that all files are the same units or that all files <BR><BR>are really small(ie then everything might get transformed to millimeters). <BR><BR><BR><BR>But you can't force that type of smart implementation on a browser. <BR><BR>Just converting everything to meters must be legal. <BR><BR><BR><BR>You language about "do no scale units when reading an x3d file" makes no <BR><BR>sense to me. Its one valid implementation. <BR><BR><BR><BR>-- <BR><BR>Alan Hudson <BR><BR><BR><BR>President Yumetech, Inc. www.yumetech.com <BR><BR>President Web3D Consortium www.web3d.org <BR><BR>206 340 8900 ext 111 <BR><BR><BR><BR>Open Source CAN be free, as in "free puppy"</BLOCKQUOTE>-- <BR>Myeong Won Lee <BR>Dept. of Internet Information Engineering, U. of Suwon <BR>Hwasung-si, Gyeonggi-do, 445-743 Korea <BR>Tel) +82-31-220-2313, +82-11-9904-4634 <BR>E-mail) mwlee@suwon.ac.kr
<!-- Mail Slogan Start -->
<!-- Mail Slogan End -->
</BODY></HTML><img width=0 height=0 src="http://mail.suwon.ac.kr/mail/rcptcheck.html/eVWZqUzNjY0/LdBbCJqamRsZ/5c_jsrW3ObKwlrE0sDg6sjkgu7IxmTIXtzmz/foo.gif">