KR20110000686A - Open framework for integrating, associating and interacting with content objects - Google Patents

Abstract

Information about the context of the mobile user, including but not limited to current mobile activity, social relationships and association history, and past mobile, search, and browsing history is identified and converted into metadata. Metadata also applies to content sources that are delivering content to search engines or custom content engines. The metadata is used in part to determine the relative display of a search result or aggregated customized information resource, such as a content object, to a mobile user as a home page. The user may select information to be automatically delivered as a content feed, including various content objects or content feeds associated with the entity on the user's home page, as presented from one or more entities or search results or in a different context to the user. Information about mobile user activity enables publishers and advertisers to identify target candidates to receive advertising or marketing material.

Description

Open framework for integrating, associating, and interacting with content objects {OPEN FRAMEWORK FOR INTEGRATING, ASSOCIATING AND INTERACTING WITH CONTENT OBJECTS}

The present invention relates generally to user queries of clusters and feeds related to search queries and mobile devices over a network.

The approach described in connection with this section may have been followed, but it is not necessarily the approach previously thought or pursued. Thus, unless indicated to the contrary, the approaches described in this section may not be prior art to the claims of this application and are not admitted to be prior art by inclusion in this section.

There have been tremendous changes on the Internet that affect our daily lives. For example, in today's society, mobile computing devices are becoming ubiquitous. Many mobile computing devices, such as personal digital assistants (PDAs), cell phones, and the like, can be used to retrieve information over the Internet as well as to communicate voice messages, emails, text messages, and the like. It's not uncommon to see people searching for shops, restaurants, music, businesses and more using their mobile devices on a bus, train or ship. It is conceivable that these devices will ultimately be allowed at least wireless internet access on the plane.

Transitioning the traditional web page browsing interaction and content consumption experience to the mobile environment has generally resulted in a less satisfactory user experience for a variety of reasons. On mobile devices, screen real estate is minimal. The search of all presented information may depend on or depend on the compartment of the particular mobile device. Typically, users are not in an environment conducive to accidental exploration of the World Wide Web. Indeed, the user may be in a changing environment which in itself requires a large share of user's attention. Therefore, tailoring search engine results and content consumption to the mobile experience is of paramount importance to the user.

In addition to the desire to perform active relevant information retrieval, some mobile device users may wish to deliver content in a more automated manner, as far as possible, tailored to their own interests, such as hobbies or social network groups. Even if the user has the time, energy, and technical capabilities needed to manually configure the mobile device, the user is still in a state of receiving a narrow set of information sources, such as news headlines, weather, and sports. It is likely to be forced to stay. Another user may want to deliver specific content according to the user's current environment.

Similarly, advertisers want to provide information that is tailored to each user to enhance the user experience. Because of the possible correlation between user search terms and the user's real interest, advertisers can be close to this goal by delivering advertising material as part of search engine results. However, in a mobile environment when a user is not searching, advertisers typically have limited ability to reach ad targets that may be in motion and require information related to the environment in which they currently belong or will proceed.

1 is a system block diagram of one embodiment of an environment in which the present invention may be practiced;
2 illustrates a sample search and clustered search results by a mobile device;
3 illustrates clustering realized through the use of metadata wrappers applied in a social networking context;
4 illustrates the generation of results based on a search yielding no named cluster results;
5 illustrates a mobile user search system that is performing a federated query against several data sources, providing a plug-in module for third parties to translate their data into a format usable by the search;
FIG. 6 illustrates a sample framework for the plug-in indicated in FIG. 5; FIG.
7 illustrates a schematic diagram of an Add Anything Engine (AAE);
8 illustrates a schematic diagram of a Mobile Homepage Targeting Engine (MHTE);
9 illustrates a portion of sample use of AAE;
10 illustrates a portion of sample use of AAE;
11 illustrates a portion of sample use of AAE;
FIG. 12 illustrates a full screenshot (with omitted portions) of a mobile device resulting from the performance operation illustrated in FIGS. 9-11;
13 illustrates information associated with entity "Boston Red Sox";
14 illustrates a user configuration screen used in connection with various embodiments of the present invention;
15 illustrates a subset of the oneSearch entity type organized by hierarchical type-subtype relationship;
16 is a block diagram of a computer system in which an embodiment of the present invention may be implemented.

In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be appreciated that the invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the present invention without necessity.

[summary]

It integrates historical search and browsing data, as well as the user's current mobile activity, social relationships, and associated histories, to address a number of aspects of the user mix of mobile content and the organization of information displayed on a user's mobile device or aggregated on a personal homepage. Personalization discloses technologies that enrich the mobile user's personalized content consumption, web browsing, and search experience. These techniques can be applied automatically or performed by a user. The content object can be any form or format of content that can be consumed by the user, such as but not limited to any one or more of the following: through browsing or voice, email, text, image, animation, gestures, Text, numerical data, images, animations, audio, video, or any combination thereof that includes content generated as a result of a search from communication with another person via audio or video. The content can come from any data processing source or device.

For example, in one embodiment, contextual information related to a user's current activity is derived from a mobile device or other source and includes general search results including location information for matching a request and classifying or reclassifying the results, Reordering into a custom result set that includes a system and method for personalizing mobile user content requests, ie search or dynamic page assembly requests, by enlarging the mobile user's input as a first set of metadata derived from the context of the input. To do this, it is passed to the search engine as metadata.

In one embodiment, one or more content objects are displayed on the mobile device. For each content object selected by the user, one or more entities or entity types are determined to correlate to the selected content object. Based at least in part on the determined entity or entity type, an information feed (information feed) is generated. The user can integrate the information feed into the user's home page or device and can automatically receive updates based on web pages or information corresponding to the content object, entity, or associated information source.

In one embodiment, the set of search results is displayed on the mobile device. For each search result selected by the user, an entity or entity type is determined for the selected search result. Based at least in part on the determined entity or entity type, an information feed is generated. You can integrate information feeds into your home page or device, and when you annotate your results and wish to include their sources, results, or search types in their mobile "home page" in the future, Updates can be automatically received based on the corresponding web page or information.

In one embodiment, the set of users is classified for the selected advertiser or product. From the set of users, to differentiate users for advertisers based on the user's context, ad copy, hierarchical structure of actual content for the user's mobile home page, and user interaction with the home page over time and usage data. The candidate targets for the set of one or more advertisers and conditions are predicted based, at least in part, on a preselected time for qualifying and evaluating the user.

In one embodiment, (2) the user's mobile device (s), with preferences and activities in which the user organizes the content, consumes the content, interacts with the content, shares the content, and performs the content. (3) the context in which the user performs these actions, as well as the user performing these actions, as well as the user's content consumption and communication by the user, provides the advertiser with information about the user's interests and intentions.

Example Operating Environment

Except where indicated, the illustrated mobile and network operating environments will not be repeated here as they are unnecessary to a complete and correct assessment of the various embodiments of the present invention. Such illustrated mobile and network operating environments can be found, for example, in application 11 / 651,102 entitled "Clustered Search Processing." 1 illustrates a high level schematic diagram of a mobile device with a web browser in communication with a server. The server is connected to the network and includes a custom content engine configured to aggregate and display heterogeneous types and sources of content, a search engine configured to perform a search of the network, and a user data tracking engine to measure and record user behavior. Include.

In FIG. 1, network system 100 includes mobile device 110 that communicates with server 130 using network 104. In one embodiment, network 104 is the Internet, but may be a non-public network, such as a telecommunications provider. Server 130 includes a collection of one or more search and data applications 134. The search and data application 134 is configured to perform a search of the data accessible through the network and the Internet and the custom content engine 140, which is configured to generate and maintain a "home page" of custom content types and sources in one central display. A search engine 150 that is included. In one embodiment, the custom content engine 140 is a Yahoo! corresponds to the onePlace mobile homepage, and the search engine 150 is a Yahoo! Or a private network of user data, such as Google.

