Figure 1 Hyperworx Platform Technical Disclosure [ Figure 1 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 Hyperworx Conceptual Diagram Hyperworx embodies a useful process and a methodology for packaging software intellectual property (System Inputs) in a form that can be subsequently used by the non-obvious Hyperworx machinery (Mechanism) to automate the manufacturing of software applications (System Output) in a manner that is a useful improvement of current methods of software application composition. Operating System Platform (e.g. Microsoft Windows, Linux, Mac OSX…) Hardware Platform (e.g. Intel, AMD, or IBM… CPU-based server or workstation) System Inputs Useful process + methodology for preparing inputs for the machinery System Outputs Useful improvement of current software application composition methodologies Mechanism Non-obvious machinery for manufacturing software applications XML-encoded Hyperworx CSDL-format specification files Platform/OS-native binary-format Hyperworx plug-in database (Hyperworx HyperPack modules) Platform/OS-native binary-format Hyperworx software application Platform/OS-native custom software application runtime memory image

Figure 2 Hyperworx Platform Technical Disclosure [ Figure 2 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 Hyperworx System Inputs Overview Useful process + methodology for preparing inputs for the machinery Hyperworx Component Software Description Language (CSDL) XML schema-compliant documents XML-encoded Portable Model Library (PML) documents(s) XML-encoded Portable Application Specification (PAS) document(s) XML-encoded Platform Binding Map (PBM) document(s) XML-encoded Semantic Binding Map (SBM) documents(s) XML-encoded Persistent Application Data (PAD) document(s) Platform/OS-specific ANSI C++ compiler installation Hyperworx HyperPack SDK (ANSI C++ library) Platform/OS-native Hyperworx HyperPack binary plug-in module Software algorithmsData structures Hyperworx binary HyperPack plug-in module creation methodology

Figure 3 Hyperworx Platform Technical Disclosure [ Figure 3 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 Hyperworx Mechanism Overview For more in-depth information, consult the large multi-page printouts. Non-obvious machinery for manufacturing software applications Hyperworx Platform packaged and deployed as a single, integrated binary software application Hyperworx Graphical User Interface View System Hyperworx Core (“Protein” Library) Virtual Machine Assembly Subsystem Virtual Machine Analysis Subsystem Virtual Machine Loader Subsystem Virtual Machine Runtime Dispatch Subsystem Plug-In Package Database Subsystem OS Platform Services Subsystem Plug-In Package Development Kit Model Librarian Subsystem Application Specification Subsystem XML Services Subsystem User Interface View Controller Subsystem Hyperworx Core State Machine Subsystem

Figure 4 Hyperworx Platform Technical Disclosure [ Figure 4 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 Hyperworx System Output Overview Useful improvement of current software application composition methodologies

Figure 5 Hyperworx Platform Technical Disclosure [ Figure 5 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 Hyperworx Deployed As a Software Development Tool Hardware Platform (e.g. Intel®-based workstation or server) Operating System Platform (e.g. Windows®, Linux)Hyperworx deployed as a single, integrated binary software application Full Hyperworx Graphical User Interface Hyperworx Core (“Protein” Library) HyperPack Plug- In Package Development Kit ANSI Standard C++ Compiler HyperPack Plug-In Packages Custom Algorithms and Logic Transforms CSDL-Encoded Model and Specification Files Hyperworx deployed as a stand-alone server Hyperworx Core (“Protein” Library)

Figure 6 Hyperworx Platform Technical Disclosure [ Figure 6 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 Hyperworx Deployed As a Software IP Syndication Platform Hardware Platform (e.g. Intel®-based workstation or server) Operating System Platform (e.g. Windows®, Linux) Commoditized Hyperworx System Input HyperPack binary plug- in packages CSDL-format software model kits Hyperworx deployed as a single, integrated binary software application Reduced Feature (Simplified) Hyperworx Graphical User Interface Hyperworx Core (“Protein” Library)

Figure 7 Hyperworx Platform Technical Disclosure [ Figure 7 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 Hyperworx Deployed As a Generic Application Server Hardware Platform (e.g. Intel®-based workstation or server) Operating System Platform (e.g. Windows®, Linux) Hyperworx Core “Protein” Library Linked Into Generic Application Server Binary Hyperworx Core (“Protein” Library) Network Transport Subsystem HyperPack binary plug- in packages Library of installed HyperPack Plug-In Packages XML-encoded service request (including the specification of the application to service the request) Request results returned in XML-format LAN/WAN/Internet Transaction

Figure 8 Hyperworx Platform Technical Disclosure [ Figure 8 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 Hyperworx’ Circuit Metaphor :: Example Hardware System All data can be thought of as signals. The hardware device shown above is a signal processing system that performs some logical processing on a set of data input signals in order to produce some set of data output signals. Generally speaking, the specific transformation of data input signals to data output signals in a hardware-based signal processing system is a function of the specific hardware components and the manner in which they are interconnected. Platform Data Input / Output User-Accessible Data Input / Output Private Data Input / Output Configuration Option Fixed-Function Logic Device Clock Signal Source Socket Mechanism Variable-Function Logic Device An Example Hardware-Based Signal Processing System

Figure 9 Hyperworx Platform Technical Disclosure [ Figure 9 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 Hyperworx’ Circuit Metaphor :: Changing the Labels For the purposes of discussing a software application’s architecture and composition, it is useful to draw analogies between hardware-based signal processing systems and software-based signal processing systems. This is valid because at a high level of abstraction hardware and software-based signal processing systems perform identically: both perform some logical processing on a set of input signals to produce a set of output signals. Input / Output to the Operating System Services Software Application User Interface Input / Output to Other Software Applications Software Application Build / Deploy Options A Fixed-Function Software Algorithm Packaged as a Re-Usable Component Asynchronous Data Source Polymorphic Software Subsystem Interface Specification Customizable Software Algorithm Packaged as a Re-Usable Component A Relabeled Hardware-Based Signal Processing System

Figure 10 Hyperworx Platform Technical Disclosure [ Figure 10 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 Hyperworx’ Circuit Metaphor :: Mathematical Graph Models In electrical engineering, digital hardware circuits are typically modeled as mathematical graphs in which the vertices represent discrete logic transforms and the edges represent interconnection wires. Similarly, software applications can be modeled using mathematical graphs in which the vertices represent software components and the edges represent interconnection protocols between the software components. Software Application Software Component Software Component Software Component Software Component Software Component Software Component Software Component Software Component Software Component Software Component Software Component

Figure 11 Hyperworx Platform Technical Disclosure [ Figure 11 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 Hyperworx Binary Plug-In Architecture Binary Plug-In Package Plug-In Entity FactoryIntrospection Interface Binary Type Handler Plug-In Introspection Interface Design Engineer-Supplied Data Structure Type Handler Binary Filter Plug-In Design Engineer- Supplied Algorithm Data Inputs Data Outputs Runtime InterfaceIntrospection InterfaceFilter Binary Plug-In Package Hyperworx Core Plug-In Package Database Subsystem Virtual Machine Loader Subsystem

Figure 12 Hyperworx Platform Technical Disclosure [ Figure 12 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 Hyperworx Binary Type and Pin Handler Plug-Ins Pin Handler Instantiation Interface Runtime Interface Multi-Context Table of Type Handler Data Structures UUID Type Handler Friendly Name String Description String UUID Pin Handler Introspection Interface Type Handler UUID Type Handler UUID Handler Revision Handler Revision Friendly Name String Description String Author String Copyright String License String Introspection Interface Data Structure

Figure 13 Hyperworx Platform Technical Disclosure [ Figure 13 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 Hyperworx Binary Filter Plug-Ins Filter UUID Filter UUID Filter Revision Filter Revision Friendly Name String Description String Author String Copyright String License String Introspection Interface Binary Pin Map Runtime Interface Design Engineer- Supplied Algorithm Binary Pin Map Pin Handler … Design-Engineer Supplied Algorithm

Figure 14 Hyperworx Platform Technical Disclosure [ Figure 14 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 HYP :: Hyperworx Binary Plug-In Package Binary Plug-In Package UUID Package UUID Package Revis. Package Revision Friendly Name String Description String Author String Copyright String License String Introspection Interface Plug-In Entity Factory Filter Type Handler Pin Handler

Figure 15 Hyperworx Platform Technical Disclosure [ Figure 15 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 PBM :: Hyperworx Platform Binding Map Binary Type Handler Plug-In Alias Map UUID Type Handler UUID Handler Revision UUID Type Handler Alias UUID Handler Revision UUID Type Handler UUID Type Handler Alias Binary Filter Plug-In Alias Map UUID Filter Alias UUID Filter UUID Filter RevisionUUID Filter UUID Filter RevisionUUID Filter Alias Binary Type Handler Plug-In Alias Map UUID Filter Pin AliasUUID Filter PinUUID Filter Pin AliasUUID Filter PinPlatform Binding Map Binary Type Handler Plug-In Alias Map Binary Filter Plug-In Alias Map Binary Filter Plug-In Pin Alias Map UUID Binding Map UUID Binding Map Revision Binding Map Revision Friendly Name String Description String Author String Copyright String License String Internal Data Structures XML Encoding

Figure 16 Hyperworx Platform Technical Disclosure [ Figure 16 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 PBM :: Hyperworx Platform Binding Map XML Skeleton Platform Binding Map Binary Type Handler Plug-In Alias Map Binary Filter Plug-In Alias Map Binary Filter Plug-In Pin Alias Map UUID Binding Map UUID Binding Map Revision Binding Map Revision Friendly Name String Description String Author String Copyright String License String CB21EAE9-147C-4e69-9FC3-9E95885FAE FB AB32-66A5D80DBAB Sample Platform Binding Map XML Skeleton File This file shows the basic form of an PBM XML document Encapsule Systems, Inc. Map copyright notice inserted here Map license terms inserted here 456B764E-3F7B-413f-861B-876DA7D98FD BE24-4fe6-A F 1C418F B0D7-26D88CA03ACE D5E450A3-0C F65EA070FD 3F413DCB ae-992D-BCA246E B4CB DC4-B9746BC59F49

Figure 17 Hyperworx Platform Technical Disclosure [ Figure 17 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 PML :: Hyperworx Portable Model Library Portable Model Library Header Entities Type Descriptor Manifest Processor Descriptor Manifest Socket Descriptor Manifest Module Descriptor Manifest Bus Descriptor Manifest Visualization Primitive Manifest Header Entities UUID Model Library UUID Model Library Revision Model Library Revision Friendly Name String Description String Author String Copyright String License String Visualization Primitive Manifest Polygon Descriptors Type Descriptor Manifest Entity Type Descriptors Processor Descriptor Manifest Processor Descriptors Socket Descriptor Manifest Socket Descriptors Module Descriptor Manifest Module Descriptors Bus Descriptor Manifest Bus Descriptors

Figure 18 Hyperworx Platform Technical Disclosure [ Figure 18 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 PML :: Portable Model Library XML Skeleton CB21EAE9-147C-4e69-9FC3-9E95885FAE FB AB32-66A5D80DBAB Sample Portable Model Library XML Skeleton File This file shows the basic form of an XPML document Encapsule Systems, Inc. Library copyright notice inserted here Library license terms inserted here … Portable Model Library Header Entities Type Descriptor Manifest Processor Descriptor Manifest Socket Descriptor Manifest Module Descriptor Manifest Bus Descriptor Manifest Visualization Primitive Manifest

Figure 19 Hyperworx Platform Technical Disclosure [ Figure 19 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 PML :: Visualization Primitives Entity <!-- currently this mechanism only supports 2-dimensional polygonal shapes. we plan to extend this mechanism to support the specification of 3-dimensional volumes, and 2D scaleable bitmap images to support advanced visualization options in the Hyperworx user interface --> 3CB DE0-4a14-85B0-64C8D06D7F06 Square Portable Model Library Header Entities Type Descriptor Manifest Processor Descriptor Manifest Socket Descriptor Manifest Module Descriptor Manifest Bus Descriptor Manifest Visualization Primitive Manifest

Figure 20 Hyperworx Platform Technical Disclosure [ Figure 20 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 PML :: Type Descriptor Entity Binary Type Handler Plug-In UUID Type Handler UUID Handler Revision Platform Binding Map Binary Type Handler Plug-In Alias Map UUID Type Handler UUID Handler Revision UUID Type Handler Alias UUID Handler Revision UUID Type Handler UUID Type Handler Alias Acme Inc. Sales Order Data F9090C61-A8BD-4e96-97F8-A86FC1D924B9 1C418F B0D7-26D88CA03ACE Portable Model Library Header Entities Type Descriptor Manifest Processor Descriptor Manifest Socket Descriptor Manifest Module Descriptor Manifest Bus Descriptor Manifest Visualization Primitive Manifest

Figure 21 Hyperworx Platform Technical Disclosure [ Figure 21 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 PML :: Pins and Pin Descriptor Entities Source and Sink Pins Sink Pin data flow Source Pin data flow All pins are associated with a specific data type Pin Connections Type A SourceType B Sink data flow Source pin drives data to sink pin(s) Type A SourceType A Sink Pins must be associated with the same data type A Source pin can drive an arbitrary number of compatible sink pins Example Type A Source Pin 258D872C-416A-4ddc-B30E-7CEA24A98BF1 F9090C61-A8BD-4e96-97F8-A86FC1D924B9 Example Type A Sink Pin 9F0BD98F-0B D9-4195A7CE7C4C F9090C61-A8BD-4e96-97F8-A86FC1D924B9 Example Type A Filter Source Pin BA5FDCB A7ED-9C967284A605 F9090C61-A8BD-4e96-97F8-A86FC1D924B9 7FBC49EB-D2DC-45b6-B9EE-88718A09FD82

Figure 22 Hyperworx Platform Technical Disclosure [ Figure 22 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 Example Processor Descriptor Insert some descriptive text here E ED74-4bd8-A1E9-0FC0305A5518 Example Type A Sink Pin E633695A-D319-4bca-B304-C7EC2C66D093 F9090C61-A8BD-4e96-97F8-A86FC1D924B9 579F1398-EBC3-4d51-AF7A-B2DA35EF1542 Contant Value Type A Sink Pin B74C5041-0F6D-4de4-9D9E-6EC49B F9090C61-A8BD-4e96-97F8-A86FC1D924B9 69BDFD af-8750-B5D13F8FCE84 Example Type A Source Pin F6AA52E3-DACF-47ae-8A3C-C64E45D63D05 F9090C61-A8BD-4e96-97F8-A86FC1D924B9 7FBC49EB-D2DC-45b6-B9EE-88718A09FD82 PML :: Processor Descriptor Entity Processor Descriptor Platform Binding Map Binary Filter Plug-In Portable Model Library Header Entities Type Descriptor Manifest Processor Descriptor Manifest Socket Descriptor Manifest Module Descriptor Manifest Bus Descriptor Manifest Visualization Primitive Manifest

Figure 23 Hyperworx Platform Technical Disclosure [ Figure 23 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 PML :: Socket Descriptor Entity Socket Outer context Inner context Example Socket Descriptor EA1-4e FE9E5 3CB DE0-4a14-85B0-64C8D06D7F06 Example Type A Sink Pin 24A62E61-23E8-48b6-BA77-B DBA F9090C61-A8BD-4e96-97F8-A86FC1D924B9 Example Type A Source Pin CEB6C7C f-943C-8D06DB6CE461 F9090C61-A8BD-4e96-97F8-A86FC1D924B9 Portable Model Library Header Entities Type Descriptor Manifest Processor Descriptor Manifest Socket Descriptor Manifest Module Descriptor Manifest Bus Descriptor Manifest Visualization Primitive Manifest

Figure 24 Hyperworx Platform Technical Disclosure [ Figure 24 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 PML :: Module Descriptor Entity Portable Model Library Header Entities Type Descriptor Manifest Processor Descriptor Manifest Socket Descriptor Manifest Module Descriptor Manifest Bus Descriptor Manifest Visualization Primitive Manifest Modules comprise: A set of zero or more outer context pins A set of zero or more inner context processors A set of zero or more inner context sockets A set of inner context pin connections (depicted as black lines in the figure) Module Processor Socket Processor Socket Inner context Outer context

Figure 25 Hyperworx Platform Technical Disclosure [ Figure 25 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 PML :: Module Descriptor Entity XML Skeleton Portable Model Library Header Entities Type Descriptor Manifest Processor Descriptor Manifest Socket Descriptor Manifest Module Descriptor Manifest Bus Descriptor Manifest Visualization Primitive Manifest Example Module Descriptor Insert some description of the module here 78F758E2-C e-96C6-13FA2051B0CB … … … … …

Figure 26 Hyperworx Platform Technical Disclosure [ Figure 26 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 PML :: Module Descriptor Visualization Portable Model Library Header Entities Type Descriptor Manifest Processor Descriptor Manifest Socket Descriptor Manifest Module Descriptor Manifest Bus Descriptor Manifest Visualization Primitive Manifest Example Module Descriptor Insert some description of the module here 78F758E2-C e-96C6-13FA2051B0CB <!-- we plan to extend this general mechanism to allow 2D icons to be filled with scaleable bitmaps (as opposed to single color), and to allow modules to be represented using 3D volumes and textures. These extensions of the existing mechanism should be claimed as they represent the basis for an entirely new type of of user interface that allows the user to manipulate objects in 3D space in order to build a software specification --> 3CB DE0-4a14-85B0-64C8D06D7F06 0xFF0000 … … … … Module as it will be visualized in the user interface (assumes no subsocket declarations)

Figure 27 Hyperworx Platform Technical Disclosure [ Figure 27 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 PML:: Module Descriptor Pin Manifest Entity Portable Model Library Header Entities Type Descriptor Manifest Processor Descriptor Manifest Socket Descriptor Manifest Module Descriptor Manifest Bus Descriptor Manifest Visualization Primitive Manifest Example Module Descriptor Insert some description of the module here 78F758E2-C e-96C6-13FA2051B0CB … Example Type A Sink Pin C42D8E1C-7AA B01F-C F0F F9090C61-A8BD-4e96-97F8-A86FC1D924B9 Example Type A Source Pin 200D00EF-CE29-49f9-958C-C888DF44FBE2 F9090C61-A8BD-4e96-97F8-A86FC1D924B9 … … … Module Outer context sink pins Outer context source pins

Figure 28 Hyperworx Platform Technical Disclosure [ Figure 28 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 PML:: Module Descriptor Subprocessor Manifest Entity Portable Model Library Header Entities Type Descriptor Manifest Processor Descriptor Manifest Socket Descriptor Manifest Module Descriptor Manifest Bus Descriptor Manifest Visualization Primitive Manifest Example Module Descriptor Insert some description of the module here 78F758E2-C e-96C6-13FA2051B0CB … … E ED74-4bd8-A1E9-0FC0305A5518 <!-- UUID assigned to this specific instance of the processor identified above. This provides a mechanism for differentiating between multiple processors declared in the module’s inner context that may have the the same UUID --> 56E3090D-3BCF-4a AA1AEA9B2CE5 … … ModuleProcessor Inner context

Figure 29 Hyperworx Platform Technical Disclosure [ Figure 29 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 PML:: Module Descriptor Subsocket Manifest Entity Portable Model Library Header Entities Type Descriptor Manifest Processor Descriptor Manifest Socket Descriptor Manifest Module Descriptor Manifest Bus Descriptor Manifest Visualization Primitive Manifest Module Socket Inner context Example Module Descriptor Insert some description of the module here 78F758E2-C e-96C6-13FA2051B0CB … … … EA1-4e FE9E5 981A5683-BBA A60D-7EAF9CC …

Figure 30 Hyperworx Platform Technical Disclosure [ Figure 30 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 PML:: Module Descriptor Pin Connection Manifest Portable Model Library Header Entities Type Descriptor Manifest Processor Descriptor Manifest Socket Descriptor Manifest Module Descriptor Manifest Bus Descriptor Manifest Visualization Primitive Manifest Example Module Descriptor Insert some description of the module here 78F758E2-C e-96C6-13FA2051B0CB … C42D8E1C-7AA B01F-C F0F CEB6C7C f-943C-8D06DB6CE A5683-BBA A60D-7EAF9CC91618

Figure 31 Hyperworx Platform Technical Disclosure [ Figure 31 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 PML :: Module Descriptor Intramodule Pin Connection Rules DATA SOURCE (TAIL) LEGAL DATA SINK (HEAD) CONNECTIONS EXPLANATION Module Sink Pin (data flowing into module from outer context) Module Source Pin Processor Sink Pin Socket Source Pin Module input drives module output directly Module input drives processor input Module input drives socket output Module Source Pin (data flowing out of module from inner context) – INVALID DATA SOURCE NO LEGAL CONNECTION Module output can’t be assigned as the source of an internal connection Processor Sink Pin (data flowing into processor from outer context) – INVALID DATA SOURCE NO LEGAL CONNECTION Processor input can’t be assigned as the source of an internal connection Processor Source Pin (data flowing out of processor from inner context) Module Source Pin Processor Sink Pin Socket Source Pin Processor output drives module output Processor output drives another processor’s input Processor output drives socket output Socket Sink Pin (data flowing out of socket from inner context) Module Source Pin Processor Sink Pin Socket Source Pin Socket input drives module output Socket input drives processor input Socket input drives another socket’s output Socket Source Pin (data flowing into socket from outer context) – INVALID DATA SOURCE NO LEGAL CONNECTION Socket output can’t be assigned as the source of an internal connection

Figure 32 Hyperworx Platform Technical Disclosure [ Figure 32 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 PML :: Bus Connection Manifest Entity Portable Model Library Header Entities Type Descriptor Manifest Processor Descriptor Manifest Socket Descriptor Manifest Module Descriptor Manifest Bus Descriptor Manifest Visualization Primitive Manifest Outer context Socket Outer context Module Example Socket / Module Bus Descriptor B870ED5E-66CD-411d-BEBB-D4697BFABEA EA1-4e FE9E5 78F758E2-C e-96C6-13FA2051B0CB CEB6C7C f-943C-8D06DB6CE461 C42D8E1C-7AA B01F-C F0F Inner context

Figure 33 Hyperworx Platform Technical Disclosure [ Figure 33 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 SBM :: Hyperworx Semantic Binding Map Semantic Binding Map PML Module Alias Map PML Socket Alias Map UUID Binding Map UUID Binding Map Revision Binding Map Revision Friendly Name String Description String Author String Copyright String License String XML Encoding PML Socket Alias Map UUID Socket AliasUUID SocketUUID Socket AliasUUID Socket PML Module Alias Map UUID Module UUID Module AliasUUID Module UUID Module Alias UUID Module Subsocket Instance Alias Set PML Module Subsocket Instance Alias Map UUID Module Subsocket Instance Alias UUID Module Subsocket Instance UUID Module Subsocket Instance Alias UUID Module Subsocket Instance Internal Data Structures

Figure 34 Hyperworx Platform Technical Disclosure [ Figure 34 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 SBM :: Semantic Binding Map XML Skeleton 0CCCE44D-2F1D-42c9-AB FB5F1 6D66A B9BA-7D65AB90777B 1 8 Sample Semantic Binding Map XML Skeleton File This file shows the basic form of an SBM XML document Encapsule Systems, Inc. Map copyright notice inserted here Map license terms inserted here … Semantic Binding Map PML Module Alias Map PML Socket Alias Map Header Entities

Figure 35 Hyperworx Platform Technical Disclosure [ Figure 35 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 SBM :: Module Alias Map Entity 78F758E2-C e-96C6-13FA2051B0CB B4B2-4cb7-B341-E642579F4ED9 981A5683-BBA A60D-7EAF9CC BA111F6-AB75-497d-A615-FA435A … Semantic Binding Map PML Module Alias Map PML Socket Alias Map Header Entities

Figure 36 Hyperworx Platform Technical Disclosure [ Figure 36 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 SBM :: Module Subsocket Alias Map Entity … EA1-4e FE9E5 60BE31E2-60BC-4a09-B9EA-D172194B289F Semantic Binding Map PML Module Alias Map PML Socket Alias Map Header Entities

Figure 37 Hyperworx Platform Technical Disclosure [ Figure 37 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 PAS :: Hyperworx Portable Application Specification

Figure 38 Hyperworx Platform Technical Disclosure [ Figure 38 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 PAS :: Header Entities

Figure 39 Hyperworx Platform Technical Disclosure [ Figure 39 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 PAS :: Module Manifest Entity

Figure 40 Hyperworx Platform Technical Disclosure [ Figure 40 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 PPD :: Hyperworx Persistent Pin Data

Figure 41 Hyperworx Platform Technical Disclosure [ Figure 41 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 Hyperworx Core (“Protein” Library) High-Level Block Diagram Hyperworx Platform packaged and deployed as a single, integrated binary software application Hyperworx Graphical User Interface View System Hyperworx Core (“Protein” Library) Virtual Machine Assembly Subsystem Virtual Machine Analysis Subsystem Virtual Machine Loader Subsystem Virtual Machine Runtime Dispatch Subsystem Plug-In Package Database Subsystem OS Platform Services Subsystem Plug-In Package Development Kit Model Librarian Subsystem Application Specification Subsystem XML Services Subsystem User Interface View Controller Subsystem Hyperworx Core State Machine Subsystem

Figure 42 Hyperworx Platform Technical Disclosure [ Figure 42 ] © 2003 Encapsule Systems, Inc. Revised: 9/9/2015 Re-usable diagram elements Just ignore this slide.x