Method and server for providing content to a user

METHOD AND SERVER FOR PROVIDING CONTENT TO A USER}

FIELD OF THE INVENTION The present invention relates generally to search queries over networks and to user configuration of feeds and clusters in relation to mobile devices.

The approaches described in connection with this section are approaches that could have been pursued, but are not necessarily approaches previously contemplated or pursued. Accordingly, unless otherwise indicated, 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.

Tremendous changes that affect our daily lives have taken place on the Internet. 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 communicate voice messages, emails, text messages, and the like, as well as retrieve information over the Internet. It's not uncommon to see people on buses, trains, or ships using their mobile devices to browse shops, restaurants, music, businesses, and more. It is conceivable that these devices will eventually be allowed at least wireless internet access on the plane.

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

Along with the desire to conduct active, relevant information retrieval, some mobile device users may wish to deliver content in a more automated manner, possibly with content tailored to unique interest groups, such as hobbies or social network groups. Although a user may have the time, energy, and technical capabilities necessary to manually configure a mobile device, the user may be constantly receiving a narrow set of certain information sources, such as news headlines, weather, and sports. likely to be compelled to keep. Another user may wish to deliver specific content according to the user's current environment.

Likewise, advertisers want to provide information tailored to each user to enhance the user experience. Because of the likely correlation between user search terms and users' actual interests, advertisers may approach this goal by delivering advertising material as part of search engine results. However, in a mobile environment when the user is not searching, advertisers typically have limited ability to reach advertising targets that may be on the move and need information related to the environment in which they currently belong or are going.

1 is a system configuration diagram for 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; Figure 4 illustrates the generation of results based on searches yielding no named cluster results; 5 illustrates a mobile user search system performing federated queries against multiple data sources, where third parties provide a plug-in module for translating their data into a format usable by search; Fig. 6 illustrates a sample framework for the plug-in shown in Fig. 5; 7 illustrates a schematic diagram of an Add Anything Engine (AAE); 8 illustrates a schematic diagram of MHTE (Mobile Homepage Targeting Engine); 9 illustrates some of the sample uses of AAE; 10 illustrates some of the sample uses of AAE; 11 illustrates some of the sample uses of AAE; Fig. 12 illustrates a full screen shot (with omissions) of the mobile device obtained 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 oneSearch entity types organized by hierarchical type-subtype relationships; 16 is a block diagram of a computer system in which embodiments 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 understood that the present 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 unnecessarily obscuring the present invention.

[summary]

It incorporates a user's current mobile activity, social relationships, and association histories, as well as historical search and browsing data, to explore multiple aspects of a user mix for mobile content and the composition of information displayed on a user's mobile device or aggregated on a personal homepage. Techniques for enriching a mobile user's personalized content consumption, web browsing, and search experience by personalization are disclosed. These techniques may be applied automatically or performed by the user. A content object may be any form or format of content consumable by a user, such as, but not limited to, any one or more of the following: via browsing or voice, email, text, image, animation, gesture, Text, numerical data, images, animations, audio, video, or any combination thereof, including content generated as a result of a search, from communications with others via audio or video. The content may originate from any data processing source or device.

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

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

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. Users may incorporate information feeds into their home pages or devices, and when users annotate results and wish to include their sources, results, or search types in their mobile "home page" in the future, they may be added to search results or information resources. You may receive updates automatically based on applicable web pages or information.

In one embodiment, a set of users is categorized for a selected advertiser or product. From a set of users, segment users for advertisers based on their context, ad copy, and hierarchical real-world content organization for the user's mobile home page, and user-homepage interaction and usage data over time. , qualify the user, and predict candidate targets for the set of one or more advertisers and conditions based, at least in part, on the preselected time to evaluate.

In one embodiment, (1) the user composes content, consumes the content, interacts with the content, shares the content, and (2) the user's mobile device(s), along with the preferences and activities they perform. In addition to the user's content consumption and communication by means of (3) the context in which the user performs these actions and who performs these actions along with the user, the advertiser is provided with information about the interests and intentions of the user.

Exemplary Operating Environment

Except where indicated, the illustrated mobile and network operating environment will not be repeated herein as it is not necessary for a complete and correct evaluation of the various embodiments of the present invention. Such exemplary mobile and network operating environments can be found, for example, in Application No. 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 instrument and record user behavior. include

1 , a network system 100 includes a mobile device 110 that communicates with a server 130 using a network 104 . In one embodiment, network 104 is the Internet, but may also be a non-public network, such as a carrier. Server 130 includes a set of one or more search and data applications 134 . The search and data application 134 is configured to perform a search for data accessible via networks and the Internet and a custom content engine 140 configured to generate and maintain a "homepage" of custom content types and sources in one central display. and a search engine 150 that is In one embodiment, the custom content engine 140 is a Yahoo! It corresponds to the onePlace mobile homepage and the search engine 150 is Yahoo! or configured to search private networks of user data, such as Google.

The search and data application 134 also includes one or more of the following modules: a user data store (UDS) 152, a mobile search refine manager (MSRM) 154, a search module 156, and a search clustering module 158. do. From a technical standpoint for understanding the methods and systems disclosed herein, these specific naming schemes are not entirely unnecessary, but are provided for the convenience of the reader. These modules will not be described in a serial fashion, but will be introduced when certain specifications and embodiments are illustrated. Although each module is described separately from the search engine 150 , each module may be integrated into the search engine 150 .

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

Before describing an illustrated operating environment in which various embodiments may be practiced, the following concepts including "social relationships and associations" and "metadata" are introduced and described. In the following, while various embodiments are discussed, additional subtle distinctions to these concepts may be set forth.