The search and data application 134 also includes one or more of the following modules: UDS (User Data Store; 152), Mobile Search Refine Manager (MSRM) 154, Search Module 156, and Search Clustering Module 158. do. These particular naming schemes are not necessary at all from a technical point of view for understanding the methods and systems disclosed herein, but are provided for the convenience of the reader. These modules will not be described in a serial manner and will be introduced when certain features and embodiments are illustrated. Although each module is described separately from search engine 150, each module may be integrated into search engine 150.

Mobile device 110 may be a mobile phone, a game or reading device, or another wireless device that provides access to one or more interconnected networks 104 (e.g., Wi-Fi or Bluetooth). It may include. Mobile device 110 includes an interactive application 120 that can browse content and data using display 126.

Before describing the illustrated operating environment in which various embodiments may be practiced, concepts are introduced and described in the following, including "social relationships and associations" and "metadata". In the following, further refinements to these concepts may be described while discussing various embodiments.

Social relationship and association

Social relationships and association concepts connect people to activities and connect people to each other. Social relationships and association graphs can be constructed from almost any activity, from dating to specialized institutions, with some networks focusing on a collection of personal or family relationships rather than specific activities.

Social relationships and associations have been extended from interpersonal activities such as bowling leagues, and now encompass all manner of offline or online activities and connections, typically made over the Internet and entangled with the WWW.

A person's social relationships and association graphs are usually not static, where the movement and interaction between an individual and his or her social relationships and associations is based on the following non-limiting factors: (1) where the person is located; (2 hours; It may be a function of one or more of (3) the person with whom the person is interacting, and (4) the person is performing, either physically or through online social relationships and associations.

Multiple alterations, combinations, and / or subtle distinctions of these factors may be involved; For example, an individual may be planning and coordinating family reunions that involve a variety of direct and indirect relationships that change over time. Information related to these factors can be captured by the mobile device or network server. Some methods and systems for the collection and use of social relationships and related information are described in applications 12 / 069,731 entitled "Identifying and Employing Latent Social Network Relationships" and "Social Aspects of Content Aggregation, Syndication, Sharing, and Updating". It is disclosed in all of the application No. 12 / 182,756.

Metadata

As described above in connection with a person's social relationships and associations, a description representing the person's current activity may provide a continuous stream of streams / status data for the user and provide for any user-such as searching or loading a mobile homepage. It may include some or all of the factors relating to “where”, “when”, “who”, and “what” that provide the correct context for the occurrence request. When used to describe specific data about an individual, these factors themselves include, for example, one or more of spatial metadata, temporal metadata, social metadata, object metadata, and / or topic metadata. Metadata is referred to as user W4 metadata.

As described herein, each of the operations of (1) the operating environment, (2) the mobile client environment, (3) the server environment, and (4) the mobile search query with respect to the location changer may be a mobile client, a server, and (optionally) ) Can be further extended with reference to a metadata wrapper, including user W4 metadata, placed around data exchanged between an administrator or a third party service provider.

User W4 metadata includes contextual metadata relating to any where, “when”, “who”, “who”, and / or “what” of a text message or voice communication. In other words, W4 metadata may be spatial or natural geography (ie "where"), time (ie "when"), social (ie "who"), and / or physical object or topic interest (i.e. " Information "). In addition, among these aspects by analyzing the similarities of these aspects among user groups as well as within the individual space, time, social, and topic aspects and between individual space, time, novel, and topic aspects, At least some of the relevance may be determined.

As further described herein, the context provided by the user W4 metadata aids in the clarification of the mobile search query, which in turn enables improved clustering of search terms and search results.

For example, the user enters the query "apple". In addition to text in and associated with web pages and documents, the term "apple" may be mapped to many abstract ideas, real objects, and digital objects and media. Collectively, these are referred to herein as "entities." In this example, clarification is performed on the string "apple" to determine at least some of the possible entities that "apple" can represent, such as a company, fruit, record label, etc., each of which is then one Can be mapped to any of the above result types. In addition, clarity may favor recent actual or online behavioral data that favors certain outcomes. For example, if a user visited an Apple Mac store and made a purchase yesterday, disambiguation may favor local receipts or a product information page that the user recently accessed in relation to the user's prior purchase or investigation.

For example, if the entity is an Apple ^® company, the different result types include geographic results (for example, company or store location), stock prices, news articles (for example, text and video), as well as existing web and mobile web links. It may include. As further described herein, clusters of result types based on the entity or entities identified in the disambiguation step and their respective mapping to result types can be rendered or manipulated. Further information regarding the clarification of the search query can be found in application 11 / 651,102 entitled "Clustered Search Processing".

For example, FIG. 15 represents a subset of the oneSearch entity type organized by hierarchical type-subtype relationship. Further relationships between entities and entity types may include numerical and symbolic relationships, as well as complex entity types such as "events" that link to other entity types such as places, times, people, and the like.

In FIG. 15, for example, row 1510 refers to entity "Apple Computer" (corresponding to the preceding discussion) and row 1520 refers to entity "Pizza Restaurant".

In addition, an entity may exist in several categories. For example, the TV series Lost may exist in the TV Show category of the Entertainment information object, but may also be referenced in the Actor category of Entertainment People. Similarly, a pizza can be a business listing, venue, place, as well as a recipe entry for Wikipedia, Reference, or Information Objects.

The integration of entities with entity types represents a significant change from simple bookmarking of web pages, because it makes it possible to store pointers to entities that can have a real-time information feed or a real-time information feed can be generated for. to be. For example, if you consider a static bookmark to the website "www.examplemovie.com", rather than bookmarking the entity "examplemovie", it will automatically review reviews about "examplemovie", local showtimes, DVD release notices, and so on. You can receive updates.

Example Mobile User and Network Configuration

In the following, various embodiments of the network system are described, where the capture and transfer of metadata is used to enhance the mobile user browsing interaction and consumption experience.

Referring to FIG. 1, storage of metadata and other user information, such as social relationships and association information, may be realized by a User Data Store (UDS) 152 that is part of a search and data application 134 on the server 130. have. UDS 152 may include databases, text, spreadsheets, folders, files, and the like, and is configured to maintain and store social relationships and association information that is collected from network 104 as well as associated with a network or user data source. Can be. For example, a four-dimensional map of a mobile device may be used as a proxy for past and current location, status, and association with other nearby or related users for the user.

In one embodiment, the social relationship and association information stored in the UDS 152 for a mobile user includes one or more of the following: (1) A social networking website, such as MySpace, Facebook, or Linkedln, to which the user belongs, Identification information of a user for; (2) contact information maintained by the user, such as for voice contact, e-mail, instant messaging, and text messaging; (3) the member group to which the user belongs; (4) subscriber information of an individual who subscribes to user-generated content, such as a subscriber to a user's Flickr account or a user's blog; And (5) a user's location, association, action, interest, or other data source accessible to the transaction.

In one embodiment, social relationship and association information stored in UDS 152 for a mobile user includes electronic communications sent or received by the mobile user, such as e-mail, instant messaging, and text messaging, while other Embodiments include all known data, communications, and transactions for users in combination with information from various devices, mobile and stationary.

In one embodiment, UDS 152 location information based on the user's actual and historical route data as well as the user's actual residence (s), account registration information, locations of interest that the user implicitly or explicitly shared with the system, and the like. ) Can be stored. Such information may indicate that the user resides in a particular town, region, city, or other similar thing within a particular county, state, country, or the like, or a location (eg, venue, district, city, region, etc.). I can indicate that I am interested in something similar. Such location information may also be organized and arranged in a hierarchical relationship in one embodiment.

