Abstract:
Conversation to reach a goal may be created by stitching together pieces of past conversations. Conversations are stored and indexed. A user specifies a goal that the user would like to achieve through conversation. Pieces of conversation that could achieve that goal are retrieved and/or stitched together from smaller conversation fragments, and the resulting conversation pieces are evaluated for merit. The merit evaluator is pluggable so that different merit calculations may be used for various different situations. The conversation may be displayed or spoken to the user as a prompt, so that the user can engage in a real conversation with a real person based on the guidance received. The system can react to the current state of the conversation, and may change conversational strategies or even conversational goals during the course of the conversation.
Abstract:
Among other things, one or more techniques and/or systems are provided for annotating content based upon user reaction data and/or for maintaining a searchable content repository. That is, a user may request and/or opt-in for user reaction data to be detected while a user is experiencing content (e.g., watching a movie, walking through a park, interacting with a website, participating on a phone conversation, etc.). Metadata associated with the content may be used to determine when and/or what sensors to use to detect the user reaction data (e.g., metadata specifying an emotional part of a movie). The content may be annotated with a reaction annotation corresponding to the user reaction data, which may be used to organize, search, and/or interact with the content. A search interface may allow users to search for content based upon annotation data and/or aggregated annotation data of one or more users who experienced the content.
Abstract:
Among other things, one or more techniques and/or systems are provided for presenting embedded content portraying an entity and/or for maintaining a user profile based upon user exposure to one or more entities. That is, content, such as an image or video, may portray one or more entities (e.g., a product, location, business, etc.). To aid a user in identifying an entity and/or remembering the entity, entity information may be embedded into the content. The entity information may describe the entity and/or provide one or more actions that the user may take with regard to the entity (e.g., open a shopping application to view a hand bag entity). Personalized recommendations may be provided to a user based upon a user profile derived from exposure of the user to various entities (e.g., a vacation recommendation may be provided based upon vacation entities exposed to the user in a positive light).
Abstract:
Providing directions from point A to point B may be treated as an information retrieval problem. In one example, actual routes that are traveled by people are received, and are stored in a database. When a person requests directions from point A to point B, a system searches the database to determine whether a route from A to B exists. If the route does exist, then the route may be provided as directions in response to the request. If no such route exists, then the system looks in the database for routes that have some amount of overlap with each other, and attempts to construct a route from A to B by joining known routes that overlap with each other. Rules may govern the degree of overlap that routes are to have before they can be joined.
Abstract:
Turn-by-turn directions can guide a user to a dynamic destination, such as a person or a rendezvous location. The turn-by-turn directions enable one user to follow another or, alternatively, multiple people to rendezvous with each other. The selection can be via identifiers used in network contexts, such as social networking. Individuals can select the circumstances under which their location can be revealed. Turn-by-turn directions enabling following utilize anticipated locations or predictions of likely destinations based on historical and contextual information. Turn-by-turn directions enabling rendezvous reference a rendezvous location, which is either the same for all users, or which differs among them. Also, the directions can reference intermediate, "staging", locations from which further intermediate, or ultimate, destinations can be routed to.
Abstract:
Architecture that motivates and utilizes users as the means for capturing geographical data of a desired location. The architecture incentivizes users (e.g., large numbers of mobile-phone and mobile-computer users) to provide the data in the form of geolocation information trails and images captured by user devices. Thus, users take multiple pictures, for example, and can validate existing coverage of specific points of interest based on variable needs of the requestor. One motivational technique is by using augmented reality (AR) games, which include shooting targets associated with the point of interest (e.g., a street). Thus, the game can be designed for the data accumulation, which includes visual data. Additionally, the architecture can determine the areas or points of interest for validation and/or additional coverage by comparing live video data to an image database to decide of the need for update.
Abstract:
Positional information is provided while minimizing the possibility that personally identifiable information can be derived therefrom. Positional information is received in the form of trails that can be aggregated. Individual cells of a grid reflect a quantity of aggregated trails through those cells, an average intensity and direction of movement through those cells, or a more detailed distribution thereof. Alternatively, individual trails are aggregated to an aggregated trail in the form of a line. Further obfuscation of personally identifiable information occurs by resampling aggregated positional information, by introducing false positional information, or by falsely modifying existing positional information, in a manner that does not impact the overall aggregations, and by pruning, or deleting, positional information, especially around sensitive locations, such as a user's home, place of business, or other location that users typically would seek to keep private. Provision of positional information is delayed until a sufficient amount is received.
Abstract:
Asynchronous methods and calls are produced automatically as a function of a declarative indication of intent. A method annotated with an asynchronous attribute or method call including a special asynchronous function can be identified. Subsequently, an asynchronous version of an identified synchronous method or call is generated automatically. Assistance is also provided for specifying intent.