as) United States
`a2) Patent Application Publication 0) Pub. No.: US 2007/0016575 Al
`(43) Pub. Date: Jan. 18, 2007
`
`Hurst-Hiller et al.
`
`US 20070016575A1
`
`(54)
`
`(75)
`
`CONSOLIDATING LOCAL AND REMOTE
`TAXONOMIES
`
`Inventors: Oliver Hurst-Hiller, Redmond, WA
`(US); Michael I. Torres, Seattle, WA
`(US); Jane T. Kim, Seattle, WA (US)
`
`Correspondence Address:
`AMIN. TUROCY & CALVIN, LLP
`24TH FLOOR, NATIONAL CITY CENTER
`1900 EAST NINTH STREET
`CLEVELAND, OH 44114 (US)
`
`(73)
`
`Assignee: Microsoft Corporation, Redmond, WA
`(US)
`
`(21)
`
`Appl. No.:
`
`11/300,804
`
`(22)
`
`Filed:
`
`Dec. 14, 2005
`
`Related U.S. Application Data
`
`(60)
`
`Provisional application No. 60/699,282, filed on Jul.
`14, 2005.
`
`Publication Classification
`
`(51)
`
`Int. CL
`(2006.01)
`7/00
`GO6F
`(2006.01)
`G06F 170
`(52) U.S. C1.
`eccccsssesssssseeestereee 707/5; 707/7; 707/100
`
`(57)
`
`ABSTRACT
`
`A tag management system that enables consolidation, aggre-
`gation and/or synchronization of tags between local and
`remote sources. Further, the system provides users with a
`single rich view of client and Internet data related to
`appropriate tagging schemes. The system allows users to
`import and export tags and taxonomies from online service
`providers and provides a central location for users to store
`their tags. The central location is accessible to the user both
`on the client and for use online.
`
`
`
`as 100
`
`106
`
`EXTERNAL SOURCES
`
`TAG LOCATOR
`
`TAG MANAGER
`
`102
`
`104
`
`LOCALDATA STORE(S)
`
`SAMSUNG 1036
`
`SAMSUNG 1036
`
`1
`
`

`

`Patent Application Publication Jan. 18,2007 Sheet 1 of 17
`
`US 2007/0016575 Al
`
`x 100
`
`EXTERNAL SOURCES
`
`106
`
`108
`
`TAG LOCATOR
`
`TAG MANAGER
`
`102
`
`104
`
`LOCAL DATA STORE(S)
`
`FIG. 1
`
`2
`
`

`

`Patent Application Publication Jan. 18,2007 Sheet 2 of 17
`
`US 2007/0016575 Al
`
`wo 100
`
`EXTERNAL SOURCES
`
`106
`
`TAG LOCATOR COMPONENT
`202
`
`102
`
`QUERY
`COMPONENT
`
`SEARCH
`COMPONENT
`
`TAG MANAGER
`
`
`
`LOCAL DATA STORE(S)
`
`FIG. 2
`
`3
`
`

`

`Patent Application Publication Jan. 18,2007 Sheet 3 of 17
`
`US 2007/0016575 Al
`
`
`
`EXTERNAL SOURCES
`
`x 100
`
`106
`
`TAG LOCATOR
`COMPONENT
`
`TAG MANAGER COMPONENT
`302
`
`104
`
`
`
`
`
`
`
`
`
`ANALYZER
`
`COMPONENT
`
`
`
`
`CONSOLIDATION
`COMPONENT
`
`LOCAL DATA STORE(S)
`
`FIG.3
`
`4
`
`

`

`Patent Application Publication Jan. 18,2007 Sheet 4 of 17
`
`US 2007/0016575 Al
`
`yx 100
`
`106
`
`
`
`406
`
`EXTERNAL SOURCES
`
`408
`
`
`EXTERNAL
`STOREn
`
`SOURCE,
`
`EXTERNAL
`
`
`
`
`
`TAG LOCATOR
`COMPONENT
`
`
`TAG MANAGER COMPONENT
`
`
`CONSOLIDATION
`
`COMPONENT
`AGGREGATION
`COMPONENT
`
`ANALYZER
`COMPONENT
`
`LOCAL DATA STORE(S)
`
`FIG. 4
`
`5
`
`

`

`Patent Application Publication Jan. 18,2007 Sheet 5 of 17
`
`US 2007/0016575 Al
`
`y~ 100
`
`106
`
`
`
`
`406
`
`EXTERNAL SOURCES
`
`
`408
`
`
`
`
`
`
`
`EXTERNAL
`
`EXTERNAL
`
`STOREn
`
`SOURCE, TAG LOCATOR
`
`COMPONENT
`
`
`
`TAG MANAGER COMPONENT
`
`402
`
` ANALYZER
`
`
`
`
`COMPONENT
`
`AGGREGATION
`COMPONENT
`
`502:
`
`
`
`SYNCHRONIZE
`COMPONENT
`
`
`
`
`TAG IMPORT
`COMPONENT
`
`
`TAG EXPORT
`COMPONENT
`
`
`LOCAL DATA STORE(S)
`
`—
`
`FIG. 5
`
`6
`
`

`