In one embodiment, mobile state information about the user may also be stored in the UDS 152. Such mobile state information may include one or more of the following: (1) the name of the mobile device 110, an operating system (OS), and a CPU; (2) current status, location, and / or usage history of mobile device 110, such as when and how long it has been powered and accessed, as well as which cell tower or network node is communicatively connected; (3) state information of an application 242 loaded on or currently active at mobile device 110, such as information about interactive application 120; (4) content of a data store of mobile device 110; And (5) information therefrom such as the coordinate history from the GPS of the mobile device 110 from which the mobile state of the user can be derived (such as the user is located in a slowly moving transportation device on a particular highway). The usage history includes not only active interaction data generated by the user's actions, but also the user's location, proximity to known landmarks or points of interest (POIs), and associations with other coexisting users, devices, networks, vehicles, or appliances. This includes manual data such as

In one embodiment, once the user provides account access or e-mail account to the user's social network, social networking information may be obtained.

In one embodiment, social relationship and association information may be obtained indirectly through monitoring various movements, actions, and interactions of the user. The interaction measures the mobile device to measure orientation, biometrics, and movement detection, as well as the use of a browser toolbar activated by the user, where some or all of the data sent to the mobile device 110 is forwarded to the UDS 152. Monitoring through other known methods of tracking user interactions. Thus, for example, implicit social relationships and associated data and / or contact information may be associated with a user regardless of whether their individual device, environmental sensor, or data feed and / or both are members of an explicit social network. It may be extracted based on data from content in a message between another user.

Information such as social networking information, communication information, location information, and mobile route or status information may be stored within the UDS 152 and conveyed along with other data as a “metadata wrapper”. As described below, the metadata wrapper can provide contextual or content information to the data that it carries. Non-limiting examples of vocabulary in which metadata can be propagated, including the use of properties, objects, and data types, are provided in the section entitled “Example Metadata Vocabulary” below.

Information stored in UDS 152 may be forwarded to MSRM (Mobile Search Refine Manager). The MSRM 154 is configured to receive a search query from the user, parse the search query into one or more primary search terms, and provide a context modifier based on information about the user stored in the UDS 152. Additional specifications of MSRM 154, including context processing and concept-based search, are described in application 11 / 651,102 entitled " Clustered Search Processing. &Quot;

In one embodiment, the context changer is provided with a metadata wrapper that is passed from the mobile device 110 towards the MSRM 154; For example, the metadata wrapper may have data accompanying a search query sent from mobile device 110 or may have a portion of a search query. In one embodiment, the context modifier is provided towards the MSRM 154 by the UDS 152.

In one embodiment, MSRM 154 identifies any concept-specific data source to be retrieved. One embodiment of how a third party can provide a user-defined data source will be described below with reference to FIGS. 5 and 6.

Using the information stored in UDS 152, MSRM 154 creates a modified search query to be processed by search module 156, with instructions for any concept-specific data sources to be searched.

Search results provided by search module 156 may be clustered into groups and optionally ranked, as disclosed in application 11 / 651,102 entitled "Clustered Search Processing." In one embodiment, search results from search module 156 are forwarded to search clustering module 158. In one embodiment, metadata passed to search module 156 is also passed to search clustering module 158.

Additionally, search results determined in relation to mobile user metadata may also be changed based on metadata derived from one or both of concept-specific and content-specific data sources. The search results can be clustered by source, term, concept, or content.

For example, metadata identified by one or both of UDS 152 and MSRM 154 may be matched to search results based on matching concept-specific data sources.

In one embodiment, the search results are combined with other known data sources to create a "virtual cluster" that can be presented to the user in the same or similar manner as the actual clustered results are presented to the user.

In one embodiment, the concepts identified by search clustering module 158 used to cluster the results are attached to the results as metadata. In one embodiment, the identified concepts are used to determine a result type or relative ranking based on the entity or entities identified in the disambiguation step.

In one embodiment, metadata representing the mobile state information of the user may be used to construct the layout of the search results that appear on the display 126 of the mobile device 100.

In this way, metadata from many different sources about the user and context is used to personalize the current mobile user's search or dynamic page assembly request. (1) current activity of the user, (2) current environment, (3) social relationships and associations, (4) third-party ratings, reputations, rankings, or other quality scoring metrics such as credit scores, and ( 5) Metadata describing the search query can be used in combination with metadata generated by a concept-specific, context-specific, or content-specific data source to convey relevant information to a mobile user.

Example User Example

(a) Clustering through the use of metadata regarding device usage and (b) Clustering relating to clarity of entities into strings is illustrated in FIGS. 2-4 which display sample search and search results at the mobile device.

Referring to FIG. 2, in panel 210, a mobile user performs a simple search using the term “sushi”. Previously acquired metadata, such as the user's location, is captured and displayed at the bottom of the search box; In this example, the user is located at "near 3000 Paradise Rd, Las Vegas".

This location metadata allows for identification and display of nearby businesses, such as restaurants, that are identified as related to the search term. The restaurant forms a cluster for a specific instance of the abstract entity type "restaurant". These results can be further differentiated by distance, as indicated by panel 210.

Preferably, the metadata wrapper may be used by other content providers, such as Yelp, Zagat, and OpenTable and displayed in the panel 210 under the heading "More business results." These corporate results may be generated based on the combination of the mobile user's location, search term, and abstract entity type such as "restaurant" and may be pushed to the user.

In panel 220, the user has selected a result for "Sushi Roku in the Forum Shops" and landed on an information display page about this restaurant. While the user is viewing the details about a particular instance of the abstract entity "restaurant", the display on the mobile device can be linked to other relevant information, such as maps, user reviews, and more tools, via a link to "Business details." Is configured to display a link of.

Panels 231, 232, and 233 display the links available from the landing page for "Sushi Roku." For the information displayed in each panel, metadata wrappers were applied to describe the data type of the content source (such as "review", "review author", "photo", "rating", etc.).

3 illustrates clustering realized through the use of a metadata wrapper applied to a social networking context. Panel 310 illustrates a search performed by a user for a person named "Will Decker". This search may be performed again in relation to the user's current location, as indicated by the location information at the bottom of the search box (“near 3000 Paradise Rd, Las Vegas”). The search generates a cluster of profile information using the abstract class "Contact" in relation to three applications, Facebook, Linkedln, and MySpace. In this example, data from these three applications (including metadata wrappers) is pulled from each other through an open API framework and assembled by the server.

As further shown in panel 310, each instance of the "Contact" class type has additional properties that can be used to further refine the results and help the user find an individual named "Will Decker" that the user actually knows. Own

In panel 320, the user has selected a profile found on Facebook, encapsulated about the individual, such as a thumbnail image of the thumb and "Berkeley Alum • UChicago Alum", corresponding to the class "Overview". Look at the summary of various people named "Will Decker" (or some variant about it) with additional information, such as summary.

In panel 330, the user can access the "Will Decker" metadata wrapper that includes photo information that can be applied by the API framework and combined with information about the physical specifications of the mobile device to present various Facebook photos in an attractive way. Go to the display of the Facebook photo gallery for a particular instance.

4 illustrates the generation of a result based on a search that yields an anonymous cluster result, in which the user is presented with one or more anonymous virtual clusters that may themselves have one or more third party open abstractions. In panel 410, the mobile user enters the search term "Audi tt". None of the search results yield named clusters, but a virtual cluster named "2008 Audi TT" is created using content from MotorTrend and Wikipedia that conforms to the open abstract model.

In panel 420, the user has selected the MotorTrend Research icon and has a landing page assembled from data and metadata that can be (1) supplied from results obtained from a universal data source or (2) supplied from a MotorTrend API plug-in. Presented. Other possibilities for the generation of results include one or more of the following: (1) generation of virtual clusters; (2) generation of a series of virtual clusters; And (3) a list of OpenAbstracts that are not clustered but meet at least one related criterion.

Integrating content sources into the mobile search framework

