Object transformations and the persistence of all states during the transformation lifecycle
OwnerAjay Jadhavinventor
Life of this patent
Estimating the term…
Abstract
A system for object transformations and persistence of all states during a transformation lifecycle includes a user interface for receiving or creating a data object, a first application capable of processing and transmitting attributes of a data object, a server capable of receiving, persisting or distributing these attributes, a second application capable of receiving and processing these attributes to create or recreate a data object, a user interface for displaying the created or recreated data object, wherein the first and second applications of the system may be the same, may reside on the same device or platform, or may reside on different devices or platforms.
Claims8
A system for transformation and persistence of all states of a data object during a transformation lifecycle of the data object from an original data object to a transformed data object, comprising:
- a computing device;
- a display connected to the computing device;
- a browser accessible by the computing device;
- a backend server connected to the browser;
- and
- an application executable on the computing device;
- wherein the browser is configured to receive and create the data object, interpret object types, and hand over the data object to the application;
- wherein the application is configured to interact and transform the data object, create data elements in each data object, separate between various types of data elements of the data object, disassemble and automatically retain original and transformed data elements of the data object to retain an ability to restore any state of the data object during the transformation lifecycle, wherein the data elements constitute attributes of each data object, wherein the attributes comprise at least object ID, directory location, orientation, and filters,
- wherein the data elements comprise a functional data element, a self-timer data element, and an object type data element;
- wherein the application renders functionality individually for each object type via the functional data element on the computing device;
- wherein the object type data element allows the data object of a particular type to call functional routines that are meant specifically for that type of object;
- and
- wherein the backend server is configured to receive, persist or distribute the data elements of each data object.
A process for transforming and persisting all states of a data object during a transformation lifecycle of the data object from an original data object to a transformed data object in a system comprising a computing device, a display connected to the computing device, a browser accessible by the computing device, a backend server connected to the browser, and an application executable on the computing device, the processing comprising:
- via the browser, receiving and creating the data object, interpreting object types, and handing over the data object to the application;
- via the application, interacting and transforming the data object, creating data elements in each data object, separating between various types of the data elements of the data object, disassembling and automatically retaining original and transformed data elements of the data object to retain an ability to restore any state of the data object during the transformation lifecycle, wherein the data elements constitute attributes of each data object, wherein the attributes comprise at least object ID, directory location, orientation, and filters;
- and
- wherein the data elements comprise a functional data element, a self-timer data element, and an object type data element;
- via the application, rendering functionality individually for each object type via the functional data element on the computing device;
- via the object type data element, allowing the data object of a particular type to call functional routines that are meant specifically for that type of object;
- and
- via the backend server, receiving, persisting or distributing the data elements of each data object.
Dependencies are inferred from the claim text.