Browse Prior Art Database

System, Method, and Computer Program Product for Migrating Disparate Forms and Data Models to XForm Solutions Disclosure Number: IPCOM000024636D
Original Publication Date: 2004-Apr-02
Included in the Prior Art Database: 2004-Apr-02
Document File: 3 page(s) / 106K

Publishing Venue



System, Method, and Computer Program Product for Migrating Disparate Forms and Data Models to XForm Based Forms Solutions The primary focus of this disclosure is the inevitable need to migrate existing Web/Portal Forms {HTML, WML, etc.} to the rapidly emerging XForms W3C standard in an automated fashion without spending a lot of time and financial resources, not to mention acquiring the proper skills needed to execute this migration. The time and money saved using this system to migrate to XForms is exponential.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 3

System, Method, and Computer Program Product for Migrating Disparate Forms and Data Models to XForm Solutions

The basic premise of this disclosure involves migrating a disparate Web/Portal Form file or set of files as input, programmatically extracting modular components of the Form, mapping these components to their corresponding XForm counterparts, and finally generating an XForm as output.

System Overview

Figure 1. Below depicts a high-level overview of our invention end-to-end. Segment A. below represents one or more files containing components capable of being ported to XForms, either imbedded or stand-alone. These components include disparate Forms such as HTML, WML, InfoPath, etc. as well as disparate model objects in which a Form interface is capable of being extrapolated, such as database tables or xml files. Segment B. depicts the interface or access point to the system.

This system can be exposed through a GUI interface such as Eclipse or WebSphere Studio or it can be invoked programmatically via public APIs. The stand-alone system design allows for the rendering of XForms to be done at either design time (client) or runtime (server). Segment C. (Figure 2.) depicts the modular system container. Segment D. describes the input quantifier engine responsible for creating a taxonomic quantification of the input described in Segment A. used by Segment E (Figure 3.) Forms Component Extractor. The Forms Component Extractor is responsible for extracting various components of the system input into objects, based on it's taxonomy. Segment F. is the optional configuration aspect of the system in which end-users can specify certain configurations to be incorporated into the end-resulting XForm, such as error handling events and other processing events available in XForms. Segment G. Forms Component Collator retrieves a handle to the taxonomy objects created in Segment E. along with any user-defined configurations in Segment F. and constructs an object model of the end-resulting XForm. This object model is then passed on to Segment H. XForms Renderer in which the XForm is either written out to a stream (server) or XForm artifacts are explicitly generated (client), depending on the operating environment. Segments I. XForm UI and J. XForm Model represent the tw...