In the example provided in FIGS. 2-4 above, cluster data from Facebook, Linkedln, and My Space can be: (1) provided to the server through a browser toolbar or (2) each web via an open API framework. It could be pooled from the site and assembled by the server. A framework for such integration of content sources and a simple schematic for cluster generation via third party content sources are illustrated in FIGS. 5 and 6 and described below.

5 illustrates a mobile search system 500 that performs a federated query to various data sources, providing a plug-in module for third parties to translate their data into a format usable by a search or custom content process. The search retrieves the data (and associated metadata) of the data stores 511, 512, 513 having the "content index". Data is delivered from the content plug-ins 521-524 described below with reference to FIG. 6 toward the content index. The results of the mobile search system 500 are also pooled directly from the content plug-in 526.

Each of the plug-ins 521-525 pulls data from the content source 531-536 or pushes the data by the content source 531-536. The content source may have application program interfaces (APIs) and / or content feeds. In addition, the results of the mobile search system 500 are also directly pooled by the content source 537 with the API. As illustrated, data may be pooled towards the plug-in from an API or content feed from a third provider; The data can be pushed towards the plug via the content feed of the third provider.

FIG. 6 illustrates a sample framework for the plug-in shown in FIG. 5. The plug-in 600 includes a parser 610, an association module 620, and a renderer 630. Parser 610 may include a metadata parser or API requester, either or both of which are in communication with one or more of the "content sources" shown in FIG. Parsed data including an optional metadata wrapper is passed from parser 610 to association module 620. Explicit inference cluster result mapping is performed by the association module 620, where the results are processed by the renderer 630. The result of the renderer provides a metadata wrapper (such as clusterID, entityID, W4 metadata, and content type metadata) that allows the system to determine the appropriate format, rendering, and user behavior for the content displayed on the mobile device. This can be handled through XML schema or template / user interface mapping. The results are then sent to one or more data stores with the "content index" of FIG.

Integration of Search Sources or Results into the Homepage

In the above description, various types of metadata are used to derive the search results from the corresponding search query. Search results can be in various types of content, such as text, numerical data, images, animations, audio, or video, and in various formats of content, such as RSS feeds, links to newspaper articles, Wikipedia entries, or parts of web pages. Can be expressed. The user may wish to integrate one or more search results into the user's home page or mobile home page that appears automatically when the browser or application is called for the first time or is called when the user activates a certain type of "home" command.

In addition, the search result or part of the search result may itself be regarded as the entity or entity type described above; For example, a web link or RSS feed can be added to an entity or entity type of a user home page and treated as an entity or entity type of a user home page. Items that may be added include: (1) web links; (2) RSS feeds; (3) a web link for generating an RSS feed for it based on a link that periodically revisits to check for updates; (4) "entity" or "entity type"; And (5) entities or entity types added through parsing web links or RSS feeds.

As a non-limiting example, the user may select a search result or any online web page or resource for future inclusion, or the user may add the entity or entities represented within that content to the user's custom content engine. At the time of the user's selection, the custom content engine can automatically or interactively determine whether the user wants to add the content, resource, or feed between one or several associated entities.

Such a preferred specification determines, when a search result or content object is associated with an icon, checkbox, user gesture, or selected or spoken content, the content type for the selected result is determined and the user home page or consumer device, e. It can be realized through displaying by an associated utterance command that generates a corresponding information feed to be integrated into the game device. In the following, the ability for a user to add any search result as an information feed is described with reference to FIG.

FIG. 7 illustrates four components of an Add Anything Engine (AAE) 700 that can be used to enable a user to add search results to a user's home page or other information collection place or device. It should be understood that the components of FIG. 7 can be easily integrated into the server 130 shown in FIG. For example, AAE 700 may be integrated into search and data application 134 of server 130. For simplicity, the following description will be made with reference to FIG.

AAE 700 includes a query manager 704, a display instrumentation manager 708, a content analyzer 712, and a registration manager 716.

The query manager 704 tracks search query information and related metadata of one or more usage data sets or search histories for the user as well as any number of devices or networks associated with the user.

In one embodiment, query manager 704 receives information from UDS 152 and MSRM 154.

Information from query manager 704 is fed to content analyzer 712 for use in determining the specific content type or format to be associated with the search results. The content analyzer 712 parses the received web links and RSS feeds for determination of that entity and entity type.

Some search results, such as RSS feeds, have an established protocol for updating, while other search results, such as static web pages, may not have an established update protocol. The content analyzer 712 forwards the results corresponding to that static content type to the registration manager 716.

The registration manager 716 can generate a recurring information feed among non-feed enabled information objects, whereby the user receives updated information from the link in various intervals. . For example, a user may want to look at a web page presentation made by a government agency, such as the United States Patent and Trademark Office (USPTO), which does not provide a web feed.

In one embodiment, the registration manager 716 periodically retrieves the data source corresponding to the non-feed enabled information object selected by the user, parses the resulting data, and applies instructions to apply the metadata wrapper. Include.

The registration manager 716 forwards the recurring random information feed to the mobile homepage manager 720 for display on the mobile device 110.

Display instrumentation manager 708 controls both the actual display of the "add this" icon and the receipt of that user input. Display metrology manager 708 forwards the announcement information feed selected for feed selection to mobile homepage manager 720 and forwards other user selections to registration manager 716. Display instrumentation manager 708 may also be configured to detect a utterance command and / or user gesture for selecting a notification information feed selected for mobile homepage manager 720 and registration manager 716 for feed generation.

9-13 illustrate an example mobile homepage environment and one way a user can add an entity to a mobile device homepage. Panel 910 first displays the portion of the mobile device screen from which the user can add content to the user's home page by activating an item named "Add Anything to Y! OnePlace." After activation, the user is presented with a panel 920. Panel 920 includes an area 921 for the user to enter text for a personalized search, where the input in area 921 corresponds to a default set of locations for adding content therefrom. Thus, the "Add Anything" function does not require the user to enter a search query, either by the user or by the user's mobile home page with context and other information about the user, available entities, and devices. It can be applied to a preselected or customized set of content objects (entities, links, RSS feeds, etc.) presented to the user, which can present one or more custom and / or custom content objects for possible addition.

10, the user viewing panel 1010 has an input text "Red Sox" in the area 1011. After activation of the "oneSearch" button in panel 1010, the user is presented with a panel 1020 that provides the user with various choices for selecting one or more content objects to add therefrom to the user's mobile home page. Some selections, such as region 1022, correspond to RSS feeds that the user can select. Other choices correspond to news articles and links to websites, for example "www.redsox.com". Region 1021 was filed on January 5, 2007, entitled “Clustered Search Processing,” and is one or more owners, publishers, or authors of information, as described in more detail in 11 / 651,102, previously incorporated by reference. Corresponds to the entity "Boston Red Sox" that can be associated with.

In FIG. 11, the user of the panel 1110 selects the first entry 1111 corresponding to the entity "Boston Red Sox" to be added to the user's homepage. In one embodiment, a default set of content and sources is automatically generated as default. In one embodiment, a user may specifically select or deselect a content source or object from those associated with a user subscription to the entity "Boston Red Sox" to assemble a custom set of aggregated content and sources associated with both the entity and the user. have. In one embodiment, the content associated with the entity may be free or paid, anonymous or registered, depending on the subject matter and standards of the implementation.

A screenshot illustrating the start and end of the user home page is shown in FIG. 12. Since the screenshot is too long to display properly here, panel 1210 represents the 'top' of the home page. The page scrolls down until it reaches panel 1220, which represents the 'bottom' of the home page. As indicated in area 1230, an icon representing the entity "Boston Red Sox" has been added to the user's homepage to allow the user to easily access the system's up-to-date custom set of content for Boston Red Sox. Provide a way.

