Background

[0001] Some applications can enable a user to navigate through content, such as a map displayed on a user interface, by moving an icon or other graphical representation through the content. Such applications, however, typically provide very simplistic navigation techniques that may have difficulty responding to variations that are often encountered in content features. For example, to navigate a route on a map, a user navigation typically has to maintain correspondence with the route to allow the navigation to remain on the route. If the user navigation fails to maintain correspondence with the route, the navigation may fail or change routes in an undesirable manner. Summary [0002] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. [0003] Various embodiments provide techniques for scrubbing variable paths in content. By way of example and not limitation, scrubbing can include receiving user input that defines a scrub path and navigating a data path through content based on the scrub path. According to some embodiments, a data path can include one or more predefined paths (e.g., a travel route) through the content. One or more of the techniques can account for variations in a data path and provide ways of maintaining adjacency between a scrub path and navigation along the data path. In some embodiments, a data path can be associated with one or more types of data path content that can be presented in response to navigation along the data path. Brief Description of the Drawings [0004] The same numbers are used throughout the drawings to reference like features. [0005] Fig. 1 illustrates an operating environment in which the inventive principles can be employed in accordance with one or more embodiments.

[0006] Fig. 2 illustrates an example way of maintaining adjacency between a scrub path and a data path navigation, in accordance with one or more embodiments.

[0007] Fig. 3 illustrates an example way of maintaining adjacency between a scrub path and a data path navigation, in accordance with one or more embodiments.

[0008] Fig. 4 illustrates an example user interface in accordance with one or more embodiments.

[0009] Fig. 5 is a flow diagram that describes steps in a method in accordance with one or more embodiments.

[0010] Fig. 6 is a flow diagram that describes steps in a method in accordance with one or more embodiments. [0011] Fig. 7 is a flow diagram that describes steps in a method in accordance with one or more embodiments.

[0012] Fig. 8 is a flow diagram that describes steps in a method in accordance with one or more embodiments.

[0013] Fig. 9 is a flow diagram that describes steps in a method in accordance with one or more embodiments.

[0014] Fig. 10 is a block diagram of a system in accordance with one or more embodiments.

Detailed Description

Overview [0015] Various embodiments provide techniques for scrubbing variable paths in content. By way of example and not limitation, scrubbing can include receiving user input that defines a scrub path and navigating a data path through content based on the scrub path. According to some embodiments, a data path can include one or more predefined paths (e.g., a travel route) through the content. For example, consider an embodiment in which a user wishes to navigate a travel route through a map displayed on a user interface. According to some embodiments, the travel route can be considered a data path and may correspond to a predefined driving route from one point to another, such as from Seattle to Sacramento. [0016] To navigate the travel route, the user can drag a cursor (e.g., via a mouse or other input device) within the map to provide an approximation of the desired travel route. The path that the cursor takes through the map can be considered a scrub path. While the scrub path may approximate the travel route (e.g., in terms of general driving direction), the scrub path may not necessarily account for one or more variations in the travel route, such as a freeway entrance/exit loop, a bypass, a construction detour, and so on. According to some embodiments, techniques discussed herein can account for variations in a data path (e.g., the travel route) and provide ways of maintaining adjacency between a navigation along the data path and the scrub path.

[0017] In one or more embodiments, a data path can be associated with one or more types of data path content, such as text content, advertisements, photographs, video content, audio content, hyperlinks, driving directions, data values, and so on. Using the map example discussed above, one example of data path content can include video content captured along the travel route. Thus, according to some embodiments, techniques discussed herein can cause the video content to be displayed in response to a user indication of the scrub path. [0018] In some embodiments, data path content can also be retrieved and/or filtered based on user-specified parameters, such as one or more user preferences. For example, a user can indicate a preference for particular content, such as seafood restaurants. In such an example scenario, data path content associated with seafood restaurants can be presented to the user responsive to a user indication of a scrub path.

[0019] While example embodiments are discussed herein with reference to scrubbing and navigation within a map, this is for purposes of example only. It is to be appreciated and understood that techniques discussed herein may be employed in a variety of different types of navigable content and different implementation scenarios without departing from the spirit and scope of the claimed embodiments. Examples of suitable navigable content and/or implementation scenarios can include 2-dimensional curves that represent one or more different data parameters (e.g., temperature, pressure, and/or mappings to higher-dimensioned spaces), as well as 3-dimensional models (e.g., computer-aided design (CAD) models), virtual reality environments, video game environments, and so on.

