Patent Grant
8078960
This invention generally relates to writing data to, and viewing data in, an electronic form that is related to a hierarchical data file, and more particularly, to a solution for a hierarchical data file that declaratively defines features of the hierarchical data file, where an electronic form can be rendered by using the solution to transform the hierarchical data file such that the electronic form can be used to write data to, and view data in, the hierarchical data file.
Extensible markup language (XML) is increasingly becoming the preferred format for transferring data. XML is a tag-based hierarchical language that is extremely rich in terms of the data that it can be used to represent. For example, XML can be used to represent data spanning the spectrum from semi-structured data (such as one would find in a word processing document) to generally structured data (such as that which is contained in a table). XML is well-suited for many types of communication including business-to-business and client-to-server communication. For more information on XML, XSLT, and XSD (schemas), the reader is referred to the following documents which are the work of, and available from the W3C (World Wide Web consortium): XML Schema Part 2: Datatypes; XML Schema Part 1: Structures, and XSL Transformations (XSLT) Version 1.0; and XML 1.0 second edition specification.
One of the reasons that data files written in XML are often preferred for transferring data is that XML data files contain data, rather than a combination of data and the software application needed to edit the data. Using XML is advantageous, as opposed to a binary data format, because it is all in a text format which makes it possible to view and edit a raw XML file using standard applications like an Internet browser and a text editor.
In some applications, in order to edit an XML data file, a user typically must interactively install a solution software application used to access, view, and edit the data file. When the user is online, the user's computer can run a host application capable of accessing the Internet, such as Microsoft® Internet Explorer®, which can silently discover and deploy a solution, which can be written in XSLT, where the solution enables the user to author and access an XML data file. Alternatively, some XML files can be directly viewed in an Internet browser so that a specific application may not be needed for this specific purpose.
An application and/or information to be put into XML data files can be collected electronically using, for example, Internet (e.g., web) or online electronic forms. Tools for using the electronic forms must be custom built applications or must use proprietary electronic forms tools. Using these custom applications and proprietary electronic forms tools causes at least four significant problems. The first problem is that the process of gathering information electronically can be inefficient. Inefficiencies occur for several reasons. One reason is that data entry personal can provide inconsistent data. Data inconsistencies occur where information is missing or provided in different formats. As such, those responsible for gathering, analyzing or summarizing the data must go back and reconcile the information provided. Another data inconsistency occurs because people provide information to one person who then inputs the data into some sort of electronic form or tool. Because the data has to be re-typed by someone who isn't the subject matter expert, this process leads to inaccurate data and to an inefficient data gathering process.
A second problem with using custom applications and proprietary electronic forms tools is that the resultant electronic forms or documents aren't very easy to use and can be extremely inflexible. Many conventional electronic forms do not provide a rich, traditional document editing experience. Without tools or features such as rich text formatting and spell checking, these forms can be hard to use. And as a result, people don't use them as frequently as they should—leading to loss of invaluable organizational information. Additionally, conventional electronic forms are static in nature, where users have to fit their information into a set number of fields and don't have the ability to explain the context behind the information. What this means is that the information provided is often incomplete. As such, the person who consumes the information has to go back to the users to find out the real story behind the data.
A third problem with using custom applications and proprietary electronic forms tools is that they require considerable expense in order to build a solution that enables a user to author and access data using an electronic form or document corresponding to the solution. Such conventional electronic forms or documents can be difficult to modify because they were built for a specific purpose and required development work. Validation of data entered in conventional electronic forms for documents requires a developer to write code or script. Additionally, data entry personnel must be trained on how to use the conventional electronic forms for documents. Moreover, once the data is collected for an organization using the conventional electronic forms, the data is difficult to re-use or re-purpose elsewhere in the organization because the collected data is locked into proprietary documents and data formats. To reuse this data, the organization must invest in significant development work to extract the data from the appropriate sources and translate the data from one format to another.
Given the foregoing, it would be an advantage in the art to provide a solution that can be discovered for a data file by which electronic forms can be used to enter data into and view data in the data file, where the solution addresses the foregoing problems.
The following description and figures describes a solution for an XML document. In one implementation, instructions are received to open an eXtensible Markup Language (XML) document. The XML document is searched to locate a processing instruction (PI) containing a href attribute that points to a URL. The solution is discovered using the URL in the PI. The XML document is opened with the solution. The solution includes an extensible stylesheet language (XSLT) presentation application and a XML schema. The XML document can be inferred from the XML schema and portions of the XML document are logically coupled with fragments of the XML schema. The XSLT presentation application is executed to render a Hypertext Markup Language (HTML) electronic form containing data-entry fields associated with the coupled portions. Data entered through the data-entry fields can be validated using the solution. Other implementations are disclosed for discovering a solution and rendering an HTML electronic form by applying XSLT to XML using the solution.
The detailed description is described with reference to the accompanying figures in which the same numbers are used throughout the disclosure and figures to reference like components and features. Series 100 numbers refer to features originally found in
a is a flow diagram illustrating an exemplary process to deploy a form template in which a user opens a form of a certain type to automatically download the corresponding latest version of a form template that is stored on the user's machine so that the user can use the form template when not connected to a network.
b is a flow diagram illustrating an exemplary process to deploy a form template by installation directly on a user's computing device, where the form template can be packaged as an executable module.
The following disclosure describes a way to access data files, either when online or when offline, using an electronic forms application. The disclosure also addresses the definition of interactivity and authoring experiences, connections to external data sources, and other functionalities with respect to the electronic forms application. If a user has opened a data file first online, or if the system has otherwise received the data file's solution, the electronic forms application can silently discover and deploy the data file's solution so that the user can edit data in the data file when offline. As used herein a solution and a form template for an electronic form are equivalent. The data file's solution declaratively defines aspects a data file such as its elements, attributes, and values, as will be discussed below. The electronic forms application allows a user to simply select a data file to open and the electronic forms application will open the data file with a discovered and deployed solution. The user need not discover, select, or even be aware that the data file requires a solution for the data file to be edited. After selecting the data file to open, the user can then edit and access the data file in a way very similar to how it would act and appear had the user opened the data file while online.
Data Files, Solutions, and Host Applications Data files, their solutions, and a host application work together to allow a user to open and edit the data file. Data files contain little or no operable code, whereas a solution file contains presentation and logic applications. The presentation and logic applications of a solution file or solution declaratively define aspects a data file such as its elements, attributes, and values. The elements, attributes, and values that are declaratively defined can include a schema for the data file, one or more views that can be used for viewing and entering data in the data file, a manifest of one of more files that enable contextual editing of the data file, and one of more user interfaces that can be used with the one or more views and can include functional components such as toolbars, menu bars, buttons, or task panes. Other declaratively defined elements, attributes, and values include a usage of specific event handlers and/or specific error handlers, and a definition of one or more back-end servers to which connectivity is available.
The elements, attributes, and values can also be programmatically defined in addition to the foregoing declarative definition. Specifically, the programmatic definition can be written in a programming code using a scripting language and can include validation rules for data entry with respect to the data file, custom error processing, implementations of data routing (data submission), and algorithms for connecting programmatically to databases, Web services or other back-end systems.
Editing a data file requires a solution. If a user tries to open a data file without a solution, the user could get an error or perhaps a flat list of the data in the data file. In order to view and edit the data file, the data file's solution is needed. As such, a solution has a corresponding solution application for the data file. The solution application is one or more files that, when installed, are used to enable a user to view, access, and edit the data file.
In addition to the data file and its solution, a host application is needed. This application works to enable the solution to function fully. In this description, an electronic forms application is described, which is capable not only of acting as a host application (allowing a solution to function properly), but can also allow a user to open a data file without actively finding and installing the data file's solution.
For discussion purposes, the system and method described herein are described in the context of a single computer, a communications network, a user-input device, and a display screen. These devices will be described first, followed by a discussion of the techniques in which these and other devices can be used.
Exemplary Architecture
The computing system 102 includes a user-input device 106, a display 108 having a screen 110, and a computer 112. The user-input device 106 can include any device allowing a computer to receive a user's preferences, such as a keyboard, a mouse, a touch screen, a voice-activated input device, a track ball, and the like. With the user-input device 106, a user can edit a data file by adding or deleting information within a data-entry field on an electronic form, for instance. The user can use the display 108 and the electronic form on screen 110 to view the data files. An electronic form, with respect implementations of an electronic forms application 122 described herein, is a document with a set of controls into which users can enter information. Electronic forms can contain controls that have features such as rich text boxes, date pickers, optional and repeating sections, data validation, and conditional formatting. An example of the electronic forms application 122 is the InfoPath™ software application provided by Microsoft Corporation of Redmond, Wash., USA, through the Microsoft Office™ software application.
The computer 112 includes a processing unit 114 to execute applications, a memory 116 containing applications and files, and a network interface 118 to facilitate communication with the communications network 104. The memory 116 includes volatile and non-volatile memory, and applications, such as an operating system 120 and the electronic forms application 122. The memory 116 also includes a solution 124 for a data file 126. The solution 124 is located locally in the memory 116, but often has a different original source, such as a source on the communications network 104. The solution 124 contains one or more files and folders, such as a presentation folder 128, a logic file 130, and a list file 132. The presentation folder 128 includes a rendering file 128a and a transformation file 128b. The components of solution 124 will be discussed in greater detail below.
The electronic forms application 122 facilitates offline editing of the data files 126 and is executed by the processing unit 114. The electronic forms application 122 is capable of acting as a host application and enabling a user to open the data file 126 without actively finding and installing the data file's solution 124. Without any user interaction, other than the user attempting to open the data file 126, the electronic forms application 122 discovers and installs the data file's solution 124. Thus, the user does not have to do anything but request to open the data file 126. The user does not have to discover the data file's solution 124. The user does not have to install the data file's solution 124. This silent discovery and deployment allows the user to view, edit, and otherwise interact with the data file 126 with just a single request. In addition, the electronic forms application 122 can provide security offline similar to the security that the user typically enjoys when running a solution online.
A view of the data file 126 can be depicted on screen 110 through execution of the data file's solution 124. The solution 124 contains one or more applications and/or files that the electronic forms application 122 uses to enable a user to edit the data file 126. To edit the data file 126 in a user-friendly way, the data file's solution 124 contains the presentation folder 128, which includes an electronic form. This presentation folder 128 is a container for components that, when used, give the user a graphical, visual representation of data-entry fields showing previously entered data or blank data-entry fields into which the user can enter data. Data files often have one solution but each solution often governs multiple data files.
The solution 124 presents the travel Itinerary form 200 but also contains the logic file 130 that governs various aspects of the travel Itinerary form 200 and the data file 126. In a data-entry field 206, for instance, the solution 124 can be configured so as to present the data-entry field 206 in a variety of visual appearances, such as by providing a white box within a gray box, by providing a description of the data desired with the text “Start Date”, and by providing logic that requires the user to pick a date by clicking on a calendar icon. Thus, if the user attempted to enter letters, the logic file 130 of the solution 124 would not permit the user's entry. The solution 124 could reject it and inform the user of the problem, such as with a sound, flashing error signal, pop-window, or the like.
The logic file 130 is employed in the solution 124 to ensure that the right kind of data is being entered and retained by the data file 126. A user's business manager attempting to reference dates with a reference number, for instance, would like the solution 124 to have dates in the data-entry field 206, otherwise, the manager may not be able to determine how a travel itinerary should be handled if the date is entered incorrectly because it contains letters.
Similarly, suppose a business manager wants the travel date for a trip. To require this, the logic file 130 of travel itinerary form 200's solution 124 could be constructed to require a date to be entered into the date data-entry field 206. The logic file 130 can be internal to the solution 124. The logic file 130 can also be a schema, such as an XML schema. Here, the XML schema is a formal specification, written in XML, that defines the structure of an XML document, including element names and rich data types, which elements can appear in combination, and which attributes are available for each element.
A solution can govern multiple data files. The exemplary travel itinerary form 200, for example, allows one or more users to fill out many different trips. Each time a user fills out a travel itinerary form 200, the system 102 can create a separate data file for that trip. Often, a user will create many different data files having the same solution. For each data file edited after the first, the system 102 is likely to have the appropriate solution stored in the memory 116. Thus, if a user previously opened a first data file and later attempts to open a second data file, both of which utilize the travel itinerary form 200 solution, the electronic forms application 122 can silently discover and deploy the travel itinerary form 200 solution to enable the user to edit the second data file. How the electronic forms application 122 discovers and deploys solutions will be discussed in greater detail below.
A solution can be one file or contain many files, so long as the files used to edit data files it governs are included. In one implementation, the solution 124 of
A solution, such as the solution 124, can also include various files or compilations of files, including a manifest file setting forth names and locations for files that are part of the solution 124. The files within the solution 124 can be packaged together, or can be separate. When separate, the list file 132 acts as a manifest of the files within the solution 124. In one implementation, the list file 132 can also include other information, such as definitions, design time information, data source references, and the like. In another implementation, file list information can be part of a manifest that stores the file list information. When the files are packaged together, the electronic forms application 122 can simply install and execute the packaged solution file for a particular data file. When not packaged, the electronic forms application 122 can read the list file 132, find the listed files, and install and execute each of the listed files for the particular data file.
Like solutions, data files can come in various types and styles. As mentioned above, data files can be written in XML or some other mark-up language, or can be written in other languages. Most data files, however, do not contain extensive logic and other files or code. One of the benefits of having data files separate from their solutions, is that it makes the data within them easier to mine. Because the data files are separate from their solution, the electronic forms application 122 makes them easy to open and edit by silently discovering and deploying the solution for the data file.
Data files also are typically concise and data-centered so that the data they contain can be more easily accessed or manipulated by multiple software applications, including software not typically used in a solution, such as an application that searches for a particular type of data and compiles that data into a report. A non-typical application, for example, could be one that compiles a report of all of the travel itineraries required to be mailed by a certain date by searching through and compiling the data entered into data files through the required data-entry field 206 of the travel itinerary form 200 electronic form.
The above devices and applications are merely representative, and other known devices and applications may be substituted for or added to those shown in
A plurality of XML solution files 300, seen in
Having discussed general data files and solutions for viewing, editing, authoring general data files, above, a discussion will now be made specifically about XML documents and solutions. The view definition files 312 are XSLT files associated with each XML document 304. The view definition files 312 define multiple layouts and view logic for the XML document 304. The view interactivity files define a contextual user interface (UI) as well as behavior of some XSLT views. Each XSLT view is an electronic form-specific display setting that can be saved with an XML solution 302 and applied to form data when the electronic form is being filled out. Users can switch between views to choose the amount of data shown in the electronic form.
The XML solution files 308-314 are a collection of files that are used to implement an electronic form as further described herein. File types can include HTML, XML, XSD, XSLT, script, and other file types that are helpful in supporting the functionality of the electronic form.
The information (e.g., data) that is collected in a single electronic form, further described herein, can be used by many different systems and processes. The usefulness of this information is due the storage of the information as XML. The electronic forms application 122 can communicate with ADO (ActiveX Data Objects) databases and XML Web services in a bi-directional manner, enabling the information stored in databases and servers to populate data-entry fields within electronic forms.
The solution definition file 306 is described above as the hub file because it can contain all the information to determine how the XML document 304 is presented to the end-user for editing of the information and ways to interact with the information, such as by navigating to different views of the information, modifying content or creating new content, etc. The solution definition file 306 can reference secondary files, some of which have types of data corresponding to XML standards, like XSD files that are used for schema information, like XSLT files that are used to specify the direct visual presentation of the XML data as views, and like XSLT style-sheets that are used to transform the XML document that has been loaded into HTML for visual presentation.
The solution definition file 306 uses XML vocabulary in an interoperable file format for XML solution 302. A declarative specification for contextual interactivity with XML data, via an XSL generated view, is included in the solution definition file 306. Additionally, the solution definition file 306 contains or references information about all other files and components used within a form, including files that contain instructions for user interface customizations, XML schemas, views, business logic, events, and deployment settings. Here, an event is an action recognized by an object, such as a mouse click or key press, for which a response by the electronic forms application 122 can be defined. An event can be caused by a user action or it can be triggered by the system. An event can be caused by a statement of business logic that is written in any supported programming language (e.g., a Visual Basic statement).
The solution definition file 306 is an XML document that can also express information that does not correspond to any XML standard via an XML syntax that allows declarative specification of XML solution 302. Various features can be provided to the end-user by the solution definition file 306.
Once feature that is provided by the solution definition file 306 is the ability to define views and commands/actions that can be made available via secondary user interface as well as how the views' availability will be determined contextually, including the interactivity that is to be made available in the views. Here, the secondary user interface (UI) referred to is a context driven UI that offers menus and toolbars. Another feature provided by the solution definition file 306 is the types of binding between the views and the underlying XML data so that data entered can be saved in an XML file. The binding here refers to a logical connection from a control (e.g., a data entry field on an electronic form) to a field or group in a data source of an data file so that data entered into the control is saved. Here, a data source is a collection of fields and groups that define and store the data for an electronic form being processed with the electronic forms application 122. Controls in the form are bound to the fields and groups in the data source. Specifically, a control is a graphical user interface object, such as a text box, check box, scroll bar, or command button, that lets users control the electronic forms application 122. Controls can be used to display data or choices, perform an action, or make the user interface easier to read. Conversely, when a control is unbound, it is not connected to a field or group, and so data entered into the control will not be saved.
A still further feature is the availability of structural or text-level editing operations on the XML data. Yet another feature includes validations (e.g., XML data validation), event handlers associated with the electronic form as a whole, and business logic associated to individual nodes of the XML Document Object Model (DOM) representing the form, where the business logic attaches to the electronic form as a whole, including the association of ‘business logic’ script with user actions. A still further feature includes simple workflow and information about routing of the XML Document 304. The availability to use global metadata information about the XML Document 304, including deployment/publishing information, is another feature. Another feature provided by the solution definition file 306 is the availability of default XML data that can be used when creating a new XML Document 304. A unique identifier for the electronic form is an other feature. A still further feature is the availability of optional schema for the XML DOM that comprises the electronic form.
The electronic forms application 122 described herein enables users to process XML documents 304. XML documents 304 are partitioned into classes or document types, based on their schemas. XML documents 304 need business logic 310 and data flow as required by the XML data solution 302 they are part of. This business logic 310 and data flow information lives outside of the XML document 304 in XML solutions 302. As such, the XML solution is a factory for given classes of XML Documents. The XML solution 302 defines the layouts and the editing behavior of the XML Documents 304. The XML solution 302 enforces data consistency and provides routing information. The electronic forms application 122 described herein may work with one or more types of XML documents 304 and provide a portal and a list views for collection of XML documents 304. XML solutions 302 can be stored on the client, such as in computer 112, and can be made available offline.
The XML schema file 406 defines the structure for the XML created when filling out the electronic form. The one or more XSLT files 408 define different views. The definition of different views can be written in a language, such as XSLT, that is used to transform XML documents into other types of documents, such as HTML or XML. As used herein, XSLT is a style-sheet language that uses the XML syntax to specify transformation information for XML files. An XSLT style-sheet specifies the presentation of a class of XML documents by describing how an instance of the class is transformed into an XML document that uses the formatting vocabulary. An XML file 410 can be used to determine the structure and content of a blank electronic form created with the form template. The XML file 404 (with an .xsf extension), which corresponds to the solution definition 306 seen in
Optional or auxiliary files for business logic 412 (e.g., Jscript or VBscript, graphics, XSLTs) define merge functionality, and/or other resources needed by the form template). An XML data file 402 corresponds to a Universal Resource Locator (URL) or a Universal Resource Name (URN) for the purposes of reference with respect to the electronic form template 420. A collection of default data in XML file 410 is included in the electronic form template 420 and includes data for creating a new (e.g., blank) electronic form. The one or more files of business logic 412, corresponding to business logic 310 seen in
As with HTML files, opening an .xml file in the Microsoft® Windows® operating system will automatically launch the application that created the file. If the Microsoft® Windows® operating system cannot detect the application that created the file, it will launch the file in the default application registered for the XML file extension. When an XML file is created or edited using the electronic forms application 122, the electronic forms application 122 creates an XML processing instruction (PI) at the beginning of that XML file, which indicates that the document should be edited specifically with the electronic forms application 122. Advantageously, the PI is part of the XML standard and does not interfere with the schema on which the XML file may be based. XML files generated by the electronic forms application 122 include the XML processing instruction that identifies the corresponding template using either a URL or a URN.
The solution design component 502 of the architecture 500, such as is seen by XML solution 302 in
In one implementation, the solution design component 502 provides a WYSIWYG forms designer and editor based on XML standards that can be used for generic XML schemas. As such, XSL editor and solution builder 510 need not be characterized as including an XML editor. Moreover, notepad 514 and support files 512 need not be present.
The runtime component 504 includes an editor frame 520 that includes XML editing 522. The XML editing 522 can function similarly to the electronic forms application 122. The editor frame 520 bidirectionally communicates with a solution infrastructure 524, such as XML solution 302 seen in
It is an option in some implementations that the XML solution infrastructure 524 works with the local XML store 526. The optional local XML store 526 can provide electronic mail (e-mail) capabilities, such as an “inbox” and a “sent items folder” for XML payloads, and to enable the ordering, filtering and aggregation of XML data that is shredded or parsed in the local XML store 526. Absent the foregoing option, XML store 526 can be omitted from XML runtime component 504.
The XML solution infrastructure 524 allows a user of computer 112 to access various XML data sources on computer 112, in an intranet, as well as on an extranet or the World Wide Web. Given the foregoing, XML Documents 530 can be displayed and edited using the XML Editing 522 of the editor frame 520.
The solutions 506 can be provided to a user of computer 112 as part of the architecture 500, where the user would like to see sample or exemplary solutions from which the user can learn about the electronic forms application 122. Solutions 506 can provide the user with a guide for customizing electronic forms and for building new solutions based on the exemplary solutions.
a and 6b provide respective processes 600A, 600B by which a user of workstation 602 can be provided with a solution having a corresponding electronic form that can be used by a user via an electronic forms application 618. The electronic forms application 618 and the workstation 602 seen in
In process 600A, seen in
Process 600B, seen in
Techniques for Silent Discovery and Deployment of a Solution for a Data File
Overview
Silent Discovery and Deployment
At block 702, the system 102 receives input from a user to open the data file 126. The user may simply click on an icon representing the data file 126 or otherwise select the data file 126 after which the system 102 opens the data file 126.
At block 704, the system 102 discovers a solution identifier in the selected data file 126. This assumes that the data file 126 is one in which the electronic forms application 122 is capable of reading. The electronic forms application 122 can read data files created at some previous time by the user's or another's electronic forms application 122. In one implementation, the electronic forms application 122 can also read the data file 126 if it is created by another application that builds a solution identifier into the data file 126. This solution identifier can give the system 102 an original source for the solution 124. The solution identifier is typically a URL (Uniform Resource Locator) or URN (Uniform Resource Name), but can include other types of names and/or locators. URLs give locations and URNs give names of resources, such as the solution 124, which are typically accessible through the communications network 104. With the solution identifier, the system 102 can determine the original source for the solution 124 (where it first came from) and whether or not the system 102 has seen the solution 124 before.
In one implementation, the solution identifier is part of a processing instruction (PI) included within the data file 126. This PI is often part of data files and can include various instructions to host applications, such as the electronic forms application 122. PIs, while not strictly data, do not rise to the level of an applet or application typically included in a solution 124 for a data file 126. For data files written in XML, for instance, the PIs are usually not written in XML, but rather are just a piece of information commonly included. A PI in an XML data file can look like
This PI gives the electronic forms application 122 a solution identifier, which here gives the original source for the solution 124 for the data file 126. This solution identifier includes a URL indicating that the original location for the solution 124 is at a remote server accessible by accessing the communications network 104 through the network interface 118.
In another implementation, the electronic forms application 122 determines a solution that is to be used with XML data, such as the data file 126. The solution is determined by locating a PI within the XML data. When the PI is located in the XML data, the payload of the PI is examined to determine the solution that is to be used with the XML data. A Universal Resource Locator (URL) in the PI can be used to identify a location of the solution. The solution can then be retrieved from its location. Once retrieved, the solution can be used to present a visual appearance of the XML data, to receive interactive edits to the XML data from an editing user, and then to update both the visual appearance and the XML data using the edits to the XML data from the editing user. An example of a PI in the XML data that uses a URL for discovery of its corresponding solution is:
Another example of a PI that identifies its solution by location is:
In this example, the PI has five (5) parts. The first part is the name of the PI which is ‘mso-infoPathSolution’. The second part is the ‘href’ that is a URL that specifies the location of the solution. Stated otherwise, the ‘href’ is a pseudo-attribute of the PI that contains a URL that specifies the location of the solution. The URL, in different alternatives, could refer to an ‘http’, to a file, or to an ‘ftp’, in accordance with known file path conventions. Additionally, relative URLs may also be used. The third part is the version of the PI (‘PIVersion’). The PIVersion pseudo-attribute is used to identify the version of the PI itself. The fourth part is the ‘solutionVersion’ which is a pseudo-attribute used to identify the version number of the solution used to generate the corresponding XML document. The fifth part is the productVersion pseudo-attribute that is used to identify the version of the electronic forms application 122 that created the XML document for which the solution is to be used. In this example, the electronic forms application 122 is the InfoPath™ software application provided by Microsoft Corporation of Redmond, Wash., USA. Also in this example, the third through fifth parts have the format of ‘x.x.x.x’.
The foregoing implementations provide two examples in which a URL in the PI could be used to identify a location of the solution to be used with an XML document. In yet another implementation, a PI in XML data contains a name from which the solution for the XML data can be discovered. Stated otherwise, the PI in the XML data identifies its solution by name. In this case, the electronic forms application 122 can determine the solution to use with XML data (e.g., the payload) by the schema of the top level node of the structured nodes in the corresponding XML data. As in prior implementations, the electronic forms application 122 performs a process in which the PI is located and examined. An example a PI that identifies a solution by name is:
In this example, the PI has five (5) parts. The first part is the name of the PI which is ‘mso-infoPathSolution’. The second part is a name pseudo-attribute that refers to a URN which is the name of the solution. Such a solution is typically registered with the electronic forms application 122 before the document is opened, and the electronic forms application 122 looks it up by name in its list of available solutions. The third through fifth parts are identical to the immediately preceding example. As in the immediately preceding example, the present example also represents that the electronic forms application 122 is the InfoPath™ software application provided by Microsoft Corporation of Redmond, Wash., USA.
In a still further implementation, the electronic forms application 122 can determine an online sandboxed solution that is to be used with an XML document. To do so, a PI in the XML document is located. An example of a PI for an online sandboxed solution is:
In this example, the href contains a solution identifier for which the solution has a path with the suffix ‘.xsf’.
In yet another implementation, the electronic forms application 122 can determine a single file online sandboxed solution that is to be used with an XML document. To do so, a PI in the XML document is located. An example of a PI for a single file online sandboxed solution is:
In this example, the href contains a solution identifier for which the solution has a path with the suffix ‘.xsn”.
In another implementation, the electronic forms application 122 can determine the solution that is to be used with a preexisting electronic form template. To do so, a PI in the XML document is located. An example of a PI for such a case is:
In this example, the URN in the ‘name’ attribute is preceded by “InfoPath:oob” to designate that the template is provided with the InfoPath™ software application provided by Microsoft Corporation of Redmond, Wash., USA.
In a still further implementation, the electronic forms application 122 can determine a trusted solution that is to be used with XML data. To do so, a PI in the XML data is located. An example of a PI for a trusted solution is:
In this case, the electronic forms application 122 can determine the solution to use with XML data (e.g., the payload) by the schema of the top level node of the structured nodes in the corresponding XML data. The solution is ‘trusted’ in the sense that a logical relationship is established between domains to allow pass-through authentication, in which a trusting domain honors the logon authentications of a trusted domain.
One of the advantages of the electronic forms application 122 is that it enables a user to open the data file 126 without the user needing to discover the data file's solution 124, install the solution 124, or even know that the solution 124 exists. This enables users to open data files simply and easily, and in many cases enables them to edit a data file offline that they would otherwise not have been able to edit.
Continuing now with the description of process 700 in
In one implementation, the electronic forms application 122 takes the solution identifier and computes a unique special name for the solution identifier. This unique special name is repeatable. The next time, the electronic forms application 122 computes a unique special name for the same solution identifier, the same unique special name will be created. By so doing, the electronic forms application 122 can find a previously downloaded solution by computing the unique, special name and then searching for the unique, special name to determine if the solution is available locally for offline use (such as by having the solution stored in the memory 116).
In another implementation, the electronic forms application 122 computes a unique special name by computing a hash, such as a Message Digest 5 hash (MD5 hash), of the solution identifier. By computing a one-way hash of the solution identifier, the electronic forms application 122 creates a unique, special name that is a file of 128 bits from the digits of the solution identifier. The MD5 hash can be computed by knowing the URL. In one implementation, a cache for a solution can be structured as:
%AppData%\InfoPath\Solution Cache\[16 character random GUID]\[MD5 hash of URL or URN,
where the random GUID protects the cache from other applications.
The system 102 uses the special name, which corresponds to a solution identifier and thus the data file 126's solution 124, to search through locally accessible sources for the solution 124 (block 708). The system 102 may, for instance, search in the memory 116 of
When the Special Name is Found
If the system 102 finds the special name (i.e., the “Yes” branch from block 710), then the solution 124 was saved earlier in the system 102 that was searched locally in the block 708. Thus, when the special name is found, the system 102 knows that the solution 124 referred to in the data file 126 (which the user is attempting to open) is accessible offline by the system 102. The solution 124 is usually stored in the memory 116 but can be stored in other searchable, local sources that the system 102 does not have to go online to find.
The solution 124, stored at the source and found using the special name, may not be current, however. Because of this, the system 102 determines whether or not the system 102 is online or offline (block 712). If online (i.e., the “Yes” branch from block 712), the system 102 will attempt to determine whether or not a more up-to-date solution should be installed (discussed below). If offline and if the locally stored solution 124 is new, then the system 102 will proceed to install the locally stored solution 124 (block 714).
If the Solution is Found and the System is Offline
If the solution 124 is found and the system 102 is offline, the system 102 proceeds to install the solution 124 from the memory 116 or another locally accessible source (block 714).
The system 102 installs the solution 124 silently in that the user does not need to know that the solution 124 was discovered, found, or was being installed. Thus, the system 102 enables a user to edit the data file 126 when offline by silently discovering and deploying the data file's solution 124.
In one implementation, the system 102 installs the solution 124 and then opens the data file 126 in such a manner as to mimic how the data file 126 would be opened had the user opened the data file 126 with the solution accessible online, such as through opening the data file 126 with Microsoft® Internet Explorer®. The system 102 does so to make opening and editing the data file 126 as comfortable for the user as possible, because many users are familiar with opening data files online. One possible difference, however, is that if the system 102 has a slow connection to the communications network 104, the electronic forms application 122, by installing the solution 124 from a local source like the memory 116, may more quickly open the data file 126 than if the user were online.
In block 716, the system 102 opens the data file 126 to enable the user to edit the data file 126. One example of an opened data file (and solution) enabling edits is the travel itinerary form 200 of
Following the previous blocks, a user can easily open a data file offline without having to discover or deploy the data file's solution. This enables users, for example, after first opening a solution online, to open a data file offline. A user can open a data file online and edit it by adding a date through the data-entry field 202 of the travel itinerary form 200 and then stop editing the data file (the data file would contain the added date by the system 102 adding the date to the data file). The user could then go offline, such as by taking his or her laptop on a business trip, and complete filling out the electronic form. Or the user could send the partially filled-out data file to another user to fill out the rest of the electronic form, which the other user could do so long as the other user's system contains a stored solution. This flexibility allows users and businesses a greater ability to use information by keeping data and solutions separate and by allowing offline use of data files.
If the Solution is Found and the System is Online
Assuming the system 102 finds the special name and the system is online, the system 102 will attempt to determine whether the current solution is the most recent version or a more up-to-date solution is available. In block 718, the system 102 compares the time stamp of the stored solution 124 and the online solution. Since the system 102 is online, it can access the solution (here we assume that the origin of the solution 124 is from an online source). If the solution identifier from the data file 126 selected by the user contains a reference to the solution 124 being accessible online, the system 102 goes online to check whether or not the online solution is newer than the stored solution 124 (block 720). In one implementation, the system 102 compares a time stamp of the online solution with a time stamp on the stored solution 124.
If the online solution is not newer (i.e., the “No” branch from block 720), the system 102 proceeds to the block 714, installing the stored solution 124. If the online solution is newer than the stored solution 124 (i.e., the “Yes” branch from block 720), the system 102 either replaces the stored solution 124 with the online solution or otherwise updates the older, stored solution 124.
Downloading the Solution for Later Use
In block 722, the architecture 100 (or the system 102 by accessing the communications network 104) downloads a solution into a locally accessible source such as the memory 116. The system 102 downloads this solution when the data file 126 selected by a user contains a solution identifier for a solution for which the system 102 does not have local access (such as it not being cached) or for which the system 102 has local access but the cached or stored version of the solution (the solution 124) is older than the online version.
In either case, the system 102 has already discovered the solution identifier for the solution and computed a special name for the solution. The system 102 then downloads the solution from the online source. Note, however, that if system 102 is offline, then process 700 will terminate in a failure mode. If system 102 is online, then process 700 proceeds from block 722 to block 724 and saves the solution into a folder named with the special name (block 724). If a solution already exists in that folder, the system 102 replaces it with the newer version or otherwise updates the currently cached solution. The resulting new or updated version will then be in the solution 124.
In one implementation, the system 102 saves the solution to a unique location within the system 102's accessible memory. The system 102 does so in cases where the system 102 is used by multiple users. By so doing, the system 102 is able to determine which of the users that use the system 102 or load files into memory locally accessible by the system 102 saved the particular solution. Also by so doing, the system 102 may provide greater security for the computer 112 and its users.
Process 700 in
In another implementation, where the solution is located in the list of locally cached solutions, it can be ascertained whether the most recent version of the solution has been obtained. To do, a version, electronic tag, or time stamp in the PI can be examined, such as by an auto-update process. If the examination indicates a change in the original solution (e.g., a server copy of the solution is different), then the latest solution can be downloaded. For instance, the electronic forms application 122 can be configured to explode the solution to a temporary location within the locally cached solutions and then can compare the version of the downloaded solution to the version of the current cached copy of the solution.
If the search by the electronic forms application 122 finds a PI but fails to locate the solution in the list of locally cached solutions or by download, then a diagnostic can be output, such as by way of a visibly displayed descriptive error. If the search by the electronic forms application 122 finds a PI that contains a name attribute associated with a URN, a computation can be performed of the name of the folder in the solution using the URN. A lookup can then be performed on a locally installed solution using the name attribute in a catalog of solutions. If the solution is thereby found, a comparison can be made between the cached version of the solution and the original version of the solution. This comparison is performed to make sure that the cached version of the solution is up-to-date. In the case of the InfoPath™ software application provided by Microsoft Corporation of Redmond, Wash., USA, through the Microsoft Office™ software application, if the name is prefixed by a character string that includes “InfoPath” and “oob”, then the XML data located by the application is referring to an InfoPath template or out-of-the-box (OOB) solution. In such a case, an assumption might be made that solutions for the InfoPath templates are installed at a location shared by all users of a specific computing device (e.g., C:\Program Files\Microsoft Office\Templates).
The steps set forth in process 700 in
When the InfoPath™ software application provided by Microsoft Corporation of Redmond, Wash., USA, through the Microsoft Office™ software application is used to design an electronic form, a PI in an XML document corresponding to the electronic form will have various characteristics. As such, any electronic forms application 122 that is attempting to discover a solution for an electronic form that was created by the InfoPath™ software application should be advantageously configured to locate the solution by searching for a PI in the corresponding XML document that has one or more of these various characteristics. When so discovered, the electronic forms application 122, which may be different than the InfoPath™ software application, can then be used to view and/or interactively enter/change XML data through the electronic form that was created by the InfoPath™ software application.
Once such characteristic of an XML document corresponding to an electronic form that was designed, created, or changed by the InfoPath™ software application is that it has a PI containing the solution identifier that will most likely be the first PI in the XML document corresponding to the electronic form. Another such characteristic is that the PI containing the solution identifier contains both a href attribute and a character string that identifying the PI version and/or the product version of the InfoPath™ software application. The href attribute need not be the first pseudo-attribute in the PI, but could be anywhere in the PI. As such, the PI version could be first in the PI followed by the href attribute. Yet another characteristic is that the target of the PI containing the solution identifier also contains the character string “mso-InfoPathSolution” solution, where that character string is the first character string in the PI and could be followed by a href attribute. Yet another characteristic is that the PI containing the solution identifier contains a URL or URN that will most likely point to a path having a suffix that is either ‘*.xsf’ (e.g., a manifest or listing other files) or ‘*.xsn’ (a file that contains multiple files compressed into one file and that are extractable with the extract ‘*.exe’ utility).
Given the foregoing characteristics of electronic forms designed, created, or changed using the InfoPath™ software application, the electronic forms application 122 can be configured to discover the solution of an electronic form by simply finding the first PI in the XML document. Alternatively, the electronic forms application 122 can be configured to discover the solution by examining a PI in the XML document for the electronic form to see if it includes a character string that is likely to represent a solution corresponding to the XML document. When the likelihood is high, the name can be used to discover the solution. As a further alternative, the electronic forms application 122 can be configured to discover the solution by examining the target in a PI in the corresponding XML document for the character string “mso-InfoPathSolution”, and/or by looking for a URL in the PI having a suffix of *.xsf or *.xsn. As yet another alternative, the electronic forms application 122 can be configured to discover the solution by trying, as a potential solution, each name that is in quotation marks in the PI and is associated with a href attribute in a PI in the XML document, and then using the solution that is returned after a success following one or more of such attempts. As mentioned above, the href attribute need not be the first pseudo-attribute in the PI, and the electronic forms application 122 may take this into account when assessing the PI for its likelihood of containing the correct solution identifier. In a still further another alternative, the electronic forms application 122 can be configured to discover the solution by trying as a potential solution each URL in each PI of an XML document, and then using the solution that is returned after a success following one or more of such attempts. As noted above, the URL or URN in the successful PI will most likely point to a ‘*.xsf’ or ‘*.xsn’ path, and the electronic forms application 122 may take this into account when assessing the PI for its likelihood of containing the correct solution identifier.
Data Files, Transformation Files, Rendering Files, and Rendered Forms
As discussed above, solution 124 contains presentation folder 128 that includes the rendering file 128a and the transformation file 128b. The data file 126, transformation file 128a, rendering file 128b, and a rendered form work together to allow a user to edit the data file 126. A user can input data into and view data in the data file 126 through the rendered form of the data file. This rendered form is the result of executing the rendering file 128a, which is created by applying the transformation file 128b on the data file 126.
Data input into a particular data-entry field of the rendered form is stored in a particular node of the data file 126. Data-entry fields of the rendered form correlate to nodes of the data file 126 in part because the rendered form is the result of the transformation file 128b being applied on the data file 126. The system 102 can use various ways to detect which data-entry fields correlate to which nodes of the data file 126, including through mapping with XML Path Language (XPath) expressions that address parts of data file 126 (e.g., an XML document) by providing basic facilities for manipulation of strings, numbers and Booleans.
Also in
The transformation file 128b also correlates to the data file 126. Nodes of the data file 126 correlate to particular parts of the transformation file 128b, also called nodes for the purposes of this description. Thus, nodes of the transformation file 128b correlate to nodes of the data file 126. This correlation can arise from nodes of the transformation file 128b being mapped to the nodes of the data file 126, including through XPath expressions, or otherwise.
That certain nodes of the transformation file 128b correlate to certain nodes of the data file 126 is often not enough, however, for the system 102 to accurately reflect a change in a particular node of the data file 126 by simply applying only a particular node of the transformation file 128b on a particular node of the data file 126. A node of the transformation file 128b, when applied on a node of the data file 126, may affect many nodes of the data file 126. Anode of the transformation file 128b could, for instance, be one that, as part of being applied on a node of the data file 126, is also applied on previously filled-in or as-yet-unfilled-in nodes of the data file 126. This concept is illustrated in
Further, the node of the transformation file 128b may direct the system to perform computations or other operations using other resources, like a database. For these and other reasons, the electronic forms application 122 analyzes the results of nodes of the transformation file 128b being applied on nodes of the data file 126 or nodes of some hypothetical data file, which will be discussed in greater detail below.
In some implementations, the transformation file 128b is an XSLT (eXtensible Style-sheet Language Transformation) file, which, when applied to an XML data file 126, generates a XHTML (eXtensible Hyper-Text Machine Language) or HTML (Hyper-Text Machine Language) rendering file (such as the rendering file 128a). The transformation file 128b can also be an arbitrary XSLT file, such as a custom-made file or some other W3C-compliant file. XHTML and HTML files can be used to show a view on the screen 110, such as the travel itinerary form 200 of
Like transformation files, data files can come in various types and styles. Hierarchical data files can be written in XML or some other mark-up language, or can be written in other hierarchical languages. Hierarchical data files also are typically concise and data-centered so that the data they contain can be more easily accessed or manipulated by multiple software applications, including software not typically used in a solution, such as an application that searches for a particular type of data and compiles that data into a report. A non-typical application, for example, could be one that compiles a report of all of the travel itineraries filled out in electronic forms by a certain person by searching through and compiling the data entered in travel itinerary data files for a particular person.
Validating Data from a User in Real-Time
Overview
A system, such as the system 102 of
Notifying a User of Errors in Real-Time
At block 902, the system 102 displays an electronic form having data-entry fields. The electronic form can be blank or contain filled data-entry fields. An expense report 1010 electronic form in
The system 102 displays an electronic form in a manner aimed at making a user comfortable with editing the electronic form. It can do so by presenting the electronic form with user-friendly features like those used in popular word-processing programs, such as Microsoft® Word®. Certain features, like undoing previous entries on command, advancing from one data-entry field to another by clicking on the data-entry field or tabbing from the prior data-entry field, cut-and-paste abilities, and similar features are included to enhance a user's data-entry experience. For example, the system 102 displays an electronic form having some of these features in
At block 904, with the electronic form presented to the user, the system 102 enables the user to input data into a data-entry field. The user can type in data, cut-and-paste it from another source, and otherwise enter data into the fields. The user can use the user-input devices 106, including a keyboard 110 and other device(s) (such as a touch screen, track ball, voice-activation, and the like). In
At block 906, the system 102 receives the data entered into the data-entry field 1012 by the user. The system 102 receives the data from the user through the user-input devices 106 and the user interface 134 (both of
At block 908, the system 102 validates the data received into the data-entry field in the electronic form. By using validation rules stored in the logic file 130 of the solution 124 and a real-time validation tool 136 stored in memory 116, the system 102 can analyze the data to determine if it is valid. In an alternative implementation, the real-time validation tool 136 can be included as a part of the solution 124 in memory 116. The real-time validation tool 136 refers to the validation rules, if any, in the logic file 120 governing that particular data-entry field (in this example the report date data-entry field 1012). The real-time validation tool 136 validates the data entered into a data-entry field without the user having to save or submit the electronic form. It can do so by applying validation rules associated with the node of the structured data file corresponding to data-entry field into which the data was entered.
The real-time validation tool 136 can apply validation rules from many different sources. One source for validation rules is a schema governing the structured data file. Other sources of validation rules can include preset and script-based custom validation rules.
For script-based custom validation rules, the real-time validation tool 136 enables these rules to refer to multiple nodes in a structured data file, including nodes governing or governed by other nodes. Thus, the real-time validation tool 136 can validate data from a data-entry field intended for a particular node by checking validation rules associated with that particular node. Through so doing, the real-time validation tool 136 can validate data entered into one node of a group with the validation rules governing the group of which the node is a part.
For example, if a group of nodes contains four nodes, and is associated with a script-based validation rule requiring that the total for the data in all of the four nodes not exceed 1000, the real-time validation tool 136 can validate each node against this rule. Thus, if the first node contains 100, the second 400, and the third 300, the real-time validation tool 136 will find the data intended for the fourth node invalid if it is greater than 200 (because 100+400+300+200=1000).
In some cases the real-time validation tool 136 can build validation rules from a schema containing logic that governs a structured data file. This logic sets forth the bounds of what data nodes in a structured data file can contain, or the structure the nodes should have. Data entered into a structured data file can violate this logic, making the structured data file invalid. This invalid data may cause a structural error or a data-type error in the structured data file, possibly making the structured data file useless. To combat this, the real-time validation tool 136 can build validation rules from a structured data file's schema.
Because structural errors are especially important, the real-time validation tool 136 treats these types of errors seriously. To make sure that a user treats these errors seriously, the real-time validation tool 136 builds validation rules for structural errors that stop a user from continuing to edit an electronic form if the real-time validation tool 136 detects a structural error. Validation rules that stop the user from continuing to edit the electronic form (except for fixing that invalid data) are called modal validation rules, and errors that violate them, modal errors.
For less serious errors, such as data-type errors, the real-time validation tool 136 builds validation rules that do not stop the user from continuing. These are called modeless validation rules, and errors that violate them, modeless errors.
To aid the real-time validation tool 136 in validating data in real-time, validation rules are associated with particular nodes. By so doing, with each new piece of data received, the real-time validation tool 136 is capable of comparing the data received against an appropriate list of validation rules associated with the node for which the data received is intended. Because this list of validation rules can be very short for each particular node, the real-time validation tool 136 has fewer validation rules to check for each piece of data entered than if it had to check all the validation rules for the node's structured data file. This speeds up the process of validation.
Continuing the previous example, at the block 908 the system 102 validates the data entered, “Jan. 27, 2003”, against validation rules associated with the report date data-entry field 1012, thereby determining if the data entered is valid.
In block 910 the system 102 determines whether to proceed to block 914 or 912 depending on whether the data is valid. If the real-time validation tool 136 determines that the data entered is not valid, it proceeds to the block 914, discussed below. If, on the other hand, the real-time validation tool 136 determines it to be valid, the system 102 continues to block 912, allowing the user to continue editing the electronic form. Continuing the ongoing example, if the real-time validation tool 136 determines that the data “Jan. 27, 2003” is valid, the system 102 continues on to the block 912. If not, it proceeds to block 914.
At the block 912, the system 102 enables the user to input data into another data-entry field. In
If the data is invalid, the system 102 proceeds to the block 914. At the block 914 the system 102, through the real-time validation tool 136, determines whether to proceed to block 916 if the error is not modal and 918 if it is.
Continuing the previous example, assume that the data entered into the report date data-entry field 1012 is invalid. Assume also that “Jan. 27, 2003” is not defined to be a modal error. (Modal errors are those for which the real-time validation tool 136 rolls back the invalid entry requiring the user to re-enter another entry before continuing on to edit another data-entry field or requires the user to correct.) Thus, in this example, “Jan. 27, 2003”, is invalid, but is a modeless error.
In the block 916, the real-time validation tool 136 alerts the user of a modeless error by marking the data-entry field as containing an error, but allows the user to continue editing the electronic form. To make the editing process as easy, intuitive, and efficient as possible, the real-time validation tool 136 can mark the data-entry field from which the invalid error was entered in many helpful ways. Optionally, or in combination with the foregoing, a prompt or diagnostic can be displayed. The real-time validation tool 136 can highlight the error in the data-entry field, including with a red box, a dashed red box, a colored underline, a squiggly underline, shading, and the like. The real-time validation tool 136 can also alert the user with a dialog box in a pop-up window, either automatically or only if the user asks for information about the error.
The real-time validation tool 136, for example, can present a dialog box or other presentation manner explaining the error or what type of data is required by the data-entry field. The real-time validation tool 136 can present a short comment that disappears quickly or is only shown if the user moves his cursor or mouse pointer over the data-entry field. The real-time validation tool 136 can also provide additional information on request. Many manners of showing the user that the data is invalid as well as showing information about the error can be used. These ways of notifying the user can be chosen by a developer when creating a custom validation rule. For modeless errors, the real-time validation tool 136 permits the user to proceed, according to the block 912, discussed above. For modal errors, however, the real-time validation tool 136 can present a dialog (block 918). The user then can dismiss the dialog. Once the dialog is dismissed, the real-time validation tool 136 rolls back the invalid entry and enables the user to continue editing the electronic form. This editing can include re-inputting data into the data-entry field (block 920), or editing another data-entry field. Alternatively, the real-time validation tool 136 leaves the error in the document, but will not allow the user to continue editing the document without first correcting the error.
In the block 918, the real-time validation tool 136 presents an alert to notify the user of the invalid entry. This alert is intended to inform the user that the error is important and must be fixed. The alert does not have to be a pop-up window, but should be obvious enough to provide the user with an easy-to-notice notification that the user has entered data causing an error. The alert, in one implementation, is a pop-up window that requires the user to pause in editing the electronic form by making the user click on an “OK” button in the alert. This stops the user mentally, helping the user to notice that he must fix the data-entry field having the error before proceeding. The alert can contain no, little, or extensive information about the error. The information can be presented automatically or after the system 102 receives a request for the information.
After presenting the user with some sort of alert in block 918 (
Through this process 900 of
The example set forth in
The above devices and applications are merely representative, and other known devices and applications may be substituted for or added to those shown in
Exemplary Computing System and Environment.
Computer 1142 further includes a hard disk drive 1156 for reading from and writing to a hard disk (not shown), a magnetic disk drive 1158 for reading from and writing to a removable magnetic disk 1160, and an optical disk drive 1162 for reading from or writing to a removable optical disk 1164 such as a CD ROM or other optical media. The hard disk drive 1156, magnetic disk drive 1158, and optical disk drive 1162 are connected to the bus 1148 by an SCSI interface 1166 or some other appropriate interface. The drives and their associated computer-readable media provide nonvolatile storage of computer-readable instructions, data structures, program modules and other data for computer 1142. Although the exemplary environment described herein employs a hard disk, a removable magnetic disk 1160 and a removable optical disk 1164, it should be appreciated by those skilled in the art that other types of computer-readable media which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks, random access memories (RAMs), read only memories (ROMs), and the like, may also be used in the exemplary operating environment.
A number of program modules may be stored on the hard disk 1156, magnetic disk 1160, optical disk 1164, ROM 1150, or RAM 1152, including an operating system 1170, one or more application programs 1172 (such as the electronic forms application 112), other program modules 1174, and program data 1176. A user may enter commands and information into computer 1142 through input devices such as a keyboard 1178 and a pointing device 1180. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are connected to the processing unit 1144 through an interface 1182 that is coupled to the bus 1148. A monitor 1184 or other type of display device is also connected to the bus 1148 via an interface, such as a video adapter 1186. In addition to the monitor, personal computers typically include other peripheral output devices (not shown) such as speakers and printers.
Computer 1142 commonly operates in a networked environment using logical connections to one or more remote computers, such as a remote computer 1188. The remote computer 1188 may be another personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to computer 1142. The logical connections depicted in
When used in a LAN networking environment, computer 1142 is connected to the local network through a network interface or adapter 1194. When used in a WAN networking environment, computer 1142 typically includes a modem 1196 or other means for establishing communications over the wide area network 1192, such as the Internet. The modem 1196, which may be internal or external, is connected to the bus 1148 via a serial port interface 1168. In a networked environment, program modules depicted relative to the personal computer 1142, or portions thereof, may be stored in the remote memory storage device. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.
Generally, the data processors of computer 1142 are programmed by means of instructions stored at different times in the various computer-readable storage media of the computer. Programs and operating systems are typically distributed, for example, on floppy disks or CD-ROMs. From there, they are installed or loaded into the secondary memory of a computer. At execution, they are loaded at least partially into the computer's primary electronic memory. The invention described herein includes these and other various types of computer-readable storage media when such media contain instructions or programs for implementing the blocks described below in conjunction with a microprocessor or other data processor. The invention also includes the computer itself when programmed according to the methods and techniques described herein.
For purposes of illustration, programs and other executable program components such as the operating system are illustrated herein as discrete blocks, although it is recognized that such programs and components reside at various times in different storage components of the computer, and are executed by the data processor(s) of the computer.
Although the invention has been described in language specific to structural features and/or methodological acts, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claimed invention.
This application is a continuation of U.S. patent application Ser. No. 10/723,863, filed on Nov. 26, 2003, titled “Rendering An HTML Electronic Form By Applying XSLT To XML Using A Solution”, which is a continuation-in-part of U.S. patent application Ser. No. 10/610,504, filed on Jun. 30, 2003, which issued as U.S. Pat. No. 7,197,515 on Mar. 27, 2007, titled “Declarative Solution Definition”, which are both incorporated in their entirety by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4201978 | Nally | May 1980 | A |
| 4498147 | Agnew et al. | Feb 1985 | A |
| 4514800 | Gruner et al. | Apr 1985 | A |
| 4564752 | Lepic et al. | Jan 1986 | A |
| 4641274 | Swank | Feb 1987 | A |
| 4674040 | Barker et al. | Jun 1987 | A |
| 4723211 | Barker et al. | Feb 1988 | A |
| 4739477 | Barker et al. | Apr 1988 | A |
| 4815029 | Barker et al. | Mar 1989 | A |
| 4847749 | Collins et al. | Jul 1989 | A |
| 4910663 | Bailey | Mar 1990 | A |
| 4933880 | Borgendale et al. | Jun 1990 | A |
| 4962475 | Hernandez et al. | Oct 1990 | A |
| 5025484 | Yamanari et al. | Jun 1991 | A |
| 5072412 | Henderson, Jr. et al. | Dec 1991 | A |
| 5179703 | Evans | Jan 1993 | A |
| 5182709 | Makus | Jan 1993 | A |
| 5187786 | Densmore et al. | Feb 1993 | A |
| 5191645 | Carlucci et al. | Mar 1993 | A |
| 5195183 | Miller et al. | Mar 1993 | A |
| 5204947 | Bernstein et al. | Apr 1993 | A |
| 5206951 | Khoyi et al. | Apr 1993 | A |
| 5218672 | Morgan et al. | Jun 1993 | A |
| 5222160 | Sakai et al. | Jun 1993 | A |
| 5228100 | Takeda et al. | Jul 1993 | A |
| 5237680 | Adams et al. | Aug 1993 | A |
| 5249275 | Srivastava | Sep 1993 | A |
| 5274803 | Dubin et al. | Dec 1993 | A |
| 5297249 | Bernstein et al. | Mar 1994 | A |
| 5297283 | Kelly, Jr. et al. | Mar 1994 | A |
| 5313631 | Kao | May 1994 | A |
| 5313646 | Hendricks et al. | May 1994 | A |
| 5317686 | Salas et al. | May 1994 | A |
| 5333317 | Dann | Jul 1994 | A |
| 5339423 | Beitel et al. | Aug 1994 | A |
| 5339424 | Fushimi | Aug 1994 | A |
| 5341478 | Travis, Jr. et al. | Aug 1994 | A |
| 5369766 | Nakano et al. | Nov 1994 | A |
| 5369778 | San Soucie et al. | Nov 1994 | A |
| 5371675 | Greif et al. | Dec 1994 | A |
| 5377323 | Vasudevan | Dec 1994 | A |
| 5379419 | Heffernan et al. | Jan 1995 | A |
| 5381547 | Flug et al. | Jan 1995 | A |
| 5390325 | Miller | Feb 1995 | A |
| 5396623 | McCall et al. | Mar 1995 | A |
| 5408665 | Fitzgerald | Apr 1995 | A |
| 5410646 | Tondevold et al. | Apr 1995 | A |
| 5410688 | Williams et al. | Apr 1995 | A |
| 5412772 | Monson | May 1995 | A |
| 5434975 | Allen | Jul 1995 | A |
| 5436637 | Gayraud et al. | Jul 1995 | A |
| 5438659 | Notess et al. | Aug 1995 | A |
| 5440744 | Jacobson et al. | Aug 1995 | A |
| 5446842 | Schaeffer et al. | Aug 1995 | A |
| 5455875 | Chevion et al. | Oct 1995 | A |
| 5459865 | Heninger et al. | Oct 1995 | A |
| 5481722 | Skinner | Jan 1996 | A |
| 5497489 | Menne | Mar 1996 | A |
| 5504898 | Klein | Apr 1996 | A |
| 5517655 | Collins et al. | May 1996 | A |
| 5535389 | Elder et al. | Jul 1996 | A |
| 5542070 | LeBlanc et al. | Jul 1996 | A |
| 5550976 | Henderson et al. | Aug 1996 | A |
| 5551035 | Arnold et al. | Aug 1996 | A |
| 5555325 | Burger | Sep 1996 | A |
| 5566330 | Sheffield | Oct 1996 | A |
| 5572643 | Judson | Nov 1996 | A |
| 5572648 | Bibayan | Nov 1996 | A |
| 5577252 | Nelson et al. | Nov 1996 | A |
| 5581686 | Koppolu et al. | Dec 1996 | A |
| 5581760 | Atkinson et al. | Dec 1996 | A |
| 5600789 | Parker et al. | Feb 1997 | A |
| 5602996 | Powers, III et al. | Feb 1997 | A |
| 5608720 | Biegel et al. | Mar 1997 | A |
| 5625783 | Ezekiel et al. | Apr 1997 | A |
| 5627979 | Chang et al. | May 1997 | A |
| 5630126 | Redpath | May 1997 | A |
| 5634121 | Tracz et al. | May 1997 | A |
| 5634124 | Khoyi et al. | May 1997 | A |
| 5640544 | Onodera et al. | Jun 1997 | A |
| 5644738 | Goldman et al. | Jul 1997 | A |
| 5649099 | Theimer et al. | Jul 1997 | A |
| 5659729 | Nielsen | Aug 1997 | A |
| 5664178 | Sinofsky | Sep 1997 | A |
| 5668966 | Ono et al. | Sep 1997 | A |
| 5669005 | Curbow et al. | Sep 1997 | A |
| 5682536 | Atkinson et al. | Oct 1997 | A |
| 5689667 | Kurtenbach | Nov 1997 | A |
| 5689703 | Atkinson et al. | Nov 1997 | A |
| 5704029 | Wright, Jr. | Dec 1997 | A |
| 5706501 | Horikiri et al. | Jan 1998 | A |
| 5717939 | Bricklin et al. | Feb 1998 | A |
| 5721824 | Taylor | Feb 1998 | A |
| 5740439 | Atkinson et al. | Apr 1998 | A |
| 5742504 | Meyer et al. | Apr 1998 | A |
| 5745683 | Lee et al. | Apr 1998 | A |
| 5745712 | Turpin et al. | Apr 1998 | A |
| 5748807 | Lopresti et al. | May 1998 | A |
| 5758184 | Lucovsky et al. | May 1998 | A |
| 5758358 | Ebbo | May 1998 | A |
| 5761408 | Kolawa et al. | Jun 1998 | A |
| 5761683 | Logan et al. | Jun 1998 | A |
| 5764984 | Loucks | Jun 1998 | A |
| 5764985 | Smale | Jun 1998 | A |
| 5778372 | Cordell et al. | Jul 1998 | A |
| 5778402 | Gipson | Jul 1998 | A |
| 5784555 | Stone | Jul 1998 | A |
| 5790796 | Sadowsky | Aug 1998 | A |
| 5798757 | Smith | Aug 1998 | A |
| 5801701 | Koppolu et al. | Sep 1998 | A |
| 5802304 | Stone | Sep 1998 | A |
| 5806079 | Rivette et al. | Sep 1998 | A |
| 5815830 | Anthony | Sep 1998 | A |
| 5826265 | Van Huben et al. | Oct 1998 | A |
| 5835777 | Staelin et al. | Nov 1998 | A |
| 5838906 | Doyle et al. | Nov 1998 | A |
| 5842018 | Atkinson et al. | Nov 1998 | A |
| 5845077 | Fawcett | Dec 1998 | A |
| 5845090 | Collins, III et al. | Dec 1998 | A |
| 5854630 | Nielsen | Dec 1998 | A |
| 5859973 | Carpenter et al. | Jan 1999 | A |
| 5862372 | Morris et al. | Jan 1999 | A |
| 5862379 | Rubin et al. | Jan 1999 | A |
| 5864819 | De Armas et al. | Jan 1999 | A |
| 5907704 | Gudmundson et al. | May 1999 | A |
| 5910895 | Proskauer et al. | Jun 1999 | A |
| 5911776 | Guck | Jun 1999 | A |
| 5915112 | Boutcher et al. | Jun 1999 | A |
| 5922072 | Hutchinson et al. | Jul 1999 | A |
| 5928363 | Ruvolo | Jul 1999 | A |
| 5929858 | Shibata et al. | Jul 1999 | A |
| 5940075 | Mutschler, III et al. | Aug 1999 | A |
| 5950010 | Hesse et al. | Sep 1999 | A |
| 5956481 | Walsh et al. | Sep 1999 | A |
| 5960199 | Brodsky et al. | Sep 1999 | A |
| 5963964 | Nielsen | Oct 1999 | A |
| 5973696 | Agranat et al. | Oct 1999 | A |
| 5974454 | Apfel et al. | Oct 1999 | A |
| 5982370 | Kamper | Nov 1999 | A |
| 5983348 | Ji | Nov 1999 | A |
| 5987480 | Donohue et al. | Nov 1999 | A |
| 5991710 | Papineni et al. | Nov 1999 | A |
| 5991731 | Colon et al. | Nov 1999 | A |
| 5991877 | Luckenbaugh | Nov 1999 | A |
| 5995103 | Ashe | Nov 1999 | A |
| 5999740 | Rowley | Dec 1999 | A |
| 6005570 | Gayraud et al. | Dec 1999 | A |
| 6014135 | Fernandes et al. | Jan 2000 | A |
| 6016520 | Facq et al. | Jan 2000 | A |
| 6018743 | Xu | Jan 2000 | A |
| 6026379 | Haller et al. | Feb 2000 | A |
| 6026416 | Kanerva et al. | Feb 2000 | A |
| 6031989 | Cordell | Feb 2000 | A |
| 6035297 | Van Huben et al. | Mar 2000 | A |
| 6035309 | Dauerer et al. | Mar 2000 | A |
| 6044205 | Reed et al. | Mar 2000 | A |
| 6052531 | Waldin et al. | Apr 2000 | A |
| 6052710 | Saliba et al. | Apr 2000 | A |
| 6054987 | Richardson | Apr 2000 | A |
| 6072870 | Nguyen et al. | Jun 2000 | A |
| 6078326 | Kilmer et al. | Jun 2000 | A |
| 6078327 | Liman et al. | Jun 2000 | A |
| 6078924 | Ainsbury et al. | Jun 2000 | A |
| 6081610 | Dwork et al. | Jun 2000 | A |
| 6084585 | Kraft et al. | Jul 2000 | A |
| 6088708 | Burch et al. | Jul 2000 | A |
| 6091417 | Lefkowitz | Jul 2000 | A |
| 6094657 | Hailpern et al. | Jul 2000 | A |
| 6097382 | Rosen et al. | Aug 2000 | A |
| 6098081 | Heidorn et al. | Aug 2000 | A |
| 6108637 | Blumenau | Aug 2000 | A |
| 6108783 | Krawczyk et al. | Aug 2000 | A |
| 6115646 | Fiszman et al. | Sep 2000 | A |
| 6121965 | Kenney et al. | Sep 2000 | A |
| 6122647 | Horowitz et al. | Sep 2000 | A |
| 6144969 | Inokuchi et al. | Nov 2000 | A |
| 6151624 | Teare et al. | Nov 2000 | A |
| 6154128 | Wookey et al. | Nov 2000 | A |
| 6163772 | Kramer et al. | Dec 2000 | A |
| 6167521 | Smith et al. | Dec 2000 | A |
| 6167523 | Strong | Dec 2000 | A |
| 6182094 | Humpleman et al. | Jan 2001 | B1 |
| 6182095 | Leymaster et al. | Jan 2001 | B1 |
| 6188401 | Peyer | Feb 2001 | B1 |
| 6191797 | Politis | Feb 2001 | B1 |
| 6192367 | Hawley et al. | Feb 2001 | B1 |
| 6195661 | Filepp et al. | Feb 2001 | B1 |
| 6199204 | Donohue | Mar 2001 | B1 |
| 6209128 | Gerard et al. | Mar 2001 | B1 |
| 6216152 | Wong et al. | Apr 2001 | B1 |
| 6219698 | Iannucci et al. | Apr 2001 | B1 |
| 6225996 | Gibb et al. | May 2001 | B1 |
| 6235027 | Herzon | May 2001 | B1 |
| 6253366 | Mutschler, III | Jun 2001 | B1 |
| 6253374 | Dresevic et al. | Jun 2001 | B1 |
| 6263313 | Milsted et al. | Jul 2001 | B1 |
| 6266810 | Tanaka et al. | Jul 2001 | B1 |
| 6268852 | Lindhorst et al. | Jul 2001 | B1 |
| 6272506 | Bell | Aug 2001 | B1 |
| 6275227 | DeStefano | Aug 2001 | B1 |
| 6275599 | Adler et al. | Aug 2001 | B1 |
| 6279042 | Ouchi | Aug 2001 | B1 |
| 6281896 | Allmpich et al. | Aug 2001 | B1 |
| 6282711 | Halpern et al. | Aug 2001 | B1 |
| 6286033 | Kishinsky et al. | Sep 2001 | B1 |
| 6292897 | Gennaro et al. | Sep 2001 | B1 |
| 6297819 | Furst | Oct 2001 | B1 |
| 6300948 | Geller et al. | Oct 2001 | B1 |
| 6307955 | Zank et al. | Oct 2001 | B1 |
| 6308179 | Petersen et al. | Oct 2001 | B1 |
| 6308273 | Goertzel et al. | Oct 2001 | B1 |
| 6311271 | Gennaro et al. | Oct 2001 | B1 |
| 6314415 | Mukherjee | Nov 2001 | B1 |
| 6321259 | Ouellette et al. | Nov 2001 | B1 |
| 6321334 | Jerger et al. | Nov 2001 | B1 |
| 6327628 | Anuff et al. | Dec 2001 | B1 |
| 6331864 | Coco et al. | Dec 2001 | B1 |
| 6342907 | Petty et al. | Jan 2002 | B1 |
| 6343149 | Motoiwa | Jan 2002 | B1 |
| 6343302 | Graham | Jan 2002 | B1 |
| 6345256 | Milsted et al. | Feb 2002 | B1 |
| 6345278 | Hitchcock et al. | Feb 2002 | B1 |
| 6345361 | Jerger et al. | Feb 2002 | B1 |
| 6347323 | Garber et al. | Feb 2002 | B1 |
| 6349408 | Smith | Feb 2002 | B1 |
| 6351574 | Yair et al. | Feb 2002 | B1 |
| 6353851 | Anupam et al. | Mar 2002 | B1 |
| 6353926 | Parthesarathy et al. | Mar 2002 | B1 |
| 6356906 | Lippert et al. | Mar 2002 | B1 |
| 6357038 | Scouten | Mar 2002 | B1 |
| 6366907 | Fanning et al. | Apr 2002 | B1 |
| 6366912 | Wallent et al. | Apr 2002 | B1 |
| 6367013 | Bisbee et al. | Apr 2002 | B1 |
| 6369840 | Barnett et al. | Apr 2002 | B1 |
| 6369841 | Salomon et al. | Apr 2002 | B1 |
| 6374402 | Schmeidler et al. | Apr 2002 | B1 |
| 6381742 | Forbes et al. | Apr 2002 | B2 |
| 6381743 | Mutschler, III | Apr 2002 | B1 |
| 6389434 | Rivette et al. | May 2002 | B1 |
| 6393456 | Ambler et al. | May 2002 | B1 |
| 6396488 | Simmons et al. | May 2002 | B1 |
| 6405221 | Levine et al. | Jun 2002 | B1 |
| 6408311 | Baisley et al. | Jun 2002 | B1 |
| 6414700 | Kurtenbach et al. | Jul 2002 | B1 |
| 6421070 | Ramos et al. | Jul 2002 | B1 |
| 6421656 | Cheng et al. | Jul 2002 | B1 |
| 6425125 | Fries et al. | Jul 2002 | B1 |
| 6429885 | Saib et al. | Aug 2002 | B1 |
| 6434563 | Pasquali et al. | Aug 2002 | B1 |
| 6434564 | Ebert | Aug 2002 | B2 |
| 6442563 | Bacon et al. | Aug 2002 | B1 |
| 6442755 | Lemmons et al. | Aug 2002 | B1 |
| 6446110 | Lection et al. | Sep 2002 | B1 |
| 6449617 | Quinn et al. | Sep 2002 | B1 |
| 6457009 | Bollay | Sep 2002 | B1 |
| 6460058 | Koppolu et al. | Oct 2002 | B2 |
| 6463419 | Kluss | Oct 2002 | B1 |
| 6470349 | Heninger et al. | Oct 2002 | B1 |
| 6473800 | Jerger et al. | Oct 2002 | B1 |
| 6476828 | Burkett et al. | Nov 2002 | B1 |
| 6476833 | Moshfeghi | Nov 2002 | B1 |
| 6477544 | Bolosky et al. | Nov 2002 | B1 |
| 6480860 | Monday | Nov 2002 | B1 |
| 6487566 | Sundaresan | Nov 2002 | B1 |
| 6490601 | Markus et al. | Dec 2002 | B1 |
| 6493702 | Adar et al. | Dec 2002 | B1 |
| 6501864 | Eguchi et al. | Dec 2002 | B1 |
| 6502101 | Verprauskus et al. | Dec 2002 | B1 |
| 6502103 | Frey et al. | Dec 2002 | B1 |
| 6505230 | Mohan et al. | Jan 2003 | B1 |
| 6505300 | Chan et al. | Jan 2003 | B2 |
| 6507856 | Chen et al. | Jan 2003 | B1 |
| 6516322 | Meredith et al. | Feb 2003 | B1 |
| 6519617 | Wanderski et al. | Feb 2003 | B1 |
| RE38070 | Spies et al. | Apr 2003 | E |
| 6546546 | Van Doorn | Apr 2003 | B1 |
| 6549221 | Brown et al. | Apr 2003 | B1 |
| 6549878 | Lowry et al. | Apr 2003 | B1 |
| 6549922 | Srivastava et al. | Apr 2003 | B1 |
| 6553402 | Makarios et al. | Apr 2003 | B1 |
| 6560616 | Garber | May 2003 | B1 |
| 6560620 | Ching | May 2003 | B1 |
| 6560640 | Smethers | May 2003 | B2 |
| 6563514 | Samar | May 2003 | B1 |
| 6571253 | Thompson et al. | May 2003 | B1 |
| 6578144 | Gennaro et al. | Jun 2003 | B1 |
| 6581061 | Graham | Jun 2003 | B2 |
| 6584469 | Chiang et al. | Jun 2003 | B1 |
| 6584548 | Bourne et al. | Jun 2003 | B1 |
| 6585778 | Hind et al. | Jul 2003 | B1 |
| 6589290 | Maxwell et al. | Jul 2003 | B1 |
| 6594686 | Edwards et al. | Jul 2003 | B1 |
| 6598219 | Lau | Jul 2003 | B1 |
| 6603489 | Edlund et al. | Aug 2003 | B1 |
| 6604099 | Chung et al. | Aug 2003 | B1 |
| 6606606 | Starr | Aug 2003 | B2 |
| 6609200 | Anderson et al. | Aug 2003 | B2 |
| 6611822 | Beams et al. | Aug 2003 | B1 |
| 6611840 | Baer et al. | Aug 2003 | B1 |
| 6611843 | Jacobs | Aug 2003 | B1 |
| 6613098 | Sorge et al. | Sep 2003 | B1 |
| 6615276 | Mastrianni et al. | Sep 2003 | B1 |
| 6629109 | Koshisaka | Sep 2003 | B1 |
| 6631357 | Perkowski | Oct 2003 | B1 |
| 6631379 | Cox | Oct 2003 | B2 |
| 6631497 | Jamshidi et al. | Oct 2003 | B1 |
| 6631519 | Nicholson et al. | Oct 2003 | B1 |
| 6632251 | Rutten et al. | Oct 2003 | B1 |
| 6635089 | Burkett et al. | Oct 2003 | B1 |
| 6636845 | Chau et al. | Oct 2003 | B2 |
| 6643633 | Chau et al. | Nov 2003 | B2 |
| 6643652 | Helgeson et al. | Nov 2003 | B2 |
| 6643684 | Malkin et al. | Nov 2003 | B1 |
| 6651217 | Kennedy et al. | Nov 2003 | B1 |
| 6654737 | Nunez | Nov 2003 | B1 |
| 6654932 | Bahrs et al. | Nov 2003 | B1 |
| 6658417 | Stakutis et al. | Dec 2003 | B1 |
| 6658622 | Aiken et al. | Dec 2003 | B1 |
| 6661920 | Skinner | Dec 2003 | B1 |
| 6668369 | Krebs et al. | Dec 2003 | B1 |
| 6671805 | Brown et al. | Dec 2003 | B1 |
| 6675202 | Perttunen | Jan 2004 | B1 |
| 6678717 | Schneider | Jan 2004 | B1 |
| 6681370 | Lawrence et al. | Jan 2004 | B2 |
| 6691230 | Bardon | Feb 2004 | B1 |
| 6691281 | Sorge et al. | Feb 2004 | B1 |
| 6697944 | Jones et al. | Feb 2004 | B1 |
| 6701434 | Rohatgi | Mar 2004 | B1 |
| 6701486 | Weber et al. | Mar 2004 | B1 |
| 6704906 | Yankovich et al. | Mar 2004 | B1 |
| 6711679 | Guski et al. | Mar 2004 | B1 |
| 6720985 | Lapstun et al. | Apr 2004 | B1 |
| 6725426 | Pavlov | Apr 2004 | B1 |
| 6728755 | de Ment | Apr 2004 | B1 |
| 6735721 | Morrow et al. | May 2004 | B1 |
| 6745367 | Bates et al. | Jun 2004 | B1 |
| 6748385 | Rodkin et al. | Jun 2004 | B1 |
| 6751777 | Bates et al. | Jun 2004 | B2 |
| 6754874 | Richman | Jun 2004 | B1 |
| 6757826 | Paltenghe | Jun 2004 | B1 |
| 6757868 | Glaser et al. | Jun 2004 | B1 |
| 6760723 | Oshinsky et al. | Jul 2004 | B2 |
| 6763343 | Brooke et al. | Jul 2004 | B1 |
| 6772139 | Smith, III | Aug 2004 | B1 |
| 6772165 | O'Carroll | Aug 2004 | B2 |
| 6774926 | Ellis et al. | Aug 2004 | B1 |
| 6779154 | Nussbaum et al. | Aug 2004 | B1 |
| 6781609 | Barker et al. | Aug 2004 | B1 |
| 6782144 | Bellavita et al. | Aug 2004 | B2 |
| 6799299 | Li et al. | Sep 2004 | B1 |
| 6801929 | Donoho et al. | Oct 2004 | B1 |
| 6816849 | Halt, Jr. | Nov 2004 | B1 |
| 6845380 | Su et al. | Jan 2005 | B2 |
| 6845499 | Srivastava et al. | Jan 2005 | B2 |
| 6847387 | Roth | Jan 2005 | B2 |
| 6848078 | Birsan et al. | Jan 2005 | B1 |
| 6871220 | Rajan et al. | Mar 2005 | B1 |
| 6874130 | Baweja et al. | Mar 2005 | B1 |
| 6876996 | Czajkowski et al. | Apr 2005 | B2 |
| 6889359 | Conner et al. | May 2005 | B1 |
| 6901403 | Bata et al. | May 2005 | B1 |
| 6915454 | Moore et al. | Jul 2005 | B1 |
| 6931532 | Davis et al. | Aug 2005 | B1 |
| 6941510 | Ozzie et al. | Sep 2005 | B1 |
| 6941511 | Hind et al. | Sep 2005 | B1 |
| 6941521 | Lin et al. | Sep 2005 | B2 |
| 6948129 | Loghmani | Sep 2005 | B1 |
| 6948133 | Haley | Sep 2005 | B2 |
| 6948135 | Ruthfield et al. | Sep 2005 | B1 |
| 6950980 | Malcolm | Sep 2005 | B1 |
| 6961897 | Peel, Jr. et al. | Nov 2005 | B1 |
| 6963875 | Moore et al. | Nov 2005 | B2 |
| 6968503 | Chang et al. | Nov 2005 | B1 |
| 6968505 | Stoll et al. | Nov 2005 | B2 |
| 6993714 | Kaler et al. | Jan 2006 | B2 |
| 6996776 | Makely et al. | Feb 2006 | B1 |
| 6996781 | Myers et al. | Feb 2006 | B1 |
| 7000179 | Yankovich et al. | Feb 2006 | B2 |
| 7002560 | Graham | Feb 2006 | B2 |
| 7003722 | Rothchiller et al. | Feb 2006 | B2 |
| 7010580 | Fu et al. | Mar 2006 | B1 |
| 7020869 | Abriari et al. | Mar 2006 | B2 |
| 7024417 | Russakovsky et al. | Apr 2006 | B1 |
| 7032170 | Poulose et al. | Apr 2006 | B2 |
| 7036072 | Sulistio et al. | Apr 2006 | B1 |
| 7039875 | Khalfay et al. | May 2006 | B2 |
| 7051273 | Holt et al. | May 2006 | B1 |
| 7058663 | Johnston et al. | Jun 2006 | B2 |
| 7062764 | Cohen et al. | Jun 2006 | B2 |
| 7065493 | Homsi | Jun 2006 | B1 |
| 7080083 | Kim et al. | Jul 2006 | B2 |
| 7080325 | Treibach-Heck et al. | Jul 2006 | B2 |
| 7086009 | Resnick et al. | Aug 2006 | B2 |
| 7086042 | Abe et al. | Aug 2006 | B2 |
| 7088374 | David et al. | Aug 2006 | B2 |
| 7100147 | Miller et al. | Aug 2006 | B2 |
| 7103611 | Murthy et al. | Sep 2006 | B2 |
| 7106888 | Silverbrook et al. | Sep 2006 | B1 |
| 7107282 | Yalamanchi | Sep 2006 | B1 |
| 7107521 | Santos | Sep 2006 | B2 |
| 7146564 | Kim et al. | Dec 2006 | B2 |
| 7152205 | Day et al. | Dec 2006 | B2 |
| 7168035 | Bell et al. | Jan 2007 | B1 |
| 7178166 | Taylor et al. | Feb 2007 | B1 |
| 7190376 | Tonisson | Mar 2007 | B1 |
| 7191394 | Ardeleanu et al. | Mar 2007 | B1 |
| 7213200 | Abe et al. | May 2007 | B2 |
| 7236982 | Zlatanov et al. | Jun 2007 | B2 |
| 7272789 | O'Brien | Sep 2007 | B2 |
| 7281018 | Begun et al. | Oct 2007 | B1 |
| 7296017 | Larcheveque et al. | Nov 2007 | B2 |
| 7313758 | Kozlov | Dec 2007 | B2 |
| 7316003 | Dulepet et al. | Jan 2008 | B1 |
| 7318237 | Moriconi et al. | Jan 2008 | B2 |
| 7334178 | Aulagnier | Feb 2008 | B1 |
| 7346610 | Ruthfield et al. | Mar 2008 | B2 |
| 7350141 | Kotler et al. | Mar 2008 | B2 |
| 20010007109 | Lange | Jul 2001 | A1 |
| 20010022592 | Alimpich et al. | Sep 2001 | A1 |
| 20010024195 | Hayakawa | Sep 2001 | A1 |
| 20010037345 | Kiernan et al. | Nov 2001 | A1 |
| 20010054004 | Powers | Dec 2001 | A1 |
| 20010056429 | Moore et al. | Dec 2001 | A1 |
| 20010056460 | Sahota et al. | Dec 2001 | A1 |
| 20020010700 | Wotring | Jan 2002 | A1 |
| 20020010743 | Ryan et al. | Jan 2002 | A1 |
| 20020010746 | Jilk et al. | Jan 2002 | A1 |
| 20020013788 | Pennell et al. | Jan 2002 | A1 |
| 20020019941 | Chan et al. | Feb 2002 | A1 |
| 20020023113 | Hsing et al. | Feb 2002 | A1 |
| 20020026441 | Kutay et al. | Feb 2002 | A1 |
| 20020026461 | Kutay et al. | Feb 2002 | A1 |
| 20020032590 | Anand et al. | Mar 2002 | A1 |
| 20020032692 | Suzuki et al. | Mar 2002 | A1 |
| 20020032706 | Perla et al. | Mar 2002 | A1 |
| 20020032768 | Voskuil | Mar 2002 | A1 |
| 20020035579 | Wang et al. | Mar 2002 | A1 |
| 20020035581 | Reynar et al. | Mar 2002 | A1 |
| 20020040469 | Pramberger | Apr 2002 | A1 |
| 20020049790 | Ricker et al. | Apr 2002 | A1 |
| 20020054126 | Gamon | May 2002 | A1 |
| 20020057297 | Grimes et al. | May 2002 | A1 |
| 20020065798 | Bostleman et al. | May 2002 | A1 |
| 20020065847 | Furukawa et al. | May 2002 | A1 |
| 20020070973 | Croley | Jun 2002 | A1 |
| 20020078074 | Cho et al. | Jun 2002 | A1 |
| 20020078103 | Gorman et al. | Jun 2002 | A1 |
| 20020083318 | Larose | Jun 2002 | A1 |
| 20020099952 | Lambert et al. | Jul 2002 | A1 |
| 20020100027 | Binding et al. | Jul 2002 | A1 |
| 20020112224 | Cox | Aug 2002 | A1 |
| 20020129056 | Conant et al. | Sep 2002 | A1 |
| 20020133484 | Chau et al. | Sep 2002 | A1 |
| 20020152222 | Holbrook | Oct 2002 | A1 |
| 20020152244 | Dean et al. | Oct 2002 | A1 |
| 20020156772 | Chau et al. | Oct 2002 | A1 |
| 20020156846 | Rawat et al. | Oct 2002 | A1 |
| 20020156929 | Hekmatpour | Oct 2002 | A1 |
| 20020169752 | Kusama et al. | Nov 2002 | A1 |
| 20020169789 | Kutay et al. | Nov 2002 | A1 |
| 20020174147 | Wang et al. | Nov 2002 | A1 |
| 20020174417 | Sijacic et al. | Nov 2002 | A1 |
| 20020178380 | Wolf et al. | Nov 2002 | A1 |
| 20020184219 | Preisig et al. | Dec 2002 | A1 |
| 20020188597 | Kern et al. | Dec 2002 | A1 |
| 20020188613 | Chakraborty et al. | Dec 2002 | A1 |
| 20020194219 | Bradley et al. | Dec 2002 | A1 |
| 20020196281 | Audleman et al. | Dec 2002 | A1 |
| 20020196288 | Emrani | Dec 2002 | A1 |
| 20020198891 | Li et al. | Dec 2002 | A1 |
| 20020198935 | Crandall et al. | Dec 2002 | A1 |
| 20030004951 | Chokshi | Jan 2003 | A1 |
| 20030007000 | Carlson et al. | Jan 2003 | A1 |
| 20030014397 | Chau et al. | Jan 2003 | A1 |
| 20030018668 | Britton et al. | Jan 2003 | A1 |
| 20030020746 | Chen et al. | Jan 2003 | A1 |
| 20030023641 | Gorman et al. | Jan 2003 | A1 |
| 20030025732 | Prichard | Feb 2003 | A1 |
| 20030026507 | Zlotnick | Feb 2003 | A1 |
| 20030028550 | Lee et al. | Feb 2003 | A1 |
| 20030037303 | Bodlaender et al. | Feb 2003 | A1 |
| 20030043986 | Creamer et al. | Mar 2003 | A1 |
| 20030046665 | Ilin | Mar 2003 | A1 |
| 20030048301 | Menninger | Mar 2003 | A1 |
| 20030051243 | Lemmons et al. | Mar 2003 | A1 |
| 20030055811 | Stork et al. | Mar 2003 | A1 |
| 20030055828 | Koch et al. | Mar 2003 | A1 |
| 20030056198 | Al-Azzawe et al. | Mar 2003 | A1 |
| 20030061386 | Brown | Mar 2003 | A1 |
| 20030061567 | Brown et al. | Mar 2003 | A1 |
| 20030084424 | Reddy et al. | May 2003 | A1 |
| 20030093755 | O'Carroll | May 2003 | A1 |
| 20030110443 | Yankovich et al. | Jun 2003 | A1 |
| 20030120578 | Newman | Jun 2003 | A1 |
| 20030120651 | Bernstein et al. | Jun 2003 | A1 |
| 20030120659 | Sridhar | Jun 2003 | A1 |
| 20030120671 | Kim et al. | Jun 2003 | A1 |
| 20030120686 | Kim et al. | Jun 2003 | A1 |
| 20030126555 | Aggarwal et al. | Jul 2003 | A1 |
| 20030128196 | Lapstun et al. | Jul 2003 | A1 |
| 20030135825 | Gertner et al. | Jul 2003 | A1 |
| 20030140132 | Champagne et al. | Jul 2003 | A1 |
| 20030158897 | Ben-Natan et al. | Aug 2003 | A1 |
| 20030163285 | Nakamura et al. | Aug 2003 | A1 |
| 20030167277 | Hejlsberg et al. | Sep 2003 | A1 |
| 20030182268 | Lal | Sep 2003 | A1 |
| 20030182327 | Ramanujam et al. | Sep 2003 | A1 |
| 20030187756 | Klivington et al. | Oct 2003 | A1 |
| 20030187930 | Ghaffar et al. | Oct 2003 | A1 |
| 20030188260 | Jensen et al. | Oct 2003 | A1 |
| 20030189593 | Yarvin | Oct 2003 | A1 |
| 20030192008 | Lee | Oct 2003 | A1 |
| 20030200506 | Abe et al. | Oct 2003 | A1 |
| 20030204511 | Brundage | Oct 2003 | A1 |
| 20030204814 | Elo et al. | Oct 2003 | A1 |
| 20030205615 | Marappan | Nov 2003 | A1 |
| 20030212664 | Breining et al. | Nov 2003 | A1 |
| 20030212902 | van der Made | Nov 2003 | A1 |
| 20030217053 | Bachman et al. | Nov 2003 | A1 |
| 20030220930 | Milleker et al. | Nov 2003 | A1 |
| 20030225469 | DeRemer et al. | Dec 2003 | A1 |
| 20030225768 | Chaudhuri | Dec 2003 | A1 |
| 20030225829 | Pena et al. | Dec 2003 | A1 |
| 20030226132 | Tondreau et al. | Dec 2003 | A1 |
| 20030233374 | Spinola et al. | Dec 2003 | A1 |
| 20030233644 | Cohen et al. | Dec 2003 | A1 |
| 20030236859 | Vaschillo et al. | Dec 2003 | A1 |
| 20030236903 | Piotrowski | Dec 2003 | A1 |
| 20030237046 | Parker | Dec 2003 | A1 |
| 20030237047 | Borson | Dec 2003 | A1 |
| 20040002939 | Arora | Jan 2004 | A1 |
| 20040003031 | Brown et al. | Jan 2004 | A1 |
| 20040003353 | Rivera et al. | Jan 2004 | A1 |
| 20040003389 | Reynar et al. | Jan 2004 | A1 |
| 20040010752 | Chan et al. | Jan 2004 | A1 |
| 20040024842 | Witt | Feb 2004 | A1 |
| 20040030991 | Hepworth et al. | Feb 2004 | A1 |
| 20040039990 | Bakar et al. | Feb 2004 | A1 |
| 20040039993 | Kougiouris et al. | Feb 2004 | A1 |
| 20040044961 | Pesenson | Mar 2004 | A1 |
| 20040044965 | Toyama et al. | Mar 2004 | A1 |
| 20040054966 | Busch et al. | Mar 2004 | A1 |
| 20040059754 | Barghout et al. | Mar 2004 | A1 |
| 20040073565 | Kaufman et al. | Apr 2004 | A1 |
| 20040073868 | Easter et al. | Apr 2004 | A1 |
| 20040078756 | Napper et al. | Apr 2004 | A1 |
| 20040083426 | Sahu | Apr 2004 | A1 |
| 20040088647 | Miller et al. | May 2004 | A1 |
| 20040088652 | Abe et al. | May 2004 | A1 |
| 20040093596 | Koyano | May 2004 | A1 |
| 20040107367 | Kisters | Jun 2004 | A1 |
| 20040117769 | Lauzon | Jun 2004 | A1 |
| 20040123277 | Schrader et al. | Jun 2004 | A1 |
| 20040146199 | Berkner et al. | Jul 2004 | A1 |
| 20040163041 | Engel | Aug 2004 | A1 |
| 20040172442 | Ripley | Sep 2004 | A1 |
| 20040181711 | Johnson et al. | Sep 2004 | A1 |
| 20040186762 | Beaven et al. | Sep 2004 | A1 |
| 20040189716 | Paoli et al. | Sep 2004 | A1 |
| 20040194035 | Chakraborty | Sep 2004 | A1 |
| 20040205473 | Fisher et al. | Oct 2004 | A1 |
| 20040205525 | Murren et al. | Oct 2004 | A1 |
| 20040205534 | Koelle | Oct 2004 | A1 |
| 20040205571 | Adler et al. | Oct 2004 | A1 |
| 20040205592 | Huang | Oct 2004 | A1 |
| 20040205605 | Adler et al. | Oct 2004 | A1 |
| 20040205653 | Hadfield et al. | Oct 2004 | A1 |
| 20040205671 | Sukehiro et al. | Oct 2004 | A1 |
| 20040210599 | Friedman et al. | Oct 2004 | A1 |
| 20040221238 | Cifra et al. | Nov 2004 | A1 |
| 20040221245 | Chickles et al. | Nov 2004 | A1 |
| 20040237030 | Malkin | Nov 2004 | A1 |
| 20040261019 | Imamura et al. | Dec 2004 | A1 |
| 20040268229 | Paoli et al. | Dec 2004 | A1 |
| 20050004893 | Sangroniz | Jan 2005 | A1 |
| 20050005248 | Rockey et al. | Jan 2005 | A1 |
| 20050015279 | Rucker | Jan 2005 | A1 |
| 20050015732 | Vedula et al. | Jan 2005 | A1 |
| 20050022115 | Baumgartner et al. | Jan 2005 | A1 |
| 20050027757 | Kiessig et al. | Feb 2005 | A1 |
| 20050033728 | James et al. | Feb 2005 | A1 |
| 20050038711 | Marlelo | Feb 2005 | A1 |
| 20050055627 | Lloyd et al. | Mar 2005 | A1 |
| 20050060324 | Johnson et al. | Mar 2005 | A1 |
| 20050060721 | Choudhary et al. | Mar 2005 | A1 |
| 20050065933 | Goering | Mar 2005 | A1 |
| 20050065936 | Goering | Mar 2005 | A1 |
| 20050066287 | Tattrie et al. | Mar 2005 | A1 |
| 20050071752 | Marlatt | Mar 2005 | A1 |
| 20050076049 | Qubti et al. | Apr 2005 | A1 |
| 20050091285 | Krishnan et al. | Apr 2005 | A1 |
| 20050091305 | Lange et al. | Apr 2005 | A1 |
| 20050102370 | Lin et al. | May 2005 | A1 |
| 20050102612 | Allan et al. | May 2005 | A1 |
| 20050108104 | Woo | May 2005 | A1 |
| 20050108624 | Carrier | May 2005 | A1 |
| 20050114757 | Sahota et al. | May 2005 | A1 |
| 20050132196 | Dietl | Jun 2005 | A1 |
| 20050138086 | Pecht-Seibert | Jun 2005 | A1 |
| 20050138539 | Bravery et al. | Jun 2005 | A1 |
| 20050171746 | Thalhammer-Reyero | Aug 2005 | A1 |
| 20050198086 | Moore et al. | Sep 2005 | A1 |
| 20050198125 | Beck et al. | Sep 2005 | A1 |
| 20050198247 | Perry et al. | Sep 2005 | A1 |
| 20050210263 | Levas et al. | Sep 2005 | A1 |
| 20050223063 | Chang et al. | Oct 2005 | A1 |
| 20050223320 | Brintzenhofe et al. | Oct 2005 | A1 |
| 20050246304 | Knight et al. | Nov 2005 | A1 |
| 20050268222 | Cheng | Dec 2005 | A1 |
| 20060020586 | Prompt et al. | Jan 2006 | A1 |
| 20060026534 | Ruthfield et al. | Feb 2006 | A1 |
| 20060031757 | Vincent, III | Feb 2006 | A9 |
| 20060036995 | Chickles et al. | Feb 2006 | A1 |
| 20060041838 | Khan | Feb 2006 | A1 |
| 20060059434 | Boss et al. | Mar 2006 | A1 |
| 20060069605 | Hatoun | Mar 2006 | A1 |
| 20060069985 | Friedman et al. | Mar 2006 | A1 |
| 20060080657 | Goodman | Apr 2006 | A1 |
| 20060085409 | Rys et al. | Apr 2006 | A1 |
| 20060101037 | Brill et al. | May 2006 | A1 |
| 20060101051 | Carr et al. | May 2006 | A1 |
| 20060129978 | Abrari et al. | Jun 2006 | A1 |
| 20060143220 | Spencer, Jr. | Jun 2006 | A1 |
| 20060161559 | Bordawekar et al. | Jul 2006 | A1 |
| 20060191662 | Deibl et al. | Aug 2006 | A1 |
| 20060200754 | Kablesh et al. | Sep 2006 | A1 |
| 20060203081 | Pulitzer | Sep 2006 | A1 |
| 20070036433 | Teutsch et al. | Feb 2007 | A1 |
| 20070050719 | Lui et al. | Mar 2007 | A1 |
| 20070061467 | Essey et al. | Mar 2007 | A1 |
| 20070061706 | Cupala et al. | Mar 2007 | A1 |
| 20070074106 | Ardeleanu et al. | Mar 2007 | A1 |
| 20070094589 | Paoli et al. | Apr 2007 | A1 |
| 20070100877 | Paoli et al. | May 2007 | A1 |
| 20070101280 | Paoli | May 2007 | A1 |
| 20070118803 | Walker et al. | May 2007 | A1 |
| 20070130504 | Betancourt et al. | Jun 2007 | A1 |
| 20070186157 | Walker et al. | Aug 2007 | A1 |
| 20070208606 | Mackay et al. | Sep 2007 | A1 |
| 20070208769 | Boehm et al. | Sep 2007 | A1 |
| 20080028340 | Davis | Jan 2008 | A1 |
| Number | Date | Country |
|---|---|---|
| 0841615 | May 1998 | EP |
| 0961197 | Dec 1999 | EP |
| 1076290 | Feb 2001 | EP |
| 1221661 | Jul 2002 | EP |
| 401173140 | Jul 1989 | JP |
| 4225466 | Aug 1992 | JP |
| 406014105 | Jan 1994 | JP |
| 2000132436 | May 2000 | JP |
| 2002183652 | Jun 2002 | JP |
| 2003173288 | Jun 2003 | JP |
| 3191429 | Jul 2003 | JP |
| WO9924945 | May 1999 | WO |
| WO9956207 | Nov 1999 | WO |
| WO0144934 | Jun 2001 | WO |
| WO0157720 | Aug 2001 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20090044103 A1 | Feb 2009 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 10723863 | Nov 2003 | US |
| Child | 12249973 | US |