In FIG. 13, panel 1310 illustrates the content assembled by the system, corresponding to the entity “Boston Red Sox”. In FIG. 13, the system added content sources corresponding to scores and schedules, upcoming games, news, photos, and rosters. Unlike simple bookmarks, each of these content sources is dynamic, and information from each source can be automatically fetched and assembled for user consumption. Selection and presentation of associated content objects and feeds for a given entity, as well as configuration or operation of the system, content publisher, user, advertiser, network operator, device manufacturer, or any combination thereof. Dynamically change (i.e., delete, reorder, different media types) based on preferences or actions related to various aspects of the context described above (ie, space, time, social, topics, etc.) that the feed can be accessed by the user. Transcoding).

14 illustrates two diagrams in which a user can reconstruct a user's mobile home page, including the relative order in which the items appear. Entry 1430 "Boston Red Sox" indicates a new entity added to their current content order for the user's mobile homepage and the associated arrow indicates that the user interactively deletes, increases or decreases the order for any entity or content in the list. To lower. In one embodiment, a user can group any entity or content in the list, name the group, and delete or reorder the groups.

Ad personalization

Dynamic mobile user web browsing interactions and content consumption experiences differ greatly from traditional static methods of web browsing typically performed by a personal computer tied to a home or work. Attempts to embed traditional web browsing interactions and content consumption experiences on small mobile screens fail to provide the benefits yielded by the methods and systems disclosed above.

Similarly, injecting advertising material onto mobile screens using traditional techniques results in a negative user experience. Traditional techniques do not emphasize user experience, but result in 'one-size-fits-all' advertising that undermines the user experience.

Substantial improvements used in actual mobile user history to (a) align mobile users with brands and / or advertisers, and (b) predict specific users for specific advertisers in specific campaign and time and / or space combinations for delivery. Is calculated. A method and system for matching an advertisement with a mobile user is described below with reference to FIG. 8.

FIG. 8 illustrates a method for matching a particular advertisement copy or specialized content with a particular advertisement or content delivery opportunity based at least on the content, format, configuration, and interaction data generated by the user and their mobile homepage, such as Yahoo's onePlace. Illustrates Mobile Homepage Targeting Engine (MHTE) 800, a fully customizable personal advertising system. It should be understood that the components of FIG. 8 can be easily integrated into the search and data applications of server 130.

The MHTE 800 may be: (a) to manage interactions of advertisers and publishers; And (b) a module for configuring the user's mobile homepage as an advertisement serving request generated by one or more of the following: (1) a network; (2) the user; And (3) third parties.

In one embodiment, MHTE 800 includes an ad copy manager 804, a mobile homepage manager 808, a matching manager 812, and an ad display manager 816.

The ad copy manager 804 can interact with the advertiser or publisher and allow the advertiser or publisher to do one or more of the following: (1) register and manage their accounts; (2) submitting advertising copy or full-text content; And (3) specifying certain actions in the form of targeting models. Specialized content can be any form of new, updated, or exclusive content that is marketed toward the user by the owner, publisher, or content retailer. The targeting model may be a function of one or more of the following user characteristics: (1) type of mobile access device; (2) an access network; (3) demographics; (4) current user activity; (5) location or proximity to one or more known persons, places, or things, (6) coexistence of other users, devices, or POIs, and (7) user history, preferences, or profiles, among others.

The advertisement display manager 816 may receive advertisement copies received from the advertisement copy manager 804 in response to specific advertisement requests regardless of whether they are requests from user, network, or third party services, such as carriers or ISPs. The full content is filled as instructed by the matching manager 812 and the metered copy is returned for display by the requestor. Such an advertisement request may include information indicative of a predetermined target user criterion, the amount or maximum amount an advertiser may pay, the limitation or condition of the display, and the duration of the offer.

The mobile homepage manager 808 measures and tracks user content, configuration, and interactions with the user's mobile homepage or other selected web pages, including utterances, tactiles, and sense input.

The matching manager 812 applies the targeting model to the user profile to account for, score, and select advertising copies or specialized content for serving in response to an ad request handled by the ad display manager 816. Data from the mobile homepage manager 808 may be forwarded to the matching manager 812 for fine discrimination or construction of various ad targeting models.

The following non-limiting example illustrates some of the benefits produced by MHTE 800. In a first instance, a user may be presented with special promotions, recent reviews, grand openings or other content, the current location of a potential target user, home, work, or other location of interest, for example, a city that the user regularly visits. In order to receive updates such as a feed or source of information related to the entity in the vicinity of the location designated as of interest, we added "Pizza Restaurant" to onePlace as an entity. Such entity "Pizza Restaurant" appears as row 1520 in a non-limiting sample subset of the oneSearch entity type illustrated in FIG. 15. The user will then be considered a potential target entitled to receive personalized advertising material or specialized content by the MHTE 800.

After a user adds "Pizza Restaurant" to onePlace as an entity, the user can add new specials or content when a local pizza restaurant posts a review about a pizza restaurant, and / or near a location of interest. You will receive updates when the pizza restaurant opens. Further consideration may be realized by the user pointing to other entities in onePlace and pointing to content that is destroyed, rejected, or canceled, as well as the placement of homepages relative to each other of these and related entities. The level and type over time of user activity associated with each entity may be used to determine the relative value of each entity in the targeted advertisement or specialized content for that user. In addition to content targeting from publishers, advertisement targeting from advertisers can also be integrated.

Information about the same user may reach the MHTE 800 through additional interaction by the user. For example, a user may add "vegetarian recipes" that may be combined with targeting information derived from the user's interaction with "Pizza Restaurant" entities, as well as content related to "vegetarian pizzas" rather than "nonvegetarian pizzas" in addition to onePlace, You may have developed a targeting profile that suggests your users will prefer ads or promotions.

An example of the benefits produced by the MHTE 800 may be as follows: A pizza maker finding new customers in a particular region. The pizza maker supplies the advertisement copy or the specialized content to the advertisement copy manager 804 along with the target data supplied to the advertisement display manager 816.

Target data are looking for men aged 18-34 who tend to eat out. The matching manager 812 identifies the set of potential targets, including the users described above.

Matching manager 812 alerts, reviews the placement of the entity on the user homepage, and takes into account the level and type of user activity associated with the entity in the determination of advertisements and content targeted for the user. In this example, matching manager 812 constructs an advertisement for a meatless pizza special that is served by a pizza maker established nearby. This advertisement is delivered to the user by the mobile homepage manager 808.

In a related example, the user enters a search request for "restaurant", which is received by the mobile homepage manager 808. Matching manager 812 reviews the user's metadata and search history and identifies the user as a potential target.

Your Yahoo! Your Yahoo! In addition to the existence of a "Vegetarian Recipes" entity in onePlace, additional data and metadata are available from Yahoo! Several searches using the oneSearch term "vegetarian" and additionally Yahoo! User targeting profiles can be further enhanced, such as prior searches for potential targets, including targets with status updates posted from oneConnect to MySpace.

Matching manager 812 alerts, reviews the user's metadata, including social relationships and associations, and constructs advertisements for meatless pizza specials served by a pizza maker established nearby. The advertisement is delivered to the user by the mobile homepage manager 808 along with the search results.

14 illustrates two ways in which a user's placement of an entity relative to a user's home page may be used by the matching manager 812 as part of the advertisement personalization process. Panel 1410 illustrates a user settings panel for adjusting a user's various e-mail accounts, instant messengers, social networks, contacts, and calendars. When enumerating these kinds of information, it is customary for the user to place the user's preferred entry near the top of each list. Thus, in panel 1410, it is revealed that the user uses the user's Facebook account more aggressively than the user's MySpace account, as revealed by the relative ranking of the two entries.

As described above, the matching manager 812 can then sort these types of metrics, such as ranking within or between groups, in higher order on their mobile homepage through past, present, or predicted activity or It can be used as part of an advertising personalization process that increases the weight of a particular user for an entity or brand based on a strong association.