[0020] In the discussion that follows, a section entitled "Operating Environment" describes but one environment in which the various embodiments can be employed. Following this, a section entitled "Example Scrubbing Techniques" describes example ways of maintaining adjacency between one or more data paths and one or more scrub paths in accordance with one or more embodiments. Next, a section entitled "Example User Interface" describes an example user interface in accordance with one or more embodiments. Following this, a section entitled "Example Methods" describes example methods in accordance with one or more embodiments. Last, a section entitled "Example System" is provided and describes an example system that can be used to implement one or more embodiments.

Operating Environment

[0021] Fig. 1 illustrates an operating environment in accordance with one or more embodiments, generally at 100. Environment 100 includes a computing device 102 having one or more processors 104 and one or more computer-readable storage media 106. The computer-readable storage media 106 can include, by way of example and not limitation, all forms of volatile and non- volatile memory and/or storage media that are typically associated with a computing device. Such media can include ROM, RAM, flash memory, hard disk, removable media and the like. One specific example of a computing device is shown and described below in Fig. 10.

[0022] The computing device 102 also includes a web browser 108, as well as other applications, that can be operable to access, display, and/or interact with various types of navigable content. Examples of other applications include navigation (e.g., GPS) applications, medical applications, graphics applications, and so on. The web browser 108 can also be operable to present (e.g., display) one or more instances of data path content, such as data path content 110. Also included on the computing device 102 is a scrubber module 112 that can implement various techniques described above and below. While the scrubber module 112 is illustrated as separate from the web browser 108 (or other applications), it is to be appreciated and understood that, in some embodiments, the web browser 108 (or other applications) may be configured to implement one or more of the techniques discussed herein.

[0023] The computing device 102 is configured to access one or more remote resources via a network 114. The network 114 can include any suitable wired and/or wireless network, such as the Internet, a wide area network, a local area network, and so on. One example of a remote resource is a remote resource 116, which can be accessed to provide a variety of different types of content, such as navigable content and/or data path content. The remote resource 116 can also be configured to perform one or more of the techniques for scrubbing variable content paths discussed herein. For example, the remote resource 116 can host a web- based algorithm and/or web-based service that can be accessed by the computing device 102 to perform one or more techniques discussed herein. Local resources can also be employed in connection with the described embodiments. [0024] Computing device 102 can be embodied as any suitable computing device such as, by way of example and not limitation, a desktop computer, a portable computer, a handheld computer such as a personal digital assistant (PDA), cell phone, and the like. According to one or more embodiments, the computing device 102 can be embodied as a device that is configured to receive touch input. Examples of devices that can be configured to receive touch input include mobile devices, tablet PCs, touchscreen kiosks, and so on. Also, one or more of the techniques discussed herein can be employed to allow disabled individuals to interact with content, such as via a stylus, an appendage, voice input, and so on. Thus, according to some embodiments, techniques discussed herein can enable the scrubbing of content paths via touch input, e.g., via a finger or other appendage. [0025] Having considered an example operating environment, consider now a discussion of example scrubbing techniques for scrubbing variable content paths. Example Scrubbing Techniques

[0026] Fig. 2 illustrates an example way of maintaining adjacency between a data path navigation and a scrub path, in accordance with one or more embodiments. Illustrated at 200 are a data path 202 and a scrub path 204. According to some embodiments, the scrub path 204 can be created by dragging a scrub point 206 using a variety of user input techniques or devices, such as, for example, dragging a cursor with a mouse, touch input, audio input, and so on. In some embodiments, dragging the scrub point 206 can cause a data point 208 to navigate along the data path 202. As discussed above, in some embodiments, the data path 202 can correspond to a previously-defined path, such as a travel route, road, highway and the like. As also discussed above, the data path 202 can be associated with one or more of a variety of data path content, and navigation of the data point 208 along the data path 202 can cause one or more instances of data path content to be presented.

[0027] In some example embodiments, a relationship between a scrub point and a data point in a data path navigation can be established using a model, e.g. a physics-based model, such as a virtual spring (hereinafter "spring") that joins the scrub point to the data point. The spring can be embodied and/or implemented as a physics-based data module, executable computer-code, and/or any other representation.