<u>Social Relations and Associations</u>

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

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

An individual's social relationships and association graphs are usually not static, where the movement and interactions between an individual and his or her social relationships and associations are determined by the following non-limiting factors: (1) where the individual is located; (2 hours; It can be a function of one or more of (3) who the individual is interacting with, either physically or through online social relationships and associations, and (4) what the individual is doing.

Many variations, combinations, and/or fine distinctions of these factors may be involved; For example, an individual may be planning and coordinating a family reunion that involves a variety of direct and indirect human relationships that change over time. Information related to these factors may be captured by a mobile device or a network server. Some methods and systems for the collection and use of social relationships and related information are disclosed in Application Serial No. 12/069,731 entitled "Identifying and Employing Latent Social Network Relationships" and "Social Aspects of Content Aggregation, Syndication, Sharing, and Updating". All of which are entitled Application No. 12/182,756.

<u>metadata</u>

As described above with respect to an individual's social relationships and associations, a description expressing an individual's current activity provides a continuous stream of route/status data for the user and any user- It may include some or all of the factors relating to "where," "when," "who," and "what" to provide precise context for a request to occur. 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 called W4 metadata of the user.

As described herein, each operation of a mobile search query relating to (1) operating environment, (2) mobile client environment, (3) server environment, and (4) location modifier is a mobile client, server, and (optionally) ) can be further extended with reference to a metadata wrapper, including user W4 metadata, placed around data exchanged between administrators or third-party service providers.

User W4 metadata includes contextual metadata regarding "where", "when", "who", and/or "what" of any given event, eg, text message or voice communication. In other words, W4 metadata is spatial or natural geography (i.e., "where"), temporal (i.e., "when"), social (i.e., "who"), and/or physical object or topic interest (i.e., " It may contain information related to "what"). Furthermore, by analyzing the similarity of these aspects among groups of users as well as patterns of these similarities within individual spatial, temporal, social, and topic aspects and between individual spatial, temporal, novel, and topic aspects, among these aspects At least some relevance may be determined.

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

For example, the user enters the query "apple". In addition to the text of web pages and documents and associated with web pages and documents, the term "apple" can map to a number of abstract ideas, physical objects, and digital objects and media. Collectively, these are referred to herein as "entities." In this example, disambiguation is performed on the string "apple" to determine at least some of the possible entities that "apple" can represent, eg, company, fruit, record label, etc. It can be mapped to the above result types. In addition, disambiguation may favor recent real or online behavioral data favoring certain results. For example, if a user visited an Apple Mac store yesterday and made a purchase, the disambiguation may favor local receipts or a product information page the user recently accessed in connection with the user's prior purchase or research.

For example, if the entity is Apple^&amp;#174; If a company, different result types may include geographic results (eg, company or store location), stock prices, news articles (eg, text and video), as well as traditional web and mobile web links. As further described herein, clusters of result types based on the entity or entities identified in the disambiguation step and their respective mappings to result types may be rendered or manipulated. Additional information regarding the disambiguation of search queries can be found in application 11/651,102 entitled "Clustered Search Processing".

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

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".

Also, entities can exist in multiple 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. Likewise, a pizza may be a recipe entry for a business listing, venue, venue, as well as a Wikipedia, Reference, or Information object.

The integration of entities and entity types represents an important shift away from simple bookmarking of web pages, as it makes it possible to store pointers to entities from which it is possible to have a real-time feed of information or for which a feed of real-time information can be created. am. For example, compared to bookmarking the entity "examplemovie", if you consider a static bookmark to the website "www.examplemovie.com", from there you automatically get a review of "examplemovie", local running times, DVD release notices, etc. You can receive updates.

<u>Example mobile user and network configuration</u>

Various embodiments of the network system are described below, wherein the capture and transmission of metadata is used to enhance the mobile user browsing interaction and consumption experience.

Referring to FIG. 1 , the storage of metadata and other user information, such as social relationship and association information, may be realized by a User Data Store (UDS) 152 that is part of a search and data application 134 on a server 130 . have. UDS 152 may include databases, texts, spreadsheets, folders, files, etc., and is configured to maintain and store social relationships and association information collected from network 104 as well as associated with networks or user data sources. 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, social relationships and association information stored in UDS 152 for mobile users includes one or more of the following: (1) a social networking website to which the user belongs, such as MySpace, Facebook, or Linkedln. user identification information for; (2) contact information maintained by the user, such as for voice contact, electronic mail, instant messaging, and text messaging; (3) the member group to which the user belongs; (4) subscriber information of individuals subscribing to user-generated content, such as subscribers to the user's Flickr account or to the user's blog; and (5) other data sources accessible about the user's location, associations, behaviors, interests, or transactions.

In one embodiment, social relationships and association information stored in UDS 152 for mobile users includes electronic communications sent or received by mobile users, such as electronic mail, instant messaging, and text messaging, while other Embodiments combine information from multiple mobile and stationary devices to include all announcement data, communications, and transactions for users.

In one embodiment, the user's actual and historical route data, as well as location information based on the user's actual residence(s), account registration information, locations of interest that the user has implicitly or explicitly shared with the system, etc., may also be included in the UDS 152 ) can be stored in Such information may indicate that the user resides in a particular town, region, city, or otherwise similar within a particular county, state, country, or other similar or a given 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 hierarchical relationships, in one embodiment.

