allowing Java to manipulate MHEG objects in its mother application. Though the MHEG-6 was not extended, it was the basis for the DAVIC's (Digital Audio Video Council) standard. DAVIC This standard was created a little later on after the MHEG-6 in 1998. It was created by adding a new series of APIs for Java to MHEG's sixth version. The APIs of the above-mentioned standard allowed the Java-created objects access to some information services, as well as control of audio and video services, and the management of resources in the receiver. Though the creation of an application was not possible with Java alone for the receiver DAVIC, the Java APIs were already capable of controlling more elements in the receiver than what was possible with other standards. DVB-MHP (The Multimedia Home Platform) This was defined by the Digital Video Broadcasting (DVB) to offer interactive services in digital television (DTV). It is a limited version of the Java virtual machine, where a set of extra functionalities are added to make adjustments to the DTV environment. To arrange this standard's specifications, there are three definable profiles, all relating to the capabilities of the STBs: 1. Interactive Broadcast: incorporates bidirectional communications via a backward IP channel towards the STB, allowing the download of applications. 2. Enhanced Broadcast Profile: interactive applications are downloaded via broadcasting. This does not incorporate a backward channel into the STB. 3. Internet Access: The STB itself processes internet content, without broadcasting. There exist two versions that cover the mentioned profiles: MHP 1.0 covers the first two profiles. This version is used most by modern receivers, and the majority implement the Interactive Broadcast profile. Many countries such as Spain, Italy and Finland have adopted it into their DTV's interactive services. MHP 1.1 covers all three profiles, but it is not found in most commercial receivers because there are limited compatible protocols. OCAP The American company CableLabs collaborated with DVB for the creation of a new open standard, which led to the acceptance of MHP as a base for OCAP standard (OpenCable Application Platform), in January of 2002. With MHP as its center, OCAP provides a common specification for the middleware layer in the cable systems within the United States. Since DVB standards are not used in the United States, OCAP is based on parts that are not DVB-specific, replacing DVB-specific parts with others. Originally, OCAP was based on the 1.0.0 version