[0028] In this particular example embodiment, a relationship between the scrub point 206 and the data point 208 is diagrammatically represented as a spring 210. According to one or more embodiments, adjacency between the scrub point 206 and the data point 208 can be determined as a function of a tension associated with the spring 210. The tension on the spring 210 can be quantified using any appropriate unit, such as newtons, pounds, and so on. [0029] Continuing with the current example, at 212 is illustrated a navigation of the data point 208 along the data path 202 responsive to a movement of the scrub point 206. In some example implementations, navigation of the data point 208 along the data path 202 can occur at approximately the same speed as a movement of the scrub point 206. According to some embodiments, a speed of movement of the scrub point 206 can correspond to a speed at which a user drags a cursor and/or provides some other suitable means of input. [0030] Also illustrated at 212 is an increase in spring tension on the spring 210, as illustrated by an elongation of the spring 210. According to some embodiments, a threshold spring tension can be specified that enables adjacency between a navigation of the data point 208 along the data path 202 and the scrub path 204 to be maintained. For example, when the tension on the spring 210 is at or below the threshold tension, the data point can be considered adjacent to the scrub point and the navigation of the data point 208 along the data path 202 can proceed in a direct navigation mode. In some embodiments, a direct navigation mode causes navigation of the data point 208 along the data path 202 to occur at approximately the same speed as the scrub point 206. As a further example, when the tension on the spring 210 is above the threshold tension, the data point can be considered not adjacent to the scrub point and the navigation of the data point 208 along the data path 202 can proceed in an indirect navigation mode. In some embodiments, in an indirect navigation mode, navigation of the data point 208 along the data path 202 accelerates until the tension on the spring 210 equals or falls below the threshold tension.

[0031] Illustrated at 214 is a further navigation of the data point 208 along the data path 202 responsive to a further movement of the scrub point 206. In this example implementation, the tension on the spring 210 has exceeded a threshold tension, and an acceleration path 216 (indicated by the dashed line) indicates a switch in a navigation of the data point 208 along the data path 202 from a direct navigation mode to an indirect navigation mode. In one or more embodiments, a switch in navigation modes can occur responsive to a change in spring tension, such as exceeding a threshold tension. In the current example, the switch to the indirect navigation mode causes the data point 208 to accelerate along the data path 202 until the tension on the spring 210 decreases such that the tension equals or falls below the threshold tension. [0032] According to some embodiments, an acceleration of the data point 208 along the data path 202 in an indirect navigation mode can cause a change in presentation of data path content. For example, the indirect navigation mode can cause some data path content to be skipped, e.g., data path content that occurs along the acceleration path 216. In a further example, the indirect navigation mode can cause data path content, such as video content, to increase in playback speed. According to some embodiments, the increase in playback speed can continue until the navigation of the data point 208 returns to a direct navigation mode, at which time the playback of the video content can return to a normal (e.g., real time) playback speed.

[0033] In some embodiments, the acceleration of the data point 208 along the data path 202 in an indirect navigation mode can be determined based on the tension on the spring 210. For example, the greater the tension on the spring 210, the greater the acceleration of the data point 208, and vice-versa. [0034] At 218, tension on the spring 210 has decreased to within the threshold tension and the navigation of the data point 208 along the data path 202 has returned to a direct navigation mode. According to some embodiments, a return to a direct navigation mode indicates adjacency between the data point 208 and the scrub point 206. [0035] Fig. 3 illustrates another example way of maintaining adjacency between a data path navigation and a scrub path, in accordance with one or more embodiments. At 300 is illustrated a data path 302 and a scrub path 304. The data path 302 includes a data point position 306 that represents a previous position of a data point 308 on the data path 302. The scrub path 304 includes a scrub point position 310 that represents a previous position of a scrub point 312 on the scrub path.

[0036] According to some embodiments, a scrub point can drag a data point along a data path using any suitable mechanism, such as a physics-based string that "attaches" the scrub point to the data point. Thus, in this particular example, as the scrub point 312 moves (e.g., in response to a user input), the string drags the data point 308 along the data path 302. In some embodiments, the string causes the data point 308 to stay within a certain distance of the scrub point 312. [0037] In some embodiments, navigation along the data path 302 can be characterized by point-to-point distances and actual path distances. A point-to- point distance refers to a distance between two data point positions, independent of the data path 302 itself. An actual path distance refers to a distance between two data point positions if the data path 302 is followed between the two positions. For example, in the illustration, a point-to-point distance 314 and an actual path distance 316 between the data point position 306 and the data point 308 is shown. In this particular example, the point-to-point distance 314 is approximately equal to the actual path distance 316. According to some embodiments, when a point-to- point distance is approximately equal to an actual path distance, the data point 308 can be considered adjacent to the scrub point 312 and a navigation of a data point along a data path can occur in a direct navigation mode. [0038] At 318, the scrub point 312 has moved to a new position on the scrub path 304 and the data point 308 has moved to a new position on the data path 302. As discussed above, the data point 308 can be attached to the scrub point 312 via a string that maintains the data point 308 within a certain distance of the scrub point 312. [0039] According to some embodiments, when a data point is maintained within a certain distance of a scrub point (e.g., via a string), the data point may occasionally jump between sections of a data path to stay within the certain distance of the scrub point. In the example illustrated at 318, the data point 308 has jumped from a previous data point position 320 to its current position and skipped the loop 322 of the data path 302.