Similarly, panel 1420 corresponds to an order of user selection of an entity, such as those illustrated in FIGS. 9-13. For example, the entity order displayed on panel 1420 corresponds to all entities shown in FIG. 12; Note the last entity in "Boston Red Sox". In panel 1420, the user can rearrange the user's entries as described above. Matching manager 812 can use this order, for example, to select a particular advertisement from a possible advertisement pool, where the selected advertisement is displayed to the user so that the potential advertisements associated with the content or entity to which the user subscribes can be identified. By increasing the ranking, the content and entities associated with the mobile homepage influence the selection of the advertisement. In addition, the user's deselection of past content or advertisers may also be used to influence ranking.

Hardware overview

According to one embodiment, the techniques described herein are implemented by one or more special purpose computing devices. Special purpose computing devices may be hard-wired to perform the technique, or may be digitally configured such as one or more application-specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs) that are permanently programmed to perform the technique. It may include an electronic device, or may include one or more general-purpose hardware processors programmed to perform a technique in accordance with program instructions in firmware, memory, other storage, or a combination. Such a general purpose computing device may also combine custom hard-wired logic, ASICs, or FPGAs with custom programming to implement the technology. Special purpose computing devices may be desktop computer systems, portable computer systems, handheld devices, mobile phones, browsing or gaming devices, networking devices, or other devices that incorporate hard-wired and / or program logic to implement the technology.

For example, FIG. 16 is a block diagram illustrating a computer system 1600 in which embodiments of the present invention may be implemented. Computer system 1600 includes a bus 1602 for communicating information or other communication mechanisms and a hardware processor 1604 coupled to bus 1602 for processing information. Hardware processor 1604 may be a general purpose microprocessor, for example.

Computer system 1600 may also include main memory 1606, such as random access memory (RAM) or other dynamic storage device, coupled to bus 1602 for storing information and instructions to be executed by processor 1604. Include. In addition, main memory 1606 may be used to store temporary variables or other intermediate information during execution of instructions to be executed by processor 1604. Such instructions, when stored in a storage medium accessible to the processor 1604, computerize the computer system 1600 for a special purpose machine customized to perform the tasks specified in the instructions.

Computer system 1600 further includes a read only memory (ROM) 1608 or other static storage device coupled to bus 1602 for storing static information and instructions for processor 1604. To store information and instructions, a storage device 1610, such as a magnetic disk or an optical disk, is provided and coupled to the bus 1602.

Computer system 1600 may be coupled to display 1612, such as a cathode ray tube (CRT), via bus 1602 to display information to a computer user. An input device 1614 comprising alphanumeric and other keys is coupled to the bus 1602 to communicate information and command selections to the processor 1604. Another type of user input device is cursor control 1616, such as a mouse, trackball, or cursor direction key, for communicating direction information and command selection towards the processor 1604 and controlling cursor movement on the display 1612. . This input device typically has two degrees of freedom in two axes, the first axis (e.g. x) and the second axis (e.g. y), allowing the device to specify its position in the plane. (two degrees of freedom). The input device 1614 also provides audio, visual, and tactile output functions as well as audio and visual (audio), visual (video and image), tactile, and gesture input or sensing input functions, and time their status and location. Mobile phone, game, reading, browsing, or communication device, which may include multi-channel functionality connected in both directions through one or more networks, such as to report in real time and to facilitate access to content and users. Can be.

The computer system 1600 combines the techniques described herein with user-defined hard-wired logic that combines the computer system to make the computer system 1600 a special purpose machine or to program the computer system 1600 to be a special purpose machine, It can be implemented using one or more ASICs or FPGAs, firmware, and / or program logic. According to one embodiment, the techniques herein are performed by computer system 1600 in response to processor 1604 executing one or more sequences of one or more instructions contained in main memory 1606. Such instructions may be read into main memory 1606 from another storage medium, such as storage 1610. Execution of the instruction sequence included in main memory 1606 causes processor 1604 to perform the process steps described herein. In other embodiments, hard-wired circuitry may be used in place of or in conjunction with software instructions.

As used herein, the term "storage medium" refers to any medium that stores data and / or instructions that cause a machine to operate in a particular way. Such storage media may include non-volatile media and / or volatile media. Non-volatile media includes optical or magnetic disks, such as, for example, storage device 1610. Volatile media includes dynamic memory, such as main memory 1606. Typical forms of storage media include, for example, floppy disks, flexible disks, hard disks, semiconductor drives, magnetic tapes or other magnetic data storage media, CD-ROMs, other optical data storage media, any physical media having a pattern of holes. RAM, PROM, EPROM, FLASH-EPROM, NVRAM, other memory chips, or cartridges.

The storage medium is distinct from the transmission medium but can be used with the transmission medium. Transmission media participates in transferring information between storage media. For example, the transmission medium includes a coaxial cable, a copper wire, and an optical fiber, including a wire having a bus 1602. In addition, the transmission medium may take the form of acoustic or light waves, such as those generated during radio wave and infrared data communications.

Various forms of media may be involved in carrying one or more sequences of one or more instructions to processor 1604 for execution. For example, instructions may initially be placed on a magnetic disk or semiconductor drive of a remote computer. The remote computer can load the instructions into dynamic memory and send the instructions over a telephone line using a modem. A modem connected directly to the computer system 1600 may receive data on the telephone line and convert the data into an infrared signal using an infrared transmitter. An infrared detector can receive the data carried in the infrared signal and a suitable circuit can place the data on the bus 1602. Bus 1602 passes data to main memory 1606 where processor 1604 draws instructions from and executes them. Instructions received by main memory 1606 may deliver mobile applications using wireless data transfer, wireless client-server communication, and wireless P2P communication as well as storage 1610 before or after execution by processor 1604. May be optionally stored on the mobile device 1614.

Computer system 1600 also includes a communication interface 1618 coupled to bus 1602. The communication interface 1618 provides bidirectional data communication that couples to a network link 1620 that is connected to the local network 1622. For example, communication interface 1618 may be an integrated services digital network (ISDN) card, a cable modem, a satellite modem, or a modem that provides a data communication connection to that type of telephone line. As another example, communication interface 1618 can be a LAN card that provides data communication connections to a compatible local area network (LAN). Wireless links may also be implemented. In any such implementation, communication interface 1618 transmits and receives electrical, electromagnetic, or optical signals that carry digital data streams representing various types of information.

Network link 1620 typically provides data communication to other data devices over one or more networks. For example, network link 1620 may provide a connection to host computer 1624 over a local network 1622 or to data equipment operated by an Internet Service Provider (ISP) 1626. ISP 1626 then provides data communication services over a worldwide packet data communication network, now commonly referred to as the " Internet " 1628. Both local network 1622 and the Internet 1628 use electrical, electromagnetic, or optical signals to carry digital data streams. Signals over various networks and signals over network lines 1620 and over communication interface 1618, which carry digital data towards and from computer system 1600, are exemplary forms of transmission media.

Computer system 1600 can transmit messages and receive data, including program code, via network (s), network lines 1620, and communication interface 1618. In an Internet example, the server 1630 may send the code requested for the application program via the Internet 1628, ISP 1626, local network 1622, and communication interface 1618.

The received code can be executed by the processor 1604 as it is received, and / or stored in storage 1610 or in other non-volatile storage for later execution.

In addition, embodiments of the present invention may be directed to a computer program product having software stored on any computer readable medium including a mobile phone or computing device. Such software, when executed on one or more data processing devices, causes the data processing device (s) to operate as described herein. Embodiments of the present invention make use of any computer readable medium so far known or known in the future. Examples of computer readable media include primary storage (eg, any type of RAM) and secondary storage devices (eg, hard drives, floppy disks, CD ROMs, straw disks, tapes, magnetic storage devices, optical storage). Devices, MEMs, nanotechnology-based storage devices, etc.), but is not limited thereto.

