Source: http://www.google.com.tw/patents/US8074217
Timestamp: 2013-05-22 13:09:24
Document Index: 606019639

Matched Legal Cases: ['Application No. 00306806', 'Application No. 97307138', 'Application No. 06111546', 'Application No. 200610051554', 'Application No. 01935325', 'Application No. 2002', 'Application No. 10012887', 'Application No. 2006103267', 'Application No. 2006105526', 'Application No. 2412611', 'Application No. 2002', 'Application No. 2006200285', 'Application No. 2408313', 'Application No. 2408527', 'Application No. 2412611', 'Application No. 01935325', 'Application No. 01939034', 'Application No. 01939368', 'Application No. 2002', 'Application No. 2002', 'Application No. 2002', 'Application No. 2002', 'Application No. 2002', 'Application No. 2006', 'Application No. 2006', 'Application No. 2006103267', 'Application No. 2006105526', 'Application No. 2006105526', 'Application No. 01813138', 'Application No. 04779161', 'art 1']

�M�Q US8074217 - Methods and systems for delivering software - Google �M�Q�j�M �Ϥ� �a�� Play YouTube �s�D Gmail ���ݵw�� ��h »�i���M�Q�j�M | �������� | �n�J�i���M�Q�j�M�M�QMethods and systems for software delivery are described. In one embodiment, an extension definition catalog structure is defined and can be used to select one or more software extensions for incorporation on a computing device. At least one software extension is identified using a uniform resource name...http://www.google.com.tw/patents/US8074217?utm_source=gb-gplus-share�M�Q US8074217 - Methods and systems for delivering software���}��US8074217 B2�X���������v�ӽЮѽs��11/927,296�o�G���2011�~12��6���ӽФ��2007�~10��29�� �u���v���2000�~6��21����L���}�M�Q��US6883168US7743063US7779027US20050033728US20050131971US20080134162�o��HSarita M. JamesJohn A. LicataSuryanarayanan V. RamanLawrence M. SanchezBrian J. Syme��M�Q�v�HMicrosoft Corporation ���M�Q������717/175717/178717/169717/173��ڱM�Q������G06F9/455G06F17/30G06F9/445G06F9/44G06F7/00 �X�@����G06F8/60G06F9/44526G06F9/44521 �ڬw������G06F 8/60G06F 9/445LG06F 9/445L2�ѦҤ��m�M�Q�ޥ� (115)�D�M�Q�ޥ� (471)�Q�H�U�M�Q�ޥ� (4)�~���s�����M�Q�ӼЧ� ���M�Q�ӼЧ��M�Q����T�� �ڬw�M�Q��Methods and systems for delivering softwareUS 8074217 B2�K�n Methods and systems for software delivery are described. In one embodiment, an extension definition catalog structure is defined and can be used to select one or more software extensions for incorporation on a computing device. At least one software extension is identified using a uniform resource name and, for the one software extension, at least one instance of the software extension is identified using a uniform resource name. For the one instance of the software extension, a uniform resource locator can be used to select the instance.
9. The computer-readable media devices of claim 8, wherein requests from the individual attachment managers comprise predicate chains that the attachment point manager uses to create and build a set of attachment points. ����
U.S. patent application Ser. No. 09/599,298, now U.S. Pat. No. 7,346,848, entitled ��Single Window Navigation Methods and Systems��;
U.S. patent application Ser. No. 09/599,806, now U.S. Pat. No. 6,948,135, entitled ��Methods and Systems of Providing Information to Computer Users��;
U.S. patent application Ser. No. 09/599,048, now U.S. Pat. No. 7,000,230, entitled ��Network-based Software Extensions��;
U.S. patent application Ser. No. 09/599,813, now U.S. Pat. No. 7,191,394, entitled ��Authoring Arbitrary XML Documents Using DHTML and XSLT��;
U.S. patent application Ser. No. 09/599,812, now U.S. Pat. No. 6,874,143, entitled ��Architectures For And Methods Of Providing Network-based Software Extensions��;
U.S. patent application Ser. No. 09/599,086, now U.S. Pat. No. 7,624,356, entitled ��Task Sensitive Methods And Systems For Displaying Command Sets��.
The methods and systems described just below provide a mechanism by which software can be delivered over a network, such as the Internet. In one specific example, various functionalities can be added dynamically to an application program. The functionalities or ��extensions�� as they will be referred to, can be advantageously added via a network such as the Internet. Extensions, which can be associated with various levels of granularity, can be added using only a Web URL as a basis for extension installation. That is, all of the files that comprise an extension can be maintained on the Web and accessed via one or more Web sites.
Consider for example, FIG. 1 which shows a user's computer 100 and several so-called extension sources 102, 104, and 106. The extension sources can comprise any entity from which a software extension can be obtained via a network. In an exemplary implementation, the network can comprise the Internet, although other networks (e.g. LANs and WANs) can certainly be utilized. Extension sources can include, without limitation, business entities such as retail stores that might maintain a network site. In one implementation, a user can execute software on their computer that provides an application program or software platform. In this document, the terms ��application program�� and ��software platform�� will be used interchangeably. Each of the different extension sources 102-106 can provide software extensions that can plug into the software platform that is executing on the user's machine. These extensions are deliverable via a network such as the Internet, and assist in providing applications that can be executed on the user's machine. In the described embodiment, the extensions are logically described in XML which is in line with emerging industry standards. Additionally, the use of XML assists in the future discoverability of extensions by promoting XML DOM properties on the Internet. It will be appreciated, however, that any suitable format can be used for describing the extensions, e.g. a binary description could be used.
In one particular implementation, the software platform on the user's machine provides various different integrated functionalities that enable a user to accomplish different document-centric tasks. An exemplary system is described in the U.S. patent application entitled ��Single Window Navigation Methods and Systems��, incorporated by reference above.
An ��extension��, as used in this document, will be considered to include, without limitation, software functionality and content that can be added to an application program or software platform. These additions typically provide some type of functionality that the application program may not have had before the extension was incorporated, or alter the behavior of at least one existing feature. The extension is incorporated or integrated directly into the application program in a way that changes, to some degree, the manner in which the application program behaves or operates. Extensions provide dynamically added content and can provide applications (such as an email application), plug-ins to extend existing applications (like a fax plug-in to an email application), or simply web pages, to name just a few.
In the described embodiment, extensions are organized in three separate but related portions: an Extension Definition File (EDF), a Package Manifest (PKG), and the code, components, or ��bits�� that make up or define the extension. An EDF can be, but need not be associated with a URL (Universal Resource Locator) that provides a way for a client to access the EDF. By convention and choice, the PKG file is located at the same URL as the EDF. It will be appreciated that the described EDFs and PKG are each not required for the other to be used. It just so happens that, in the example that is given is this document, the two are employed together. To that end, each of these features can be separately and independently employed.
User interface elements Behaviors/Components/Objects Store Elements User-defined objects Or anything else that represents a point of extensibility in the application or platform EDFs advantageously have an ��open schema�� which means that third party developers can extend the extension mechanism and include their own extensions by creating their own tags. Additionally, extensions can themselves be extended by other developers. EDFs can also have one or more predefined tags. Exemplary predefined XML tags for user interface elements can include tags for feature types such as: tool bars, accelerators, menu items, and themes. These feature types are utilized in the single navigable window application incorporated by reference above and defined in the table immediately below:
In the described embodiment, the EDFs have a particular XML schema that is utilized. The schema comprises collections of XML tags that are arranged in a hierarchical organization to facilitate information dissemination to software components that need certain extensions. In the described embodiment, the outer (encompassing tag) for EDFs is an ��extension�� tag.
FIG. 4 shows an exemplary extension tag. ��extension�� tags can include one or more of the following attributes, all of which are optional:
Within the ��extension�� outer tag are one or more child tags, also referred to as ��top level tags��. These top level tags are each associated with a feature type that can be added by a particular extension. Exemplary feature types are discussed in connection with Tables 1-3 above. Underneath each top level tag there can be one or more child tags that are individually associated with a particular feature of the feature type that is to be added by a particular extension.
FIG. 5 shows an exemplary XML schema organization in accordance with this embodiment. For each top level tag in an EDF, there is an associated attachment manager which is a software component that receives data associated with the tag so that the data can be used to incorporate the extension into the platform or application program. Different attachment managers may interpret the data from the tag in different ways to provide different types of extensibility, so different top level tags will contain different types of data in different structures. This will become more evident in the ��Architecture�� section below. Note that the ��edf:�� XML namespace qualifier enables support of an open schema where extensions can provide their own tags and corresponding attachment managers. Tags within the edf namespace are used by built-in attachment managers in the application or software platform. Tags in other namespaces are used by third-parties to provide additional points of extensibility.
Another consideration of interest pertains to the efficiency with which the extension files or ��bits�� are delivered to the client. To address this consideration, the described embodiment utilizes a couple of different download approaches: a throttled download and a background download. Throttled downloading conducts download operations while taking into account the available bandwidth and type of media over which the files are being transferred. Any suitable throttled download process can be employed and will be understood by those of skill in the art. Background download is conducted while the user is working within the application program and is implemented by allocating a background thread so that the user can continue their work. One optimization that is utilized is that packages are prioritized and delivered in accordance with what a user might be working on.
When a file is updated, hash values can serve a useful purpose in identifying files that have not been changed between different versions of an extension. Consider FIG. 7, for example. There, an old directory 700 in a client package cache contains package A which include two files�Xfile 1 with hash=x, and file 2 with hash=y. Assume that this package is associated with an older version of an extension. When an updated version is produced, its package manifest is delivered to the client. The updated extension version is represented on a source directory of a code or web server 704. The package manifest includes the hash values for all of the files in the new extension version. A new client destination directory 702 is defined for all of the files of the new extension. If any of the hash values for files in the new extension are the same as the hash values of the files in the old directory 700, then those files can be copied directly from the old directory 700 to the new destination directory 702. In this example, file 1's hash value is the same as the hash value for file 1 on the source directory 704, so it can be copied into the new destination directory 702. File 2's hash value, however is different from the hash value for file 2 on the source directory, so it is not copied from the old directory 700. Rather, file 2 is downloaded from the code server. A new file 3 has been added and is also downloaded from the code server. Hence, in this example, a new version of an extension resulted in a download of less than all of the files in the extension version. This is because hash values for each of the files in the old extension version were able to be compared with hash values of the files in the new extension version. Those hash values that are the same indicate files that have not changed as between versions.
The reason for the dependencies section is to allow for legacy code that relies on being loaded by virtue of being in the search path of some other dll. In this case we have to make sure that the dependency dll is in the package cache directory before the dependant dll is loaded. FIG. 6 shows an exemplary package manifest 600 that is defined in a hierarchical tag-based language. Advantageously, the tag-based language comprises XML which is desirably extensible and flexible. In this example, a number of tags are provided in a hierarchical arrangement. The ��package�� tag contains information about the size of the package. The ��files�� tag is a child of the ��package�� tag and contains information about the file groups that are contained in that particular package. The ��file�� tag is a child of the ��group�� tag and contains information about specific files that comprise the extension, i.e. file name and hash value. A ��dependency�� tag is provided as a child of the ��file�� tag and lists any dependencies as discussed above. A ��COMClass�� tag is also provided as a child of the ��file�� tag and contains IDs as mentioned above. The ordering of the file groups in this schema implicitly defines the download order of the files.
Second, a background download approach is utilized. Background downloads enable a user to continue to work within an application program while content is downloaded. Foreground downloads are used when the user has explicitly requested a file/extension by clicking, for example, on an extension link, or requested an action, for example, by clicking on the ��Compose�� mail button, that requires download of files which are not available locally.
URL for the package manifest information on a code server URN for package destination directory in the package cache at the client (Optional) URN for the old package directory (if one exists) in the package cache From this information, the package manager creates a package object and adds the package object to a download queue. The download queue is designed for easy rearrangement of a package download order. Consider, for example, FIG. 8 which shows a portion of a download queue 800 that contains two package objects�Xpackage object 802 (corresponding to package A) and package object 804 (corresponding to package B). The package objects maintain a list of which files of a corresponding package have been downloaded or installed. In the present example, files 1 and 2 from package A have been installed while file 3 has not been installed; and files 1, 2, and 3 have not been installed from package B. The download queue can be rearranged based on what the user is doing. That is, based on the actions that a user takes, the priority of files that are to be downloaded can be changed. In this example, the package manager is designed to process the first uninstalled file in the package at the head of the download queue. If, however, the user starts to use a file in an extension that is different from the extension whose files are at the head of the download queue, the corresponding package for the file that the user has started to use can be moved to the head of the download queue. Because a file's package is specified by its URN, the file's package can be quickly identified and located in the download queue. For example, and considering FIG. 8, if one of the files in package B is requested before the package manager has started to install package A's third file, then package B will be moved to the head of the download queue.
Extension directory File group information and DLL load dependencies (Optional) File usage statistics from scenario runs (Optional) The extension directory input parameter specifies the directory containing all of the files that will be described by the package manifest. If this is the only parameter, then tool 1100 will generate a manifest in which the EDF and DLLs in the directory are listed in the ��Required�� set, and all other content is ��Offline��.
<Group Name= ��required��>
<File Name = ��bar.dll��/>
<File Name = ��foo.dll��/>
<File Name= ��bar.dll��/>
<File Name= ��myextension.edf��/>
<File Name= ��errorhandling.gif��>
The file usage statistics from scenario runs parameter is an optional parameter. This parameter enables the file download priority to be determined based on scenario runs. A scenario is a script of tasks that the average user typically follows when using a product during a particular portion of product use. For example, one scenario might pertain to the tasks involved in sending an email message (i.e. click ��new mail�� button, type in ��TO�� well, type is ��Subject�� well, etc.). In the described embodiment, file usage statistics from scenario runs are collected from running IIS logs on various scenarios. The different scenarios are directed to ensuring, with some degree of probabilistic support, that the file download order reflects, in some way, the files that will likely be used by the user first.
In one implementation, the approach is somewhat more sophisticated. Additional information (in addition to the scripted steps) is stored in the IIS logs and includes scenario priority and checkpoints. The scenario priority is a priority that is assigned for each scenario. So, for example, if one scenario is ten times more important than another scenario, this information can be maintained. The priority (e.g. a rating from between 1 to 100, with 100 being the highest priority), should be equal to a best guess as to the percentage of the time that users will step through the scenario, assuming they use the extension at all. Checkpoints provide a way to separate one scenario from another. For example, checkpoints designated as ��Offline�� and ��Shutdown�� can be automatically added at the beginning and end of the scenarios, respectively, so there can be a differentiation between scenario runs in the log. Additionally, script authors can optionally use checkpoints mid-scenario to indicate a change in group priority, e.g. part of a scenario script could be labeled as an ��On demand�� feature and another part could be labeled as ��Offline��.
Step 1300 sorts files by file group. Recall that in the illustrated example above, files can be grouped in one of four possible groups: Required, Offline, On Demand and Online Only. A file's group is determined first by the manifest, and, if it does not provide any group information, then by the highest priority group that it uses, according to checkpoint information in the log. Files in the ��Required�� set should not be considered because their order is already known. If no group information is included about a file, then an assumption is made that the EDF and all DLLs are ��Required�� files and all other files in the directory are ��Offline��.
In this example, there are three scenarios that have files associated with them. Each of the scenarios has a priority with which it is associated. The files are first sorted by group (step 1300). Recall that in this ordering heuristic, DLLs are ��Required�� and all other files are considered ��Offline��. This provides the following sorted files:
FileC, FileA, FileB, File D Code, Components and ��Bits��
Customized UI and keyboard shortcuts Components and Behaviors XML browsing and editing components (including XSL and business logic objects) Static pages or other resources Third-party defined custom content Users install extensions by navigating to a network site for the extension. In an Internet implementation, the user navigates to an appropriate URL for the extension. Hosting administrators can also ��push�� extensions so that users can automatically receive them by adding an entry into the appropriate users' ��Preference�� settings.
The flow diagram, in this example, is illustrated in connection with three separate ��zones��, one of which represents a client, one of which represents a ��platform�� Internet server, and one of which represents a third party Internet server. The acts that are described in connection with the different zones are performed, in this example, by the entities assigned to the zone. In some configurations, one or more of these zones may overlap. For instance, the platform server may be the same device as the extension server.
Step 1400 navigates a user to a particular Internet site that is associated with the software platform that is to be utilized as the foundation for extension installation described below. In step 1402, the user clicks an ��install�� button that sends a message to the software platform server that indicates that a user wishes to install the software platform. This step can be an optional step. Steps 1404 and 1405 then download the software associated with the software platform to the client. In the illustrated example, step 1404 downloads the package file for the single navigable window application and based on that file's contents step 1405 downloads other components and files to the user's computer. Step 1406 installs the software code on the client machine and can create local directories for the application cache, a local store and preferences. It will be appreciated, however, that local directories or preferences are not necessarily needed. Step 1408 launches the software platform.
Step 1410 uses a link that is associated with an extension to access the extension. This step can be implemented by a user navigating their browser to a particular Internet site through which one or more extensions can be accessed. Alternately, a reference to the link can be placed in the user's preferences or the preferences of a computing group with which the user is associated (e.g. the system administrator can place a reference in a group's preferences). The link can advantageously be associated with a third party Internet server or Internet site. Step 1412 downloads extension files according to the PKG associated with an EDF. The files are delivered to the client and step 1414 places the extension files in a local store as specified by the PKG specification. At this point, an extension is installed and the user can utilize the functionality provided by the extension. Step 1416 determines whether extension updates are available. This can be done by periodically polling an extension catalog (discussed in an ��Extension Catalog�� section below) to ascertain whether there are any updates to various extensions. Alternately, notifications might be automatically sent to the client so that the client is aware of updates or any other method might be used to determine if updates are available. If there are updates available, step 1418 branches to step 1412 which downloads the extension files associated with the update and installs them on the client.
The default language of the netdocs-planner is the English version. The default English version is 1.1. The default French version is 1.0. If there is no version available in the user's specified language on the platform, they will get the English version 1.1 by default. The English version of netdocs-planner has been upgraded from V1 to V1.1. There is also a French version. The extension URN is the same as the English version. There is no 1.1 release for French yet, so 1.0 is the current version for French speaking users. A query against the catalog returns only the rows where language matches the user's language preferences. The query would also return all rows where language is the user's language or default=��yes�� and throw out duplicates for the same name. Architecture
The EDF, as pointed out above, can be defined in an XML schema that includes a root node (i.e. the ��extension�� tag) and one or more child nodes. In this particular example, the child nodes generally correspond to the individual extension feature types that are desired for incorporation into the software platform. For example, recall that Tables 1-3 above describe various exemplary predefined feature types that can be added through an extension using the predefined XML schema.
Consider now a developer who wants to add two menus and a toolbar to the software platform. The menus and toolbar might be associated with a retail store that maintains a Web site for its customers. The retail store might want a customer who visits its Web site to be presented with a UI that is unique to the retail store and provides services that are specifically tailored to the store. To do this, the developer develops two different menus, one of which might be associated with displaying the most recent specials, and other of which might be associated with providing a search mechanism through which the user can search for specific products. The toolbar might contain specific buttons that are unique to the retail store. A simplified EDF called ��retail.edf�� for the retail store's extension is shown directly below:
<edf:extension name= ��retail extension�� urn= ��extension.retail.com��>
<edf:menu url= ��url1.htm��/>
<edf:menu url= ��url2.htm��/>
<edf:toolbar url= ��url3.htm��/>
Here, the outer ��extension�� tag designates this XML file as an extension. The inner ��menus�� and ��toolbars�� tags are top level tags that designate that the information between these tags pertains respectively to menus and toolbars that correspond to the extensions that the developer has added. The boldface ��menu�� and ��toolbar�� tags describe data pertaining to the actual extension and contain a URL that is associated with each extension as described above. The EDF above logically describes the extensions that are being provided as including two menus and one tool bar.
For each top level tag (i.e. ��menus�� and ��toolbars�� tags), there is a corresponding attachment manager 1704 that uses data provided by the attachment points to incorporate a particular type of feature within the software platform. Each attachment manager requests a set of attachment points from the attachment point manager 1702. These manipulate the data exposed by the EDFHub 1700. In the illustrated example, the attachment points can be requested as a predicate chain that the attachment point manager uses to create and build a set of attachment points that operate on the data exposed by the EDFHub 1700.
1) Initially attach to one or more data sources. These could be files or, commonly, other attachment points. 2) Process the data based on some logic. Usually the logic is quite simple and could involve something like filtering the objects based on some criteria. 3) Expose the results of the processing step 2 in a new collection of objects. 4) Fire events to indicate how the exposed collection of objects changed (OnInserted(index, count) or OnRemoved(index, count). 5) Optionally, continue to listen for changes in the data sources and repeat step 2-4 when changes occur. Alone, each attachment point is quite simple, but when different types of attachment points are combined to form ��chains��, where one attachment point processes data from a second attachment point, the processing can be quite powerful. This is especially true if the attachment points only process the changed data in step 2, since they only do a small amount of simple work at any one time. In the exemplary system, this incremental processing means that the whole system does not have to be re-queried when a new extension is installed or when an existing extension is removed. Additionally, each attachment manager in the exemplary system uses a specific chain of attachment points and so is only informed of changes that impact its area of extensibility.
Explode(Filter(��menus��, Explode (URL (��retail.edf��))))
This string represents all of the menus in the retail.edf file. The XML file located at retail.edf is loaded by the URL attachment point which exposes the root node of the XML file as the only object in its collection. The inner Explode attachment point uses the URL attachment point as its data source and exposes all of the children of the objects in that source collection. In this case, the children of the root node are the top level XML tags ��menu�� and ��toolbars��. The Filter attachment point uses the Explode attachment point as its data source and filters the exposed objects looking only for the nodes that are ��menus��. The outer Explode attachment point uses the Filter attachment point as its data source and exposes all of the children of the filtered menu nodes to provide a list containing the two menus that are added by the extension. Since this particular XML file contained menus that were identified by the attachment points associated with menu attachment manager, that attachment manager is then notified that two menus have been added by an extension.
This process is diagrammatically illustrated in FIG. 19 which shows attachment points 1900, 1902, 1904, and 1906. Each attachment point exposes a list of XML nodes. URL attachment point 1900 takes an input (a URL to an XML file�Xe.g. retail.edj) and exposes a list of XML nodes. This list contains only the root node ��<edf:extension>��. Explode attachment point 1902 takes as an input attachment point 1900 and exposes a list of XML nodes which are children of source XML nodes. In this example, the list of XML nodes exposed by attachment point 1902 are the ��<menus>�� nodes and the ��<toolbars>�� nodes. The filter attachment point 1904 takes attachment point 1902 as an input and filters on ��menus.�� It then exposes an XML list having only ��<menus>�� nodes in it. The explode attachment point 1906 takes attachment point 1904 as an input and exposes a list with the XML nodes that are contained in the ��<menus>�� nodes�Xhere both of the ��<menu>�� nodes.
Consider additionally that the toolbar attachment manager would request a predicate chain of attachment points which would also use URL attachment point, an Explode attachment point and a filter attachment point 1904 that filters on ��toolbars��. Thus, the corresponding explode attachment point 1906 would expose an XML list containing only the ��<toolbar>�� node. But, the attachment point manager would detect the commonality of the URL attachment point and the inner Explode attachment point, so it would reuse the same attachment points it created for the menu attachment manager. The Filter attachment points used by the toolbar attachment manager and the menu attachment manager would use the same Explode attachment point as their data sources but would expose different collections of nodes, because they were filtering based on different criteria.
��expression�� attribute and binds to it. If
�M�Q�ޥ� �ޥΪ��M�Q�ӽФ���o�G��� �ӽЪ��M�Q�W��US28048781954�~6��29��1957�~9��3��Power Brake Equipment CompanyGovernor for brake air compressorUS30910771960�~12��29��1963�~5��28��Nordberg Manufacturing CompanyEngine controlUS31045201957�~9��11��1963�~9��24��The Garrett CorporationTurbosupercharger bypass ejectorUS31958051961�~10��25��1965�~7��20��The Garrett CorporationTurbocharger differential pressure controlUS31966061961�~10��30��1965�~7��27��The Garrett CorporationAntidetonant control for turbocharged enginesUS38129421972�~6��12��1974�~5��28��Bosch R Gmbh,DtHydraulic systemUS38748281973�~11��12��1975�~4��1��Gardner-Denver CompanyRotary control valve for screw compressorsUS39617481975�~6��30��1976�~6��8��The Trane CompanyAir distribution regulator apparatusUS40055781975�~3��31��1977�~2��1��The Garrett CorporationMethod and apparatus for turbocharger controlUS40055791975�~3��31��1977�~2��1��The Garrett CorporationTurbocharger control and methodUS40603401975�~12��24��1977�~11��29��Midland-Ross CorporationAir compressor with inlet diversion valveUS40896231975�~12��30��1978�~5��16��Sullair Schraubenkompressoren GmbhCompressor intake controlUS42019781978�~10��19��1980�~5��6��NCR Canada Ltd. -- NCR Canada LteeDocument processing systemUS42560191979�~6��12��1981�~3��17��The Garrett CorporationTurbocharger control actuatorUS43624751981�~3��16��1982�~12��7��Joy Manufacturing CompanyCompressor inlet valveUS43911841980�~9��30��1983�~7��5��Nissan Motor Co., Ltd.Diaphragm actuatorUS43963451981�~5��7��1983�~8��2��Ingersoll-Rand CompanyUnloader valve having bypass valving meansUS44981471982�~11��18��1985�~2��5��International Business Machines CorporationMethodology for transforming a first editable document form prepared with a batch text processing system to a second editable document form usable by an interactive or batch text processing systemUS45148001981�~5��22��1985�~4��30��Data General CorporationDigital computer system including apparatus for resolving names representing data items and capable of executing instructions belonging to general instruction setsUS45149851984�~10��15��1985�~5��7��Benditalia S.P.A.Master cylinderUS45647521982�~12��23��1986�~1��14��Ncr Canada LtdConcurrent, image-based, reject-re-entry system and methodUS46412741985�~8��19��1987�~2��3��International Business Machines CorporationMethod for communicating changes made to text form a text processor to a remote hostUS46740401984�~12��26��1987�~6��16��International Business Machines CorporationMerging of documentsUS47232111984�~8��30��1988�~2��2��International Business Machines Corp.Editing of a superblock data structureUS47394771984�~8��30��1988�~4��19��International Business Machines Corp.Implicit creation of a superblock data structureUS47836481986�~6��27��1988�~11��8��Hitachi, Ltd.Display control system for multiwindowUS48150291985�~9��23��1989�~3��21��International Business Machines Corp.In-line dynamic editor for mixed object documentsUS48477491986�~6��13��1989�~7��11��International Business Machines CorporationJob interrupt at predetermined boundary for enhanced recoveryUS49106631987�~7��10��1990�~3��20��Tandem Computers IncorporatedSystem for measuring program execution by replacing an executable instruction with interrupt causing instructionUS49264761989�~2��3��1990�~5��15��Motorola, Inc.Method and apparatus for secure execution of untrusted softwareUS49338801988�~6��15��1990�~6��12��International Business Machines Corp.Method for dynamically processing non-text components in compound documentsUS49624751988�~3��15��1990�~10��9��International Business Machines CorporationMethod for generating a document utilizing a plurality of windows associated with different data objectsUS49756901988�~11��7��1990�~12��4��Ibm CorporationMethod for concurrent data entry and manipulation in multiple applicationsUS50254841988�~8��15��1991�~6��18��Kabushiki Kaisha ToshibaCharacter reader deviceUS50724121987�~3��25��1991�~12��10��Xerox CorporationUser interface with multiple workspaces for sharing display system objectsUS51405631991�~12��5��1992�~8��18��Timex CorporationMultimode electronic timepiece having a mutually exclusive submode displayUS51797031990�~4��23��1993�~1��12��International Business Machines CorporationDynamically adaptive environment for computer programsUS51827091990�~2��28��1993�~1��26��Wang Laboratories, Inc.System for parsing multidimensional and multidirectional text into encoded units and storing each encoded unit as a separate data structureUS51877861991�~4��5��1993�~2��16��Sun Microsystems, Inc.Method for apparatus for implementing a class hierarchy of objects in a hierarchical file systemUS51916451991�~2��28��1993�~3��2��Sony Corporation Of AmericaDigital signal processing system employing icon displaysUS51951831991�~10��28��1993�~3��16��Norand CorporationData communication system with communicating and recharging docking apparatus for hand-held data terminalUS52049471990�~10��31��1993�~4��20��International Business Machines CorporationApplication independent (open) hypermedia enablement servicesUS52069511991�~4��3��1993�~4��27��Wang Laboratories, Inc.Integration of data between typed objects by mutual, direct invocation between object managers corresponding to object typesUS52186721990�~1��19��1993�~6��8��Sony Corporation Of AmericaOffline editing system with user interface for controlling edit list generationUS52206491991�~4��29��1993�~6��15��Microsoft CorporationScript/binary-encoded-character processing method and system with moving space insertion modeUS52221601990�~12��28��1993�~6��22��Fujitsu LimitedDocument revising system for use with document reading and translating systemUS52281001990�~7��10��1993�~7��13��Hitachi Software Engineering Co., Ltd.Method and system for producing from document image a form display with blank fields and a program to input data to the blank fieldsUS52376801990�~9��27��1993�~8��17��Sun Microsystems, Inc.Method for incremental rename propagation between hierarchical file name spacesUS52492751991�~4��30��1993�~9��28��Texas Instruments IncorporatedApparatus and method enabling a compiled program to exactly recreate its source codeUS52512731992�~4��15��1993�~10��5��International Business Machines CorporationData processing system and method for sequentially repairing character recognition errors for scanned images of document formsUS52576461992�~8��17��1993�~11��2��Nelson Irrigation CorporationO-ring damped regulatorUS52748031991�~4��26��1993�~12��28��Sun Microsystems, Inc.Method and apparatus for aligning a restored parent environment to its child environments with minimal data lossUS52972491990�~10��31��1994�~3��22��International Business Machines CorporationHypermedia link marker abstract and search servicesUS52972831992�~10��16��1994�~3��22��Digital Equipment CorporationObject transferring system and method in an object based computer operating systemUS53136311991�~5��21��1994�~5��17��Hewlett-Packard CompanyDual threshold system for immediate or delayed scheduled migration of computer data filesUS53136461991�~6��10��1994�~5��17��Sun Microsystems, Inc.Method and apparatus for translucent file systemUS53176861993�~3��10��1994�~5��31��Lotus Development CorporationData processing apparatus and method for a reformattable multidimensional spreadsheetUS53333171992�~11��3��1994�~7��26��Bull Hn Information Systems Inc.Name resolution in a directory databaseUS53394231993�~3��9��1994�~8��16��International Business Machines CorporationSystem for accessing objects external to an application using tables containing path definitionsUS53394241992�~4��17��1994�~8��16��Mitsubishi Denki Kabushiki KaishaSystem and method for compiling and executing a computer program written in more than one programming languageUS53414781993�~11��3��1994�~8��23��Digital Equipment CorporationMethods and apparatus for providing dynamic invocation of applications in a distributed heterogeneous environmentUS53697661993�~3��25��1994�~11��29��Taligent, Inc.Object-oriented loader system with support for different load formatsUS53697781993�~9��27��1994�~11��29��Wang Laboratories, Inc.Data processor that customizes program behavior by using a resource retrieval capabilityUS53716751992�~6��3��1994�~12��6��Lotus Development CorporationSpreadsheet program which implements alternative range referencesUS53773231991�~9��13��1994�~12��27��Sun Microsytems, Inc.Apparatus and method for a federated naming system which can resolve a composite name composed of names from any number of disparate naming systemsUS53794191990�~12��7��1995�~1��3��Digital Equipment CorporationMethods and apparatus for accesssing non-relational data files using relational queriesUS53815471990�~10��24��1995�~1��10��Siemens AktiengesellschaftMethod for dynamically linking definable program elements of an interactive data processing systemUS53889671993�~3��10��1995�~2��14��Sullair CorporationCompressor start control and air inlet valve thereforUS53889681994�~7��28��1995�~2��14��Ingersoll-Rand CompanyCompressor inlet valveUS53903251992�~12��23��1995�~2��14��Taligent, Inc.Automated testing systemUS53966231992�~10��30��1995�~3��7��Bmc Software Inc.Method for editing the contents of a DB.sub.2 table using an editproc managerUS54086651993�~4��30��1995�~4��18��Borland International, Inc.System and methods for linking compiled code with extended dictionary supportUS54106461994�~2��23��1995�~4��25��Park City Group, Inc.System and method for creating, processing, and storing forms electronicallyUS54106881990�~7��16��1995�~4��25��Hewlett-Packard CompanyDistributed object based systems for communicating object data among different storage domainsUS54127721992�~10��13��1995�~5��2��Novell, Inc.System for permitting a view of an object or a user interface to be exchanged between operating system environmentsUS54287381993�~5��21��1995�~6��27��Novell, Inc.Logical expression calculation interfaceUS54349751992�~9��24��1995�~7��18��At&T Corp.System for interconnecting a synchronous path having semaphores and an asynchronous path having message queuing for interprocess communicationsUS54366371993�~3��5��1995�~7��25��Borland International, Inc.Graphical user interface system and methods for improved user feedbackUS54386591992�~10��8��1995�~8��1��Hewlett-Packard CompanyObject-action user interface management systemUS54407441994�~11��15��1995�~8��8��Digital Equipment CorporationMethods and apparatus for implementing server functions in a distributed heterogeneous environmentUS54468421993�~2��26��1995�~8��29��Taligent, Inc.Object-oriented collaboration systemUS54558751993�~8��3��1995�~10��3��International Business Machines CorporationSystem and method for correction of optical character recognition with display of image segments according to character dataUS54565821993�~12��23��1995�~10��10��Sullair CorporationCompressor inlet valve with improved response timeUS54598651993�~4��5��1995�~10��17��Taligent Inc.Runtime loaderUS54637261994�~9��6��1995�~10��31��International Business Machines CorporationMethod and apparatus for graphic accessing of multiple software applicationsUS54817221994�~11��14��1996�~1��2��Sun Microsystems, Inc.Method and apparatus for merging change control delta structure files of a source module from a parent and a child development environmentUS54974891995�~6��7��1996�~3��5��Chemicals Pty Ltd.Data storage and retrieval systems having labelling for dataUS55048981994�~6��20��1996�~4��2��Candle Distributed Solutions, Inc.Threaded environment for AS/400US55176551995�~6��28��1996�~5��14��Hewlett-Packard CompanyMethod for monitoring transactions in an object-oriented environmentUS55353891993�~1��26��1996�~7��9��International Business Machines CorporationBusiness process objects with associated attributes such as version identifierUS55375961995�~4��17��1996�~7��16��Apple Computer, Inc.Method and apparatus for overriding resource maps in a computer systemUS55405581995�~8��7��1996�~7��30��Ingersoll-Rand CompanyApparatus and method for electronically controlling inlet flow and preventing backflow in a compressorUS55420701994�~12��19��1996�~7��30��Ag Communication Systems CorporationMethod for rapid development of software systemsUS55509761992�~12��8��1996�~8��27��Sun Hydraulics CorporationDecentralized distributed asynchronous object oriented system and method for electronic data management, storage, and communicationUS55510351995�~3��16��1996�~8��27��Lucent Technologies Inc.Method and apparatus for inter-object communication in an object-oriented program controlled systemUS55553251993�~10��22��1996�~9��10��Lockheed Martin Federal Systems, Inc.Data capture variable priority method and system for managing varying processing capacitiesUS55562711994�~11��23��1996�~9��17��Coltec Industries Inc.Valve system for capacity control of a screw compressor and method of manufacturing such valvesUS55663301995�~2��23��1996�~10��15��Powersoft CorporationMethod for forming a reusable and modifiable database interface objectUS55726431995�~10��19��1996�~11��5��Internetad Systems LlcWeb browser with dynamic display of information objects during linkingUS55726481993�~1��19��1996�~11��5��Canon Kabushiki KaishaSystem for simultaneously displaying a static tool palette having predefined windowing tool functions and a dynamic tool palette which changes windowing tool functons in accordance with a context of an executed application programUS58017021995�~3��9��1998�~9��1��Terrabyte TechnologySystem and method for adding network links in a displayed hierarchyUS58058241996�~2��28��1998�~9��8��Hyper-G Software Forchungs-Und Entwicklungsgesellschaft M.B.H.Method of propagating data through a distributed information systemUS59632081998�~7��14��1999�~10��5��Michael A. DolanIntegrated network access user interface for navigating with a hierarchical graphUS60525311998�~3��25��2000�~4��18��Symantec CorporationMulti-tiered incremental software updatingUS61065701998�~9��18��2000�~8��22��Kabushiki Kaisha ToshibaNetwork computer, and file transfer method applied to network computerUS61785511998�~7��1��2001�~1��23��Japan Airlines Co., Ltd.Method of and system for installing a computer programUS63857671999�~9��30��2002�~5��7��Unisys CorporationMethod and system for creating and manipulating extensions to version control systemsUS64010771999�~5��28��2002�~6��4��Network Commerce, Inc.Method and system for providing additional behavior through a web pageUS65131541997�~10��21��2003�~1��28��Nipkow Disk LlcSystem and method for testing of computer programs in programming effortUS65746551999�~6��29��2003�~6��3��Thomson Licensing SaAssociative management of multimedia assets and associated resources using multi-domain agent-based communication between heterogeneous peersUS66042382000�~3��30��2003�~8��5��Hewlett-Packard Development Company, L.P.Method and system for installing softwareUS66256221999�~8��23��2003�~9��23��Eisenworld, Inc.Apparatus and method for transfering information between platformsUS72932682001�~1��19��2007�~11��6��Fujitsu LimitedInstallation method, activation method, execution apparatus and medium of application programUS76536872007�~6��8��2010�~1��26��Intellectual Ventures I LlcMethod for distributing content to a user stationUS200100521212001�~1��19��2001�~12��13��Masuda TakahiroInstallation method, activation method, execution apparatus and medium of application program�D�M�Q�ޥ��ѦҤ��m1"Advisory Action", U.S. Appl. No. 10/185,048, (Jun. 20, 2006),3 Pages.2"Advisory Action", U.S. Appl. No. 10/185,048, (Sep. 16, 2005),3 Pages.3"Advisory Action", U.S. Appl. No. 10/632,437, (Aug. 23, 2006),3 pages.4"Advisory Action", U.S. Appl. No. 10/916,692, (Dec. 10, 2008),3 Pages.5"Applicants' Statement Regarding a Non-Public Use", (May 31, 2006),1 page.6"EP Search Report", EP Application No. 00306806, (Jul. 16, 2003),3 pages.7"EP Search Report", EP Application No. 97307138, (Mar. 21, 2003),3 pages.8"European Search Report", EP Application No. 06111546.5, (Nov. 9, 2006),5 pages.9"Final Office Action", U.S. Appl. No. 10/185,048, (Jun. 3, 2005),14 Pages.10"Final Office Action", U.S. Appl. No. 10/185,048, (Mar. 13, 2006),14 Pages.11"Final Office Action", U.S. Appl. No. 10/402,640, (Sep. 10, 2007),16 pages.12"Final Office Action", U.S. Appl. No. 10/632,437, (Jan. 25, 2008),25 pages.13"Final Office Action", U.S. Appl. No. 10/632,437, (Jun. 1, 2006),21 pages.14"Final Office Action", U.S. Appl. No. 10/781,586, (Aug. 9, 2007),20 pages.15"Final Office Action", U.S. Appl. No. 10/876,418, (May 22, 2008),14 pages.16"Final Office Action", U.S. Appl. No. 10/916,692, (Oct. 2, 2008),10 Pages.17"Final Office Action", U.S. Appl. No. 10/955,087, (May 16, 2008),13 pages.18"Final Office Action", U.S. Appl. No. 10/955,666, (Aug. 30, 2007),19 pages.19"Final Office Action", U.S. Appl. No. 10/955,666, (Oct. 31, 2008),24 pages.20"Final Office Action", U.S. Appl. No. 10/976,451, (Jul. 27, 2010),12 pages.21"Final Office Action", U.S. Appl. No. 10/977,198, (Oct. 11, 2007),10 pages.22"Final Office Action", U.S. Appl. No. 10/977,198, (Sep. 3, 2008),13 pages.23"Final Office Action", U.S. Appl. No. 10/988,718, (Dec. 22, 2008),17 pages.24"Final Office Action", U.S. Appl. No. 10/988,718, (Jan. 30, 2008),15 pages.25"Final Office Action", U.S. Appl. No. 10/988,732, (Dec. 10, 2008),29 pages.26"Final Office Action", U.S. Appl. No. 10/988,732, (Nov. 13, 2009),33 pages.27"Final Office Action", U.S. Appl. No. 11/012,472, (Mar. 23, 2010),10 pages.28"Final Office Action", U.S. Appl. No. 11/095,254, (Dec. 22, 2008),9 pages.29"Final Office Action", U.S. Appl. No. 11/227,550, (Aug. 19, 2010),12 pages.30"Final Office Action", U.S. Appl. No. 11/227,550, (Jan. 19, 2010), 12 pages.31"Final Office Action", U.S. Appl. No. 11/234,767, (Jan. 26, 2010), 23 pages.32"Final Office Action", U.S. Appl. No. 11/295,178, (Dec. 24, 2009), 38 pages.33"Final Office Action", U.S. Appl. No. 11/295,178, (Jul. 30, 2010),43 pages.34"Final Office Action", U.S. Appl. No. 11/567,140, (Aug. 19, 2010),10 pages.35"Foreign Office Action", Application Serial No. 200610051544.X, (Dec. 4, 2009), 9 pages.36"Foreign Office Action", Chinese Application No. 200610051554.X, (Jun. 25, 2010),10 pages.37"Foreign Office Action", EP Application No. 01935325.9, (Jul. 20, 2010),6 pages.38"Foreign Office Action", Japanese Application 2002-504575, (Dec. 14, 2010),4 pages.39"Foreign Office Action", Japanese Application No. 2002-530701, (Aug. 10, 2010),11 pages.40"Issue Notification", U.S. Appl. No. 10/955,087, (Mar. 18, 2009),1 page.41"Issue Notification", U.S. Appl. No. 10/988,718, (Aug. 12, 2009),1 page.42"Issue Notification", U.S. Appl. No. 11/095,254, (Feb. 10, 2010),1 page.43"Issue Notification", U.S. Appl. No. 11/276,585, (Jan. 21, 2009),1 page.44"Lotus Notes Release 5, Step by Step", Lotus Development Corporation, (1999),224 pages.45"Netscape Window", Netscape Screenshot, (Oct. 2, 2002),1 page.46"Non Final Office Action", U.S. Appl. No. 09/599,806, (Aug. 17, 2004),5 pages.47"Non Final Office Action", U.S. Appl. No. 09/599,806, (Mar. 12, 2003),7 pages.48"Non Final Office Action", U.S. Appl. No. 10/395,505, (Sep. 11, 2006),8 pages.49"Non Final Office Action", U.S. Appl. No. 10/402,640, (Apr. 25, 2007),16 pages.50"Non Final Office Action", U.S. Appl. No. 10/402,640, (Feb. 12, 2008),16 pages.51"Non Final Office Action", U.S. Appl. No. 10/402,640, (Oct. 6, 2006),15 pages.52"Non Final Office Action", U.S. Appl. No. 10/402,640, (Sep. 8, 2008),16 pages.53"Non Final Office Action", U.S. Appl. No. 10/632,437, (Dec. 16, 2005),22 pages.54"Non Final Office Action", U.S. Appl. No. 10/632,437, (Jul. 26, 2007),19 pages.55"Non Final Office Action", U.S. Appl. No. 10/632,437, (Sep. 10, 2008),28 pages.56"Non Final Office Action", U.S. Appl. No. 10/770,240, (Aug. 24, 2004),25 pages.57"Non Final Office Action", U.S. Appl. No. 10/770,240, (May 1, 2008),30 pages.58"Non Final Office Action", U.S. Appl. No. 10/955,087, (Nov. 19, 2007),22 pages.59"Non Final Office Action", U.S. Appl. No. 10/955,666, (Dec. 26, 2006),20 pages.60"Non Final Office Action", U.S. Appl. No. 10/955,666, (Feb. 4, 2008),20 pages.61"Non Final Office Action", U.S. Appl. No. 10/977,198, (Jan. 10, 2008),10 pages.62"Non Final Office Action", U.S. Appl. No. 10/977,198, (Mar. 9, 2007),9 pages.63"Non Final Office Action", U.S. Appl. No. 10/988,718, (Jan. 25, 2007),13 pages.64"Non Final Office Action", U.S. Appl. No. 10/988,718, (Jul. 21, 2008),18 pages.65"Non Final Office Action", U.S. Appl. No. 10/988,718, (Jul. 26, 2007),21 pages.66"Non Final Office Action", U.S. Appl. No. 11/567,140, (Feb. 18, 2011),8 pages.67"Non-Final Office Action", U.S. Appl. No. 10/185,048, (Dec. 8, 2004),14 Pages.68"Non-Final Office Action", U.S. Appl. No. 10/402,640, (Dec. 30, 2009), 16 pages.69"Non-Final Office Action", U.S. Appl. No. 10/610,504, (Mar. 9, 2006),12 Pages.70"Non-Final Office Action", U.S. Appl. No. 10/781,586, (Oct. 20, 2006),21 pages.71"Non-Final Office Action", U.S. Appl. No. 10/854,961, (Nov. 15, 2006),21 pages.72"Non-Final Office Action", U.S. Appl. No. 10/871,586, (Jan. 9, 2008),22 pages.73"Non-Final Office Action", U.S. Appl. No. 10/876,418, (Sep. 13, 2007),14 pages.74"Non-Final Office Action", U.S. Appl. No. 10/916,692, (Apr. 1, 2008),9 Pages.75"Non-Final Office Action", U.S. Appl. No. 10/955,665, (Sep. 11, 2008),16 pages.76"Non-Final Office Action", U.S. Appl. No. 10/988,732, (Apr. 1, 2008),27 pages.77"Non-Final Office Action", U.S. Appl. No. 10/988,732, (Jun. 11, 2009),30 pages.78"Non-Final Office Action", U.S. Appl. No. 10/988,732, (May 26, 2010),36 pages.79"Non-Final Office Action", U.S. Appl. No. 11/012,472, (Jul. 1, 2010),9 pages.80"Non-Final Office Action", U.S. Appl. No. 11/012,472, (Oct. 6, 2009),8 pages.81"Non-Final Office Action", U.S. Appl. No. 11/036,910, (Aug. 19, 2010),8 pages.82"Non-Final Office Action", U.S. Appl. No. 11/107,347, (Jul. 9, 2010),16 pages.83"Non-Final Office Action", U.S. Appl. No. 11/170,521, (Dec. 17, 2009), 11 pages.84"Non-Final Office Action", U.S. Appl. No. 11/218,149, (Jan. 14, 2010), 15 Pages.85"Non-Final Office Action", U.S. Appl. No. 12/021,894, (Dec. 31, 2009), 10 pages.86"Notice of Allowance", U.S. Appl. No. 10/854,961, (Jun. 14, 2007),12 pages.87"Notice of Allowance", U.S. Appl. No. 10/942,528, (Dec. 3, 2009), 8 pages.88"Notice of Allowance", U.S. Appl. No. 10/955,087, (Dec. 11, 2008),10 pages.89"Notice of Allowance", U.S. Appl. No. 10/955,665, (Dec. 30, 2009), 2 pages.90"Notice of Allowance", U.S. Appl. No. 10/990,152, (Dec. 21, 2009), 6 pages.91"Notice of Allowance", U.S. Appl. No. 11/056,500, (Dec. 2, 2009), 17 pages.92"Notice of Allowance", U.S. Appl. No. 11/872,703, (Jan. 27, 2010), 19 pages.93"Restriction Requirement", U.S. Appl. No. 10/402,640, (Aug. 29, 2006),5 pages.94"Restriction Requirement", U.S. Appl. No. 11/012,472, (Jun. 9, 2009),7 pages.95"About Microsoft Word", Microsoft Word 2000, published 1983-1999, and Microsoft Excel 2000 (see Screen Shot "About Microsoft Excel") Published 1988-1999,(Oct. 21, 2005), 3 pages.96"Adobe GoLive 5.0: User Guide," Adobe Systems, 2000, Chapter 12, (2000), 11 pages.97"Advisory Action", U.S. Appl. No. 10/898,657, (Mar. 25, 2008), 3 pages.98"Advisory Action", U.S. Appl. No. 10/942,528, (Oct. 26, 2009),3 pages.99"Advisory Action", U.S. Appl. No. 11/036,910, (Sep. 10, 2009),3 pages.100"Architecture for a Dynamic Information Area Control", IBM Technical Disclosure Bulletin, IBM Corp, NY, US vol. 37, No. 10, Jan. 10, 1994,pp. 245-246.101"Copying the Search Form to Custom Pages in Windows SharePoint Services-based Web Sites", Retrieved from <www.sharepointcustomization.com/resources/tipstricks/04wss-searchbox-tip.htm> on Feb. 11, 2009, Microsoft Corp,(2003),1 page.102"Copying the Search Form to Services-based Web Sites", Cybook, Inc., the whole document, (Jul. 26, 2004),1 page.103"Enter Key", Retrieved from the Internet at http://systems.webopedia.com/TERM/Enter�Xkey.html on Dec. 20, 2006, 1 page.104"EP Office Action", Application Serial No. 06111546.5, (Oct. 15, 2008),5 pages.105"European Search Report", EP Application No. 10012887.5, (Jul. 4, 2011),12 pages.106"Excel Developer Tip: Determining the Data Type of a Cell", Retrieved from <http://jwalk.com/ss/excel/tips/tip62.htm>, (May 13, 1998),1 page.107"Final Office Action", U.S. Appl. No. 09/599,086, (Aug. 8, 2005), 27 pages.108"Final Office Action", U.S. Appl. No. 09/599,086, (Jul. 5, 2006), 34 pages.109"Final Office Action", U.S. Appl. No. 09/599,086, (Mar. 6, 2008), 47 pages.110"Final Office Action", U.S. Appl. No. 09/599,086, (May 10, 2007), 41 pages.111"Final Office Action", U.S. Appl. No. 09/599,086, (May 25, 2004), 23 pages.112"Final Office Action", U.S. Appl. No. 09/599,299, (Apr. 20, 2004), 23 pages.113"Final Office Action", U.S. Appl. No. 09/599,812, (Aug. 12, 2003), 38 pages.114"Final Office Action", U.S. Appl. No. 10/178,291, (Dec. 19, 2005), 21 pages.115"Final Office Action", U.S. Appl. No. 10/402,640, (Aug. 28, 2009),17 pages.116"Final Office Action", U.S. Appl. No. 10/609,274, (Oct. 3, 2008),50 pages.117"Final Office Action", U.S. Appl. No. 10/609,274, (Oct. 31, 2007),41 pages.118"Final Office Action", U.S. Appl. No. 10/723,188, (Jan. 9, 2009), 20 pages.119"Final Office Action", U.S. Appl. No. 10/723,863, (Sep. 19, 2007), 34 Pages.120"Final Office Action", U.S. Appl. No. 10/770,240, (Apr. 13, 2011),17 pages.121"Final Office Action", U.S. Appl. No. 10/770,240, (Jun. 26, 2009),15 pages.122"Final Office Action", U.S. Appl. No. 10/770,240, (Jun. 29, 2007),28 pages.123"Final Office Action", U.S. Appl. No. 10/846,428, (Mar. 3, 2008), 23 pages.124"Final Office Action", U.S. Appl. No. 10/857,689, (Jan. 6, 2009),23 pages.125"Final Office Action", U.S. Appl. No. 10/897,647, (Jul. 14, 2009), 36 pages.126"Final Office Action", U.S. Appl. No. 10/897,647, (Mar. 6, 2008), 25 pages.127"Final Office Action", U.S. Appl. No. 10/898,656, (Nov. 15, 2007), 16 pages.128"Final Office Action", U.S. Appl. No. 10/898,657, (Jan. 3, 2008), 21 pages.129"Final Office Action", U.S. Appl. No. 10/916,692, (Nov. 16, 2009),10 pages.130"Final Office Action", U.S. Appl. No. 10/938,476, (Jun. 20, 2011),19 pages.131"Final Office Action", U.S. Appl. No. 10/942,528, (Sep. 17, 2009),27 pages.132"Final Office Action", U.S. Appl. No. 10/955,666, (Oct. 14, 2009),24 pages.133"Final Office Action", U.S. Appl. No. 10/976,451, (Apr. 6, 2011),10 pages.134"Final Office Action", U.S. Appl. No. 10/976,451, (Jul. 2, 2009),13 pages.135"Final Office Action", U.S. Appl. No. 10/977,198, (Aug. 19, 2009),15 pages.136"Final Office Action", U.S. Appl. No. 10/988,732, (Nov. 12, 2010), 37 pages.137"Final Office Action", U.S. Appl. No. 11/036,910, (Jun. 1, 2009),15 pages.138"Final Office Action", U.S. Appl. No. 11/036,910, (May 26, 2010),9 pages.139"Final Office Action", U.S. Appl. No. 11/044,106, (Apr. 13, 2009),20 pages.140"Final Office Action", U.S. Appl. No. 11/056,500, (Apr. 16, 2009),10 pages.141"Final Office Action", U.S. Appl. No. 11/072,087, (Nov. 16, 2009),9 pages.142"Final Office Action", U.S. Appl. No. 11/107,347, (Apr. 2, 2009),15 pages.143"Final Office Action", U.S. Appl. No. 11/107,347, (Mar. 22, 2010),11 pages.144"Final Office Action", U.S. Appl. No. 11/170,521, (Jun. 29, 2010),13 pages.145"Final Office Action", U.S. Appl. No. 11/170,521, (Sep. 8, 2009),12 pages.146"Final Office Action", U.S. Appl. No. 11/203,818, (Apr. 14, 2009),31 pages.147"Final Office Action", U.S. Appl. No. 11/203,937, (May 7, 2009),13 pages.148"Final Office Action", U.S. Appl. No. 11/218,149, (May 19, 2010),17 pages.149"Final Office Action", U.S. Appl. No. 11/218,149, (Nov. 16, 2009),18 pages.150"Final Office Action", U.S. Appl. No. 11/226,044, (Apr. 20, 2009),24 pages.151"Final Office Action", U.S. Appl. No. 11/234,767, (Jun. 10, 2009),24 pages.152"Final Office Action", U.S. Appl. No. 11/234,767, (Mar. 10, 2011),28 pages.153"Final Office Action", U.S. Appl. No. 11/557,931, (Feb. 26, 2010),8 pages.154"Final Office Action", U.S. Appl. No. 12/061,613, (Apr. 28, 2011),11 pages.155"Final Office Action", U.S. Appl. No. 12/126,532, (Oct. 14, 2011), 25 pages.156"Foreign Decision of Grant", Russian Application No. 2006103267, (Aug. 13, 2010), 18 pages.157"Foreign Decision of Grant", Russian Application No. 2006105526, (Nov. 8, 2010), 16 pages.158"Foreign Notice of Allowance", Canadian Application No. 2412611, (Sep. 19, 2011), 1 page.159"Foreign Notice of Allowance", Japanese Application No. 2002-504581, (Sep. 16, 2011), 6 pages.160"Foreign Notice of Allowance", Mexican Application No. PA/a/2005/012067, (Nov. 13, 2009),3 pages.161"Foreign Office Action", Application Serial No. 2,412,611, (Feb. 9, 2009),6 pages.162"Foreign Office Action", Application Serial No. 2002-503702, Final Notice of Rejection,(Jun. 5, 2009),212 pages.163"Foreign Office Action", Application Serial No. 200610003709.2, (Jan. 9, 2009),8 pages.164"Foreign Office Action", Application Serial No. 200610051554.X, (Jul. 10, 2009),11 pages.165"Foreign Office Action", Australian Patent Application No. 2006200285, (May 20, 2010),2 pages.166"Foreign Office Action", Canadian Application No. 2408313, (Oct. 26, 2010), 5 pages.167"Foreign Office Action", Canadian Application No. 2408527, (Sep. 27, 2011), 3 pages.168"Foreign Office Action", Canadian Application No. 2412611, (Oct. 26, 2010), 2 pages.169"Foreign Office Action", European Patent Application No. 01935325.9,(Jun. 20, 2011),5 pages.170"Foreign Office Action", European Patent Application No. 01939034.3, (Nov. 5, 2007), 3 pages.171"Foreign Office Action", European Patent Application No. 01939368.5, (Feb. 25, 2010),3 pages.172"Foreign Office Action", Japanese Application No. 2002-503700, (Aug. 30, 2011), 4 pages.173"Foreign Office Action", Japanese Application No. 2002-503700, (May 10, 2011), 5 pages.174"Foreign Office Action", Japanese Application No. 2002-503701,(May 31, 2011),10 pages.175"Foreign Office Action", Japanese Application No. 2002-504581, (Dec. 17, 2010), 24 pages.176"Foreign Office Action", Japanese Application No. 2002-504581, (May 27, 2011), 6 pages.177"Foreign Office Action", Japanese Application No. 2006-060050, (Aug. 26, 2011), 4 pages.178"Foreign Office Action", Japanese Application No. 2006-071589, (Mar. 29, 2011), 9 pages.179"Foreign Office Action", Mexican Patent Application No. PA/a/2006/002493, (Sep. 14, 2009), 5 pages.180"Foreign Office Action", Russian Application No. 2006103267, (Apr. 20, 2010),10 pages.181"Foreign Office Action", Russian Application No. 2006105526, (Apr. 15, 2010),10 pages.182"Foreign Office Action", Russian Application No. 2006105526, (Aug. 24, 2010), 5 pages.183"HP Blade Sever BH Series Operating System Guide", Hewlett-Packard,(Jul. 2002).184"Manual of Patent Office Practice", Computer-Implemented Inventions, Chapter 16.09.02, Data Structures, (Oct. 2010), 3 pages.185"Microsoft Computer Dictionary 5th Edition", Entry for "Stack," Microsoft Press, ISBN 0-7356-1495-4, (May 1, 2002), p. 495.186"Microsoft Visual Basic 5.0 Programmer's Guide", Microsoft Press, (1997),pp. 42-43, 54-58.187"Microsoft Word 2000 Screenshots", (2000),11-17.188"Microsoft Word 2000 Screenshots", Word,(2000),1-17.189"Microsoft Word 2000", Screenshots,(1999),1-5.190"Mott Porous Metal. The Most Reliable Means of Restricting Gas Flow", Mott Corporation Webpage, retrieved from <<http://www.mottcorp.com/industry/oem/oem�Xflowres.htm>> on Aug. 23, 2004, 4 pages.191"Netscape Communicator 4.61 for OS/2 Warp", Netscape Communication Corporation, Software 1999, The Whole software release & Netscape�XVersion 4.61 {en}�X010615, Netscape Screenshot,(Oct. 2, 2002),1 page.192"Non Final Offfice Action", U.S. Appl. No. 11/170,521, (Jan. 21, 2009),86 pages.193"Non Final Office Action", U.S. Appl. No. 09/599,086, (Jan. 30, 2006), 33 pages.194"Non Final Office Action", U.S. Appl. No. 09/599,086, (Mar. 3, 2005), 25 pages.195"Non Final Office Action", U.S. Appl. No. 09/599,086, (Nov. 13, 2006), 33 pages.196"Non Final Office Action", U.S. Appl. No. 09/599,086, (Nov. 14, 2008), 55 pages.197"Non Final Office Action", U.S. Appl. No. 09/599,086, (Oct. 28, 2003), 21 pages.198"Non Final Office Action", U.S. Appl. No. 09/599,086, (Oct. 31, 2007), 48 pages.199"Non Final Office Action", U.S. Appl. No. 09/599,809, (May 13, 2009),25 pages.200"Non Final Office Action", U.S. Appl. No. 10/178,291, (Apr. 29, 2004), 14 pages.201"Non Final Office Action", U.S. Appl. No. 10/178,291, (Jun. 27, 2005), 22 pages.202"Non Final Office Action", U.S. Appl. No. 10/178,291, (Nov. 26, 2004), 21 pages.203"Non Final Office Action", U.S. Appl. No. 10/609,274, (Apr. 2, 2008),43 pages.204"Non Final Office Action", U.S. Appl. No. 10/609,274, (Jan. 17, 2007),43 pages.205"Non Final Office Action", U.S. Appl. No. 10/770,240, (Aug. 24, 2006), 25 pages.206"Non Final Office Action", U.S. Appl. No. 10/770,240, (May 1, 2008), 30 pages.207"Non Final Office Action", U.S. Appl. No. 10/770,240, (May 13, 2010), 15 pages.208"Non Final Office Action", U.S. Appl. No. 10/770,240, (Oct. 29, 2010), 14 pages.209"Non Final Office Action", U.S. Appl. No. 10/857,689, (Jun. 11, 2009),25 pages.210"Non Final Office Action", U.S. Appl. No. 10/876,433, (Apr. 24, 2009),62 pages.211"Non Final Office Action", U.S. Appl. No. 10/897,647, (Nov. 14, 2008), 28 pages.212"Non Final Office Action", U.S. Appl. No. 10/897,647, (Sep. 6, 2007), 21 pages.213"Non Final Office Action", U.S. Appl. No. 10/898,656, (Apr. 18, 2008), 17 pages.214"Non Final Office Action", U.S. Appl. No. 10/898,656, (Jul. 13, 2007), 13 pages.215"Non Final Office Action", U.S. Appl. No. 10/898,657, (Jul. 18, 2007), 18 pages.216"Non Final Office Action", U.S. Appl. No. 10/898,657, (Sep. 8, 2008), 24 pages.217"Non Final Office Action", U.S. Appl. No. 10/916,692, (Apr. 30, 2009),14 pages.218"Non Final Office Action", U.S. Appl. No. 10/939,588, (Feb. 18, 2009),40 pages.219"Non Final Office Action", U.S. Appl. No. 10/942,528, (Mar. 6, 2009),31 pages.220"Non Final Office Action", U.S. Appl. No. 10/955,665, (Apr. 2, 2009),19 pages.221"Non Final Office Action", U.S. Appl. No. 10/955,666, (May 7, 2009),28 pages.222"Non Final Office Action", U.S. Appl. No. 10/976,451, (Feb. 23, 2009),39 pages.223"Non Final Office Action", U.S. Appl. No. 10/977,198, (Feb. 2, 2009),15 pages.224"Non Final Office Action", U.S. Appl. No. 10/988,720, (Apr. 2, 2009),19 pages.225"Non Final Office Action", U.S. Appl. No. 10/990,152, (May 28, 2009),19 pages.226"Non Final Office Action", U.S. Appl. No. 11/036,910, (Oct. 2, 2008), 7 pages.227"Non Final Office Action", U.S. Appl. No. 11/095,254, (Jun. 8, 2009),21 pages.228"Non final Office Action", U.S. Appl. No. 11/234,767, (Feb. 26, 2009),37 pages.229"Non Final Office Action", U.S. Appl. No. 11/295,178, (May 27, 2009),111 pages.230"Non-Final OA", U.S. Appl. No. 10/939,588, (Feb. 18, 2009),29 pages.231"Non-Final Office Action", U.S. Appl. No. 09/599,299, (Aug. 12, 2004), 12 pages.232"Non-Final Office Action", U.S. Appl. No. 09/599,299, (Oct. 28, 2003), 32 pages.233"Non-Final Office Action", U.S. Appl. No. 09/599,812, (Feb. 27, 2003), 20 pages.234"Non-Final Office Action", U.S. Appl. No. 09/599,812, (Feb. 5, 2004), 35 pages.235"Non-Final Office Action", U.S. Appl. No. 10/011,150, (May 19, 2005), 7 pages.236"Non-Final Office Action", U.S. Appl. No. 10/402,640, (Apr. 30, 2010),4 pages.237"Non-Final Office Action", U.S. Appl. No. 10/723,863, (Aug. 23, 2006), 16 Pages.238"Non-Final Office Action", U.S. Appl. No. 10/723,863, (Feb. 8, 2007), 30 Pages.239"Non-Final Office Action", U.S. Appl. No. 10/723,863, (Nov. 6, 2007), 7 Pages.240"Non-Final Office Action", U.S. Appl. No. 10/846,428, (Jul. 19, 2007), 19 pages.241"Non-Final Office Action", U.S. Appl. No. 10/846,428, (Oct. 15, 2008), 23 pages.242"Non-Final Office Action", U.S. Appl. No. 10/916,692, (Apr. 5, 2010),6 pages.243"Non-Final Office Action", U.S. Appl. No. 10/939,588, (Aug. 27, 2009),28 pages.244"Non-Final Office Action", U.S. Appl. No. 10/976,451, (Apr. 9, 2010),11 pages.245"Non-Final Office Action", U.S. Appl. No. 10/976,451, (Nov. 10, 2010), 9 pages.246"Non-Final Office Action", U.S. Appl. No. 10/976,451, (Oct. 29, 2009),14 pages.247"Non-Final Office Action", U.S. Appl. No. 11/036,910, (Nov. 13, 2009),9 pages.248"Non-Final Office Action", U.S. Appl. No. 11/044,106, (Sep. 24, 2009),17 pages.249"Non-Final Office Action", U.S. Appl. No. 11/095,254, (Apr. 17, 2008),8 pages.250"Non-Final Office Action", U.S. Appl. No. 11/107,347, (Sep. 17, 2009),9 pages.251"Non-Final Office Action", U.S. Appl. No. 11/170,521, (Aug. 3, 2011), 16 pages.252"Non-Final Office Action", U.S. Appl. No. 11/218,149, (Sep. 20, 2010), 15 pages.253"Non-Final Office Action", U.S. Appl. No. 11/227,550, (Aug. 3, 2009),10 pages.254"Non-Final Office Action", U.S. Appl. No. 11/227,550, (Mar. 10, 2010),12 pages.255"Non-Final Office Action", U.S. Appl. No. 11/234,767, (Aug. 12, 2009),24 Pages.256"Non-Final Office Action", U.S. Appl. No. 11/234,767, (Nov. 26, 2010), 28 pages.257"Non-Final Office Action", U.S. Appl. No. 11/295,178, (May 26, 2010),45 pages.258"Non-Final Office Action", U.S. Appl. No. 11/557,931, (Oct. 20, 2009),27 pages.259"Non-Final Office Action", U.S. Appl. No. 11/567,140, (May 18, 2010),8 pages.260"Non-Final Office Action", U.S. Appl. No. 11/567,149, (Sep. 8, 2009),5 pages.261"Non-Final Office Action", U.S. Appl. No. 12/028,651, (Jan. 3, 2011),16 pages.262"Non-Final Office Action", U.S. Appl. No. 12/061,613, (Sep. 28, 2010), 9 pages.263"Notice of Allowance", U.S. Appl. No. 09/599,086, (Aug. 17, 2009), 59 pages.264"Notice of Allowance", U.S. Appl. No. 09/599,299, (Nov. 30, 2004), 7 pages.265"Notice of Allowance", U.S. Appl. No. 09/599,806, (Jan. 21, 2005),9 pages.266"Notice of Allowance", U.S. Appl. No. 09/599,812, (Aug. 3, 2004), 12 pages.267"Notice of Allowance", U.S. Appl. No. 10/011,150, (Dec. 16, 2005), 4 pages.268"Notice of Allowance", U.S. Appl. No. 10/178,291, (Feb. 6, 2006), 7 pages.269"Notice of Allowance", U.S. Appl. No. 10/395,505, (Oct. 4, 2006),8 pages.270"Notice of Allowance", U.S. Appl. No. 10/402,640, (Jun. 15, 2010),6 pages.271"Notice of Allowance", U.S. Appl. No. 10/404,312, (Jan. 12, 2009),12 pages.272"Notice of Allowance", U.S. Appl. No. 10/610,504, (Sep. 6, 2006),4 Pages.273"Notice of Allowance", U.S. Appl. No. 10/632,437, (May 21, 2009),15 pages.274"Notice of Allowance", U.S. Appl. No. 10/723,863, (Jun. 30, 2008), 9 Pages.275"Notice of Allowance", U.S. Appl. No. 10/781,586, (May 9, 2008),6 pages.276"Notice of Allowance", U.S. Appl. No. 10/846,428, (Apr. 29, 2009), 10 pages.277"Notice of Allowance", U.S. Appl. No. 10/876,418, (Dec. 31, 2008),8 pages.278"Notice of Allowance", U.S. Appl. No. 10/897,647, (Jan. 19, 2010), 13 pages.279"Notice of Allowance", U.S. Appl. No. 10/898,656, (Jan. 2, 2009), 9 pages.280"Notice of Allowance", U.S. Appl. No. 10/898,657, (Jun. 11, 2009), 20 pages.281"Notice of Allowance", U.S. Appl. No. 10/916,692, (Jun. 14, 2010),6 pages.282"Notice of Allowance", U.S. Appl. No. 10/939,588, (Mar. 10, 2010),10 pages.283"Notice of Allowance", U.S. Appl. No. 10/955,665, (Nov. 3, 2009),8 pages.284"Notice of Allowance", U.S. Appl. No. 10/988,718, (Apr. 9, 2009),17 pages.285"Notice of Allowance", U.S. Appl. No. 10/988,720, (Sep. 17, 2009),18 pages.286"Notice of Allowance", U.S. Appl. No. 11/036,910, (Dec. 7, 2010), 7 pages.287"Notice of Allowance", U.S. Appl. No. 11/044,106, (Mar. 15, 2010),7 pages.288"Notice of Allowance", U.S. Appl. No. 11/072,087, (Feb. 23, 2010),4 pages.289"Notice of Allowance", U.S. Appl. No. 11/095,254, (Nov. 18, 2009),8 pages.290"Notice of Allowance", U.S. Appl. No. 11/107,347, (Dec. 13, 2010),11 pages.291"Notice of Allowance", U.S. Appl. No. 11/167,514, (Mar. 11, 2009),6 pages.292"Notice of Allowance", U.S. Appl. No. 11/203,937, (Aug. 3, 2009),7 pages.293"Notice of Allowance", U.S. Appl. No. 11/203,937, (Aug. 31, 2009),2 pages.294"Notice of Allowance", U.S. Appl. No. 11/203,937, Supplemental,(Sep. 15, 2009),2 pages.295"Notice of Allowance", U.S. Appl. No. 11/218,149, (Feb. 11, 2011),7 pages.296"Notice of Allowance", U.S. Appl. No. 11/295,178, (Mar. 22, 2011),20 pages.297"Notice of Allowance", U.S. Appl. No. 11/557,931, (May 5, 2010),7 pages.298"Notice of Allowance", U.S. Appl. No. 11/567,140, (Oct. 11, 2011), 11 pages.299"Notice of Allowance", U.S. Appl. No. 11/872,703, (May 14, 2010),18 pages.300"Notice of Allowance", U.S. Appl. No. 11/931,730, (Feb. 2, 2011),7 pages.301"Notice of Allowance", U.S. Appl. No. 12/021,894, (Oct. 29, 2010), 9 pages.302"Notice of Allowance", U.S. Appl. No. 12/249,973, (Sep. 28, 2011), 9 pages.303"Notice of Re-Examination", Application Serial No. 01813138.7, (Mar. 11, 2009),27 pages.304"Notice of Reexamination", Chinese Application No. 01813138.7, (Apr. 22, 2011), 14 pages.305"OLE Open Doc and Network", Retrieved from http://www.pcwebopedia.com on May 9, 2006, Webopedia entries,(May 16, 1998),7 pages.306"OMG XML Metadata Interchange (XMI) Specification", Retrieved from: <http://www.omg.org/cgi-bin/doc?formal/02-01-01.pdf> on Dec. 2, 2009, Version 1.2,(Jan. 2002),268 pages.307"PCT Search Report", PCT Application No. PCT/IB98/01392, (Apr. 9, 1999),3 pages.308"PCT Search Report", PCT Application No. PCT/IB99/02003, (Nov. 28, 2000),3 pages.309"PCT Search Report", PCT Application No. PCT/US01/15581, (Jan. 29, 2003), 3 pages.310"PCT Search Report", PCT Application No. PCT/US99/09620, (Sep. 22, 1999),3 pages.311"Restriction Requirement", U.S. Appl. No. 09/599,806, (Mar. 3, 2003),5 pages.312"Restriction Requirement", U.S. Appl. No. 10/011,150, (Dec. 15, 2004), 5 pages.313"Restriction Requirement", U.S. Appl. No. 10/770,240, (Jan. 26, 2009),7 pages.314"Restriction Requirement", U.S. Appl. No. 10/781,586, (Jun. 26, 2006),5 pages.315"Restriction Requirement", U.S. Appl. No. 11/095,254, (Nov. 1, 2007),8 pages.316"Restriction Requirement", U.S. Appl. No. 11/227,550, (Apr. 2, 2009),8 pages.317"SmartUpdate Developer's Guide", Retrieved from http://developer.netscapte.com:80/docs/manuals/communicator/jarman/index.htm on Dec. 8, 2000, Netscape Communications Corp,(Mar. 11, 1999),83 pages.318"Stack Algorithm for Extracting Subtree from Serialized Tree", IBM Technical Disclosure Bulletin, TDB-ACC-NO; NN94033, (Mar. 1, 1994),2 pages.319"Store and Organize Related Project Files in a Binder", Getting results with Microsoft Office,(1990),pp. 109-112.320"Streamlining Content Creation", Ixia Soft Jun. 6, 2002,pp. 1-16.321"Supplemental Notice of Allowance", U.S. Appl. No. 10/781,586, (Jul. 18, 2008),3 pages.322"Supplemental Notice of Allowance", U.S. Appl. No. 10/781,586, (Jun. 4, 2008),2 pages.323"Supplemental Notice of Allowance", U.S. Appl. No. 10/955,665, (Feb. 4, 2010),2 pages.324"Supplemental Notice of Allowance", U.S. Appl. No. 10/955,665, (Mar. 5, 2010),2 pages.325"Supplemental Notice of Allowance", U.S. Appl. No. 10/955,665, (Nov. 27, 2009),2 pages.326"Supplemental Notice of Allowance", U.S. Appl. No. 10/990,152, (Apr. 19, 2010),2 pages.327"Supplemental Notice of Allowance", U.S. Appl. No. 11/036,910, (Jan. 5, 2011),2 pages.328"Supplemental Notice of Allowance", U.S. Appl. No. 11/044,106, (May 13, 2010),6 pages.329"Supplemental Notice of Allowance", U.S. Appl. No. 11/044,106, (May 19, 2010),5 pages.330"Supplemental Notice of Allowance", U.S. Appl. No. 11/072,087, (Apr. 19, 2010),2 pages.331"Supplemental Notice of Allowance", U.S. Appl. No. 11/107,347, (Jun. 10, 2011),10 pages.332"Supplemental Notice of Allowance", U.S. Appl. No. 11/218,149, (Apr. 5, 2011),2 pages.333"Supplemental Notice of Allowance", U.S. Appl. No. 11/218,149, (Jun. 6, 2011),2 pages.334"Supplemental Notice of Allowance", U.S. Appl. No. 11/931,730, (Apr. 22, 2011), 2 pages.335"Supplemental Notice of Allowance", U.S. Appl. No. 11/931,730, (Mar. 2, 2011),2 pages.336"Supplemental Notice of Allowance", U.S. Appl. No. 11/931,730, (May 6, 2011),2 pages.337"Supplemental Notice of Allowance", U.S. Appl. No. 12/021,894, (Feb. 8, 2011),6 pages.338"Supplemental Notice of Allowance", U.S. Appl. No. 12/021,894, (Jan. 12, 2011),6 pages.339"Supplementary European Search Report", Application No. 04779161.1, (Jul. 14, 2011), 4 pages.340"TEI: P4 Guidelines", TEI Consortium, (Mar. 2002), 340 pages.341"Text Encoding Initiative", TEI Consortium, (Mar. 2002),1 page.342"Validation with MSXML and XML Schema", Windows Developer Magazine, (Jan. 1, 2002),5 pages.343"Whitehill Composer Software product", Retrieved from www.xml.com/pub/p/221 on Apr. 8, 2004, Whitehill Technologies, Inc., (Apr. 8, 2004),2 pages.344"XForm 1.0", W3C,(Jul. 16, 2001).345"XML Forms Architecture (XFA)", Retrieved from http://xml.coverpages.org/xfa.html on Aug. 17, 2006, Cover Pages Technology Reports,,(Jun. 16, 1999),p. 1.346Adams, Susie et al., "BizTalk Unleashed", Sams publishing, 2002, first printing Mar. 2001, 1-2, 31-138.347Adams, Susie et al., "BizTalk Unleashed", Sams publishing, 2002, first printing Mar. 2001,1-2, 31-138.348Akihiro, Senda "Word 2000, Conservative-Looking but ��Attentive�� New Function", NIKKEI PC 21, vol. 4, No. 8,(Aug. 1, 1999),pp. 115-116.349Alschuler, Liora "A Tour of XMetal", Retrieved from: <http://www.xml.com/pub/a/SeyboldReport/ip031102.html> on Feb. 5, 2003, XML.com, Online! XPOO2230081,(Jul. 14, 1999),3 pages.350Altova, "Altova Tools for XPath 1.0/2.0", Retrieved from http://www.altova.comdev�Xportal�Xxpath.html, Altova,(2007),1-12.351Altova, "XML Spy 4.0 Manual", 1998-2001 Altova Inc. & Altova GmbH, (Sep. 10, 2001),pp. 1-90, 343-362.352Altova, et al., "User and Reference Manual Version 4.4", www.xmlspy.com, (May 24, 2007),1-565.353Altova, et al., "XML Spy, XML Integrated Development Environments", Altova Inc.,(2002),pp. 1-18.354Anat, Eyal et al., "Integrating and Customizing Hererogeneous E-Commerce Applications", The VLDB Journal�XThe International Journal on Very Large Data Bases, vol. 10, Issue 1,(Aug. 2001),16-38.355Asche, Ruediger R., "Multithreading for Rookies", Microsoft Developer Network Technology Group, Retrieved Apr. 17, 2002 from http://msdn.microsoft.com/library/en-us/dndllpro/html/msdn�Xthreads.asp?frame=true, (Sep. 24, 1993),13 pages.356Au, Irene et al., "Netscape Communicator's Collapsible Toolbars", CHI 98, Human Factors in Computing Systems, Conference Proceedings, LA, CA,(Apr. 18-23, 1998),pp. 81-86.357Baldwin, J F., et al., "A Mass Assignment Based ID3 Algorithm for Decision Tree Introduction", International Journal of Intelligent Systems, vol. 12, No. 7, (1997),pp. 523-548.358Barker, et al., "Creating In-Line Objects Within An Integrated Editing Environment", IBM Technical Disclosure Bulletin, vol. 27, No. 5,(Oct. 1984),p. 2962.359Battle, Steven A., et al., "Flexible Information Presentation with XML", The Institution of Electrical Engineers, (1998),6 pages.360Beauchemin, Dave "Using InfoPath to Create Smart Forms", Retrieved from the Internet at http:/www.microsoft.com/office/infopath/prodinfo/using.mspx on Jan. 21, 2007,(Mar. 27, 2003).361Begun, Andrew et al., "Support and Troubleshooting for XML Schemas in InfoPath 2003", Microsoft Office InfoPath 2003 Technical Articles, Retrieved from the Internet at http://msdn2.microsoft.com/en-us/library/aa168241(office.11,d=printer).aspx on Jan. 21, 2007,(Aug. 2004).362Ben-Natan, Ron et al., "Internet Platform for Creating and Supporting Communities", U.S. Appl. No. 60/203,081, filed May 9, 2000,31 pages.363Berg, A "Naming and Binding: Monikers", Inside OLE, Chapter 9, Harmony Books, (1995),pp. 431-490.364Borland, Russo "Running Microsoft Word 97", 314-315, 338, 361-362, 390, and 714-719.365Brabrand, et al., "Power Forms Declarative Client-side Form Field Validation", (2002),1-20.366Bradley, Neil "The XML Companion, Third Edition", Published by Addison Wesley Professional, http://proquest.safaribooksonline.com0201770598, http,(Dec. 12, 2001),1-18.367Bray, Tim "Extensible Markup Language (XML)", http://www.textuality.com/sgml-erb/WD-xml.html, second named inventor Jean Paoli, third named inventor C.M. Sperberg-McQueen,(Feb. 10, 1998),37 Pages.368Brogden, William "Arbortext Adept 8 Editor Review", Retrieved from: <www.xml.com/pub/a/1999/09/adept/AdeptRvw.htm> on Feb. 5, 2003, O'Reilly XML.COM, Online!,(Sep. 22, 1999),4 pages.369Burch, Barbara "Notes R5 Technical Overview", Retrieved from: on Aug. 13, 2010, (Apr. 1, 1999),14 pages.370Burch, Barbara "Notes R5 Technical Overview", Retrieved from: <http://www.ibm.com/developerworks/lotus/library/1s-Notes�XR5�XTechnical�XOverview> on Aug. 13, 2010, (Apr. 1, 1999),14 pages.371Chen, Ya B., et al., "Designing Valid XML Views", S. Spaccapietra, S.T. March, and Y. Kambayashi (Eds.): ER 2002, LNCS 2503, Copyright: Springer-Verlag Berlin Heidelberg 2002,(2002),pp. 463-477.372Chen, Yi et al., "XKvalidator: A Constraint Validator for XML", CIKM '02, Nov. 4-9, 2002, McLean, VA, USA, Copyright 2002, ACM, ISBN 1-58113-492-4/02/0011,(Nov. 4-9, 2002),pp. 446-452.373Chien, et al., "Efficient Management of Multiversion Documents by Object Referencing", Proceedings of the 27th VLDB Conference,(2001),pp. 291-300.374Chien, Shu-Yao et al., "Efficient Schemes for Managing Multiversion XML Documents", The VLDB Journal 2002, (Dec. 19, 2002),pp. 332-353.375Chien, Shu-Yao et al., "Storing and Querying Multiversion XML Documents using Durable Node Numbers", IEEE,(2002),pp. 232-241.376Chien, Shu-Yoa et al., "XML Document Versioning", SIGMOD Record, vol. 30, No. 3,,(Sep. 2001),pp. 46-53.377Chuang, Tyng-Ruey "Generic Validation of Structural Content with Parametric Modules", ICFP 2001 International Conference on Functional Programming, vol. 36, No. 10, Available at <http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.7.6412&rep=rep1&type=pdf>,(Sep. 3, 2001),12 pages.378Ciancarini, Paolo A., et al., "Managing Complex Documents Over the WWW: A Case Study for XML", Transactions on Knowledge and Data Engineering, vol. 11, No. 4, Available at <http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.18.1679&rep=rep1&type=pdf>,(Apr. 1999),pp. 1-14.379Clapp, D "The NeXT Application Kit Part 1: Non-Responsive Classes", The NeXT Bible Chapter 16, (1990),pp. 275-293.380Clark, James "XSL Transformation (XSLT), Version 1.0", Retrieved from: <www.w3.org/TR/1999/REC-xslt19991116> on Oct. 26, 2009, WC3,(Nov. 16, 1999),57 pages.381Clark, James et al., "XML Path Language (XPath)", Retrieved from: <www.w3.org/TR/1999/RCE-xpath-19991116> Oct. 26, 2009, Version 1.0,(Nov. 16, 1999),37 pages.382Clark, Peter "From Small Beginnings", Knowledge Management, (Nov. 2001),pp. 28-30.383Cloete, I et al., "CID3: An Extension of ID3 for Attributes with Ordered Domains", South African Computer Journal, vol. 4, (1991),pp. 10-16.384Cover, Robin "XML Forms Architecture (XFA)", Cover Pages. Retrieved from "http://xml.coverpages.org/xfa.html" on Aug. 17, 2006, (Apr. 19, 2000),4 pages.385Davidow, Ari "XML Editors: Allegations of Functionality in Search of Reality", Retrieved from: <http://www.ivritype.com/xml/> on Feb. 9, 2009, SP002230082,(Oct. 12, 1999),16 pages.386Dayton, Linnea et al., "Photo Shop 5/5.5 WOW! Book", 2000, Peachpit Press, (2000),pp. 8-17.387Dilascia, Paul et al., "Sweeper", Microsoft interactive developer, vol. 1., No. 1,(1996),pp. 16-52.388Dodds, "Toward an XPath API", xml.com,(May 7, 2001),1-3.389Dorward, Sean et al., "Unix Variants", Unix Review, vol. 10, No. 4, (Apr. 1992),pp. 29-31.390Dubinko, Micah "XForms and Microsoft InfoPath", Retrieved from the Internet at http://www.xml.com/Ipt/a/1311 on Jan. 21, 2007,(Oct. 29, 2003).391Duce, et al., "Web 2D Graphics File Formats", Google 2003, (2003), pp. 43-65.392Dyck, Timothy "XML Spy Tops as XML Editor", eWeek, vol. 19, No. 47, ,(Nov. 25, 2002),3 pages.393Esposito, Dino "Cutting Edge No. 8", Microsoft Internet Developer, (Jan. 18, 2000),13 pages.394Grosso, et al., "XML Fragment Interchange", W3C,(Feb. 2001),1-28.395Halberg, Bruce et al., "Using Microsoft Excel 97", (1997),191-201, 213-219.396Halberg, et al., "Using Microsoft Excel 97", Que Corporation,,(1997),pp. 1-9, 18-25, 85-89, 98-101, 106-113, 124-127, 144-147, 190-201, 209-210, 213-227, 581-590, 632-633, 650-655, 712-714.397Hall, Richard S., "Agent-based Software Configuration and Development", http://www.doc.ic.ac.uk/˜alw/edu/theses/hall-phd-0599.pdf on Jun. 8, 2009, Thesis of the University of Colorado,(May 1, 1999),182 pages.398Hall, Richard S., "Evaluating Software Deployment Languages and Schema", In Proceedings of International Conference on Software Maintenance,(Nov. 1998),9 pages.399Hall, Richard S., et al., "Specifying the Deployable Software Description Format in XML", CU-SERL-207-99, Software Engineering Research Laboratory, University of Colorado at Boulder,(Mar. 31, 1999), 17 pages.400Han, Richard et al., "Websplitter: A Unified XML Framework for Multi-Device Collaborative Web Browsing", ACM Conference on Computer Supported Cooperative Work, (2000),10 pages.401Hardy, Matthew R., et al., "Mapping and Displaying Structural Transformations between XML and PDF", Proceedings of the 2002 ACM symposium on Document engineering, (Nov. 8-9, 2002),pp. 95-102.402Haukeland, Jan-Henrick "Tsbiff-tildeslash biff�XVersion 1.2.1", http://web.archive.org/web/19990912001527/http://www.tildeslash.com/tsbiff/., (Jun. 1999),2 pages.403Herzner, Wolfgang et al., "CDAM-Compound Document Access and Management. An Object-Oriented Approach", ACM SIGOIS Bulletin, vol. 12, Issue 1, MultiMedia Systems Interaction and Applications, Chapter 3,,(Jul. 1991),18 pages.404Hoffman, Michael "Architecture of Microsoft Office InfoPath 2003", Microsoft Office InfoPath 2003 Technical Articles, Retrieved from the Internet at http://msdn2.microsoft.com/en-us/library/aa219024(office.11,d=printer).aspx on Jan. 21, 2007,(Jun. 2003).405Honkala, Mikko et al., "Multimodal Interaction with XForms", ICWE '06, (2006), pp. 201-208.406Howlett, Scott "A New Function for SQL Server 2000", MSDN Magazine, No. 1, (Apr. 18, 2000),11 pages.407Hu, et al., "A Programmable Editor for Developing Structured Documents based on Bidirectional Transformations", ACM,(Aug. 2004),178-179.408Hwang, Kai et al., "Micro-Firewalls for Dynamic Network Security with Distributed Intrusion Detection", IEEE International Symposium on Network Computing and Applications 2001, (2001),pp. 68-79.409Idle, et al., "Outline of the International Standard Linguistic Annotation Framework", Proceedings of the ACL 2003 workshop on Linguistic Annotation, (Jul. 2003), 5 pages.410Kaiya, Haruniko et al., "Specifying Runtime Environments and Functionalities of Downloadable Components under the Sandbox Model", International Symposium on Principles of Software Evolution 2000, (2000),pp. 138-142.411Kanemoto, Hirotaka et al., "An Efficiently Updatable Index Scheme for Structured Documents", DEXA'98, (1998),pp. 991-996.412Kaori, Iwantani et al., "Perfect Manual of Clarisworks 4.0 for Macintosh", 1st Edition, Japan,(07/297),pp. 153-167.413Kath, Randy "Managing Virtual Memory in Win32", Microsoft Developer Network Technology Group, Retrieved Apr. 17, 2002 from http://msdn.microsoft.comilibrary/en-us/dngenlib/html/msdn�Xvirtmm.asp?frame=true, (Jan. 20, 1993),9 pages.414Kay, Michael "XSL Transfornmations (XSLT) Version 2.0", http://www.w3.org/TR/2005/WD-xslt20-20050404, (04/205),1-374.415Kim, Sang-Kyun et al., "Immediate and Partial Validation Mechanism for the Conflict Resolution of Update Operations in XML Databases", WAIM 2002, LNCS 2419, 2002, Springer-Verlag Berlin Heidelberg, (2002),pp. 387-396.416Klarlund, Nils "DSD: A Schema Language for XML", ACM, FSMP Portland Oregon, (2000),101-111.417Kobayashi, M. et al., "An Update on BTRON-specification OS Development", Proceedings of the 8thTRON Project Symposium, 1991, 0-8186-2475-2/91,(1991),pp. 132-140.418Komatsu, Naohisa et al., "A Proposal on Digital Watermark in Document Image Communication and It's Application to Realizing a Signature", Electronics and Communication in Japan, Part I: Communications, vol. 73, No. 5, (May 1990),pp. 22-23.419Leblond, et al., "PC Magazine Guide to Quattro Pro for Windows", Ziff-Davis Press,(1993),pp. 9-11, 42-61.420Lehtonen, Miro et al., "A Dynamic User Interface for Document Assembly", Department of Computer Science, University of Helsinki,(Nov. 2002).421Mansfield, Ron "Excel 97 for Busy People", Osborne/McGraw-Hill,,(Jan. 27, 1997),pp. 48-50.422McCright, John S., "New Tool Kit to Link Groove with Microsoft SharePoint", Retrieved from: <http://www.eweek.com/c/a/Enterprise-Applications/New-Tool-Kit-to-Link-Groove-With-Microsoft-SharePoint/> on Dec. 28, 2009, (Jul. 29, 2002),3 pages.423Mehta, Manish et al., "SLIQ: A Fast Scalable Classifier for Data Mining", available at <<http://www.dbis.informatik.hu-berlin.de/dbisold/lehre/WS0405/KDD/paper/MAR96.pdf>>, (Mar. 1996),15 Pages.424Mengel, A et al., "MATE Dialogue Annotation Guidelines", http://www.ims.uni-stuttgart.de/projekte/mate/mdag, (Jan. 8, 2000), 64 pages.425Musgrave, S "Networking Technology�XImpact and Opportunities", Survey and Statistical Computing 1996, Proceedings of the Second ASC International Conference, London, UK,, (Sep. 1996),pp. 369-378.426Nelson, Joe "Client-side Form Validation Using JavaScript", Developer Advisory, (Sep. 21, 2001).427Noore, Afzel "A Secure Conditional Access System using Digital Signature and Encryption", International Conference on Consumer Electronics, (Jun. 2003),pp. 220-221.428Noriko, Matsushita "Step-up Training of Clarisworks (tabulation), Successful Use of Spreadsheet and Tabulation", Mac People, vol. 4, No. 19,(Oct. 1, 1998),pp. 138-139.429Pacheco, Xavier et al., "Delphi 5 Developer's Guide", Sams Publishing. Chapter 31, Section: Data Streaming,(1999),4.430Pike, Rob et al., "Plan 9 From Bell Labs", AT&T Bell Laboratories, UKUUG, Summer 1990, 10 pages.431Pike, Rob et al., "The Use of Name Spaces in Plan 9", Operating Systems Review, vol. 27, No. 2, (Apr. 1993),pp. 72-76.432Prevelakis, Vassilis et al., "Sandboxing Applications", FREENIX Track: 2001 USENIX Annual Technical Conference, (2001),pp. 119-126.433Prosise, Jeff "Programming Microsoft Net", retrieved from: <http://academic.safaribooksonline.com/print?xmlid=0-7356-1376-1/IDAVO3T> on Mar. 3, 2011, Microsoft Press,(May 15, 2002),24 pages.434R. Moats, RFC2141, URN Syntax, published on May 1997, pp. 1-9.435R. Moats, RFC2648, A URN Namespace for IETF Documents, published on Aug. 1999, pp. 1-31.436Rado, Dave "How to create a template that makes it easy for users to ��fill in the blanks�� without doing any programming,", Retrieved from http://word.mvps.org/FAQs/Customization/FillinTheBlanks.htm, (Apr. 2004),pp. 1-2.437Raggett, "HTML Tables", Retrieved from: <http:www.//is-edu.homuns.edu.vn/WebLib/books/Web/Tel/html3-tables.html> on Aug. 6, 2006, W3C Internet Draft,(Jul. 7, 1995),pp. 1-12.438Raman, T. V., et al., "XForms 1.0", (Dec. 2001),Section 1-12.2.3 & Appendices A-G.439Rapaport, Lowell "Get More From SharePoint", Transform Magazine, vol. 11, No. 3, (Mar. 2002),2 pages.440Reagan, Moore W., et al., "Collection-based persistent digital archives", Provisional U.S. Appl. No. 60/191,662, filed Mar. 23, 2000, 133.441Rees, Michael J., "Evolving the Browser Towards a Standard User Interface Architecture", School of Information Technology, Bond University, Australia,(2001).442Reilly, Douglas J., "Programming Microsoft Web Forms", retrieved from: <http://academic.safaribooksonline.com/print?xmlid=0735621799/systemdotwebdotuidotweb> on Mar. 3. 2011, Microsoft Press,(Nov. 2, 2005),52 pages.443Rogge, Boris et al., "Validating MPEG-21 Encapsulated Functional Metadata", IEEE 2002, ISBN 0-7803-7304-9/02,(2002),pp. 209-212.444Sato, T. et al., "XFIG Version 3.2 Patchlevel 2 Users Manual Edition 1.0", Available at http://tinf2.vub.ac.be/˜dvermeir/manuals/xfig/lib/X11/xfig/html/index.html, (Jul. 2, 1998), 37 pages.445Schmid, Mathew et al., "Protecting Data from Malicious Software", 18th Annual Security Applications Conference, (2002),pp. 199-208.446Sebastiani, F "A Tutorial on Automated Text Categorisation", In Analia Amandi and Ricardo Zunino, editors, Proceedings of ASAI-99, 1st Argentinean Symposium on Artificial Intelligence, Buenos Aires, AR, (1999),pp. 7-35.447Singh, Darshan "Microsoft InfoPath 2003 By Example", Retrieved from the Internet at http://www.perfectxml.com/InfoPath.asp on Jan. 21, 2007,(Apr. 20, 2003).448Sollins et al., RFC1737 Functional Requirements for Uniform Resource Names, published on Dec. 1994, pp. 1-8.449Staneck, W "Internal and External Media", Electronic Publishing Unleashed, Chapter 22,,(1995),pp. 510-542.450STYLUSSTUDIO, "StylusStudio: XPath Tools", 2004-2007, StylusStudio,1-14.451Sun, Q et al., "A Robust and Secure Media Signature Scheme for JPEG Images", Proceeding of 2002 IEEE Workshop on Multimedia Signal Processing,(Dec. 2002),pp. 296-299.452Sutanthavibul, Supoj et al., "XFIG Version 3.2 Patchlevel 2 (Jul. 2, 1998) Users Manual (Edition 1.0)", Retrieved from: <www.ice.mtu.edu/online�Xdocs/sfig332/> on Jan. 28, 2003, Internet Document XP002229137,(Jul. 2, 1998),60 pages.453Tomimori, Hiroyuki et al., "An Efficient and Flexible Access Control Framework for Java Programs in Mobile Terminals", Proceeding of 22nd Int'l Conference on Distributed Computing Systems Workshops,(2002),pp. 777-782.454Trupin, J "The Visual Programmer", Microsoft Systems Journal,(Apr. 1996),pp. 103-105.455Udell, Jon "InfoPath and XForms", Retrieved from the Internet at http://weblog.infoworld.com/udell/2003/02/26.html,(Feb. 26, 2003).456Usdin, Tommie et al., "XML: Not a Silver Bullet, But a Great Pipe Wrench", Standard View vol. 6, No. 3, (Sep. 2, 1998),pp. 125-132.457Van Hoff, Arthur et al., "The Open Software Description Format", Retrieved from: <www.w3.org/TR/NOTE-OSD> on Nov. 7, 2003, (Aug. 13, 1997),11 pages.458Varlamis, Iraklis et al., "Bridging XML-Schema and relational database. A System for generating and manipulating relational databases using valid XML documents", DocEng 01, ACM 1-58113-432-0/01/0011,(Nov. 9-10, 2001),pp. 105-114.459Vasters, Clemens F., "BizTalk Server 2000 A Beginner's Guide", Osborne/McGraw-Hill,(2001),1-2, 359-402.460Villard, et al., "An Incremental XSLT Transformation Processor for XML Document Manipulation", http://www2002.org/CDROM/refereed/321, Printed on May 18, 2007,(May 2002),25 pages.461Watt, Andrew "MIcrosoft Office Infopath 2003 Kick Start", (Published by Sams) Print ISBN-10:0-672-32623-X, (Mar. 24, 2004),1-57.462WEBOPEDIA, "Definition of Network", Retrieved from: <http://www.webopedia.com/TERM/n/network.html>,(Sep. 1, 1996),2 pages.463WEBOPEDIA, "Definition of OLE", Retrieved from: <http://www.webopedia.com/TERM/O/OLE.html>,(May 16, 1998),3 pages.464WEBOPEDIA, "Definition of OpenDoc", Retrieved from: <http://www.webopedia.com/TERM/O/OpenDoc.html>,(Sep. 18, 1997),3 pages.465Williams, Sara et al., "The Component Object Model: A Technical Overview", Microsoft Corp,(Oct. 1994),pp. 1-14.466Wong, Raymond K., et al., "Managing and Querying Multi-Version XML Data with Update Logging", DocEng '02, (Nov. 8-9, 2002),8 pages.467XMLSPY, "XmlSpy 2004 Enterprise Edition Manual", Altova,(May 17, 2004),1-25, 220-225.468Yasuji, Fukuhara "Clarisworks, Introduction to Business Document Construction, No. 4, Estimate", NIKKEI Mac, No. 14,(May 17, 1994),pp. 197-204.469Zaki, Mohammed J., et al., "Parallel Classification for Data Mining on Shared-Memory Multiprocessors", ACM, (Mar. 1999),pp. 1-8.470Zdonik, S "Object Management System Concepts", ACM,(1984),pp. 13-19.471Zdonik, Stanley B., "Object Management System Concepts", Supporting Integrated Office Workstation Applications, Doctoral Thesis, Massachusetts Institute of Technology, (1983), 262 pages.�Q�H�U�M�Q�ޥ� �ޥΥ��M�Q�ӽФ���o�G��� �ӽЪ��M�Q�W��US82812982007�~8��27��2012�~10��2��International Business Machines CorporationEvaluating computer driver update complianceUS84024522009�~4��2��2013�~3��19��International Business Machines CorporationAutomatically recommending an upgrade approach for a customizable software productUS200902717832009�~4��15��2009�~10��29��Htc CorporationElectronic device and user interface display method thereofUS201002575182009�~4��2��2010�~10��7��International Business Machines CorporationAutomatically recommending an upgrade approach for a customizable software product������l�Ϥ�Google ���� - Sitemap - USPTO �j�q�U�� - ���p�v�F�� - �A�ȱ�� - ���� Google �M�Q - �N���^�X��ƬO�Ѭ��ӷ~�M�Q��Ʈw (IFI CLAIMS Patent Services) ����©2012 Google