Future Ideas for OpenSim
Combining the idea of distributed grid service with distributed inventory service creates a structure for OpenSim that is similar to the structure of modern web pages where page layout is provided by one server, and page content is provided by another server. Further, we can see that Linden Lab has stifled the growth of Second Life by keeping its structure proprietary. If we can imagine a truly OpenSim not tied to the limits of Second Life there are several clear expansion paths that can be taken.
CSS for OpenSim
One idea is that the three-dimensional markup language for OpenSim be expanded to include its own version of three dimensional CSS. This three-dimensional CSS would include the ability to specify standardized units of dimension per simulation, similar to standard units in real world building trades. More importantly, physical objects could be positioned precisely in three dimensions. With this precise specification and positioning possible, there would then be a direct route to export objects from industry standard three dimensional modeling programs and import these items into OpenSim. If used in this way, OpenSim could be used as tool for effective architectural modeling and fly-through. I can imagine a scenario where buildings could be precisely built in OpenSim and then made available for public review online before they were built in the real world.
Javascript for OpenSim
Currently the scripting language for OpenSim is Second Life’s Linden Scripting Language (LSL). LSL is not only a highly limited scripting language, but it is also non-standard. If there was an OpenSim scripting language that was closer to the JavaScript that most web developers are already familiar with, then industry standard web development tools and libraries could be used, and more sophisticated OpenSim applications could be developed. OpenSim could be developed in the direction of greater business productivity. I imagine that Google Docs could be integrated into OpenSim so that collaborators could use voice, video, and live editing to work on the same document at the same time. In this case, OpenSim would be an integration platform for several existing technologies, which would be facilitated by a more standard scripting platform in OpenSim.
Plug-ins for OpenSim
From almost the beginning, web browsers have been extensible with the use of plug-ins to be able to open non-supported data types. Again, Linden Lab’s failure to keep up with the industry has limited the growth of Second Life. We have seen some browser plug-ins become so common that they have now become industry standard. One such plug-in is Adobe Flash. Now the idea of a scripted graphical Canvas has become so common that it has now been adopted into HTML5 and will supersede the need for both Adobe Flash and Microsoft Silverlight plug-ins. This is one recent demonstration of how HTML has been extended and inspired by the functionality of this plug-in. There are also similar examples for playing audio and video file types. If OpenSim could accept plug-ins, this would allow the broad Internet community to contribute to the expansion of virtual world technology, something again that Linden Lab has intentionally prevented from happening.
Where OpenSim Could Go
Using CSS, improved scripting, and the ability to accept plug-ins have allowed the entire Internet developer community to contribute to the growth of web technology. In time, one can imagine that if OpenSim were not tied to the technology bottleneck of Linden Lab, virtual worlds could eventually become part of the operating system of personal computers, integrating social media from a variety of sources. In time, I can imagine that your friends’ avatars will be able to visit you on your personal computer and walk across the three dimensional space of your virtual desktop.