[0040] At 318 is also illustrated a point-to-point distance 324 and an actual path distance 326 (illustrated as the dashed line) between the new location of the data point 308 and the previous data point position 320. In this particular example, since the data point 308 jumped positions on the data path 302 and skipped the loop 322, the actual path distance 326 is larger than the point-to-point distance 324. According to some embodiments, a threshold difference can be specified between an actual path distance and a point-to-point distance. If the difference between an actual path distance and a point-to-point distance exceeds the threshold difference, a data point can be considered not adjacent to a scrub point, and a navigation of the data point on a data path can transition from the direct navigation mode to the indirect navigation mode.

[0041] In the current example, the difference between the actual path distance 326 and the point-to-point distance 324 has exceeded a threshold difference, and the navigation of the data point 308 has transitioned to an indirect navigation mode. According to some embodiments, a transition from direct navigation mode to indirect navigation mode can cause changes in the presentation of data path content associated with the data path 302. For example, some data path content can be skipped and/or a playback speed of some data path content can be accelerated. [0042] At 328, the scrub point 312 has again moved to a new position on the scrub path 304 and the data point 308 has again moved to a new position on the data path 302. Also illustrated at 328 is a point-to-point distance 330 and an actual path distance 332. In this example, the difference between the actual path distance 332 and the point-to-point distance 330 has returned to within the threshold difference, and thus the navigation of the data point 308 along the data path 302 has returned to a direct navigation mode. According to some embodiments, a return to a direct navigation mode can cause a presentation of data path content to transition from one mode to another. For example, video content playback that was accelerated in response to a transition to indirect navigation mode can return to a normal playback speed. [0043] Having described example user interfaces in accordance with one or more embodiments, consider now a discussion of an example user interface in accordance with one or more embodiments.

Example User Interface

[0044] Fig. 4 illustrates an example user interface 400 in accordance with one or more embodiments. User interface 400 is illustrated as a web browser interface for purposes of example only, and any suitable user interface and/or application may be utilized without departing from the spirit and scope of the claimed embodiments. [0045] The user interface 400 includes a navigation region 402 and a content region 404. According to some embodiments, the navigation region 402 is configured to display navigable content and to receive user input regarding the navigable content. In this particular example, the navigable content includes a navigable map. Although, this is for purposes of example only, and other examples of suitable navigable content are mentioned above.

[0046] The navigation region 402 includes a scrub path 406 and a data path 408. As discussed above, and in accordance with some embodiments, the scrub path 406 can be generated responsive to user input to the navigation region 402, such as a user's finger or mouse dragging over the navigation region 402. Responsive to generating the scrub path 406, a navigation can occur along the data path 408. According to one or more embodiments, the data path 408 can correspond to a predetermined travel route. [0047] According to some embodiments, navigation of the data path 408 can proceed according to a direct navigation mode and/or an indirect navigation mode. For example, at navigation sections 410 and 412 (encircled by the dashed line), the data path 408 is adjacent to the scrub path 406. Accordingly, in some embodiments, the navigation of the data path 408 at the navigation sections 410 and 412 can proceed according to a direct navigation mode. Further to some embodiments, at a navigation section 414 (encircled by the dashed line), the data path 408 is not adjacent to the scrub path 406. Thus, the navigation of the data path 408 at the navigation section 414 can proceed according to an indirect navigation mode. As discussed above, a navigation of the data path 408 can transition between direct navigation modes and indirect navigation modes according to one or more of the techniques discussed herein.

[0048] A navigation of the data path 408 can cause data path content associated with the data path 408 to be presented. Suitable examples of data path content are described above. According to some embodiments, data path content can be presented in a content region 404. The content region 404 can be configured to present any suitable type of data path content. In this particular example, the content region 404 presents video content associated with the data path 408 responsive to a navigation of the data path 408.

[0049] The arrangement of visual elements included in the user interface 400 is for purposes of example only, and it is to be appreciated that any suitable arrangement of visual elements may be utilized without departing from the spirit and scope of the claimed subject matter.