`Patent Application Publication Jan. 18,2007 Sheet 6 of 17
`
`US 2007/0016575 Al
`
`106 yx600
`
`
`
` 406
`EXTERNAL SOURCES
`40
`
`EXTERNAL
`SOURCE,
`
`EXTERNAL
`STOREn
`
`TAG LOCATOR COMPONENT
`
`202
`
`204
`
`QUERY
`COMPONENT
`
`SEARCH
`COMPONENT
`
`
`
`
`TAG MANAGER COMPONENT
`
`
`
`
`
`302
`
`402
`
`404
`
`
`
`ANALYZER
`COMPONENT
`
`
`
`
`
`AGGREGATION
`COMPONENT
`
`
`
`
`
`SYNCHRONIZE
`COMPONENT
`
`
`
`502
`
`504
`
`TAG IMPORT
`COMPONENT
`
`
`
`TAG EXPORT
`COMPONENT
`
` RENDERING
`COMPONENT
`
`602
`
`LOCAL DATA STORE(S)
`
`FIG. 6
`
`7
`
`

`

`Patent Application Publication Jan. 18,2007 Sheet 7 of 17
`
`US 2007/0016575 Al
`
`DESKTOP
`
`http://www.abc.com
`704
`
`CLICK HERE TO ADD
`ABC TAG SEARCH TO
`DESKTOP
`
`http:/Awww.def.com
`704
`CLICK HERE TO ADD
`DEF TAG SEARCH TO
`DESKTOP
`
`http://www.ghi.com
`a 704
`CLICK HERE TO ADD
`GHI TAG SEARCH TO
`
`
` 708
`Hawaii vacation
`( SEARCH}
`
`a 706
`
`Desktop Search Results
`
`Resultst- 40 of 462 fortag: “hawaii vacation”
`Show more results from this source
`
`
`
`
`
`
`
`
`
`
` Show more results from this source
`
`
`
`
`Show more results from this source
`
`716
`
`
`
`FIG. 7
`
`8
`
`

`

`Patent Application Publication Jan. 18,2007 Sheet 8 of 17
`
`US 2007/0016575 Al
`
`http://www.abc.com
`
`CLICK HERE TO ADD
`ABC TAG SEARCH TO
`
`www.abc.com/autoshow...
`Updated 5/27/05at 3:05pm
`
`802 oN ae
`
`DESKTOP EXPLORER
`
`
`- af
`
`
`
`Show more results from this
`SOUrCe
`
`FIG. 8
`
`9
`
`

`

`Patent Application Publication Jan. 18,2007 Sheet 9 of 17
`
`US 2007/0016575 Al
`
`900f
`
`902
`
`904
`
`906
`
`DEFINE SEARCH
`PARAMETERS
`
`SEARCH
`
`
`
`
`
`SEARCH? END
`
`
`
`RENDER SEARCH
`RESULTS
`
`908
`
`CONTINUE
`
`10
`
`

`

`Patent Application Publication Jan. 18,2007 Sheet 10 of 17
`
`US 2007/0016575 Al
`
`1000f
`
`1002
`
`1004
`
`1006
`
`CONTACT SOURCE OR
`SERVICE
`
`IMPORT TAGS
`
`SELECT TAGS
`
`FIG. 10
`
`11
`
`

`

`Patent Application Publication Jan. 18,2007 Sheet 11 of 17
`
`US 2007/0016575 Al
`
`o 1100
`
`1102
`
`71102
`file
`
`1106
`1108
`1108
`Co
`fit
`
`
`
`PUBLIC TAGS
`e XXX
`* YYY YYY
`© ZZZZ7ZZ
`
`
`
`
`
`
`PRIVATE TAGS
`e XXX
`* YYY YYY
`© ZZZ2ZZ
`
`
`
`
`
`|
`
`
`
`
`
`PRIVATE TAGS
`oe XXX
`* YYY YYY
`© ZZZZ72
`
`
`
`CLIENT
`
`
`
`« Export your tags
`¢ Export the 100 most popular
`public tags
`¢ Import your tags
`
`« Export your tags
`e Import your tags
`
`
`f 1112
`
`
`
`
`PRIVATE TAG
`PUBLIC TAG
`
`
`TABLE
`TABLE
`
`
`e XXX
`© XXX
`
`
`
`° YYY YYY
`° YYY YYY
`
`
`e ZZZZZZ
`© ZZZZ2Z2
`
`
`e AAA
`« AAA
`
`
`* BBB BBB
`° BBB BBB
`
`
`
`¢ CCCCCC
`e CCCCCC
`« XYZ XY
`© XYZ XY
`
`
`
`* XYZ XY
`°e XYZ XY
`
`
`
`eo XXX
`© XXX
`
`
`
`eYYY YYY
`© YYYYYY
`
`
`© ZZZ72Z2
`© ZZZZZZ
`
`
`e AAA
`e AAA
`
`
`
`
`
`FIG. 11
`
`12
`
`12
`
`

