4.2.1
VEOS Licenses
home page

NOTIFICATION

The use of VEOS is restricted by the WTC license.

The Xlisp component of VEOS was written by Niels Mayer and David Betz; Xlisp is copyrighted with a permission to use without restriction.

The VOGL component of VEOS was written by Eric Echidna; VOGL is copyrighted with a permission to use without restriction, however, Eric would appreciate it if you were to send him some beer.

computer code
virtual reality

∆ licenses

links
site structure
Comment without legal training and without recommendation

The WTC license was written in 1992. VEOS was distributed in the public domain in 1992 and 1993 under this license. The license disallows commercial use. It seems to me to be a quite strange license, making code public while maintaining that the source code written by graduate students as part of their degree program is "confidential" and that WTC retains "trade secrecy rights to the source code". Doesn't trade secret mean that something is secret? The license also states that any derivative work belongs to WTC, and it ends by soliciting commercial opportunities.

What is a University program doing with a license that straddles public and commercial usage? In 1992, the status of University generated computer code was not very clear, and the charter of WTC (Washington Technology Center) was to facilitate the growth of business in the State. Perhaps the HIT Lab, which was affiliated with the Industrial Engineering and not the Computer Science Department, was blinded by its own VR hype. When I was asked to find a way to make money from the VEOS code, in order to justify funding the software program at the Lab, I was just astonished!

In any event, the code is of excellent quality, although I'd be hard pressed to identify any "confidential methods" within the code. The methods were published over a decade ago, and to my knowledge, there has been no conscientious effort to maintain or grow the technology.