Example Methods

[0050] Fig. 5 is a flow diagram that describes a method in accordance with one or more embodiments. The method can be implemented in connection with any suitable hardware, software, firmware, or combination thereof. In at least some embodiments, the method can be implemented by software executing or executable (e.g., the web browser 108 (or other application) and/or the scrubber module 112) to scrub navigable content. [0051] Step 500 receives an indication of movement of a scrub point. According to some embodiments, the movement of a scrub point can be responsive to user manipulation of the scrub point via one or more suitable techniques for user input. Step 502 causes a data point to navigate a data path in a direct navigation mode. As discussed above, in some embodiments the navigation of the data path can be responsive to the movement of the scrub point. [0052] Step 504 determines if the data point is adjacent to the scrub point. If the data point is adjacent to the scrub point ("Yes"), the method returns to step 502. If, on the other hand, the data point is not adjacent to the scrub point ("No"), step 506 causes the data point to navigate the data path in an indirect navigation mode. In accordance with some embodiments, the method can return to step 504 to determine if the data point has achieved adjacency with the scrub point or if the data point can continue navigating in the indirect navigation mode. Example ways for determining if a data point is adjacent to a scrub point are discussed above and below. [0053] Fig. 6 is a flow diagram that describes a method in accordance with one or more embodiments. The method can be implemented in connection with any suitable hardware, software, firmware, or combination thereof. In at least some embodiments, the method can be implemented by software executing or executable (e.g., the web browser 108 (or other application) and/or the scrubber module 112) to determine if a data point is adjacent to a scrub point in a data path navigation. [0054] Step 600 connects a data point to a scrub point. For example, and as discussed above, a virtual spring can be used to create a virtual connection between a data point and a scrub point. Step 602 receives an indication of movement of a scrub point. Step 604 causes the data point to navigate a data path in a direct navigation mode. Step 606 monitors tension of the connection between the data point and the scrub point. [0055] Step 608 determines if the tension of the connection exceeds a threshold tension. For example, a threshold tension can be specified, e.g., 4 pounds. If the tension does not exceed the threshold tension ("No"), the method returns to step 604. If, however, the tension exceeds the threshold tension ("Yes"), step 610 causes the data point to navigate the data path in an indirect navigation mode. According to some embodiments, the method can return to step 608.

[0056] Fig. 7 is a flow diagram that describes a method in accordance with one or more embodiments. The method can be implemented in connection with any suitable hardware, software, firmware, or combination thereof. In at least some embodiments, the method can be implemented by software executing or executable (e.g., the web browser 108 (or other application) and/or the scrubber module 112) to determine if a data point is adjacent to a scrub point.

[0057] Step 700 receives an indication of movement of a scrub point. Step 702 causes a data point to navigate a data path in a direct navigation mode. According to one or more embodiments, causing the data point to navigate the data path can occur responsive to receiving the indication of the movement of the scrub point. [0058] Step 704 determines a point-to-point distance between a first data point position and a second data point position on the data path. Step 706 determines an actual path distance between the first data point position and the second data point position on the data path. The point-to-point distance and/or the actual path distance can be determined in terms of pixels, vector lengths, or any other suitable way of determining a distance between points. [0059] Step 708 determines if a difference between the actual path distance and the point-to-point distance exceeds a threshold difference. For example, a threshold difference can be specified of 75 pixels. If the difference does not exceed the threshold ("No"), the method returns to step 702. [0060] If, however, the difference between the actual path distance and the point-to-point distance exceeds the threshold distance, step 710 causes the data point to navigate the data path in an indirect navigation mode. For example, if the distance is above 75 pixels, the navigation of the data path can transition to an indirect navigation mode. According to some embodiments, the method can return to step 708.