`

`Patent Application Publication Jan. 18,2007 Sheet 12 of 17
`
`US 2007/0016575 Al
`
`x 1200
`
`
`
`TAG CONTROLLER
`
`
`
`
`
`
`
`ALL TAGS
`TAG STORE:
`
`
`[TAG BROWSER:| XY
`
`COPY
`
`COPY & PASTE
`
`XY
`XYYX
`XY HH
`XYYY YW
`XYABC
`XYXYXYXY
`
`FIG. 12
`
`13
`
`13
`
`

`

`Patent Application Publication Jan. 18,2007 Sheet 13 of 17
`
`US 2007/0016575 Al
`
`
`
`1102
`(1102
`1102 \
`1102
`
`List of public GHI tags
`List of public ABC tags
`List of private ABC
`List of DEF tags
`
`XXX
`tags
`XXX
`XXX
`
`
`yyy yyy
`XXX
`yyy yyy
`yyy yyy
`
`
`
`Z222ZZ
`yyy yyy
`2ZZZZZ
`ZZzzzz
`aaa
`22Zz2zz
`aaa
`aaa
`
`
`
`bbb bbb
`aaa
`bbb bbb
`bbb bbb
`
`
`
`eccccc
`bbb bbb
`ccecec
`ececec
`
`
`
`xyz xy
`ceccee
`xyz xy
`xyz xy
`
`
`
`xyz xy
`xyz xy
`xyz xy
`xyz xy
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`http/Avww def.com
`http/Avww abc.com
`
`
`DEE Export your ABC tags Ex
`Export your GHI tags
`
`
`
`Export the 100 most popular
`Export the 100 most popular
`
`
`
`ABC public tags
`
`
` Import your tags
`
`
`Import your tags
`
`httpa/Avww ghi-com
`
`
`
`Client Computer
`Tag Controller
`
`Alltags_
`
`Tag browset
`
` Copy& Paste
`
`
`clientfile
`
`
`
`
`
`
`
`<>
`
`
`system
`So 1302
`Internet Explorer
`
`
`
`
`
`
`
`_ C) O O O[Www abc.comautoshow.
`
`
`List of private
`List of tags downloade
`Client -only tags
`from service providers
`XXX
`XXX
`yyy yyy
`yyy yyy
`zz2zzzz
`zzzzzz
`aaa
`aaa
`bbb bbb
`bbb bbb
`ccccee
`ececce
`xyz xy
`xyz xy
`xyz xy
`xyz xy
`XXX
`XXX
`yyy yyy
`yyy yyy
`zzzz72
`222772
`aaa
`aaa
`bbb bbb
`bbb bbb
`cecece
`cecece
`xyz xy
`xyz xy
`xyz xy
`xyz xy
`XXX
`XXX
`yyy yyy
`yyy yyy
`2Z2ZZzZ
`zzzzzz
`aaa
`aaa
`bbb bbb
`bbb bbb
`ececec
`cecece
`xyz xy
`xyz xy
`
`
`
`
`
`:
`Tags applied to Internet
`Content
`
`
`
`FIG. 13
`
`14
`
`14
`
`

`

`
`
`
`TAG LOCATOR COMPONENT
`
`202
`
`QUERY
`COMPONENT
`
`204
`
`SEARCH
`COMPONENT
`
`
`
`
`
`Patent Application Publication Jan. 18,2007 Sheet 14 of 17
`
`US 2007/0016575 Al
`
`106
`
`a 1400
`
`406
`
`
`
`EXTERNAL SOURCES
`
`406
`
`EXTERNAL
`STOREn
`
`
`
`5408
`
`EXTERNAL
`
`SOURCE,
`
`
`
`
`
`
`
`102
`
`
`
`
`TAG MANAGER COMPONENT
`402 404
`
`
`COMPONENT SYNCHRONIZE
`
`
`
`
`RULES-BASED
`LOGIC
`COMPONENT
`
`1402
`
`
`
`ANALYZER
`COMPONENT
`
`
`COMPONENT
`
`504
`
`AGGREGATION
`
`TAG IMPORT
`COMPONENT
`
`TAG EXPORT
`COMPONENT
`
` RENDERING
`
`
`COMPONENT
`
`
`LOCAL DATA STORE(S)
`
`602
`
`FIG. 14
`
`15
`
`15
`
`

`

`Patent Application Publication Jan. 18,2007 Sheet 15 of 17
`
`US 2007/0016575 Al
`
`106 x 1500
`
`
`
`
`406
`406
`EXTERNAL SOURCES
`
`EXTERNAL
`408[
`SOURCE,
`
`
`
`EXTERNAL
`
`202
`
`204
`
`QUERY
`COMPONENT
`
`SEARCH
`COMPONENT
`
`ARTIFICIAL
`INTELLIGENCE
`COMPONENT
`
`STORE TAG LOCATOR COMPONENT
`
`TAG MANAGER COMPONENT
`
`
`
`
`402
`
`404
`
`ANALYZER
`COMPONENT
`
`AGGREGATION
`COMPONENT
`
`SYNCHRONIZE
`COMPONENT
`
`504
`
`
`
`TAG IMPORT
`TAG EXPORT
`
`COMPONENT
`COMPONENT
`
`
` RENDERING
`COMPONENT
`
`
`
`LOCAL DATA STORE(S)
`
`602
`
`FIG. 15
`
`16
`
`16
`
`

`

`Patent Application Publication Jan. 18,2007 Sheet 16 of 17
`
`US 2007/0016575 Al
`
`1602
`
`y— 1600
`
`|
`EXTERNAL
`|
`“— HDD_ — 7
`
`1644
`
`
`OPTICAL
`DRIVE
` 1638
`
`VIDEO
`
`ADAPTOR
`
`1640
`
`1630
`| OPERATING SYSTEM |
`PROCESSING
`A7162
`1608
`1 “APPLICATIONS" 4
`__[1634
`MODULES
`|
`oo£-1636
`DATA
`\
`wee ee em em me ee HHH eH
`
`
`
`
`1642 WIRED/WIRELESS)
`
`INPUT
`
`DEVICE
`
`
`INTERFACE
`REMOTE
`
`
`COMPUTER(S)
`
` 1650
`NETWORK
` (WIRED/WIRELESS)
`ADAPTOR
`
`MEMORY/
`
`STORAGE
`
`FIG. 16
`
`17
`
`17
`
`

`

`Patent Application Publication Jan. 18,2007 Sheet 17 of 17
`
`US 2007/0016575 Al
`
`ras 1700
`
`CLIENT(S)
`
`SERVER(S)
`
`FRAMEWORK
`
`COMMUNICATION
`
`CLIENT DATA STORE(S)
`
`SERVER DATA STORE(S)
`
`FIG. 17
`
`18
`
`18
`
`

`

`US 2007/0016575 Al
`
`Jan. 18, 2007
`
`CONSOLIDATING LOCAL AND REMOTE
`TAXONOMIES
`
`CROSS-REFERENCE TO RELATED
`APPLICATIONS
`
`[0001] This application claims the benefit of U.S. Provi-
`sional Patent application Ser. No. 60/699,282 entitled
`“ENABLING CLIENT-BASED TAGGING OF INTER-
`NET CONTENT AND VIEWING OF TAGGED INTER-
`
`NET CONTENT”andfiled Jul. 14, 2005. The entirety of the
`above-noted application is incorporated by reference herein.
`
`BACKGROUND
`
`[0002] The amount of data available to information seek-
`ers has grown astronomically, whether as the result of the
`proliferation of information sources on the Internet, or
`because of private efforts to organize business information
`within a company,or any of a variety of other causes. As the
`amountof available data grows, so does the need to be able
`to categorize or label that data so that the data can be more
`efficiently searched. One approachis to use tagging for this
`task.
`
`[0003] Tagging is the processing of adding or attaching
`metadata such as descriptive attributesto a data object. A tag
`can be thought of as a category name. Asusedherein, a data
`object can be any type of data (e.g., a website, a text file, an
`image). Typically, the data object content is unchanged by
`the application of a tag. Operating systems, search mecha-
`nismsandfiltering mechanisms may utilize tags to organize,
`sort or filter data objects. A taxonomy or system ofclassi-
`fication can be defined by a set of tags.
`
`[0004] Tagging has becomeprevalent on the Internet as a
`means for organizing, and identifying relevant websites,
`articles and other data objects. Internet services allow users
`to apply tags to websites, photographic images, articles and
`the like. Tagging provides users with the ability to classify
`data objects both for their own use and for use by others.
`Popular web sites such image sharing applications allow
`users to tag and share photographic images and websites
`with communities of users.
`
`[0005] Tagging is also useful within the context of a single
`client and allows the user to organize data withinthe client.
`For example, a user maystore a collection of photographic
`images on the client. As such, the user may apply the tag
`“vacation” to photographs taken while on holiday and
`“graduation” to photographs graduation ceremony. Bysort-
`ing the photographs utilizing the tags, the user is able to
`retrieve the appropriate photographs quickly andefficiently
`without having to view irrelevant and/or unwanted photo-
`graphs.
`
`In general, a user may use one or more taxonomies
`[0006]
`for various websites or web services and a separate tax-
`onomy or taxonomies for a client computer. However,
`utilizing separate taxonomies makesit difficult for the user
`to maintain consistent organization of relevant data objects.
`Slight variations in tag names may result in users being
`unable to locate relevant information. For example, a user
`may apply the tag “vacation” to data objects stored on the
`client computer. Similar, relevant data objects can be tagged
`“vacation_Paris” or “vacation__2005” in a taxonomy on an
`Internet service. A search on the Internet service for those
`
`similar data objects utilizing the user’s “vacation” tag will
`mostlikely fail to locate those relevant data objects.
`
`In addition, inconsistent taxonomies make it more
`[0007]
`difficult to share data objects and a data object with a unique
`tag is less likely to be found by other users. A data object
`with tags that are consistent with the taxonomy used by an
`Internet service or a group is much morelikely to be located
`and used by other users than a data object with uniquetags.
`Moreover, a given taxonomy can become more valuable as
`more data objects are tagged within the given taxonomy. As
`the numberof participants utilizing taxonomy increases, the
`volume and variety of the data objects retrievable using that
`taxonomytendto increase.
`
`[0008] Conventional computer systems require a user to
`run separate searches to retrieve data objects from Internet
`services and from the client computer and other local data
`storage, even if the userutilizes identical taxonomies on the
`client computer and on Internet services. Consequently,
`users may have to run multiple searches to locate data
`objects from various data sources. In addition, the user may
`forget to search a relevant data source and, therefore, fail to
`locate pertinent data objects.
`
`SUMMARY
`
`[0009] The following presents a simplified summary of
`one or more embodiments of a data management system in
`order to provide a basic understanding of some aspects of
`such embodiments. This summary is not an extensive over-
`view, and is intended to neither identify key or critical
`elements of the embodiments nor delineate the scope of such
`embodiments. Its sole purpose is to present some concepts
`of the described embodiments in a simplified form as a
`prelude to the more detailed description that is presented
`later.
`
`[0010] The data management system and/or methods as
`described herein, in one aspect thereof, provides for man-
`aging, sorting and/orfiltering data objects. The data man-
`agement system can include a rich viewing mechanism that
`provides an aggregated view of data objects retrieved from
`external sources and client data sources.
`
`the data management system
`In another aspect,
`[0011]
`mayalso include a tag management system that allows users
`the ability to import and export tags and taxonomies from
`external data sources and servicesto a tag table onthe client
`computer and vice versa. The tag table can provide a
`mechanism that enables users to utilize the sameset of tags
`for local data objects as well as data objects available from
`external data sources and/or services. In addition, the data
`management system can includea user interface system that
`enables users to apply tags from the tag table to local data
`objects and/or data objects available from external data
`sources and services.
`
`Still another aspect employs rules-based logic to
`{0012]
`predetermine and/or preset one or more thresholds in accor-
`dance with the novel functionality of the innovation. In yet
`another aspect thereof, an artificial intelligence component
`is provided that employs a probabilistic and/or statistical-
`based analysis to prognose or infer an action that a user
`desires to be automatically performed.
`
`To the accomplishmentofthe foregoing and related
`[0013]
`ends, certain illustrative aspects of the innovation are
`
`19
`
`19
`
`

`

`US 2007/0016575 Al
`
`Jan. 18, 2007
`
`described herein in connection with the following descrip-
`tion and the annexed drawings. These aspects are indicative,
`however, of but a few of the various ways in which the
`principles of the innovation can be employed andthe subject
`innovation is intended to include all such aspects and their
`equivalents. Other advantages and novel features of the
`innovation will become apparent from the following detailed
`description of the innovation when considered in conjunc-
`tion with the drawings. The following description and the
`annexed drawings set forth in detail certain illustrative
`aspects of the one or more embodiments of the novel
`functionality of the innovation.
`
`FIG. 16 illustrates a computing environment for a
`[0029]
`data management system.
`
`FIG. 17 illustrates an operational environment for
`[0030]
`a data management system.
`
`DETAILED DESCRIPTION
`
`[0031] The innovation is now described with reference to
`the drawings, wherein like reference numerals are used to
`refer to like elements throughout. In the following descrip-
`tion, for purposes of explanation, numerousspecific details
`are set forth in order to provide a thorough understanding of
`the subject innovation. It can be evident, however, that the
`innovation can be practiced without these specific details. In
`other instances, well-known structures and devices are
`[0014] FIG.1illustrates an embodiment of a system that
`shown in block diagram form in orderto facilitate describing
`facilitates consolidating local and remote taxonomies in
`the innovation.
`accordance with an aspect of the innovation.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`FIG.2 illustrates an embodiment of a system that
`[0015]
`employs a query component and a search component to
`locate data related to a taxonomy.
`
`[0016] FIG. 3 illustrates an architectural diagram of a
`system that facilitates analyzing and consolidating taxono-
`mies in accordance with an aspect of the novel subject
`matter.
`
`FIG.4 illustrates a block diagram of a system that
`[0017]
`facilitates aggregating and/or synchronizing taxonomies in
`accordance with an aspect of the innovation.
`
`[0018] FIG. 5 illustrates an architectural diagram of a
`system that facilitates importing and exporting taxonomies
`in accordance with an aspect of the innovation.
`
`FIG.6 illustrates an exemplary block diagram of a
`[0019]
`system that facilitates rendering local and external data in
`accordance with consolidated taxonomies.
`
`[0020] FIG. 7 illustrates a further embodiment of a user
`interface for a system for viewing aggregated data objects.
`
`Asusedin this application, the terms “component”
`[0032]
`and “system” are intended to refer to a computer-related
`entity, either hardware, a combination of hardware and
`software, software, or software in execution. For example, a
`component can be, but is not limited to being, a process
`running on a processor, a processor, an object, an executable,
`a thread of execution, a program, and/or a computer. By way
`of illustration, both an application running on a server and
`the server can be a component. One or more components can
`reside within a process and/or thread of execution, and a
`component can be localized on one computer and/or dis-
`tributed between two or more computers.
`
`[0033] As used herein, the term to “infer” or “inference”
`refer generally to the process of reasoning aboutor inferring
`states of the system, environment, and/or user from a set of
`observations as captured via events and/or data. Inference
`can be employed to identify a specific context or action, or
`can generate a probability distribution over states,
`for
`example. The inference can be probabilistic-that
`is,
`the
`computation of a probability distribution over states of
`interest based on a consideration of data and events. Infer-
`
`ence can also refer to techniques employed for composing
`[0021] FIG.8illustrates an exemplary user interface that
`higher-level events from a set of events and/or data. Such
`generates a rich view of a standing query in accordance with
`inference results in the construction of new events or actions
`an aspect of the innovation.
`from a set of observed events and/or stored event data,
`whether or not the events are correlated in close temporal
`proximity, and whether the events and data come from one
`or several event and data sources.
`
`FIG.9 illustrates a method for performing periodic
`[0022]
`searches in accordance with an aspect.
`
`[0023] FIG. 10 illustrates an exemplary method for
`importing tags from an external data source or service.
`
`[0024] FIG. 11 illustrates a tag management system for
`importing tags from an external data source or service in
`accordance with an aspect of the innovation.
`
`[0025] FIG. 12 illustrates an embodimentofa user inter-
`face for tag management.
`
`[0026] FIG. 13 illustrates an embodiment of a tag man-
`agement system in accordance with an aspect of the inno-
`vation.
`
`[0027] FIG. 14 illustrates an exemplary architectural block
`diagram of a system that employs a rules-based logic
`component in accordance with tag management.
`
`[0028] FIG. 15 illustrates an exemplary architectural block
`diagram of a system that employs an artificial intelligence
`component in accordance with tag management.
`
`[0034] While certain ways of displaying information to
`users are shown anddescribed with respect to certain figures
`as screenshots, those skilled in the relevantart will recognize
`that various other alternatives can be employed. The terms
`“screen,’““web page,” and “page” are generally used inter-
`changeably herein. The pages or screens are stored and/or
`transmitted as display descriptions, as graphical user inter-
`faces, or by other methods of depicting information on a
`screen (whether personal computer, PDA, mobile telephone,
`or other suitable device, for example) where the layout and
`information or content to be displayed on the page is stored
`in memory, database, or another storage facility.
`
`[0035] Referring initially to the drawings, FIG. 1 illus-
`trates a system 100 that facilitates rich tagging of content via
`disparate sources. Generally, system 100 can include a tag
`locator component 102 and a tag manager component 104.
`In one aspect, the system 100 can facilitate integration of
`
`20
`
`20
`
`

`

`US 2007/0016575 Al
`
`Jan. 18, 2007
`
`tagged content from external sources 106 with tagged con-
`tent from internal or local sources 108. Moreparticularly, the
`system 100 can enable integration with tagged external
`sources 106 (e.g., Internet). It will be appreciated thatthis is
`especially compelling since tagging is oftentimes very much
`a critical mass mechanism, both in terms of breadth of data
`stores and the number of participants (e.g.,
`for public
`community tagging, folksonomies).
`
`[0036] The system illustrated in FIG. 1 can facilitate
`client-based functionalities by enabling external source
`(e.g., 106) tagging via a client or other remote device. In
`doing so, the tag locator component 102 and the tag manager
`component 104 can facilitate searching (e.g., querying)
`external services (e.g., Internet, remote data stores) thereaf-
`ter integrating located data into rich data views. Addition-
`ally, these components (102, 104) can facilitate roaming and
`synchronizing user tags (e.g.,
`local tags) with tags from
`external sources 106. It is to be understood and appreciated
`that the novel functionality described herein can be applied
`to any operating system, search mechanism, toolbar or the
`like without departing from the spirit and scope described
`herein.
`
`In operation, the tag locator component 102 can be
`[0037]
`employed to locate (e.g., search, query) for existing tags
`both from external sources 106 (e.g., Internet, Intranet,
`user-specific cloud, external server) and from device-based
`(e.g., client-based) data stores 108. Accordingly,
`the tag
`manager component 104 can be employed to consolidate,
`synchronize, render, and display all or a subset of located
`tags and/or data related thereto. By way of example, the tag
`manager component 104 can be utilized to consolidate all
`tags associated to a particular user or content type. These
`consolidated tags can be placed into an aggregated list or
`“sandbox” which can be accessed with respect to tagging
`content. One particular advantage of this approach is the
`ability to effectuate constancy with respect
`to tags that
`correspond to a particular type of content.
`
`[0038] Referring now to FIG. 2, an alternative block
`diagram of system 100 that facilitates locating and managing
`tags in accordance with an aspectof the innovation is shown.
`As described with reference to FIG. 1, the system 100 can
`include a tag locator component 102 and a tag manager
`component 104. These components (102, 104) can facilitate
`obtaining, organizing and rendering tags from disparate
`locations (e.g., external sources 106 and local data stores
`108).
`
`[0039] Turning now to a discussion of the tag locator
`component 102, this component can include a query com-
`ponent 202 and a search component 204. The query com-
`ponent 202 can facilitate a specific query or look-up oftags.
`In one example, a query can be generatedto locate tags that
`correspond to a specific user. In another aspect, the query
`can be established to locate tags that contain a specific
`keyword, group of keywords, or part of a keyword. Instill
`another example, the query component 202 can be employed
`to locate tags that correspond to a specific data type (e.g.,
`photos, music).
`
`applied to an endless numberof scenarios, each of which is
`to be included within spirit and scope of this disclosure and
`claims appendedhereto.
`
`In one example, a user can define query criteria
`[0041]
`based upon a specific utility and/or preference. In another
`example,
`the system can automatically define the query
`based upon a predefined rule or set of rules as well as an
`inferred intention. These rules-based and artificial intelli-
`
`gence (AI) query generation mechanisms will be described
`in detail infra with respect to FIGS. 14 and 15. As will be
`described with reference to FIGS. 14 and 15, these features
`can facilitate automatic generation of query criterion.
`
`[0042] Once a query has been defined via the query
`component 202, the search component 204 can be employed
`to implement the query. As shown, the search component
`204 can be employed to locate tags in an external source 106
`and/or an internal or local data store 108. As described with
`
`reference to the query component 202, rules-based logic
`and/or AI mechanisms can be utilized to infer a location or
`group of locations for which to search.
`
`FIG.3 illustrates yet another architectural diagram
`[0043]
`of system 100 that facilitates managing tags from a number
`of disparate sources (e.g., 106, 108) in accordance with an
`aspect of the innovation. More particularly, tag manager
`component 104 can include an analyzer component 302 and
`a consolidation component 304. Each of these components
`will be described in detail below.
`
`[0044] Additionally, although the tag manager component
`104 is
`illustrated with particular components included
`therein, it will be appreciated that other aspects of the tag
`manager component 104 can include a subset of these
`components. Moreover, additional components can be
`included within the tag manager component 104 and can
`particularly enhance functionality thereof. These additional
`aspects of the tag manager component 104 will be described
`in detail below.
`
`In accordance with the aspect of FIG.3, once a tag
`[0045]
`or group oftags is located via the tag locator component 102,
`the analyzer component 302 can be employed to examine
`the obtained tags. For example, the analyzer component 302
`can compare eachofthe retrieved tags to each other as well
`as to tags maintained within a user space (e.g., sandbox). In
`a specific example, the analyzer component 302 can com-
`pare tags relating to a specific data type.
`
`[0046] Accordingly, the consolidation component 304 can
`be employed to aggregate and/or synchronize tags between
`local and external sources (e.g., 108, 106). In aspects, this
`consolidation can include an aggregation ofall tags related
`to a user and/or type of content (e.g., photos). Additionally,
`the consolidation component 304 can be employed to syn-
`chronize tags between disparate sources. By way of
`example, the consolidation component 304 can be employed
`to synchronize tags between a user space on the Internet
`(e.g., user cloud related to external source 106) and an
`internal data store 108. This example will be better under-
`stood with reference to FIG. 4.
`
`It is to be understood that an unlimited number of
`[0040]
`additional query options exist. These alternative aspects are
`to be included within this scope of this disclosure and claims
`appended hereto. In other words, it is understood that the
`novel concepts and functionality described herein can be
`
`FIG.4 illustrates an alternative architectural block
`[0047]
`diagram of system 100 in accordance with an aspect of the
`innovation. As shown, the tag manager component 104 can
`include an analyzer component 302, an aggregation com-
`ponent 402 and a synchronization component 404. As
`
`21
`
`21
`
`

`

`US 2007/0016575 Al
`
`Jan. 18, 2007
`
`the system 100 can
`described with reference to FIG. 3,
`aggregate and synchronize tags in accordance with a pre-
`defined and/or inferred criterion. The aggregation compo-
`nent 402 and synchronization component 404 can effectuate
`these actions upon the tags.
`
`cally exported to appropriate locations within external
`sources 106. The query functionality of the tag locator
`component 102 can be employed to locate appropriate
`locations and/or data to tag with this new locally established
`tag.
`
`[0048] Also illustrated in FIG. 4 is an external sources
`component 106 that can include 1
`to N external stores,
`where N is an integer. These 1 to N external stores can be
`referred to individually or collectively as external stores 406.
`In one example, an external store 406 can be representative
`of the Internet as a whole or a specific location therein. In
`another example, an external store 406 can include a remote
`server and/or database.
`
`Ina more specific example, consider an external
`[0049]
`service such as an online photo managementsharing appli-
`cation. In this example, a user can define a query (e.g., via
`type, keyword) and thereafter employ the tag locator com-
`ponent 102 to facilitate obtaining tags from the application.
`These tags can include public as well as private tags (e.g.,
`those contained within a user cloud 408) associated with the
`application. Once obtained, the analyzer component 302 can
`be employed to work in conjunction with the aggregation
`component 402 and/or the synchronize component 404 to
`manage the tags.
`
`[0050] Continuing with the example, the aggregation com-
`ponent 402 can combine the obtained tags to those main-
`tainedlocally (e.g., local data store(s) 108). Additionally, the
`synchronize component 404 can compare the obtained tags
`to those maintained locally thereafter generating a synchro-
`nized set of tags. This synchronized set of tags can be
`communicated to both the external sources 106 as well as to
`the local data store 108 thus harmonizingthe local tags with
`remote tags.
`
`FIG.5 illustrates a system 100 that facilitates a tag
`[0051]
`import component 502 and a tag export component 504 in
`accordance with an aspect of the innovation. In operation,
`the tag import component 502 can facilitate importing tags
`from external sources 106 into local data stores 108. This tag
`import component 502 can work together with the tag
`locator component 102 to locate tags specific to a user, data
`type, etc. thereafter automatically importing the tag infor-
`mation into the local data stores(s) 108. It will further be
`appreciated that this tag import component 502 can dynami-
`cally import tags that fall within a predefined and/or inferred
`category.
`
`[0052] By way of example, a standing query can be put
`into place via the tag locator component 102. As such, any
`tags that fall within criterion defined by this standing query
`can be automatically or dynamically imported via the tag
`import component 502. In one example, when a user gen-
`erates a new tag with an online photo sharing application,
`the system 100, via tag import component 502, can auto-
`matically import
`this new tag thereafter employing the
`aggregation and/or synchronization component 402, 404 to
`incorporate this tag to data maintained within local data
`stores 108.
`
`Similarly, a tag export component 504 can be
`[0053]
`provided to aggregate and/or synchronize locally established
`tags with external
`sources 106. Continuing with the
`example, suppose a user establishes a local tag that corre-
`sponds to a Hawaiian vacation. This tag can be automati-
`
`FIG. 6 illustrates a system 600 that includes yet
`[0054]
`another novel feature of the innovation described herein.
`
`Specifically, a rendering component 602 can be provided in
`order to facilitate a rich data view ofall tags associated to a
`user and/or device. For example, this rendering component
`602,
`together with the tag manager component 104 can
`facilitate rendering an aggregated and/or synchronized view
`of all tags associated with a user. Moreover, the rendering
`component602 can facilitate generation of a rich view ofall
`data (local and/or remote) that correspondsto a tag or set of
`tags. The novel functionality of the rendering component
`602 will be better understood upon a review ofthe figures
`that follow.
`
`It is a novel feature of the innovation to provide a
`[0055]
`rich data view with respect to all tags associated to or
`available to a user and/or device. For example, the system
`