Virtual world framework

The DoD owns the rights to the source code of the VWF; however, as it is licensed using Apache II, it is freely usable by any and all as long as original attribution is given to the creators.[8]

The framework is licensed under the Apache II license, which essentially states that the user of the software is granted a royalty-free license to use, modify, and sell derivative works of, the software as long as the original license and attribution file(s) are included in the distribution of any and all subsequent works. The original work is licensed "as is" and contains no warranties of any kind.

Content rights are managed via the provisions contained in the Apache 2 license. The current content version control is affected by the primary engineers through github, with the latest stable builds published under unique serial numbers.

The designers are David A. Smith (computer scientist) (Lockheed Martin Chief Innovation Officer – project oversight, design, architecture), David Easter (LM Engineer - Development/Architecture), Richard Boyd (Lockheed Martin Virtual world Labs Chief Architect - governance and ecosystem design), Allison Corey (LM Engineer – development), Scott R. Haynes (LM Engineer - Development), Michael J. Vacirca (LM Engineer - Development), Steven D. Carr (LM Engineer - Development), Cynthia L. Moore (contractor, OSD(P&R) TRS – design, future specs, governance), Carlton Rosengrant OSD(P&R) TRS – overall Program Manager, Frank C. DiGiovanni (Director, OSD(P&R)TRS),[9] Coles/RDECOM (Edge interfacing), Robert Chadwick (ADL – code efficiency and applications), and emerging partners as new functions and libraries are proposed.

VWF is posted on github,[10] and is open to any and all developers who wish to contribute forks, projects, suggestions or build-outs for the framework. The original creators especially seek major platform developers who wish to add interfacing to their platform for use with VWF, such as MMOs, simulations designers, terrain mapping providers, 3D modeling, virtual landscapes, etc. The paper "A Virtual World Ecosystem Framework", presented at the IITSEc conference in 2012, explains the philosophy of contribution to the system.[11]

The VWF is managed via github and developer inputs through a loose consortium of the original creators. In time, the community will stand up a non-profit governing organization, in order to conduct full-time partnerships and version control of the software. Through the use of the latest codecs, interfacing partnerships with major content, object and texture providers, and a persistent location, it is additionally the goal of the creators that VWF will evolve into the standard for interfacing content with users on the web.

The VWF is available for use in web applications, and there are a few minor applications/demonstrations already constructed as proofs of concept.[12] As the community extends the robustness of the VWF, increases the libraries and finalizes the toolkits, these applications will gain in complexity as well. Developers are welcome to construct web applications with the existing code and examples. There is nothing special required to run completed applications outside of having access to a compatible browser with WebGL and potentially web sockets capability depending on the location of the source objects and interactions.

There are many applications available which advertise themselves as Thin Clients or web interfaces. There are no open source development tools in widespread use that interface different entities in a persistent, secure manner using a thin client through web-browsers.[13] While there are many tools available, many of them are highly specialized and require proprietary software installed on both the client and server side. There are still other tools which produce virtual environments, avatars, and content, but none of the ones known tie them together, spontaneously create interfaces among them or provide seamless communications to all of the entities regardless of their timing and without a heavy burden in bandwidth or processing power for the client. VWF does this and will do more as it continues its evolution. VWF utilizes web sockets and WebGL, directly providing a content link between entities and build 3D objects in the quickest, most efficient manner possible. Other virtual interfacing programs utilize Flash which also provides direct content, but does so in a less efficient manner.

VWF information is available on two sites: Virtual World Framework Homepage (mirrored on vwf mirror site) and github (search virtual-world-framework).

VWF can be applied to content to train on most tasks which do not require solely live training. Specifically: Curriculum facilitated through simulations, classroom training, augmented reality, mixed media training, and games are the ideal candidates for VWF. Augmented reality content delivered to classrooms, or augmented additions to mobile devices such as this one Also simulations which combine live training with simulated content are good candidates for VWF. The complexity of the training and the number of trainees largely dictates the date by which this VWF capability will be delivered. For delivery of classroom-type training the VWF is capable of being used to develop content. For simulations-type training, following the persistence and synchronization elements of the VWF being developed in the next 6 months (by fall 2012), this capability of the VWF should be possible. For augmented reality and truly immersive gaming, VWF will be under development with critical partners and hopes to have this capability in the coming 24 months, depending on current technologies and partnerships.

Ideally, VWF will be used in live, virtual, and constructive simulation (LVC) exercises as a primary or secondary delivery mechanism. LVC is ideal for VWF delivery due to its large virtual/digital component and its need to be delivered to myriad audiences in a variety of locations/platforms.

Live objects such as aircraft, weapons and vehicles will pass data to the simulator through sensors (read off of the radar/weapons/sensors on the live equipment directly into the simulation and then the input/output data passed through VWF to the myriad participants), data streaming through interfacing servers (in the case of personnel/equipment trackers such as Blue Force Tracking) and through information injection through constructive simulations (such as placing live units on a map and manually tracking their status/positions).

Simulations do not take place "in" the Virtual World Framework. The VWF is a tool to help interface different entities.[14] constructive simulations, in which simulated people operate simulated systems, are stimulated using human inputs. Ostensibly the VWF would provide the interface (via the web) for some or all of these humans who would be inputting data into the system, then would receive the simulation results from the program executing on the server machine/cloud/locally-determined-host, and would display the results in some fashion via web interface.