[0061] Fig. 8 is a flow diagram that describes a method in accordance with one or more embodiments. The method can be implemented in connection with any suitable hardware, software, firmware, or combination thereof. In at least some embodiments, the method can be implemented by software executing or executable (e.g., the web browser 108 (or other application) and/or the scrubber module 112) to scrub one or more paths in a simulated 3 -dimensional environment. [0062] Step 800 receives an indication of a 2-dimensional movement of a scrub point. Step 802 causes a data point to navigate a data path through a simulated 3- dimensional environment utilizing a direct navigation mode and/or an indirect navigation mode. As in the above examples, selection of the direct or indirect navigation modes can be made based upon criteria which is the same as or similar to the criteria mentioned above. Examples of a simulated 3-dimensional environment include CAD models, virtual reality environments, video game environments, and so on. [0063] Fig. 9 is a flow diagram that describes a method in accordance with one or more embodiments. The method can be implemented in connection with any suitable hardware, software, firmware, or combination thereof. In at least some embodiments, the method can be implemented by software executing or executable (e.g., the web browser 108 (or other application) and/or the scrubber module 112) to cause data path content to be presented based on a direct navigation mode and/or an indirect navigation mode. [0064] Step 900 receives an indication of a data point navigation of a data path. Step 902 determines if the data point is navigating the data path in a direct navigation mode or an indirect navigation mode. If the data point is navigating the data path in a direct navigation mode, step 904 causes data path content to be presented in a presentation mode associated with the direct navigation mode. For example, in accordance with the direct navigation mode, video content can be played back in a normal (e.g., real time) playback mode. If, however, the data point is navigating the data path in an indirect navigation mode, step 906 causes data path content to be presented in a presentation mode associated with the indirect navigation mode. Continuing with the video playback example, and in accordance with the indirect navigation mode, the video content can be played back in an accelerated playback mode. According to some embodiments, the method can return from each of steps 904, 906 to step 902 to switch between presentation modes based on one or more changes in data path navigation modes. [0065] According to some embodiments, techniques discussed herein can be utilized in scrubbing movement along a graph that includes junctions. For example, when a scrubbed data point approaches a junction on a graph (e.g., where two curves on a graph intersect), a corresponding data point can have the option of following one of several different possible data curves. In one or more embodiments, techniques discussed herein can select a data curve that is closest to the scrub point. In some implementations, if the scrub point is very close to a junction (e.g., within a preset junction threshold), the decision as to which data curve to follow with the data point can be very noisy. In such implementation scenarios, when the scrub point is very close to a junction on a graph, one or more of the techniques discussed herein can wait for the scrub point to proceed past the junction before deciding on which curve to follow. Thus, by waiting until the scrub point moves past the junction, more information can be provided with which to determine an appropriate curve to follow with the data point. Example System

[0066] Fig. 10 illustrates an example computing device 1000 that can implement the various embodiments described above. Computing device 1000 can be, for example, computing device 102 of Fig. 1 or any other suitable computing device. [0067] Computing device 1000 includes one or more processors or processing units 1002, one or more memory and/or storage components 1004, one or more input/output (I/O) devices 1006, and a bus 1008 that allows the various components and devices to communicate with one another. Bus 1008 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. Bus 1008 can include wired and/or wireless buses.

[0068] Memory/storage component 1004 represents one or more computer storage media. Component 1004 can include volatile media (such as random access memory (RAM)) and/or nonvolatile media (such as read only memory (ROM), Flash memory, optical disks, magnetic disks, and so forth). Component 1004 can include fixed media (e.g., RAM, ROM, a fixed hard drive, etc.) as well as removable media (e.g., a Flash memory drive, a removable hard drive, an optical disk, and so forth). [0069] One or more input/output devices 1006 allow a user to enter commands and information to computing device 1000, and also allow information to be presented to the user and/or other components or devices. Examples of input devices include a keyboard, a cursor control device (e.g., a mouse), a touch input device (e.g., a touch screen), a microphone, a scanner, and so forth. Examples of output devices include a display device (e.g., a monitor or projector), speakers, a printer, a network card, and so forth.

[0070] Various techniques may be described herein in the general context of software or program modules. Generally, software includes routines, programs, objects, components, data structures, and so forth that perform particular tasks or implement particular abstract data types. An implementation of these modules and techniques may be stored on or transmitted across some form of computer readable media. Computer readable media can be any available medium or media that can be accessed by a computing device. By way of example, and not limitation, computer readable media may comprise "computer storage media". [0071] "Computer storage media" include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.

Conclusion [0072] Various embodiments provide techniques for scrubbing variable paths in content. By way of example and not limitation, scrubbing can include receiving user input that defines a scrub path and navigating a data path through content based on the scrub path. According to some embodiments, a data path can include one or more predefined paths (e.g., a travel route) through the content. One or more of the techniques discussed herein can account for variations in a data path and provide ways of maintaining adjacency between a scrub path and navigation along the data path. In some embodiments, a data path can be associated with one or more types of data path content that can be presented in response to a navigation of the data path. [0073] Although the subject matter has been described in language specific to structural features and/or methodological steps, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or steps described. Rather, the specific features and steps are disclosed as example forms of implementing the claimed subject matter.