In one embodiment, mobile state information about the user may also be stored in 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) the current state, location, and/or usage of the mobile device 110 , such as when and for how long it was powered on and accessed as well as which cell tower or network node it was communicatively connected to; (3) status information of the application 242 loaded on the mobile device 110 or currently running on the mobile device 110 , such as information about the interactive application 120 ; (4) the contents of the data store of the mobile device 110; and (5) information such as the coordinate history from the GPS of the mobile device 110 from which the user's mobile state (such as that the user is located in a slow moving transportation device on a particular highway) can be derived. Usage history includes active interaction data generated by the user's actions, as well as the user's location, proximity to known landmarks or Points of Interest (POI), and association with other coexisting users, devices, networks, vehicles, or appliances. It also includes manual data such as

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

In one embodiment, social relationships and related information may be obtained indirectly through monitoring various movements, actions, and interactions of the user. Interaction may include the use of a user-activated browser toolbar, in which some or all of the data sent towards the mobile device 110 is forwarded towards the UDS 152, as well as instrumenting the mobile device for orientation, biometrics, and motion detection. may be monitored through other known methods of tracking user interactions, including Thus, for example, implicit social relationship and associated data and/or contact information may be communicated with a user regardless of whether the user's individual device, environmental sensor, or data feed and/or both are members of an explicit social network. It can be extracted based on data from content in messages between different users.

Information such as social networking information, communication information, location information, and mobile route or status information may be stored within UDS 152 and passed along with other data as "metadata wrappers". As described below, a metadata wrapper may provide context information or content information to the data it accompanies. A non-limiting example of a vocabulary through which metadata may be propagated, including the use of properties, objects, and data types, is provided in the following section entitled "Example Metadata Vocabulary".

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

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

In one embodiment, the MSRM 154 identifies any concept-specific data sources to be searched for. One embodiment of a method by which a third party may provide a custom 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 , along with instructions to any concept-specific data sources to be searched.

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

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

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

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

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

In one embodiment, metadata representing the user's mobile state information may be used to configure the layout of the search results displayed on the display 126 of the mobile device 100 .

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

<u>Exemplary User Examples</u>

(a) clustering through the use of metadata about device usage and (b) clustering with respect to disambiguation of strings into entities are illustrated in Figures 2-4 displaying sample searches and search results on mobile devices.

Referring to FIG. 2 , in panel 210 , the mobile user performs a simple search using the term "sushi". The previously obtained 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 identification and display of nearby businesses, such as restaurants, that are identified as relevant to the search term. A restaurant forms a cluster for a specific instance of the abstract entity type "restaurant". These results can be more finely differentiated by distance, as displayed in panel 210 .

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

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. Although the user is viewing details regarding a particular instance of the abstract entity "restaurant", the display on the mobile device is displayed with other relevant information, such as maps, user reviews, and more tools, via links to "Business details". is configured to display a link of

Panels 231 , 232 , and 233 display links available from the landing page for "Sushi Roku". For the information displayed in each panel, a metadata wrapper was 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 in the location information ("near 3000 Paradise Rd, Las Vegas") at the bottom of the search box. This search generates a cluster of profile information using the abstract class "Contact" with respect to three applications, Facebook, Linkedln, and MySpace. In this example, data (including metadata wrappers) from these three applications is pulled from each through an open API framework and assembled by the server.

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

In panel 320, the user selected a profile found on Facebook, and encapsulated an encapsulated summary about that individual, such as "Berkeley Alum UChicago Alum", corresponding to the class "Overview", with a picture of the size of a thumb. summary), as well as a summary of various people named "Will Decker" (or some variations on it) with additional information.

In panel 330, the user can access a "Will Decker" metadata wrapper that contains 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. Moved to display of Facebook photo gallery for specific instance.

4 illustrates the generation of results based on a search yielding anonymous cluster results, in which the user is presented with one or more anonymous virtual clusters, which themselves may 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 a named cluster, 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 a landing page that is assembled from data and metadata that (1) may be supplied from results obtained from a general purpose data source or (2) may be supplied from the MotorTrend API plugin. presented Other possibilities for the occurrence of an outcome include one or more of the following: (1) the occurrence of a virtual cluster; (2) the occurrence of a series of virtual clusters; and (3) a list of OpenAbstracts that are not clustered but satisfy at least one relevant criterion.

<u>Integrating content sources towards mobile search frameworks</u>

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

5 illustrates a mobile search system 500 for performing federated queries to multiple data sources, where third parties provide plug-in modules 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 a "content index". Data is transferred from the content plug-in 521-524 to be described later with reference to FIG. 6 toward the content index. The results of the mobile search system 500 are also pulled directly from the content plug-in 526 .

Each of the plug-ins 521-525 pulls data from or pushes data by the content sources 531-536. Content sources may include application program interfaces (APIs) and/or content feeds. Additionally, the results of the mobile search system 500 are also pulled directly by the content source 537 having an API. As illustrated, data may be pulled towards plugins from APIs or content feeds from third-party providers; Data may be pushed towards the plug via a content feed of a third party provider.

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, one or both of which are in communication with one or more of the "content sources" shown in FIG. 5 . The parsed data, including optional metadata wrappers, is passed from the parser 610 to the association module 620 . Explicit inferred cluster result mapping is performed by association module 620 , which is processed by renderer 630 . The result of the renderer is to provide a metadata wrapper (such as clusterID, entityID, W4 metadata, and content type metadata) that enables the system to determine the format, rendering, and user actions appropriate for content displayed on a mobile device. , can be processed through XML schema or template/user interface mapping. The results are then sent to one or more data stores comprising the "content index" of FIG. 5 .

<u>Integration of search sources or results into the home page</u>

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

