[Korea-chapter] [X3D] Agenda items for the Korea chapter meeting (Wed. 5:10pm PST / Thu 9:10am Korea)

[Justin Couch]

Myeong Won Lee wrote:

> It is recommended that this is replaced with the following:
> "It is necessary to convert the units specified in the inlined file into the 
> units in the first file
> by the conversion factor. To be able to compare units specified objects with 
> their relative
> scales is an advantage of using units. Otherwise, the unit statements need not 
> change scenes
> at all, and then they became useless, and give only units information per file 
> like comments."       

Oh gees no! Don't do that! The whole point of a units specification is
to create a real world equivalent for modeling purposes. Units are
absolute, not relative. Make it relative and you'll never be able to
compose worlds together of different scales. If the parent file is in
millimetres and the child file is in kilometres, everything should
render as you expect. If you applied a relative scale the contained file
would look completely wrong.

The specification should be absolutely silent on any concept of
inter-file relationships. All units specifications must be absolute.
And, because they are absolute, all the interfile issues are
automatically resolved without needing any additional spec language.

-- 
Justin Couch                         http://www.vlc.com.au/~justin/
Java Architect & Bit Twiddler              http://www.yumetech.com/
3D Java Graphics Information                    http://www.j3d.org/
-------------------------------------------------------------------
      Programming is essentially a markup language surrounding
      mathematical formulae and thus, should not be patentable.
-------------------------------------------------------------------