In the foregoing specification, embodiments of the present invention have been described with reference to a number of specific details, which may vary from implementation to implementation. As such, the exclusive and exclusive guidance on what the invention is and what it is intended to be by the applicant is, in certain forms issued by the claims, including any subsequent amendments, such claims originating from this application. Is a set of. Any definitions explicitly set forth herein for terms contained in such claims will affect the meaning of those terms used in the claims. Accordingly, limitations, elements, features, specifications, advantages, or attributes not expressly stated in the claims will not in any way limit the scope of such claims. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.

Example Metadata Vocabulary

searchmonkey-profile vocabulary

This manual will be distributed on a regular basis to improve compliance with industry standard vocabulary and to ensure that common use cases are realized in a consistent manner. This manual will be updated approximately every week during the alpha and beta periods, working closely with partners.

Introduction to the searchmonkey-profile vocabulary

The searchmonkey-profile vocabulary can be used in DataRSS feeds and with pages embedded with RDFa and eRDF.

The entire searchmonkey-profile consists of a number of vocabulary definitions, including an industry-standard definition as well as a simple way to declare all prefixes. When used with DataRSS, declare the searchmonkey-profile lexical definition by adding the following processing instructions to the beginning of the feed:

<? profile http://search.yahoo.com/searchmonkey-profile?>

Typically this would require more than a dozen lines of xmlns declarations, but other software that recognizes Yahoo! 'S open search platform and searchmonkey-profile will accept this single line instead.

The next section describes the individual vocabulary. Feel free to navigate around the sections below, especially those that apply to your field. However, in other instances, at least a quick glance can be helpful to get a sense of how best to model your particular metadata.

Large plots of possible values may be burdensome, so each section, along with usage hints and examples, highlights specific characteristics to pay attention to.

rel vocabulary

The rel vocabulary defines the value to use for the item's rel attribute. The naming convention for these attributes is that they always begin with the rel: prefix, which is accompanied by short words that describe a person, place, thing, idea, or concept. Although these are not officially meant RDF classes, they are actually used in much the same way, sharing the convention that they start with the first capital letter, without considering the prefix.

The most common relationship possible is rel: Resource. All other relationships in this vocabulary are direct or indirect "subclasses" from rel: Resource. In the table listing all rel values, the "Parent Class" column indicates the next more general relationship. To illustrate from more specific to more general, the rel: Resource of rel: Image is rel: Media.

What if there is no good match for the kind of item for which you want to extract metadata? Suppose you are extracting information about the Seattle garage band. There is no rel: SeattleGarageBand or rel: GarageBand or even rel: Band properties. The most specific applicable character present on the chart, is rel: Organization, which you should use in this case. In addition, it may be a good idea to request that a new value be added to the vocabulary using the documentation's feedback email address.

To use this vocabulary in a feed or with RDFa / eRDF in a web page, you must map as close as possible to the item you identified as the class of the item from this vocabulary. If you can learn about an existing RDF vocabulary, you can populate the rel attribute with an existing property as long as the property takes a resource as its domain, not a string. Some of the more common features in this category include foaf: knows and foaf: homepage.

Common rel

● rel: Agent, representing someone, organization, club, or "things that show organs"

Rel: Photo, rel: Image, rel: Video, and rel: Audio to represent embedded multimedia components

Rel: Photoset, rel: Videoset for a set of audio / videos

• rel: Thumbnail for audio or video where smaller thumbnails can be represented.

● rel: Review to express the review rating

● a page with a full set of something about it, for example a search result page or a rel: Cluster to represent a list of hotels in a city

Specific references are also a task family of rel properties. These are deliberately defined in a fairly general way, so let's pick the closest match. Here are just a few of the more commonly used ones;

● rel: Append for writing new reviews, blog comments, or creating new content for a page in general

● rel: CheckAvailability to perform non-binding checks of product or service availability

Rel: Edit to edit the wiki page for the instance. For wiki sites, the rel: Edit property is especially useful.

Rel: Procure to order, bid or book something

Rel: SendEmail to email this page (or something about it)

Rel: SendToPhone to send this page (or something about it) to the phone

● Full review: vocabulary. Note that the default scale is 1 to 5, but the upper and lower limits can be changed by review: best and review: worst.

Encyclopedia / Reference / Info

● common rel

• rel: Section to distinguish a particular section. Should contain only notable sections, not all sections in general

● rel: Discussion to link to a separate discussion page

● rel: History to link to a separate history page

Business / Commercial / Directory

● common rel

Rel: Listing to represent the entire list

● rel: Business to represent the actual business (with street addresses, not lists)

Rel: Neighborhood (usually with a dc: description child) to indicate a particular neighbor

News / Events / Gossip

● common rel

● rel: NewsItem

Shopping / Commerce / Product page

● common rel

Rel: Listing to represent the entire list

● rel: Product to represent the product itself (with shippingWeight rather than a list)

● rel: Specification

Social networking

● common rel

• rel: Section to distinguish a particular section. Should contain only notable sections, not all sections in general

● rel: Discussion to link to a separate discussion page

● rel: History to link to a separate history page

● rel: WorkExperience for career related items

● rel: CurrentWorkExperience for your current rank

● rel: Degree to refer to specific educational credentials ("degrees" as well as diplomas, doctoral degrees, certificates, or other types of educational attainment). Additional details in this section may be specified in dc: description or other properties.

Travel / Destination

● common rel

● rel: Business to link to a specific business

● rel: Hotel to link to a specific hotel

● rel: Restaurant to link to a specific restaurant

● rel: Flight to link to information about a specific flight

● rel: Map for linking to local maps

● rel: Discussion to link to a separate discussion page

● rel: History to link to a separate history page

Characteristic vocabulary

Attribute attributes contained within meta tags associate string values with resources. Widely used formal and informal industry standards make up the bulk of the list. Unless existing vocabulary is widely used, certain characteristics important to this profile are defined. The next section provides guidance on which vocabulary to use. All properties are listed in the searchmonkey-profile vocabulary specification.

In addition to domains, scopes are associated with properties. The domain specifies what kind of item the property applies to. For example, media: width only has meaning for the rel: Media item; For example, it is meaningless when applied to rel: Person. The range specifies what kind of string value can be expected from this property. For example, the dc: date attribute must accept a date in a certain format, ie YYYY-MM-DD, also known in ISO-8601 format.

Common properties

Dc: title for common titles

Dc: date for common dates

Dc: identifier This is often a URL but may be an ISBN or other identifier.

Dc: creator for the creator of the resource

Dc: rights for copyright policy

● dc: description for short, paragraph length description

Reference: summary for a very short one-line description if dc: description already exists

Tagspace: tags as a space-separated list of tags

Tagspace: tag for a single tag (which may contain spaces)

● atom: updated if you need to specifically call the last updated timestamp

• media: height and media: width for audio / video resources. These attributes are good for specifying sizes in pixels.

● geo: location for a generally human-readable location, such as "San Francisco" or "South Bay Area"

● geo: point for specific latitudes / longitudes (separated by spaces)

● geo: floor for the number of floors in the building

Finance: stockTickers for a list of related stock quotes (a semicolon separated list, accompanied by NY Times metadata)

Business / Commercial / Directory

● Common characteristics

Vcard: adr for representing street addresses as semicolon separated parts

● vcard: tel for phone number

● vcard: url for your website

● Full commerce: vocabulary

News / Events / Gossip

● Common characteristics

● full news: vocabulary

Shopping / Commerce / Product

● Common characteristics

● Full product: vocabulary

Social networking

● Common characteristics

Travel / Destination

● Common characteristics

● Full travel: ^* vocabulary

Data type

Data type vocabulary has two uses. Some properties, such as dc: identifier, can have many other possible values, such as URL or ISBN numbers. In this case, the range of this property is just a "string", but if you want to explicitly specify that the value entered there is more specific than the range allows, you can specify a data type.