Additionally, a search result or portion of a search result may itself be considered an entity or entity type described above; For example, a web link or RSS feed may be added to an entity or entity type of a user's home page and treated as an entity or entity type of a user's home page. Items that may be added include: (1) web links; (2) RSS feeds; (3) a web link for which an RSS feed for it is created based on links that are periodically revisited to check for updates; (4) "entity" or "entity type"; and (5) entities or entity types added through parsing of web links or RSS feeds.

As a non-limiting example, a user may select a search result or any online web page or resource for future inclusion, or the user may add an 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 may automatically or interactively determine whether the user wishes to add that content, resource, or feed amongst one or several associated entities.

Such preferred specifications determine a search result or content object associated with an icon, checkbox, user gesture, or content type for the selected result, when selected or uttered, and a user home page or consuming device, such as an e-book reading device, or This may be realized through display by an associated uttered command generating a corresponding information feed to be integrated into the gaming device. In the following, the ability for a user to add arbitrary search results as an information feed is described with reference to FIG. 7 .

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

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

The query manager 704 tracks search query information and associated metadata of the search history or one or more sets of usage data 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 the query manager 704 is fed to a content analyzer 712 for use in determining a particular content type or format to be associated with that search result. The content analyzer 712 parses the received web link and RSS feed for determination of the corresponding entity and entity type.

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

The registration manager 716 may generate a recurring information feed among non-feed enabled information objects, and accordingly, the user receives updated information from the corresponding link in various sections. . For example, a user may want to look at a web page announcement 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, registration manager 716 issues instructions to periodically fetch data sources corresponding to non-feed enabled information objects selected by the user, parse the resulting data, and apply metadata wrappers. include

Registration manager 716 forwards any recurring feeds of information to mobile home page manager 720 for display on mobile device 110 .

The display metrology manager 708 controls both the actual display of the "add this" icon and the reception of corresponding user input. The display metrology manager 708 forwards the selected announcement information feed to the mobile home page manager 720 for feed selection and forwards other user selections to the registration manager 716 . Display metrology manager 708 may also be configured to detect spoken commands and/or user gestures to select selected announcement information feeds for mobile homepage manager 720 and registration manager 716 for feed generation.

9-13 illustrate an exemplary mobile home page environment and one way in which a user may add an entity to a mobile device home page. Panel 910 displays the portion of the mobile device screen from which the user can add content to the user's home page by first activating an item entitled "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 custom search, where input in area 921 corresponds to a default set of locations for adding content therefrom. Thus, the "Add Anything" function can be added to the search query entered by the user or to the user's mobile home page using context and other information about the user, available entities, and devices, without requiring the user to enter a search query. It may be applied to a pre-selected or customized set of content objects (entities, links, RSS feeds, etc.) presented to the user, which may present one or more custom and/or custom content objects for possible additions.

Continuing to refer to FIG. 10 , the user viewing panel 1010 has the input text "Red Sox" in the area 1011 . After activation of the "oneSearch" button in panel 1010, the user is presented with panel 1020 that provides the user with various choices from which to select one or more content objects to add to the user's mobile home page. Some selections, such as area 1022 , correspond to RSS feeds from which the user may select. Another choice corresponds to links to news articles and websites, for example "www.redsox.com". Area 1021 is one or more information owners, publishers, or authors as described in more detail in Serial No. 11/651,102, filed Jan. 5, 2007, entitled "Clustered Search Processing," and incorporated hereinabove by reference. It corresponds to the entity "Boston Red Sox" that can be associated with.

In FIG. 11 , the user of the panel 1110 has selected the first entry 1111 corresponding to the entity "Boston Red Sox" to be added to the user's home page. In one embodiment, a default set of content and sources are automatically created as defaults. In one embodiment, a user can specifically select or deselect a content source or object from those associated with a user's 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, content associated with an entity may be free or paid, anonymous or registered, depending on the subject matter and standards of the practice.

Screenshots illustrating the start and end of the user homepage are shown in FIG. 12 . Since the screenshot is too long to be properly displayed here, panel 1210 represents the 'top' of the home page. The page scrolls down until reaching the panel 1220 representing the 'bottom' of the home page. As indicated in area 1230, an icon representing the entity "Boston Red Sox" is added to the user's home page, giving the user an easily accessible view of the system's latest custom set of content corresponding to the Boston Red Sox. provides a way

In FIG. 13 , panel 1310 illustrates content assembled by the system, corresponding to the entity "Boston Red Sox". In Figure 13, the system added content sources corresponding to scores and schedules, upcoming games, news, photos, and roster. Unlike simple bookmarks, each of these content sources is dynamic, and information from each source can be automatically retrieved and assembled for consumption by the user. 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, as well as associated content object and associated content object for a given entity; Dynamically change (i.e., delete, reorder, different media types) based on preferences or behaviors related to various aspects of the above-described context (i.e., spatial, temporal, social, topical, etc.) in which the feed may be accessed by the user. can be transcoded into .

14 illustrates two diagrams in which a user may reconfigure 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 home page and the associated arrow indicates that the user can interactively delete, increase, or delete an order for any entity or content in the list. , to lower it. In one embodiment, the user can group any entity or content in the list, give the group a name, and delete or reorder the group.

<u>Ad personalization</u>

Dynamic mobile user web browsing interactions and content consumption experiences differ significantly from traditional static methods of web browsing, typically performed by personal computers tied to home or work. Attempts to cram traditional web browsing interactions and content consumption experiences onto small mobile screens fail to provide the benefits produced by the previously disclosed methods and systems.

Likewise, using traditional techniques to squeeze advertising material onto mobile screens results in a negative user experience. Traditional technologies result in 'one-size-fits-all' advertisements that undermine the user experience rather than emphasize it.

