To date, integrating services such as web services and local services with client applications has been a challenging task. Challenges are posed not only from the standpoint of easing integration with client applications, but also exposing services in a graceful, consistent way. These challenges have resulted in complex coding scenarios as well as inconsistent user experiences which, in turn, can lead to dissatisfaction on the part of users.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
Various embodiments provide a service platform that integrates services, such as web services and/or local services, across a variety of applications. In at least some embodiments, services can be integrated with legacy applications that are “unaware” of such services, as well as applications that are aware of such services.
In at least some embodiments, the platform comprises a multi-layered structure designed to integrate services across a variety of applications. The multi-layered structure includes, in at least some embodiments, a global integration layer that is designed to integrate services with legacy applications, as well as a common control integration layer and a custom integration layer. The common control integration layer can be used to provide a common control that can be used across applications to integrate not only services of which the applications are aware, but services of which the applications are not aware. The custom integration layer can be used by various applications to customize user interfaces that are designed to integrate various offered services.
The same numbers are used throughout the drawings to reference like features.
Overview
Various embodiments provide a service platform that integrates services, such as web services and/or local services, across a variety of applications. In at least some embodiments, services can be integrated with legacy applications that are “unaware” of such services, as well as applications that are aware of such services. Services can include, by way of example and not limitation, any of a variety of services such as search services, definition services, investigation services, mapping services, news services, image services, translation services and the like. In one or more embodiments, the service platform is extensible to provide for integration of new or changed services in a seamless manner across a variety of applications.
In at least some embodiments, the platform comprises a multi-layered structure designed to integrate services across a variety of applications. The multi-layered structure includes, in at least some embodiments, a global integration layer that is designed to integrate services with legacy applications, as well as a common control integration layer and a custom integration layer. The common control integration layer can be used to provide a common control that can be used across applications to integrate not only services of which the applications are aware, but services of which the applications are not aware. The custom integration layer can be used by various applications to customize user interfaces that are designed to integrate various offered services.
In the discussion that follows, a section entitled “Operating Environment” is provided and describes one environment in which one or more embodiments can be employed. Following this, a section entitled “Example Multi-layered Service Platform” is provided and describes a multi-layered platform in accordance with one or more embodiments. Next, a section entitled “Implementation Example” describes an example implementation of a multi-layered service platform. Next, a section entitled “Declarative Model” is provided and describes an example declarative model that can be used to enable service providers to describe services that are offered. Following this, sections entitled “Global Integration Layer—User Interface Example”, “Common Control Integration Layer—User Interface Example”, and “Custom Integration Layer—User Interface Example” each respectively provide examples of user interfaces in accordance with one or more embodiments. Next, a section entitled “Example Methods” describes example methods in accordance with one or more embodiments. A section entitled “Example APIs” gives a description of a set of APIs in accordance with one or more embodiments. Finally, a section entitled “Example System” describes an example system that can be utilized to implemented one or more embodiments.
Operating Environment
In addition, computing device 102 includes a service platform 110. The service platform is designed to integrate services, such as web services and/or local services, across a variety of applications such as those mentioned above and others. In at least some embodiments, services can be integrated with legacy applications that are “unaware” of such services, as well as applications that are aware of such services as will become apparent below. As indicated in the figure, the service platform resides in the form of computer-readable instructions or code that resides on computer-readable media 106.
In addition, environment 100 includes a network 112, such as the Internet, and one or more web sites 114 from and to which content can be received and sent. Websites 114 can offer a variety of services that can be integrated by service platform 110, as will become apparent below.
Computing device 102 can be embodied as any suitable computing device such as, by way of example and not limitation, a desktop computer, a portable computer, a handheld computer such as a personal digital assistant (PDA), cell phone, and the like.
Example Multi-Layered Service Platform
In the illustrated and described embodiment, the global integration layer 212 is designed to enable applications that are not “service aware” to nonetheless allow a user to access and use such services from within the applications. To this end, in at least some embodiments, the global integration layer provides a generic user interface that displays one or more services that are available and which can be invoked from within an application. In this embodiment, functionality of the global integration layer is supported by an operating system operating on a local client device. When a user wishes to ascertain which services are available from within an application that is not service aware, the user can take a particular action, such as using a shortcut on the operating system desktop (e.g. keying a hot key combination) which is detected by the operating system. Responsive to detecting the user action, the operating system can make an API call to a local service store to receive a listing of services that are available. The operating system can then present a generic user interface that lists the available services for the user.
In one or more embodiments, once the generic user interface has been presented to the user, the user can take a number of different actions. For example, in some embodiments, the user can hover their cursor over a particular service description or icon and receive a preview of that service. Alternately or additionally, a user can click on a particular service description or icon and then be navigated to that service's functionality. Navigation to a particular service's functionality can include a local navigation or a web-based navigation. In one or more embodiments, navigation can include sending data, such as that selected by a user, to the service for operation by the service.
Thus, in this embodiment, the generic user interface which is provided by the operating system is knowledgeable of the particular API calls that are used to present available services and to enable users to select one or more of the services. In this manner, applications that are not “service aware” can still be used as a starting point for a user to access services.
In the illustrated and described embodiment, the common control integration layer 214 provides a control that can be hosted by one or more applications. The control can allow applications to populate those services that the applications natively support, as well as to provide a means by which services which are not natively supported by the applications can nonetheless be offered to a user. When a user wishes to ascertain which services are available from within an application, the user can take a particular action such as making a particular selection, such as a text selection or file selection. Responsive to detecting the user action, the hosted control can make an API call to a local service store to receive a listing of services that are available. The control can then present a user interface that lists the available services for the user. These services can include services that are offered by the application natively, as well as services that are offered by other service providers either locally or remotely.
In one or more embodiments, once the user interface has been presented to the user, the user can take a number of different actions. For example, in some embodiments, the user can hover their cursor over a particular service description or icon and receive a preview of that service. Alternately or additionally, a user can click on a particular service description or icon and then be navigated to that service's functionality. Navigation to a particular service's functionality can include a local navigation or a web-based navigation.
Thus, in this embodiment, the control is knowledgeable of the particular API calls that are used to present available services and to enable users to select one or more of the services. In this manner, applications can use the control to both offer services natively and provide services offered by other service providers. In addition, as the control can be hosted by many different applications, a common user experience can be provided across a variety of applications.
In one or more embodiments, the custom integration layer 216 provides a set of APIs that can be used by applications that are aware of the APIs to receive a list of offered services and then create their own user interface and user experience through which a user can consume the offered services.
Having described the general notion of a multi-layered service platform, consider now an implementation example that describes one specific instance of a multi-layered service platform. It is to be appreciated and understood that the following description provides but one example, and is not to be used to limit application of the claimed subject matter to a specific implementation. Accordingly, other implementations can be utilized without departing from the spirit and scope of the claimed subject matter.
Implementation Example
In this particular example, a global integration layer includes a system service menu 312 and a service management component 314, and a common control integration layer includes a common context menu 316. Further, in one or more embodiments, a custom integration layer includes a data recognizer component 318, an application program interface or API 320, a service store 322, a preview component 324, and an execute component 326.
In one or more embodiments, the system service menu 312 of the global integration layer can be invoked by a user while using one or more applications and with context provided by the application(s). In practice, applications that are not “service aware” can be used to invoke the system service menu. In one or more embodiments, the system service menu is supported by the client device's operating system and can be invoked in any suitable way. For example, in at least some embodiments, a user can access the system service menu by keying in a particular hot key combination. Once detected by the operating system, the hot key combination results in an API call to application program interface 320 to receive a list of available services. The available services can be services that are offered locally and/or services that are offered by remote service providers. System service menu 312 then presents a user interface that lists the available services that can be accessed by the user. In one or more embodiments, the user interface presented by the system service menu 312 is generic across a variety of applications, thus offering an integrated, unified user experience.
Once the services are listed for the user via the user interface presented by the system service menu 312, the user may choose a particular service. In one or more embodiments, a user can receive a preview of a service, via a preview component 324 by taking some action with respect to a displayed service. For example, a user may hover their cursor over or near a particular description or icon associated with the service and receive the preview of that service. In one or more embodiments, previews can be provided for the user without the user having to leave the context of their application. When the user hovers their cursor in this manner, the operating system can make an API call to the preview component 324 to receive information or data that is to be presented as part of the preview. Alternately or additionally, by clicking on a particular service description or icon, a user can cause the service to execute. When this happens, the operating system can make an API call to the execute component 326 which, in turn, can cause the service to execute. Execution of the service can include, by way of example and not limitation, a navigation activity which can be either or both of a local navigation or a remote navigation. Examples of how this can be done are provided below.
In one or more embodiments, service management component 314 provides various management functionalities associated with services. For example, in one or more embodiments, the service management component 314 can provide functionality that enables a user to add, delete, and/or update the particular service. Further, in one or more embodiments, the service management component can enable a user to set a particular service as a default service for easy access.
In one or more embodiments, the common context menu 316 of the common control integration layer provides a common context menu across a variety of applications. In one or more embodiments, the common context menu is a control that can be hosted by a variety of applications. In at least some embodiments, these applications do not have to natively understand how a service or associated activity works. Yet, by hosting the control, the application can still offer the service as part of the application experience. When an application hosts the common context menu, the application can populate the menu with services it offers, as well as other services that are offered by other service providers. As such, an application can offer both native services as well as non-native services. In one or more embodiments, the common context menu is knowledgeable of the application program interface 320 and can make appropriate API calls to receive information on services that are offered and described in service store 322. Specifically, in one or more embodiments, the common context menu is aware of the particular service API.
In one or more embodiments, data recognizer 318 is configured to recognize data associated with particular API calls in which service listings are requested. Accordingly, the data recognizer 318 can then ensure that a proper set of services are returned to the caller. For example, if a user selects a particular portion of text, such as an address, then a particular subset of services may be inappropriate to return. In this case, the data recognizer 318 can see to it that a correct listing of services is returned.
In one or more embodiments, application program interface 320 provides a set of APIs that can be used to add, delete, or otherwise manage services that can be presented to the user. The APIs can include those that are used to receive a listing of services. But one example of the set of APIs is provided below in a section entitled “Example APIs”.
In one or more embodiments, service store 322 is utilized to maintain information and/or data associated with different services that can be offered. Services can be flexibly added and deleted from the service store. This can be done in any suitable way. In one or more embodiments, this can be done through the use of a declarative model that service providers use to describe the services that they offer. One example of a declarative model is provided just below in a section entitled “Declarative Model”. When a call is received by the application program interface 320, information associated with the call can be retrieved from the service store 322 and presented accordingly.
In one or more embodiments, the preview component 324 can be utilized to provide a preview of one or more offered services. An example of how this can be done is provided below.
In one or more embodiments, the execute component 326 can be utilized to execute one or more of the services that are offered. An example of how this can be done is provided below.
Declarative Model
In one or more embodiments, service providers can utilize a declarative model to describe services that are offered. In at least some embodiments, the declarative model utilizes an XML description to describe aspects of offered services. As an example, consider
Specifically, the XML description pertains to a mapping service. The XML description provides a homepage URL which is the homepage associated with the offered service. In addition, a <display> tag enables a service provider to provide a name that is then used in a preview display as shown. An <activity> tag contains information associated with the offered service. Specifically, in this example, the <activity> tag describes a category of service which, in this example, is a “map” service. An <activityAction> tag then describes context that can trigger the service, as well as behaviors that can be performed responsive to a triggering context.
Specifically, in this example, when a user makes a particular selection (i.e. context=“selection”), a preview action can be performed. In this case, the user's selection is provided as a value parameter which is then sent to the URL listed in the <preview> tag. The recipient of the value parameter can then return content associated with a preview of the user's selection, such as the illustrated preview map. Likewise, if a user clicks on or otherwise selects the preview, their selection is provided to the URL listed in the <execute> tag and the user can be navigated to that URL to be exposed to further functionality provided by the service provider. In this example, if a user clicks on the preview map, they are navigated to the listed URL and one or more of the included parameters are used to provide driving directions to a particular address.
By using a declarative model as described above, services can be easily extended and/or modified by service providers. Specifically, service providers can continually modify and change their provided services and can simply update their declarative model for incorporation in the service platform. In addition, this makes it easier for the system hosting these services to be more secure and provide a consistent experience.
Having now considered a system that implements a multi-layered service platform as well as an example declarative model, consider now a discussion of example user interfaces that can be employed in connection with the global integration layer, the common control integration layer, and the custom integration layer, each of which appears under its own heading.
Global Integration Layer—User Interface Example
Referring to
Referring to
At this point, the user may or may not choose to execute the service. If the user chooses to execute the service by, for example, clicking on the preview 600, a full navigation to a definition site can take place. For example,
In this manner, an application that does not natively support a particular service can, nonetheless, through the support of the operating system, provide access to a number of services.
As another example, consider
Referring to
Again, in this instance, a reader application that does not natively support a mapping service can nonetheless, through the support of the operating system, provide access to a mapping service.
Common Control Integration Layer—User Interface Example
In one or more embodiments, the common control integration layer can provide a common control that can be used by applications to expose services that can be accessed by an application. In one or more embodiments, the common control takes the form of a system service menu such as that provided by system service menu 312 (
Responsive to the user's selection, a common control can be presented which can display for the user not only services offered by the application, but services that are offered by other service providers. As an example, consider
Referring to
In this manner, a common control can be used across a variety of applications to enable services to be presented to a user that are natively supported by the application as well as those that are not natively supported by the application. Use of a common control across different applications provides a unified, integrated user experience.
Custom Integration Layer—User Interface Example
In one or more embodiments, the custom integration layer provides a set of APIs that can be used by applications that are aware of the APIs to receive a list of offered services and then create their own user interface and user experience through which a user can consume the offered services. As an example, consider
Referring to
Example Methods
Step 1600 detects, with an operating system, a user action. In the examples above, a user is working within an application such as a legacy application that does not necessarily support services that are desired to be offered. Here, a user action can be one that indicates that the user wishes to learn about and possibly consume one or more services that are not offered by the application. Accordingly, through the user's action, which can constitute any type of action such as a hot key combination, the user can indicate that they wish to learn about offered services. The user action is detected by the operating system and, responsively, step 1602 retrieves a list of services that are not natively supported by the application. The list of services can be retrieved in any suitable way. In the examples above, the list is retrieved through an operating system call to a platform-supported API. Step 1604 displays the list of services for the user. This step can be performed in any way using any suitable user interface. Step 1606 provides a preview of one or more services. This step can be performed in any suitable way. In the examples above, previews are provided responsive to the user taking some action such as hovering their cursor over or near an icon associated with the service or a description of the service. Step 1608 provides access to service functionality which can include, in this example, navigating the user to a remote website where the service functionality is offered. Alternately or additionally, service functionality can be provided locally.
Step 1700 provides a control that can be hosted by multiple applications. Examples of such a control are provided above. Step 1702 populates the control with services offered by an application. Here, the services that are offered by the application are those that are natively offered by the application. Step 1704 populates the control with services that are not natively offered by the application. This step can be performed in any suitable way. For example, an API call can be made by the control to an API to retrieve a list of services that are not natively offered by the application. Step 1706 displays a list of populated services for the user. Examples of how this can be done are provided above. Step 1708 provides a preview of one or more services and step 1710 provides access to service functionality associated with one or more of the services. Examples of how this can be done are provided above.
Step 1800 maintains a service store that describes various services. Examples of various services are provided above. Step 1802 provides an application program interface that can be called to discover services. In one or more embodiments, the application program interface can be called by different entities or different types of entities. For example, in some embodiments, a caller might constitute an operating system. An example of this is provided in the global integration layer described above. Alternately or additionally, a caller might constitute a control, such as a common control that can be hosted across different types of applications. An example of this is provided in the common control integration layer described above. Alternately or additionally, a caller might constitute an application that is aware of the application program interface. Collectively, these different types of callers can provide for a robust service platform implementation which supports service offerings across a variety of applications including those that are not aware of services that are offered as well as those applications that are aware of services that can be offered.
Step 1804 receives a call to discover one or more services. As noted above, this call can come from different entities or types of entities. Step 1806 retrieves information associated with one or more services. This step can be performed by accessing a service store, such as the one that is described above. Step 1808 provides information to the caller for display for a user. Specifically, in this example, the retrieved information associated with the services can be provided to the caller so that it can be displayed or otherwise exposed for the user.
Step 1810 displays a list of services for the user. Examples of how this can be done are provided above. Step 1812 provides a preview of one or more services and step 1814 provides access to service functionality. Examples of how this can be done are provided above.
Having described a number of methods that can be implemented in one or more embodiments, consider now an example set of APIs that can be provided by the service platform. It is to be appreciated and understood that the example provided just below is intended to serve as an example only. Accordingly, the example is not meant to limit application of the claim subject matter to the specific APIs shown and described.
Example APIs
In accordance with one or more embodiments, the following set of APIs can be included and exposed by the service platform and/or used by third party providers as indicated. It is to be appreciated and understood that the following set of APIs constitutes an example only. As such, other APIs can be utilized without departing from the spirit and scope of the claimed subject matter.
Having described an example set of APIs, consider now an example system that can be utilized to implement one or more of the above-described embodiments.
Example System
Computing device 1900 includes one or more processors or processing units 1902, one or more memory and/or storage components 1904, one or more input/output (I/O) devices 1906, and a bus 1908 that allows the various components and devices to communicate with one another. Bus 1908 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. Bus 1908 can include wired and/or wireless buses.
Memory/storage component 1904 represents one or more computer storage media. Component 1904 can include volatile media (such as random access memory (RAM)) and/or nonvolatile media (such as read only memory (ROM), Flash memory, optical disks, magnetic disks, and so forth). Component 1904 can include fixed media (e.g., RAM, ROM, a fixed hard drive, etc.) as well as removable media (e.g., a Flash memory drive, a removable hard drive, an optical disk, and so forth).
One or more input/output devices 1906 allow a user to enter commands and information to computing device 1900, and also allow information to be presented to the user and/or other components or devices. Examples of input devices include a keyboard, a cursor control device (e.g., a mouse), a microphone, a scanner, and so forth. Examples of output devices include a display device (e.g., a monitor or projector), speakers, a printer, a network card, and so forth.
Various techniques may be described herein in the general context of software or program modules. Generally, software includes routines, programs, objects, components, data structures, and so forth that perform particular tasks or implement particular abstract data types. An implementation of these modules and techniques may be stored on or transmitted across some form of computer readable media. Computer readable media can be any available medium or media that can be accessed by a computing device. By way of example, and not limitation, computer readable media may comprise “computer storage media”.
“Computer storage media” include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.
Conclusion
Various embodiments provide a service platform that integrates services, such as web services and/or local services, across a variety of applications. In at least some embodiments, services can be integrated with legacy applications that are “unaware” of such services, as well as applications that are aware of such services.
In at least some embodiments, the platform comprises a multi-layered structure is designed to integrate services across a variety of applications. The multi-layered structure includes, in at least some embodiments, a global integration layer that is designed to integrate services with legacy applications, as well as a common control integration layer and a custom integration layer. The common control integration layer can be used to provide a common control that can be used across applications to integrate not only services of which at the applications are aware, but services of which the applications are not aware. The custom integration layer can be used by various applications to customize user interfaces that are designed to integrate various offered services. In addition, users can have access to their services from many different types of applications regardless of how the applications choose to surface them.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
This application is a continuation of and claims priority to U.S. patent application Ser. No. 11/953,835, filed Dec. 10, 2007, entitled “Service Platform for In-Context Results”, the disclosure of which is incorporated in its entirety by reference herein.
Number | Name | Date | Kind |
---|---|---|---|
5818446 | Bertram | Oct 1998 | A |
5859636 | Pandit | Jan 1999 | A |
6072486 | Sheldon et al. | Jun 2000 | A |
6560633 | Roberts | May 2003 | B1 |
6678696 | Helland | Jan 2004 | B1 |
6785670 | Chiang et al. | Aug 2004 | B1 |
6839650 | Sutton et al. | Jan 2005 | B2 |
6912582 | Guo et al. | Jun 2005 | B2 |
6970869 | Slaughter | Nov 2005 | B1 |
7032211 | Janzig et al. | Apr 2006 | B1 |
7114148 | Irving | Sep 2006 | B2 |
7243298 | Yozell-Epstein et al. | Jul 2007 | B2 |
7243309 | Koay | Jul 2007 | B2 |
7343625 | Zaidi | Mar 2008 | B1 |
7395317 | Naick et al. | Jul 2008 | B2 |
7428570 | Nobili | Sep 2008 | B2 |
7487446 | Hargarten et al. | Feb 2009 | B2 |
7581194 | Iwema et al. | Aug 2009 | B2 |
7607136 | Kuno et al. | Oct 2009 | B2 |
7640348 | Atwal et al. | Dec 2009 | B2 |
7657609 | Klevenz et al. | Feb 2010 | B2 |
7716234 | Naibo et al. | May 2010 | B2 |
7721228 | Burke et al. | May 2010 | B2 |
7949230 | Tsukamoto | May 2011 | B2 |
8032482 | Rosenberg et al. | Oct 2011 | B2 |
8117542 | Radtke et al. | Feb 2012 | B2 |
8146110 | Lyndersay | Mar 2012 | B2 |
8381133 | Iwema et al. | Feb 2013 | B2 |
8464168 | Bump et al. | Jun 2013 | B2 |
20010034646 | Hoyt | Oct 2001 | A1 |
20020073058 | Kremer et al. | Jun 2002 | A1 |
20020080154 | Matthews, III et al. | Jun 2002 | A1 |
20020085224 | Price et al. | Jul 2002 | A1 |
20020186257 | Cadiz et al. | Dec 2002 | A1 |
20030043200 | Faieta | Mar 2003 | A1 |
20030090510 | Shuping | May 2003 | A1 |
20030097233 | Sutton et al. | May 2003 | A1 |
20030146939 | Petropoulos et al. | Aug 2003 | A1 |
20030164862 | Cadiz et al. | Sep 2003 | A1 |
20030177248 | Brown et al. | Sep 2003 | A1 |
20040054690 | Hillerbrand et al. | Mar 2004 | A1 |
20040068527 | Smith, III | Apr 2004 | A1 |
20040157202 | Hopkins et al. | Aug 2004 | A1 |
20040205672 | Bates et al. | Oct 2004 | A1 |
20040243942 | Cortright | Dec 2004 | A1 |
20040263475 | Wecker et al. | Dec 2004 | A1 |
20050005248 | Rockey et al. | Jan 2005 | A1 |
20050015462 | Lee et al. | Jan 2005 | A1 |
20050039141 | Burke et al. | Feb 2005 | A1 |
20050086304 | Naick et al. | Apr 2005 | A1 |
20050102629 | Chen et al. | May 2005 | A1 |
20050108052 | Omaboe | May 2005 | A1 |
20050125741 | Clow et al. | Jun 2005 | A1 |
20050132296 | Milic-Frayling | Jun 2005 | A1 |
20050160434 | Tan | Jul 2005 | A1 |
20050240902 | Bunker et al. | Oct 2005 | A1 |
20060036568 | Moore et al. | Feb 2006 | A1 |
20060036945 | Radtke et al. | Feb 2006 | A1 |
20060041891 | Aaron | Feb 2006 | A1 |
20060069990 | Yozell-Epstein et al. | Mar 2006 | A1 |
20060074869 | Rosenberg et al. | Apr 2006 | A1 |
20060085741 | Weiner et al. | Apr 2006 | A1 |
20060095343 | Clarke et al. | May 2006 | A1 |
20060101046 | Hargarten et al. | May 2006 | A1 |
20060112141 | Morris | May 2006 | A1 |
20060143568 | Milener | Jun 2006 | A1 |
20060179440 | Besbris | Aug 2006 | A1 |
20060184890 | Altenhofen | Aug 2006 | A1 |
20060200780 | Iwema et al. | Sep 2006 | A1 |
20060206559 | Xie et al. | Sep 2006 | A1 |
20060206567 | Milligan et al. | Sep 2006 | A1 |
20060212593 | Patrick et al. | Sep 2006 | A1 |
20060218086 | Campbell et al. | Sep 2006 | A1 |
20060230068 | Coulombe | Oct 2006 | A1 |
20060271858 | Yolleck et al. | Nov 2006 | A1 |
20070016573 | Nanavati | Jan 2007 | A1 |
20070044086 | Sampath | Feb 2007 | A1 |
20070079250 | Bump et al. | Apr 2007 | A1 |
20070100650 | Ramer et al. | May 2007 | A1 |
20070106952 | Matas et al. | May 2007 | A1 |
20070106956 | Platt | May 2007 | A1 |
20070150546 | Karakashian | Jun 2007 | A1 |
20070168926 | Rajah | Jul 2007 | A1 |
20070174420 | Khusial et al. | Jul 2007 | A1 |
20070226614 | Lorenzen et al. | Sep 2007 | A1 |
20070229861 | Forbush et al. | Oct 2007 | A1 |
20070255689 | Sun et al. | Nov 2007 | A1 |
20070280206 | Messer et al. | Dec 2007 | A1 |
20070282879 | Degenkolb et al. | Dec 2007 | A1 |
20080022229 | Bhumkar et al. | Jan 2008 | A1 |
20080092171 | Roberts et al. | Apr 2008 | A1 |
20080098085 | Krane et al. | Apr 2008 | A1 |
20080134093 | Dharmarajan et al. | Jun 2008 | A1 |
20080195628 | Kim | Aug 2008 | A1 |
20080214153 | Ramer et al. | Sep 2008 | A1 |
20080228924 | Herberger et al. | Sep 2008 | A1 |
20080307385 | Dreiling et al. | Dec 2008 | A1 |
20090024953 | Selig | Jan 2009 | A1 |
20090063415 | Chatfield et al. | Mar 2009 | A1 |
20090083289 | Morris | Mar 2009 | A1 |
20090083618 | Campbell | Mar 2009 | A1 |
20090100342 | Jakobson | Apr 2009 | A1 |
20090150910 | Lyndersay | Jun 2009 | A1 |
20090228804 | Kim | Sep 2009 | A1 |
20090256558 | Fujita et al. | Oct 2009 | A1 |
20090259969 | Pallakoff | Oct 2009 | A1 |
20090282361 | Cortright | Nov 2009 | A1 |
20090286558 | Zufi et al. | Nov 2009 | A1 |
20090298490 | Janik | Dec 2009 | A9 |
20090309849 | Iwema et al. | Dec 2009 | A1 |
20090319680 | Owen et al. | Dec 2009 | A1 |
20100069035 | Johnson | Mar 2010 | A1 |
20100174713 | Baessler et al. | Jul 2010 | A1 |
20100179876 | Holte | Jul 2010 | A1 |
20100192098 | Kim | Jul 2010 | A1 |
20100332325 | Holte | Dec 2010 | A1 |
20110078232 | Van Den Driessche | Mar 2011 | A1 |
20110193780 | Schaaf | Aug 2011 | A1 |
20120190386 | Anderson | Jul 2012 | A1 |
Number | Date | Country |
---|---|---|
200747988 | Sep 2008 | JP |
WO-2007142430 | Dec 2007 | WO |
Entry |
---|
“Defining Cross-Browser Tooltips”, Mozilla Developer Network, Retrieved from: <https://developer.mozilla.org/en/Defining—Cross-Browser—Tooltips> on May 19, 2011,(May 27, 2007),4 pages. |
“Enhance your Web Browsing Experience!”, Retrieved from <http://www.crazybrowser.com/> on Dec. 12, 2007., pp. 1-2. |
“Final Office Action”, U.S. Appl. No. 12/042,333, (May 26, 2011), 13 pages. |
“Foreign Office Action”, Chinese Application No. 200980107880.X, (Aug. 12, 2011),9 pages. |
“Microsoft Office Word 2003 Screenshots”, Microsoft Corporation 1983-2003,(2003),2 pages. |
“Non-Final Office Action”, U.S. Appl. No. 11/953,835, (Apr. 5, 2011),20 pages. |
“Non-Final Office Action”, U.S. Appl. No. 12/042,333, (Dec. 9, 2010),9 pages. |
“Non-Final Office Action”, U.S. Appl. No. 12/042,333, (May 9, 2012),13 pages. |
“Notice of Allowance”, U.S. Appl. No. 11/953,835, (Nov. 17, 2011),16 pages. |
“PCT Search Report and Written Opinion”, Application No. PCT/US2009/034122, (Sep. 28, 2009),11 pages. |
“Slim Browser”, Retrieved from http://www.flashpeak.com/sbrowser/ on Dec. 12, 2007., 2 Pages. |
Almaer, Dion “Tooltip.js: Creating Simple Tooltips”, Retrieved from: <http://ajazian.com/archives/tooltipsjs-creating-simple-tooltips> on May 19, 2011,(Nov. 29, 2005),14 pages. |
Chavez, Joe “Multi-tier Internet Architecture with Java, UML and OOA&D”, Astronomical Data Analysis Software and Systems IX, ASP Conference Series, vol. 216 (2000),pp. 75-78. |
Ferguson, D. F., et al., “Service-Oriented Architecture: Programming Model and Product Architecture”, Retrieved from: <http://www.research.ibm.com/journal/sj/444/ferguson.html> on Oct. 9, 2007, IBM Systems Journal,(Oct. 21, 2005),23 pages. |
Galli, Marcio et al., “Inner-Browsing: Extending Web Browsing the Navigation Paradigm”, Retrieved from: <http://devedge-temp.mozilla.org/viewsource/2003/inner-browsing/index—en.html> on Dec. 12, 2007, (May 16, 2003),6 Pages. |
Huffman, Lee “New Climate Area Released”, Retrieved from: <http://blogs.hamweather.com> on May 19, 2011,(Feb. 2008),3 pages. |
Sheng, Quan Z., et al., “Self-Serv: A Platform for Rapid Composition of Web Services in a Peer-to-Peer Environment”, Proceedings of the 28th VLDB Conference, Available at <http://eprints.qut.edu.au/archive/00000586/01/dumas—self-serv.pdf>,(2002),4 pages. |
“Final Office Action”, U.S. Appl. No. 12/042,333, (Oct. 16, 2012), 15 pages. |
“Accelerators in Internet Explorer 8 Beta 2”, Retrieved from <http://www.code-magazine.com/Article.aspx?quickid=0811062> on Dec. 1, 2008, pp. 1-5. |
Garrett “Ajax: A New Approach to Web Applications”, Retrieved from: <http://www.adaptivepath.com/ideas/essays/archives/000385.php> on Nov. 28, 2008., Feb. 18, 2005, 6 Pages. |
“Filename extension”, Retrieved from <http://web.archive.org/web/20071202041958/http://en.wikipedia.org/wiki/Filename—extension> on Jan. 27, 2013, Dec. 1, 2007, 7 pages. |
“Final Office Action”, U.S. Appl. No. 12/362,314, Jan. 5, 2012, 26 pages. |
“Final Office Action”, U.S. Appl. No. 12/362,314, Feb. 22, 2013, 36 pages. |
“Non-Final Office Action”, U.S. Appl. No. 12/362,314, Jul. 7, 2011, 18 pages. |
“Non-Final Office Action”, U.S. Appl. No. 12/362,314, Oct. 15, 2012, 34 pages. |
“Non-Final Office Action”, U.S. Appl. No. 12/362,314, Jul. 18, 2013, 41 pages. |
“What's New for IE8 Search”, Retrieved from http://blogs.msdn.com/ie/Default.aspx?p=2 on Dec. 1, 2008., 34 Pages. |
“Extended European Search Report”, EP Application No. 09716904.9, Sep. 17, 2012, 6 pages. |
“Foreign Office Action”, CN Application No. 200980107880.X, Jan. 16, 2014, 14 Pages. |
“Foreign Office Action”, CN Application No. 200980107880.X, Jan. 30, 2013, 15 pages. |
“Foreign Office Action”, CN Application No. 200980107880.X, Jun. 18, 2013, 14 pages. |
“Foreign Office Action”, CN Application No. 200980107880.X, Jul. 3, 2012, 12 pages. |
“Foreign Office Action”, EP Application No. 09716904.9, Jun. 21, 2013, 6 Pages. |
“Foreign Office Action”, JP Application No. 2010-549700, Feb. 20, 2013, 6 pages. |
“Foreign Office Action”, JP Application No. 2010-549700, Jul. 25, 2014, 34 pages. |
“Foreign Office Action”, JP Application No. 2010-549700, Nov. 12, 2012, 8 pages. |
“Intent to Grant”, EP Application No. 09716904.9, Jun. 17, 2014, 13 Pages. |
“Summons to Attend Oral Proceedings”, EP Application No. 09716904.9, Jan. 31, 2014, 9 pages. |
“Final Office Action”, U.S. Appl. No. 12/042,333, May 4, 2015, 13 pages. |
“Non-Final Office Action”, U.S. Appl. No. 12/042,333, Oct. 5, 2015, 13 pages. |
“Final Office Action”, U.S. Appl. No. 12/042,333, Jun. 13, 2016, 17 pages. |
“Non-Final Office Action”, U.S. Appl. No. 12/042,333, Nov. 17, 2014, 11 pages. |
“Foreign Office Action”, JP Application No. 2010-549700, Oct. 30, 2013, 6 pages. |
Number | Date | Country | |
---|---|---|---|
20120204129 A1 | Aug 2012 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11953835 | Dec 2007 | US |
Child | 13430241 | US |