E.g:

Another use of data types is disambiguation. Let's say we are extracting information about a photo and have two different ways to represent the constructor by username and URL. The data type distinguishes between different duplicate dc: creator statements.

excuse:

When the property you need doesn't exist in the list

There may be cases where the kind of metadata you want to extract is not found in the searchmonkey-profile lexical reference. It may be an existing RDF vocabulary, or something you had to construct yourself.

For example, let's say your metadata is the number of megapixels your digital camera can handle. At a minimum, you should try to define the property prefix, name, domain (what kind of object it applies to), and range (what kind of value the data can be). In short, it should look like another row in the property plot. Of course, the more formal RDF vocabulary definition is much larger.

The prefix should be something reasonably short, technical, and unlikely to be used for purposes unrelated by others. As in all CURIE cases, the prefix must represent a longer URL that you must define. It must be something behind the domain name you control.

The actual definition occurs as xmlns: _prefix_attribute. If the prefix is digicam, the property is megapixels, the URL is http://example.com/vocab/digicam, the domain is rel: Product, and the range is decimal, the theoretical chart entry would be:

The declaration and use of the prefix would look like this:

excuse

Example of Encyclopedia / Reference / Info DataRss

Encyclopedia / Reference / Info RDFa Example

Vocabulary chart

If it contains structured data, choose from the following object types:

Object chart

These are nouns; Recommended value for the rel attribute of an item that represents a person, place, or thing that may have additional metadata properties.

Character chart

These are the recommended property values for use in the property properties of the meta.

The domain column indicates what type of object can have the listed properties. For example, media: url applies to objects of the rel: Media class, including child classes rel: Image, rel: Thumbnail, and others.

An empty value in the domain column indicates that the enumerated properties apply to all objects.

The range column indicates what kind of value is appropriate for the enumerated property. Integers, floating point numbers, decimal numbers, and periods all map to XML schema data types of the same name. The date is mapped to the XML schema dateTime using the ISO 8601 format. The URI maps to the XML schema anyURI and must be an absolute URL that does not begin with a slash. Email maps to email addresses defined by RFC 2822. List maps to a space-separated list.

Empty values in the range column indicate that the listed properties can accept values of any format.

excuse:

essence

42

Boolean

One

Boolean

0

Boolean

Oh yeah

Boolean

lie

Floating point

3.14159

Decimal

2.00

term

P3D [3 days]

term

PT8H [8 hours]

date

2007-12-12T03: 04: 05 + 06: 00

date

2007-12-12

uri

http://search.yahoo.com/mrss

e-mail

address@email.com

Blank-list

2007 Croatia photos vacation fun [space separated list]

Comma-list

2007, Croatia photos, vacation, fun [Comma separated list, individual list items may have meaningless leading or trailing spaces, but internal spaces are important]

Semicolon-list

622 9th Ave W; Williston, ND; 58801 [semicolon separated list]

nonempty

"OK"

Data type chart

These are the recommended property values for use with the meta data type.

Note that for the values found in the rel and property attributes, the following preferred vocabulary and associated prefixes are automatically provided:

atom

Vocabulary for Atom Concepts <http://www.w3.org/2005/Atom>

cc

Creative Commons <http://creativecommons.org/licenses/>

dc

Dublin Core Metadata <http://purl.org/dc/elements/1.1/>

foaf

Friend-of-a-friend <http://xmlns.com/foaf/0.1/>

geo

Vocabulary for Geographic Metadata <http://www.georss.org/georss>

media

RSS-Media <http://search.yahoo.com/mrss/>

rdf

RDF <http://www.w3.org/1999/02/22-rdf-syntax-ns#>

rdfs

RDF Schema <http://www.w3.org/2000/01/rdf-scherna#>

review

RDF review <http://www.purl.org/stuff/rev#>

vcal

RDF calendar <http://www.w3.org/2002/12/cal#>

vcard

vcard <http://www.w3.org/2006/vcard/ns>

... and ...

rel

Object vocabulary <http://search.yahoo.com/searchmonkey-relation/>

... and ...

assert

Vocabulary for Error Detection and Flagging in Metadata <http://search.yahoo.com/searchmonkey/assert/>

commerce

Vocabulary for Commerce Related Metadata <http://search.yahoo.com/searchmonkey/commerce/>

context

Vocabulary for transient contextual information

<http://search.yahoo.com/searchmonkey/context/>

finance

Vocabulary for Financial Metadata

<http://search.yahoo.com/searchmonkey/finance/>

job

Vocabulary for Job-Related Metadata

<http://search.yahoo.com/searchmonkey/job/>

news

Vocabulary for News Metadata

<http://search.yahoo.com/searchmonkey/news/>

product

Vocabulary for Product-Related Metadata

<http://search.yahoo.com/searchmonlcey/product/>

reference

Vocabulary for Bibliography and Links

<http://search.yahoo.com/searchmonkey/reference/>

social

Vocabulary for Social Graph Access and Information

<http://search.yahoo.com/searchmonkeysocial/>

tagspace

Vocabulary for tagsets <http://search.yahoo.com/searchmonkey/tagspace/>

... and ...

country

Data type used to indicate a specific country

<http://search.yahoo.com/searchmonkey-datatype/country/>

currency

Data type used to indicate a particular currency

<http://search.yahoo.com/searchmonkey-datatype/currency/>

use

Data type used to differentiate the use of the property

<http://search.yahoo.com/searchmonkey-datatype/use/>

Claims (15)

Receiving user input;
Associating first metadata with the user input, the first metadata describing a user environment and providing a context for the user input;
Associating second metadata with one or more content sources; And
Sending to the user content based at least in part on the user input data, the first metadata, and the second metadata, the method comprising:
The method is performed by one or more special purpose computing devices
Way. The method of claim 1,
Wherein the first metadata includes entity information derived from performing disambiguation of the user input. The method of claim 2,
The entity information is at least one of a person, agency, association, location, business, event, object, vehicle, device, appliance, tag, label, link, time, or time period. The method of claim 1,
Wherein the first metadata comprises at least one of spatial data, temporal data, social data, physical object-related data, or topical data. The method of claim 1,
Wherein the first metadata includes social relationships and association information. The method of claim 1,
The one or more content sources comprise one or more of a content index, a feed, a file, an ftp site, a web drive, a network cloud, and a mobile device. The method of claim 1,
Each of the one or more content sources having one or both of a content feed and an application program interface. One or more storage media storing instructions that, when executed by one or more computing devices, cause the method of any one of claims 1 to 7 to be performed. One or more processors;
Memory operably coupled to the one or more processors;
A storage device for storing a user data store (UDS), wherein the user data store associates first metadata with input from a user, wherein the first metadata describes a user environment and also describes the user input. -Provide context for;
A mobile search refine manager (MSRM) for parsing a search query included in the user input to form a modified search query;
A search module for performing a search using the modified search query in combination with second metadata associated with one or more content sources; And
A search clustering module for sending content to the user, the content being based at least in part on the user input data, the first metadata, and the second metadata
A server having a. 10. The method of claim 9,
The first metadata includes entity information derived from performing clarification of the user input. The method of claim 10,
The entity information is at least one of person, agency, association, location, business, event, object, vehicle, device, appliance, tag, label, link, time, or time period. 10. The method of claim 9,
The first metadata includes at least one of spatial data, temporal data, social data, physical object-related data, or topic data. 10. The method of claim 9,
Wherein the first metadata includes social relationship and association information. 10. The method of claim 9,
The one or more content sources comprise one or more of a content index, a feed, a file, an ftp site, a web drive, a network cloud, and a mobile device. 10. The method of claim 9,
Wherein each of the one or more content sources includes one or both of a content feed and an application program interface.

Images