Significant improvement where actual mobile user histories are used to (a) align mobile users with brands and/or advertisers and (b) predict specific users for specific advertisers in specific campaigns and time and/or spatial combinations for delivery This is calculated A method and system for matching advertisements with mobile users is described below with reference to FIG. 8 .

8 illustrates a method for matching specific ad copy or full text content with specific ad or content delivery opportunities based at least on content, format, configuration, and interaction data generated by the user and their mobile homepage, such as Yahoo's onePlace. A fully customizable personal advertising system, MHTE (Mobile Homepage Targeting Engine; 800) is illustrated. It should be appreciated that the components of FIG. 8 can be easily integrated into the search and data applications of the server 130 .

The MHTE 800 may: (a) manage interactions between advertisers and publishers; and (b) a module for configuring the user's mobile homepage as an ad serving request generated by one or more of the following: (1) a network; (2) users; 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 .

Ad copy manager 804 may interact with an advertiser or publisher and allow the advertiser or publisher to do one or more of the following: (1) register and manage their account; (2) submit advertising copy or professional content; and (3) specifying certain actions in the form of targeting models. Professional content may be any form of new, updated, or exclusive content marketed to users by an 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) access networks; (3) demographics; (4) current user activity; (5) location or proximity to one or more known people, places, or things, (6) coexistence of other users, devices, or POIs, and (7) user histories, preferences, or profiles, among others.

The ad display manager 816 may display ad copy received from the ad copy manager 804 or Fill in the full text content as directed by the match manager 812 and return the metered copy for display by the requestor. Such an advertisement request may include information indicating predetermined target user criteria, the amount or maximum amount the advertiser can pay, limitations or conditions of the display, and the period of provision.

The mobile homepage manager 808 measures and tracks the user's interactions with the mobile homepage or other selected web pages, including user content, composition, and utterance, tactile, and sensory inputs.

Matching manager 812 applies a targeting model to user profiles to consider, score, and select ad copy or full text content for serving in response to ad requests handled by ad display manager 816 . Data from the mobile homepage manager 808 may be forwarded to the matching manager 812 for fine-grained differentiation or configuration of various ad targeting models.

The following non-limiting examples illustrate some of the benefits produced by MHTE 800 . In a first example, the user may contact the user for a special promotion, recent review, grand opening or other content, a potential target user's current location, home, work, or other location of interest, eg, a city they visit regularly. Added "Pizza Restaurant" as an entity to onePlace in order to receive updates such as feeds or sources of information related to the entity in the vicinity of locations designated as of interest by 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 by the MHTE 800 as a potential target entitled to receive customized advertising materials or specialized content.

After the user adds "Pizza Restaurant" as an entity to onePlace, the user can access new items when a local pizza restaurant publishes a new special dish or content, when a review is written about the pizza restaurant, and/or near a location of interest. You will receive an update when the pizza restaurant opens. Additional considerations may be realized by the user pointing to other entities in onePlace and the placement of these and related entities relative to each other of the home page as well as content to be destroyed, rejected, or canceled. The level and type of user activity associated with each entity over time may be used to determine the relative value of each entity in targeted advertising or specialized content for that user. Targeting of content from publishers as well as targeting of advertisements from advertisers may be incorporated.

Information about the same user may arrive toward the MHTE 800 through additional interaction by the user. For example, the user may add to onePlace also "vegetarian recipes" that can be combined with targeting information derived from the user's interaction with the "Pizza Restaurant" entity, content related to "vegetarian pizzas" and not "nonvegetarian pizzas"; You may have developed a targeting profile that users are likely to prefer to advertise or promote.

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

Target data is looking for men aged 18-34 who tend to eat out. Match manager 812 identifies a set of potential targets, including users described above.

Matching manager 812 is vigilant, reviews the placement of entities on a user's home page, and considers the level and type of user activity associated with the entity in determining advertisements and content targeted for the user. In this example, the matching manager 812 constructs an advertisement for a meatless pizza special served by a pizza maker established nearby. This advertisement is delivered to the user by the mobile home page manager 808 .

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

Your Yahoo! A user's Yahoo! In addition to the existence of a "Vegetarian Recipes" entity in onePlace, additional data and metadata are included in the Yahoo! A few searches using the term "vegetarian" from oneSearch and additionally a Yahoo! User targeting profiles can be further enhanced, such as a previous search history of potential targets, including targets with status updates posted from oneConnect to MySpace.

Matching manager 812 is vigilant, reviews the user's metadata, including social relationships and associations, and constructs advertisements for meatless pizza specials served by pizza makers established nearby. This advertisement is delivered to the user by the mobile home page manager 808 along with the search results.

14 illustrates two ways in which a user's placement of an entity on 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 that adjusts the user's various e-mail accounts, instant messengers, social networks, contacts, and calendars. When listing these kinds of information, it is customary for users to place their favorite entries near the top of each list. Accordingly, in panel 1410, it is revealed that the user is more actively using the user's Facebook account than the user's MySpace account, as indicated by the relative ranking of the two entries.

As described above, the match manager 812 can assign these types of metrics, such as ranking within or between groups, to a higher order on their mobile home page through past, current, or predicted activity or It can be used as part of an ad personalization process that increases a specific user's weight for an entity or brand based on strong associations.

