Abstract: Aspects of the technology described herein are directed towards, among other things, identifying a country(s) likely intended in association with a query. In embodiments, a query is analyzed to identify a set of place entities that each indicate a specific location and a set of location labels that each indicate an aspect of a location. Additionally, map view data is analyzed to identify a set of location candidates that each indicate a country presented within a map view. The map view data indicates at least a portion of a boundary of the map view. Thereafter, a machine learned model is used to identify a set of countries likely to be intended in association with the query based on the set of place entities, the set of location labels, and the set of location candidates. The set of countries can be provided for use in identifying information related to the query.

Abstract: Aspects of the technology described herein are directed towards, among other things, identifying a country(s) likely intended in association with a query. In embodiments, a query is analyzed to identify a set of place entities that each indicate a specific location and a set of location labels that each indicate an aspect of a location. Additionally, map view data is analyzed to identify a set of location candidates that each indicate a country presented within a map view. The map view data indicates at least a portion of a boundary of the map view. Thereafter, a machine learned model is used to identify a set of countries likely to be intended in association with the query based on the set of place entities, the set of location labels, and the set of location candidates. The set of countries can be provided for use in identifying information related to the query.

Abstract: Techniques to provide proxies for web services are described. A technique may include providing proxies for web services that translate one format to a format native used, or understood, by the web service without having to rewrite existing APIs. In one embodiment, for example, an apparatus may comprise a processing unit and a network interface coupled to the processing unit. The apparatus may further include a web service executing web service requests on the processing unit using a native format. The apparatus may further include a proxy to receive a web service request in a first format via the network interface and to translate the web service request from the first format to the native format. Other embodiments are described and claimed.

Abstract: Techniques to provide proxies for web services are described. A technique may include providing proxies for web services that translate one format to a format native used, or understood, by the web service without having to rewrite existing APIs. In one embodiment, for example, an apparatus may comprise a processing unit and a network interface coupled to the processing unit. The apparatus may further include a web service executing web service requests on the processing unit using a native format. The apparatus may further include a proxy to receive a web service request in a first format via the network interface and to translate the web service request from the first format to the native format. Other embodiments are described and claimed.

Abstract: A communication application automatically aggregates contact information. The communication application classifies contact information retrieved from data sources as either duplicate or complimentary contact information to a contact. The communication application aggregates the contact information and the contact into a unified contact object by eliminating the duplicate contact information and adding the complimentary contact information. The application presents the unified contact object through a user interface.

Abstract: The present invention supports the design of a process using a drawing surface that specifies the process with underlying programmatic constructs. In response to a user's command, a construct corresponding to a shape is selected from a palette and inserted onto a design region that shows the specified process. The command is verified to be consistent with semantics of an associated process type. If so, a visual image of the specified process is updated. If not, an indicator is generated in a proximity of a relevant portion of the visual image in order to help the user resolve the inconsistency. The user is able to correct errors before generating computer-executable instructions from a high-level code emission. Computer-executable instructions are also generated from high-level code emission. A process engine is cognizant of the associated high-level lines of code and an infrastructure knowledge base while executing the computer-executable instructions.

Abstract: Providing data bound workflow activities to model messaging between a workflow instance and a workflow host. The workflow author associates a data source with each data bound activity in a workflow without specifying details of the underlying messaging technology. The data bound activity in the workflow instance communicates with a data source service in the workflow host to exchange data.

Abstract: Modifying a componentized workflow model during execution of the workflow. Each step of the workflow is modeled as an activity that has metadata to describe design time aspects, compile time aspects, and runtime aspects of the workflow step. A user selects and arranges the activities to create the workflow via user interfaces or application programming interfaces. Metadata is associated with each of the activities in the workflow. During execution of the workflow, the user modifies the metadata to affect execution of the workflow without recompiling the workflow.

Abstract: Visual composition of an activity for re-use in a composite activity or in a workflow. A user declaratively and/or programmatically generates reusable composite activities from existing activities interactively using a visual designer. The activity has one or more configuration properties associated therewith that define the behavior of an aspect of the activity. Depending on the value of the configuration properties, the activity may be, for example, partially configured, fully configured, or minimally configured. A user or developer completes the configuration of the activity during re-use of the activity in a composite activity or in a workflow.

Abstract: Building a componentized workflow model. Each step of the workflow is modeled as an activity that has metadata to describe design time aspects, compile time aspects, and runtime aspects of the workflow step. A user selects and arranges the activities to create the workflow via user interfaces or application programming interfaces. The metadata associated with each of the activities in the workflow is collected to create a persistent representation of the workflow. Users extend the workflow model by authoring custom activities. The workflow may be compiled and executed.

Abstract: Representing a componentized workflow model via a declarative markup language. Each step of the workflow is modeled as an activity that has metadata to describe design time aspects, compile time aspects, and runtime aspects of the workflow step. A user selects and arranges the activities to create the workflow via user interfaces or application programming interfaces. The metadata associated with each of the activities in the workflow is collected to create a persistent representation of the workflow. Users extend the workflow model by authoring custom activities.

Abstract: Building a componentized workflow model via an application programming interface. Each step of the workflow is modeled as an activity that has metadata to describe design time aspects, compile time aspects, and runtime aspects of the workflow step. A user selects and arranges the activities to create the workflow via the application programming interfaces. The metadata associated with each of the activities in the workflow is collected to create a persistent representation of the workflow. Users extend the workflow model by authoring custom activities. Users also compile the workflow via the application programming interface.

Abstract: The present invention supports the design of a process using a drawing surface that specifies the process with underlying programmatic constructs. In response to a user's command, a construct corresponding to a shape is selected from a palette and inserted onto a design region that shows the specified process. The command is verified to be consistent with semantics of an associated process type. If so, a visual image of the specified process is updated. If not, an indicator is generated in a proximity of a relevant portion of the visual image in order to help the user resolve the inconsistency. The user is able to correct errors before generating computer-executable instructions from a high-level code emission. Computer-executable instructions are also generated from high-level code emission. A process engine is cognizant of the associated high-level lines of code and an infrastructure knowledge base while executing the computer-executable instructions.

Abstract: Partner management systems and methods are disclosed. A designer designs a business process that provides selection criteria for selecting business partners. The business process is compiled and executed by a business process execution engine. During the execution of the business process, the business process execution engine uses the selection criteria to select business partners. The identification of business partners and attributes of the business partners may be modified without modifying the business process.