Web application development platform with relationship modeling

• US 9,513,885 B2
• Filed: 08/22/2013
• Issued: 12/06/2016
• Est. Priority Date: 08/22/2013
• Status: Active Grant

• Current Assignee: Peter Warren
• Original Assignee: Peter Warren
• Inventors: Warren, Peter
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): FRANCO, CHRISTOPHER J
• Application Number:
  US13/973,888
• Publication Number:
  US 20150058831A1
• Time in Patent Office: 1,202 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• CPC Class Codes: G06F 16/116 Details of conversion of file system types or formats
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 8/31 Programming languages or programming paradigms
• CPC Class Codes: G06F 8/35 model driven
• CPC Class Codes: G06F 8/40 Transformation of program code
• CPC Class Codes: G06F 8/41 Compilation

Abstract

A system and method for dynamically creating web applications from data is described. Simple data is transformed into a declarative application data model that is then parsed by a server and compiled into a functional web application. Application functionality is partly determined by rules applied to web application objects in response to user actions. These rules are triggered by various cues, including user actions and relationships among objects in the web applications. A web application is considered an n-dimensional problem space, and relationships among application objects can be modeled using set theory. The status of a particular relationship among objects and user actions can trigger specific application behavior. Additionally application behavior can be triggered in other ways, like conditions in arbitrary scripts or combinations of multiple triggers combined using logical connectives.

Claims

1. A computer-implemented method comprising:

receiving one or more base data files at a platform server;

transforming the base data files into one or more application data files, the application data files being defined in a declarative application modeling language, the declarative application modeling language comprising named data elements arranged in a hierarchical structure, the names and structure of the named data elements describing an application user interface and behavior, the declarative application modeling language including a structure for managing rules that define in part the behavior of an application, the rules comprising at least a given action and a given action trigger, the given action being automatically performed by the application upon the occurrence of the given action trigger, the given action trigger being dynamically evaluated during execution of the application and based in part on user actions, wherein the base data files are input into one or more data transformations to yield one or more application data files, each application data file describing a different application user interface and behavior corresponding to different web applications;

compiling, by execution of a data processor, each application data file into the corresponding different web applications; and

causing the web applications to be served to a browser, wherein the web application caches application states using state identifiers.

2. The method as claimed in claim 1 wherein the web application provides an Application Programming Interface (API) to enable external code to interface with web application functionality.

3. The method as claimed in claim 1 wherein base data is transformed into application data.

4. The method as claimed in claim 1 wherein multiple base datasets can be input into a single data transformation to yield multiple, different web applications.

5. The method as claimed in claim 1 wherein the web application is compiled once and then cached.

6. The method as claimed in claim 1 wherein base data is automatically generated without manual intervention via an automated process.

7. The method as claimed in claim 1 wherein the application data is automatically generated without manual intervention via an automated process.

8. The method as claimed in claim 1 wherein the web application compilation process is triggered via a single web request, either via a user click or an automated request.

9. The method as claimed in claim 1 wherein the platform server embeds the web application into a client host page by retrieving the client host page, modifying the client host page to include all necessary resources required by the web application, and serving the application web page that includes the embedded web application.

10. The method as claimed in claim 1 wherein the application web page is delivered using reverse proxy.

11. The method as claimed in claim 1 wherein the application web page is delivered using a client subdomain.

12. The method as claimed in claim 1 wherein the web application uses position-based relationship modeling to control application behavior.

13. The method as claimed in claim 1 wherein the web application uses script-based relationship modeling to control application behavior.

14. The method as claimed in claim 1 wherein the web application uses combinations of position-based and script-based relationships combined via logical connectives, including “

and”

, “

or”

, and “

not”

.

15. The method as claimed in claim 1 wherein the web application uses relationships between user selections and application objects to control application behavior.

16. The method as claimed in claim 1 wherein the web application uses state identifiers to represent application state.

17. The method as claimed in claim 1 wherein the web application is partitioned into multiple sub-applications and downloads the sub-applications only when needed.

18. The method as claimed in claim 1 wherein the platform server computes and caches application states in a compiled web application.

19. The method as claimed in claim 1 wherein web application state can be shared via social, sharing mechanisms.

20. The method as claimed in claim 1 wherein web applications can be nested and/or linked.

21. The method as claimed in claim 1 wherein the web application uses post-processing directives to control application behavior.

22. The method as claimed in claim 1 wherein the web application uses an offline application cache to make the web application available to users without a network connection.

23. The method as claimed in claim 1 wherein the platform server uses versioning to enable platform upgrades with no impact to clients using previous versions of the platform.

24. The method as claimed in claim 1 wherein the platform server can be installed and executed in multiple network environments, including a cloud system, a virtual private cloud, and a private client network.

25. The method as claimed in claim 1 wherein the platform server can be secured using Hypertext Transfer Protocol (HTTP) authentication, Transport Layer Security (TLS)/Secure Sockets Layer (SSL), signed Uniform Resource Locators (URLs), Virtual Private Network (VPN), and Internet Protocol Security (IPsec).

26. The method as claimed in claim 1 wherein the web application functions correctly on mobile devices without any modifications.