Similarly, panel 1420 corresponds to a user selection order of entities, such as those illustrated in FIGS. 9-13 . For example, the order of entities shown in panel 1420 corresponds to all entities shown in FIG. 12 ; Note the last entity in "Boston Red Sox". In panel 1420, the user may rearrange the user's entries as described above. Matching manager 812 may use this sequence, for example, to select a particular advertisement from a pool of possible advertisements, which may be displayed to the user, such that the user may be prompted for a list of potential advertisements related to the content or entity to which the user is subscribed. By increasing the ranking, the content and entities associated with the mobile homepage influence the selection of advertisements. In addition, a user's deselection of past content or advertisers can 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. A special purpose computing device may be hard-wired to perform the technology, or may be digitally programmed to perform the technology, such as one or more application-specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs). It may include electronic devices, or it may include one or more general purpose hardware processors programmed to perform techniques according to program instructions in firmware, memory, other storage, or combination. In addition, such general purpose computing devices may realize the technology by combining custom hard-wired logic, ASICs, or FPGAs with custom programming. A special purpose computing device may be a desktop computer system, portable computer system, handheld device, mobile phone, browsing or gaming device, networking device, or other device that incorporates 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 or other communication mechanism for communicating information and a hardware processor 1604 coupled to bus 1602 for processing information. Hardware processor 1604 may be, for example, a general-purpose microprocessor.

Computer system 1600 also includes 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 Main memory 1606 may also be used to store temporary variables or other intermediate information during execution of instructions to be executed by processor 1604 . Such instructions, when stored on a storage medium accessible to the processor 1604 , machine the computer system 1600 into a special purpose machine that is customized to perform the tasks specified in the instructions.

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

Computer system 1600 may be coupled to a display 1612 , such as a cathode ray tube (CRT), via bus 1602 , for displaying information to a computer user. An input device 1614 comprising alphanumeric and other keys is coupled to the bus 1602 for communicating information and command selections towards the processor 1604 . Another type of user input device is a cursor control 1616 , such as a mouse, trackball, or cursor direction keys, for communicating directional information and command selections towards the processor 1604 and for controlling cursor movement on the display 1612 . . This input device typically has two degrees of freedom in two axes, a first axis (eg x) and a second axis (eg y) that allow the device to specify a position in a plane. (two degrees of freedom). In addition, the input device 1614 provides audio, visual, and tactile output functions, as well as voice and recording (audio), visual (video and image), tactile, and gesture input or sensing input functions, and time its state and location. be a mobile phone, gaming, reading, browsing, or communication device that may include multi-channel functionality that is connected bi-directionally over one or more networks, such as to report in real-time and to facilitate access to content and users. can

Computer system 1600 may combine the techniques described herein with the computer system to make computer system 1600 a special purpose machine, or user defined hard-wired logic to program computer system 1600 to be a special purpose machine; It may 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 sequence of instructions contained 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" means any medium that stores data and/or instructions that cause a machine to operate in a particular manner. Such storage media may include non-volatile media and/or volatile media. Non-volatile media include, for example, optical or magnetic disks, such as storage device 1610 . Volatile media includes dynamic memory, such as main memory 1606 . Common forms of storage media include, for example, floppy disks, flexible disks, hard disks, semiconductor drives, magnetic tape 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.

A storage medium is distinct from a transmission medium, but may be used with a transmission medium. A transmission medium participates in transferring information between storage media. Transmission media, for example, include coaxial cables, copper wires, and optical fibers, including wires with bus 1602 . Transmission media may also take the form of sound waves or light waves, such as those generated during radio and infrared data communications.

Various forms of media may be involved in carrying one or more sequences of one or more instructions to the processor 1604 for execution. For example, the instructions may initially be loaded onto a magnetic disk or solid state drive of a remote computer. A remote computer can load instructions into dynamic memory and send the instructions over a telephone line using a modem. A modem directly connected to the computer system 1600 may receive the data on the telephone line and convert the data to an infrared signal using an infrared transmitter. An infrared detector may receive the data carried in the infrared signal and suitable circuitry may place the data on the bus 1602 . Bus 1602 passes data to main memory 1606 from which processor 1604 fetches and executes instructions therefrom. The instructions received by the main memory 1606 may be executed before or after execution by the processor 1604 to deliver the mobile application using the storage device 1610 as well as wireless data transfer, wireless client-server communication, and wireless peer-to-peer communication. It may also optionally be stored on a mobile device 1614 that may be

Computer system 1600 also includes a communication interface 1618 coupled to bus 1602 . Communication interface 1618 provides bidirectional data communication that couples to network link 1620 that is connected to 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 may be a LAN card that provides a data communication connection to a compatible local area network (LAN). A wireless link may also be implemented. In any such implementation, communication interface 1618 transmits and receives electrical, electromagnetic, or optical signals carrying digital data streams representing various types of information.

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

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

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

Further, 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 utilize any computer readable medium, heretofore or to be known in the future. Examples of computer-readable media include primary storage devices (eg, any type of RAM) and secondary storage devices (eg, hard drives, floppy disks, CD ROMs, zip disks, tapes, magnetic storage devices, optical storage devices). devices, MEMs, nanotechnology-based storage devices, etc.), but are not limited thereto.

In the foregoing specification, embodiments of the present invention have been described with reference to numerous specific details, which may vary from implementation to implementation. As such, the exclusive and exclusive guidance as to what the invention is and what is intended by the applicant to be an invention, including any subsequent amendments, shall be provided, in the particular form in which the claims are issued, from such claims is a set of Any definitions expressly set forth herein for terms included in such claims will affect the meaning of those terms as used in those claims. Accordingly, no limitation, element, characteristic, specification, advantage, or attribute not expressly recited in a claim shall in any way limit the scope of such claim. Accordingly, the description and drawings are to be regarded in an illustrative rather than a restrictive sense.