Developers use the VWF to build simulations using Java script and functionality provided through the VWF. The VWF generates the appropriate display and manipulation files at the time of compilation. As the VWF develops a construction environment will be developed in order to allow users to drag and drop content and manipulate it, greatly reducing production time/complexity. This environment is under construction, and is anticipated to be completed at the end of 2012.

The web is agnostic to content. The VWF is not secure or unsecure. The use of secure socket layer encryption (SSL), virtual private networks (VPN), public key encryption (PKI), proprietary encryption, hardware secured network systems, etc. provides the security needed to secure any simulations produced and interfaced using the VWF. With the use of IPv6, bit-wise security protocols are available that were previously not available to data transport. A potential additional security method is to add a security bit header to the data transported via VWF in order to provide an additional layer of security. This measure has not yet been added to the current build.

The problem with opening a continuous connection between two computers via a web browser using Web sockets is that it potentially opens up the link to something called cache poisoning, in which someone can directly introduce viruses or other malware to the link, compromising the system.[15] Here is a summary of other weaknesses: Security tool for Web Sockets). Originally, potential security issues led Mozilla and Opera to discontinue support for Web Sockets until the Internet Engineering Task Force (IETF) could produce a standardized Web Sockets protocol as part of HTML5. A work around based on Connect based handshakes (as opposed to upgrade- based handshakes) proved to be secure. The semantics of the handshake as coded into VWF will take this into account. Since late 2011 this has been largely addressed with latest builds and standards, and many web platforms do support Web Sockets.

WebGL (web graphics library) is a JavaScript Application Programming Interface (API) for rendering interactive 3D graphics within any compatible web browser without using plug-ins. WebGL programs include control code (written in Java Script) and shader code which is executed on the graphics processing unit on the video card (GPU). WebGL is designed and maintained by the non-profit Khronos Group.

Mozilla Firefox 6.0 onward, Opera 11 onward, Google Chrome 9 onward (native support), Safari 5.1 onward. So far, Internet Explorer does not support WebGL and has not announced any plans to support WebGL. Chrome Frame and IEWebGL plug-ins support WebGL for IE 6.0 onward.[16]

The WebGL standard is affected by the Khronos Group, Mozilla, Apple and Google along with influence from United States Computer Emergency Readiness Team which raises security concerns to which the WebGL consortium (headed by the Khronos Group) react.[17]

Most PCs, laptops, and tablets support WebGL capable browsers. Mobile support for WebGL is nascent. Expectations are that current mobile bindings for JavaScript and WebGL are not good enough[18] but there is an Android version of Firefox with WebGL (only about 10% of potential users access content via mobile device requiring WebGL support). Opera also supports WebGL on Android platforms. iPhone does not support WebGL yet.

Microsoft does not have plans to support WebGL due to security concerns over handshake vulnerabilities.[19] There are two plug-ins for Internet Explorer which support WebGL interfaces: Chrome Frame and IEWebGL. It is true that native support tends to run better than plug-in support, and not all security organizations will support the installation of additional plug-ins to web browsers.

Java Script is a prototype-based scripting language that is dynamic, weakly typed, general purpose and supports object oriented, imperative, and functional programming styles. This means that JavaScript enables the programmer to build a series of prototypes and interact with them using a mostly literal syntax based on C. Due to its ease of use and widespread appeal, JavaScript quickly became one of the most popular programming languages for web applications.

Java Script runs locally in the browsers, does not require additional plug ins or environments (like the Java runtime environment) to run, and does not require compilation or .exe files to be run on the client machine in order to work. It is faster, more efficient, and simpler to build and execute than both Java and C#.

HTML 5.0, ECMAScript5, WebGL, Web Sockets, Collada (or other later file formats), and others as the tool matures.

Developers can download the latest build of VWF from github and submit their recommendations, code and applications directly on the site. Github allows users to create their own forks, submit pull requests, and leave questions, comments and support related items in the issue tracker.

VWF is available freely and openly on github to any and all persons, regardless of origin. VWF content specifically designed for operations will be negotiated on a case-by-case basis depending on the content, training objectives, and coalition goals being exercised. There is no standing reason why VWF cannot be shared and there are no security restrictions on the original code.[20]

Can commercial entities build services or games with the VWF? Absolutely. The VWF is meant to interface content via the web, but it also contains construction pieces enabling the creation of games or communications services wholly executable within the web browser. VWF is licensed using Apache II, but this allows for a commercial repackaging of the open-source portions as part of a larger work. These games and services would capitalize on the direct link between entities facilitated by the VWF, while the company would determine where the resources were located. For example: A game company might use VWF to create an online game using their proprietary graphics, and store both the graphics and the program files on their own servers while delivering that content through the web; a teleconference company might more efficiently create an e-classroom with the VWF to take their own streaming media codec and pass their video through the web to a digital classroom environment created wholly with the VWF, complete with avatars and interactive objects.

There is a multitude of partners and advisors for the VWF project. There are the creators (mentioned earlier), as well as partnerships with Mark P. McCahill from Duke University, Advanced Distributed Learning (ADL), Doug Maxwell (for MOSES) and Cole Corporation (for the Edge military MMO). All of these personnel provide advisory support to the VWF. The creators encourage additional partnerships meant to expand the scope and scale of VWF.