Exemplary Metadata Vocabulary

<b>searchmonkey-profile vocabulary</b>

This manual will be released on a regular basis to improve conformance with industry standard vocabulary and to enable common use cases to be realized in a consistent manner. This manual, working closely with partners, will be refreshed approximately weekly during the alpha and beta period.

<b>Introduction to the searchmonkey-profile vocabulary</b>

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

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

&lt;?profile http://search.yahoo.com/searchmonkey-profile ?&gt;

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

The following sections describe individual vocabularies. Feel free to browse around the sections below, especially those that apply to your field. However, even with other examples, it can be helpful to at least skim through them to get a feel for how best to model your particular metadata.

A large table of possible values can be burdensome, so each section highlights specific characteristics to pay attention to, along with usage hints and examples.

<b>rel vocabulary</b>

The rel vocabulary defines the value to use for the rel attribute of an item. The naming convention for these attributes is that they always begin with the prefix rel: followed by a short word that expresses a person, place, thing, idea, or concept. Although they are not RDF classes in the official sense, in practice they are used in much the same way, so they share the convention of starting with the first capital, if prefixes are not taken into account.

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

What if there is no good match for the kind of item from which you want to extract metadata? Let's say you are extracting information about the Seattle garage band. No rel:SeattleGarageBand or rel:GarageBand or even rel:Band properties exist. The most applicable specific character present in the diagram, is rel:Organization, which you should use in this case. Additionally, it would be a good idea to request that new values be added to the vocabulary using the feedback email address in the manual.

To use this vocabulary in a feed or with RDFa/eRDF in a web page, you must map it as closely as possible to the item you identified as the class of item from this vocabulary. If you know about the 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 properties that are common in this category include foaf:knows and foaf:homepage.

<b>common rel</b>

rel:Agent for a person, institution, club, or "organs"

rel:Photo, rel:Image, rel:Video, rel:Audio for expressing embedded multimedia components

rel:Photoset, rel:Videoset for audio/video aggregation

rel:Thumbnail for audio or video where smaller thumbnails can be displayed

rel:Review to express review evaluation

A page with a whole bunch of something about it, for example a search results page or a rel:Cluster to represent a list of hotels in a city.

A specific reference is also the Task family of rel properties. These are intentionally defined in a fairly generic way, so let's pick the closest match to them. The following are just some of the more commonly used;

rel:Append to write a new review, comment on a blog, or in general to create new content for a page.

rel:CheckAvailability to perform a non-binding check of product or service availability

rel:Edit to edit the wiki page for the instance. For wiki sites, the rel:Edit attribute is particularly useful.

rel:Procure to order, bid, or reserve 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 bounds can be changed by review:best and review:worst.

<b>Encyclopedia/Reference/Info</b>

common rel

rel:Section to distinguish a specific section. Not all general sections, only noteworthy sections should be included

rel:Discussion to link to a separate discussion page

rel:History to link to a separate history page

<b>Business/Commercial/Directory</b>

common rel

rel:Listing to express the entire list

rel:Business to represent a real business (with street addresses, not lists).

rel:Neighborhood (usually with a dc: description child) to indicate a specific neighbor

<b>News/Events/Gossip</b>

common rel

rel:NewsItem

<b>Shopping/Commerce/Product page</b>

common rel

rel:Listing to express the entire list

rel:Product to represent the product itself (with shippingWeight and not a list)

rel:Specification

<b>Social Networking</b>

common rel

rel:Section to distinguish a specific section. Not all general sections, only noteworthy sections should be included

rel:Discussion to link to a separate discussion page

rel:History to link to a separate history page

rel:WorkExperience for career-related topics

rel:CurrentWorkExperience for your current position.

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

<b>Travel/Destination </b>

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 specific flights

rel:Map to link to a map of a region

rel:Discussion to link to a separate discussion page

rel:History to link to a separate history page

<b>characteristic vocabulary</b>

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 the existing vocabulary is widely used, certain important characteristics are defined in this profile. The following sections provide guidelines on which vocabulary to use. All properties are listed in the searchmonkey-profile lexical specification.

Scope as well as domain are associated with properties. A domain specifies what kind of item the property applies to. For example, media:width has meaning only for rel:Media entries; For example, it has no meaning if applied to rel:Person. The range specifies what kind of string value can be expected for this property. For example, the dc:date property must accept a date in a certain format, ie, YYYY-MM-DD, also known as ISO-8601 format.

<b>common characteristics</b>

dc:title for general titles

dc:date for common dates

dc:identifier This is often a URL, but can also be an ISBN or other identifier

dc:creator for creators of resources

dc:rights for copyright policy

dc:description for short, paragraph-length descriptions

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)

If you need to specifically call the last updated timestamp, atom:updated

As media:height and media:width for audio/video resources, it is good to specify the size in pixels with these properties.

geo:location for generally human readable locations such as "San Francisco" or "South Bay Area"

geo:point for a specific latitude/longitude (separated by spaces)

geo:floor for the number of floors in a building

finance:stockTickers for a list of related stock quotes (a semicolon-separated list accompanying the NY Times metadata).

<b>Business/Commercial/Directory</b>

Common characteristics

vcard:adr to represent street addresses as semicolon-separated parts

vcard:tel for phone number

vcard:url for website

Full commerce:vocabulary

<b>News/Events/Gossip </b>

Common characteristics

Full news:vocabulary

<b>Shopping/Commerce/Product </b>

Common characteristics

Full product:vocabulary

<b>Social Networking</b>

Common characteristics

<b>Travel/Destination</b>

Common characteristics

Full travel:^*vocabulary

<b>data type </b>

The data type vocabulary has two uses. Some properties, such as dc:identifier, can have many other possible values, i.e., a URL or an ISBN number. In this case, the range of this property is just "string", but if you want to explicitly specify that the value entered into it is more specific than the range would allow, you can specify the data type.

E.g:

<img file="KR101475552B1_D0001.tif" />

Another use of data types is disambiguation. Let's say you are extracting information about a photo and you have two different ways to represent the creator by username and URL. The data type separates other redundant dc:creator statements.

excuse:

<img file="KR101475552B1_D0002.tif" />

<b>When the trait you need isn't on the list</b>

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

For example, let's say your metadata is the number of megapixels a 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). Simply put, it should look like any other row in the feature diagram. Of course, the more formal RDF vocabulary definitions are much more extensive.

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

The actual definition occurs with xmlns:_prefix_attribute. If the prefix is digicam, the attribute is megapixels, the URL is http://example.com/vocab/digicam, the domain is rel:Product, and the range is decimal, a theoretical diagram entry would look like this:

<img file="KR101475552B1_D0003.tif" />

The declaration and use of prefixes would be as follows:

<img file="KR101475552B1_D0004.tif" />

<b>excuse</b>

<b>Encyclopedia/Reference/Info DataRss Example</b>

<img file="KR101475552B1_D0005.tif" />

<img file="KR101475552B1_D0006.tif" />

<b>Encyclopedia/Reference/Info RDFa Examples</b>

<img file="KR101475552B1_D0007.tif" />

<img file="KR101475552B1_D0008.tif" />

<img file="KR101475552B1_D0009.tif" />

<b>vocabulary chart</b>

When containing structured data, choose from the following object types:

<b>object diagram</b>

These are nouns; A recommended value to use for the rel attribute of items representing people, places, or things that may have additional metadata properties.

<img file="KR101475552B1_D0010.tif" />

<img file="KR101475552B1_D0011.tif" />

<img file="KR101475552B1_D0012.tif" />

<img file="KR101475552B1_D0013.tif" />

<b>characteristic diagram</b>

These are the recommended attribute values to use for attribute properties in the meta.

<img file="KR101475552B1_D0014.tif" />

<img file="KR101475552B1_D0015.tif" />

<img file="KR101475552B1_D0016.tif" />

<img file="KR101475552B1_D0017.tif" />

<img file="KR101475552B1_D0018.tif" />

<img file="KR101475552B1_D0019.tif" />

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

An empty value in the Domain column indicates that the enumerated property applies to all objects.

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

An empty value in the Range column indicates that the enumerated property can accept values in any format.

excuse:

essence

42

boolean

1

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 insignificant leading or trailing spaces, but inner spaces are important]

semicolon-list

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

nonempty

"OK"

<b>data type chart</b>

These are the recommended property values for use with meta datatypes.

<img file="KR101475552B1_D0020.tif" />

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

atom

Vocabulary for Atom Concepts &lt;http://www.w3.org/2005/Atom&gt;

cc

Creative Commons &lt;http://creativecommons.org/licenses/&gt;

dc

Dublin Core Metadata &lt;http://purl.org/dc/elements/1.1/&gt;

foaf

Friend-of-a-friend &lt;http://xmlns.com/foaf/0.1/&gt;

geo

Vocabulary for geographic metadata &lt;http://www.georss.org/georss&gt;

media

RSS-Media &lt;http://search.yahoo.com/mrss/&gt;

rdf

RDF &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#&gt;

rdfs

RDF Schema &lt;http://www.w3.org/2000/01/rdf-scherna#&gt;

review

RDF review &lt;http://www.purl.org/stuff/rev#&gt;

vcal

RDF calendar &lt;http://www.w3.org/2002/12/cal#&gt;

vcard

vcard &lt;http://www.w3.org/2006/vcard/ns&gt;

...and...

rel

Object-related vocabulary &lt;http://search.yahoo.com/searchmonkey-relation/&gt;

...and...

assert

Vocabulary for error detection and flagging in metadata &lt;http://search.yahoo.com/searchmonkey/assert/&gt;

commerce

Vocabulary for commerce-related metadata &lt;http://search.yahoo.com/searchmonkey/commerce/&gt;

context

Vocabulary for temporal contextual information

&lt;http://search.yahoo.com/searchmonkey/context/&gt;

finance

Vocabulary for Financial Metadata

&lt;http://search.yahoo.com/searchmonkey/finance/&gt;

job

Vocabulary for job-related metadata

&lt;http://search.yahoo.com/searchmonkey/job/&gt;

news

Vocabulary for News Metadata

&lt;http://search.yahoo.com/searchmonkey/news/&gt;

product

Vocabulary for product-related metadata

&lt;http://search.yahoo.com/searchmonlcey/product/&gt;

reference

Vocabulary for references and links

&lt;http://search.yahoo.com/searchmonkey/reference/&gt;

social

Vocabulary for social graph access and information

&lt;http://search.yahoo.com/searchmonkeysocial/&gt;

tagspace

Vocabulary for tagsets &lt;http://search.yahoo.com/searchmonkey/tagspace/&gt;

...and...

country

Data type used to indicate a specific country

&lt;http://search.yahoo.com/searchmonkey-datatype/country/&gt;

currency

Data type used to indicate a specific currency

&lt;http://search.yahoo.com/searchmonkey-datatype/currency/&gt;

use

The data type used to differentiate the use of the attribute.

&lt;http://search.yahoo.com/searchmonkey-datatype/use/&gt;