Note-taking and tablet applications are becoming more popular for users who prefer to use a straightforward interface and tools when interacting and communicating with others. Currently, users can use note taking applications to create and organize ideas, correspondence, and other information. For example, users can use a note-taking application to create notebooks, folders, sections, pages, etc. However, it is difficult to link and relate information using current note-taking applications. Users become frustrated when they are unable to link and relate information in a meaningful and resilient manner. A user may have to perform lengthy and sometimes unsuccessful searches to find relevant information, such as notebooks, sections, pages, notes, and other information.
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 as an aid in determining the scope of the claimed subject matter.
Embodiments are provided to create and maintain one or more links or associations to different types of data and other information. In an embodiment, one or more links can be created and maintained, wherein the one or more links provide one or more pathways between structured information. In one embodiment, a user can create a link to locate desired information, such as a notebook, section group, section, page, and/or page object, wherein user actions can be used to automatically determine a potential link target.
These and other features and advantages will be apparent from a reading of the following detailed description and a review of the associated drawings. It is to be understood that both the foregoing general description and the following detailed description are explanatory only and are not restrictive of the invention as claimed.
Embodiments are provided to create and maintain one or more links or associations to different types of data and other information. In an embodiment, one or more links can be created and maintained, wherein the one or more links provide one or more pathways between structured information. The various embodiments enable a user to quickly and efficiently create a link to a desired target. Correspondingly, a user does not have to determine or know the actual address and/or path to the desired target when creating a link.
In one embodiment, a note-taking application is configured to allow a user to quickly and efficiently create links to desired information. The various embodiments enable users to create references or associations between various items of a hierarchal information structure, but are not so limited. For example, a user can use the note-taking application to create links to notebooks, sections, pages, and/or page objects. The note-taking application enables users to quickly and efficiently create links. Users can use the note-taking application and simply point to a notebook, section, page, and/or page object to create a link to the desired target without having to determine or worry about the actual address or path to the target. Accordingly, the note-taking application is configured to create and maintain links that account for the unique nature of notes and associated information. Thereafter, a user can use a link to locate desired information, such as locating a notebook, section group, section, page, and/or page object.
The note-taking application 102 is configured to capture and organize notes, which may include text, handwriting, pictures, drawings, audio, video, and/or other information. The note-taking application 102 can be used to record, organize, edit, and/or transmit information, including audio, textual, graphical, and other visual information. For example, the note-taking application 102 can be used to view and edit meeting agendas, to-do lists, date/event reminders, etc. As further example, the note-taking application 102 can also be used to share information, such as one or more notes, between one or more computing devices, such as one or more computers of a distributed computer network.
The note-taking application 102 includes an organizer component 104 to organize information associated with the note-taking application 102. For example, the organizer component 104 can be used to organize notebooks, section groups, sections, pages, page objects, and/or other information. The note-taking application 102 also includes a link component 106. The link component 106 is configured to create and maintain one or more links to different types of data and other information. For example, the link component 106 can be used to create hyperlinks that point to web content, such as to web objects and/or web locations of the World Wide Web (WWW). The note-taking application 102 also includes a locator component 108 for locating a link target. In an embodiment, the locator component 108 is configured to use a path associated with a link to locate the link target.
The link component 106 is also configured to quickly and efficiently create links to a notebook, section, page, page object (e.g. image, paragraph, sentence, etc.), and other note-relating information. In one embodiment, the link component 106 is configured to quickly and efficiently create links to a desired target, wherein the link is created based in part on a user's interaction with the note-taking application 102, as described further below. For example, the link component 106 can be used to create various associations, including, but not limited to: a table of contents on a page with links to the other pages in the section or with links to other parts of the same page; a favorites list that comprises a list of links to pages and sections are visited or used frequently; a definition or reference link from a term, a name, or a topic on one page to more detailed information in another place in the notes.
The note-taking application 102 and link component 106 can be used to create links to other notes on a page, in an e-mail, and/or in other documents. For example, a user can create a link and then send the link to one or more recipients in an e-mail. Thereafter, a recipient can click the link to jump to the link target (e.g. if the notes are associated with a shared notebook). Links created with the note-taking application 102 and associated link component 106 can be used inside and outside of a note-taking application (e.g. e-mail, meeting items, documents, web pages, etc.).
The note-taking application 102 can use the organizer component 104 to organize notes and the link component 106 to create links to items associated with a hierarchal information structure. In an embodiment, the note-taking application 102 is configured to organize notes according to a hierarchal structure, such that pages are contained within sections, sections are contained within section groups, and section groups are contained within notebooks (e.g. notebook>section group>section>page>page object). A user can use the note-taking application 102 to create a link to refer to information at any level. For example, a user can use the note-taking application 102 to create links that point to a notebook, section, page, and/or paragraph of notes. As described herein, a user can use the note-taking application 102 to quickly and efficiently create a link to a link target, without having to undergo an onerous and complicated procedure to create the link.
As shown in
For example, the user can paste the created link in a shared notebook, word processing document, e-mail, or other location. If a link is pasted into another application or location outside of the note-taking application 102, the link will be configured as an absolute link (an absolute path to the link target, as described below). A user can also use the note-taking application 102 to right-click on a word or phrase on a page, and then click “Create Linked Page.” Thereafter, the note-taking application 102 and link component 106 operate to create a link to the page with the associated title at the end of the current section and the selected word or phrase will be linked thereto.
As shown in
As described above, the note-taking application 102 is configured to track a user's interaction and/or predict a link target based in part on the interaction. In one embodiment, the note-taking application 102 is configured to track the user's interaction and predict the user's intended link target by populating the “Selected target” field 416, “Address” field 404, and/or “Text to display” field 406. These fields can be repopulated with updated information as the user navigates through note-related information. For example, if a user has clicked a particular section, the note-taking application 102 will populate the “Selected target” field 416, “Address” field 404, and/or “Text to display” field 406 with the associated section information (e.g. section name, path, and friendly name). If the user then clicks a page in the section, the note-taking application 102 will repopulate the “Selected target” field 416, “Address” field 404, and/or “Text to display” field 406 with the associated page information (e.g. page name, path, and friendly name) (see
For example, the note-taking application 102 can populate the “Selected target” field 416 as follows, depending on the target the user has interacted with:
1) if the user clicks a notebook: ‘Notebook “<notebook name>’”
2) if the user clicks a folder: ‘Folder “<folder name>’”
3) if the user clicks a section: ‘Section “<section name>’”
4) if the user clicks a page: ‘Page “<page name>’”
5) if the user clicks any page object: use the string as specified for the page object (text, pictures, etc.) in section Friendly name. Example: ‘Picture on page “User Requests’”.
In one embodiment, the note-taking application 102 is configured to interpret a navigation event as selecting a target after a user has selected the radio button 414. For example, the note-taking application can be configured to interpret the following user interactions and make predictions based thereon, but is not so limited:
1) The target is predicted to be a folder, section, or page when a user navigates to a folder, section, or page via a tab.
2) The target is predicted to be a notebook, folder, or section when a user navigates to a notebook, folder, or section icon via the navigation tree.
3) The target is predicted to be a page when a user navigates to a page by Ctrl+Page Down/Up.
4) The target is predicted to be a section when a user navigates to a section by Ctrl+TAB/Shift TAB.
5) The target is predicted to be a page when a user navigates to a page from the Page List pane.
6) The target is predicted to be a page if a user has navigated to a page as a result of search.
7) The target is predicted to be a notebook, folder, or section if a user selects File→Open→Notebook, Folder, or Section.
8) The target is predicted to be a note flag if a user navigates to a note flag (e.g. from Note Flag Summary).
9) The target is predicted to be a page if a user selects a page tab.
10) The target is predicted to be a section if a user selects a section tab.
11) The target is predicted to be a new location of user input (e.g. relocated page object) or a selection on the page.
12) The target is predicted to be a notebook, folder, section, page, or page object if a user right-clicks on any notebook, folder, section, page, or page object and does “Copy address” (the address and friendly name are also populated in the respective fields).
In one embodiment, the “Insert Link” button 410 is grayed out until both the “Address” field 404 and the “Text to display” field 406 are populated. If the “Address” field 404 and the “Text to display” field 406 are populated, when a user clicks on “Insert Link” 410, the link is inserted at a location on the original page where the user clicked Insert→Hyperlink and the note-taking application 102 navigates back to that page. If the page where the link should be inserted has become unavailable (e.g. a password protected section is locked), the user will see a password prompt. If the password is correct, the link is inserted successfully. If the user cancels out of the password dialog, the insertion action is cancelled by the note-taking application 102. If the user clicks the “Cancel” button 412 or closes the user interface pane 400b, the link is not inserted and the user is returned to the original page and/or selection.
In one embodiment, the user can insert a link using an insert command and thereafter use one or more user interface panes (e.g.
At 502, a user can interact with the note-taking application 102 to select a potential desired target. For example, a user may want to select a particular notebook, section, page, page object, and/or some other item. At 504, the note-taking application tracks and captures items (e.g. notebooks, sections, pages, page objects, etc.) and associated parameters as the user clicks on one or more items in the note-taking application 102. At 506, the note-taking application 102 populates a display (e.g. one or more fields of the user interface pane 400b) to inform the user of a potential link target. The note-taking application 102 refreshes or repopulates the display with new target information as a user further interacts with notes (e.g. clicks another item). The note-taking application 102 also maintains the path information associated with each link target as it is populated in the display.
At 508, the note-taking application 102 generates link parameters for the link target. For example, the note-taking application 102 can generate link parameters for the link target if the user is no longer selecting items or after some amount of idle time. At 510, the note-taking application 102 stores the link parameters to memory. The stored parameters and/or other information can be used by the note-taking application 102 or some other application when locating and/or navigating to a link target. The link parameters also can be included as part of the link address. For example, the link address can include information that is associated with the path to the target and/or location of the link.
In an embodiment, the note-taking application 102 generates and stores parameters associated with an absolute link path, a relative link path, and/or a maximally relative link path to a target. In one embodiment, the note-taking application 102 generates and stores parameters associated with a relative link path based on a user's input, such as after a paste operation for example. At 512, the user can insert the link at a desired location in the note-taking application or some other location.
Thereafter, when a user interacts with the link (e.g. clicks the link, presses enter, etc.), if the link target is located, the link target is provided to the user (e.g. notebook, section, page, page object, etc.). In one embodiment, the link target points to a page object, and the note-taking application 102 is configured to locate a page and then look for the page object. For example, a link may specify which object the page should be scrolled to, such as an outline object (e.g. container of data), an outline element (e.g. paragraph), ink, an image, an icon for inserted document, etc. If the object is not found, the note-taking application 102 is configured to navigate to the target page or section.
The note-taking application 102 is configured to generate and/or store an absolute path, a relative path, and/or a maximally relative path to a link target. An absolute path refers to a full link to a location associated with a note-taking application 102 (e.g. notebook, section group, section, page, page object, etc.). In one embodiment, an absolute path is included on a clipboard (e.g. global clipboard) when a link is created and the relative path is created when the link is pasted to some location in a note-taking application 102. The link and absolute path provided on the clipboard has all the information needed to get to a notebook (e.g. includes the full network address). For example, if a user pasted a link in a different application, such as in a word processing document, an e-mail, etc., the path remains absolute and will navigate to the link target if clicked from the different application under certain conditions (e.g. server available, user credentials, user authentication, etc.). As further example, if a user pasted a link from one computing device to a different computing device, the link path will remain absolute.
In one embodiment, the note-taking application 102 is configured to create a relative path to a target when a link is pasted to a location in the note-taking application 102. The relative path is associated with the absolute path but includes fewer parameters than the absolute path. Moreover, the relative path is configured to include as few details as necessary to navigate to a link target. Correspondingly, the note-taking application 102 uses a minimal amount of information (and memory) to create the relative path from the absolute path. The relative path also remains valid if a user moves large chunks of the hierarchal structure. That is, links contained within the relocated structure are configured to continue to point to a proper target.
An absolute path can become maximally relativized under certain conditions. In one embodiment, an absolute path gets maximally relativized whenever a link created by the note-taking application 102 is pasted onto a notebook page. The maximally relative path can also include the target page name if the link is to a page or page object (e.g. “..\..\Specs.one#Templates”). The “#” identifies a page.
Take for example the relative link path:
“onenote:..\Misc%20Work\Meetings.one#Content%20Council.”
The above path is deciphered to mean go up from the current folder (“..”), then go to folder “Misc Work”, then to section “Meetings”, then to page “Content Council”. The total path to the folder “Misc Work” is not required.
As part of the link pasting or positioning operation, in one embodiment, the note-taking application 102 is configured to include a base path as part of the link. The base path is included as part of the relative path and defines an absolute path to the location (e.g. section, page, etc.) where the link is pasted or positioned. That is, the note-taking application 102 can use the base path to determine where the link is located.
For example, the following link includes a base path:
“onenote:..\Misc%20Work\Meetings.one#Content%20Council&base-path=tkzaw-pro-16\Mydocs4\username\My%20Documents\OneNote%20Notebooks.”
As described above, if a target is on a different share, it may not be relativized.
For example:
“onenote:///\\server06\Shared\Shared%20Notebooks\OneNote%20Best%20Practices\More%20Cool%20Features.one#Tables.”
This absolute path will not be relativized since the link is associated with a shared notebook.
For example, an absolute path may include:
“onenote:///\\server06\Shared\Shared%20Notebooks\OneNote%20Best%20Practices\More%20Cool%20Features.one#Tables”.
“OneNote%20Best%20Practices” refers to a particular notebook. “More%20Cool%20Features.one” refers to the particular section and “Tables” is the page associated with the section. However, the user may only see a friendly name for the link, such as “Tables” for example. The path can be inspected if the user hovers over the link. The user can also right click on the link and view its properties. As described above, if the link is created by the note-taking application 102, the link is configured to include information that can be used to locate the link and/or link target if an associated parameter has changed.
A link created by the note-taking application 102 may include additional information that can be used when locating a link target. In one embodiment, a link includes one or more target identifiers, such as Globally Unique Identifiers (GUIDs) for example. The one or more GUIDs can be included as part of a link and used to locate a target. For example, a link may include:
“onenote:http://onetest/PM%20Team%20Notebook/Home.one#OneNote%20Example%20Customers§ion-id={2C741A71-2F80-4A1A-85B2-5CE98A397837}&page-id={6D4390E2-8DDC-4D88-B90D-F0DADECDABCC}&end.”
The section-id and page-id refer to GUIDs that the note-taking application 102 can use to locate a particular target with additional granularity. The section-id GUID is associated with a particular section. Likewise, the page-id GUID is associated with a particular page. The section GUID is “2C741A71-2F80-4A1A-85B2-5CE98A397837” and the page GUID is “6D4390E2-8DDC-4D88-B90D-F0DADECDABCC”. The note-taking application 102 can use one or more GUIDs to locate a target when the name of a page is changed for example. In such a circumstance, the note-taking application 102 may not be able to locate the target based on the relative path and page title, so it can use the one or more GUIDs to locate the target. A link may include one or both of the GUIDs. A link may also include a page object identifier (e.g. GUID).
Once a link is created with the note-taking application 102, the link can be interacted with to navigate to a target. For example, the note-taking application 102 can use the absolute path and/or relative path to the target when navigating to the target. The link can be interacted with (e.g. “clicked”) while a user is using a note-taking application or some other application. Accordingly, user can use a link (e.g. clicking the link) to access the associated target information, such as a notebook, section group, section, page, page object, for example. The note-taking application 102 is also configured to create link to external target information, such as information on the internet, in a shared notebook, etc. A user can associate a friendly name with a link so that the link is readily identified upon examination. As described above, a friendly name can be automatically applied by the note-taking application as the name of the link target (e.g. notebook name, folder name, section name, page name, etc.).
For example, a link and associated path may include parameters, such as:
“onenote:<maximally relative file path><#page title>&<Original section and page GUIDs>&base-bath=<path to original section where this link was pasted>”.
If the target is not found at 604, the flow returns to 604, and the note-taking application is configured reexamine the link parameters, including additional link parameters, to locate the link target. If the target is found at 604, the note-taking application 102 navigates to the target at 606. If the target is not found after a certain number of attempts using various parameters, the note-taking application 102 is configured to, inform the user that the link is broken (e.g. displays an error message). The embodiments and examples described herein are not intended to limit. For example, the note-taking application 102 can perform the above-described steps in order, with greater or fewer steps, or in some other manner.
Some other features of the note-taking application 102 follow:
If a user copies to the clipboard (e.g. “Copy Link to this <X>”): the note-taking application 102 will use the following:
For HTML: “<a href=”the onenote: link address>“>Friendly name of the link</a>”.
The address can include: the absolute path to the target, target GUID, and the friendly name.
For example:
“onenote:///\\tkzaw-pro-16\Mydocs4\username\My%20Documents\OneNote%20Notebooks\Misc%20Work\Meetings.one#section-id={1021B20A-242A-46F1-A3FE-5D41DEF78070}&end”.
For plain text the link address includes the same information as above.
If a user copies a link to clipboard from a link on a page, the note-taking application 102 will use the following:
For HTML: “<a href=”onenote: link address as is“>Text of the link (friendly name)</a>”.
For plain text, the text of the link is used.
If a user right-clicks a link and selects “Copy Link”, the note-taking application 102 will use the following:
For HTML: “<a href=”onenote: link address as is“>Text of the link (friendly name)</a>”
For plain text, the address of the link is used.
If the user selects only part of any link, the full address is still placed on the clipboard, but only the copied part is used for the friendly name.
If a user pastes a link onto a page, the note-taking application 102 is configured to perform the following:
1) If the link is relative and specifies no base path, it is pasted as is.
2) If the link is relative and a base path is given, the note-taking application 102 constructs the absolute path to the target.
3) If the link is absolute, the note-taking application 102 attempts to maximally relativize the link and store the relative path. If the note-taking application 102 was able to relativize the link, it adds a base path (e.g. the path to the current section/page where the link is being pasted).
The table below includes a number of link examples and the associated procedures used by the note-taking application.
If the link is to another object on the same page, the note-taking application 102 maintains the page info if the link is maximally relativized, since the base path may not contain the page info.
For example:
“onenote:#Page&page-id={<GUID>}&object-id={<GUID>}&base-path=C:\My Documents\My Notebook\Templates.one”.
As described herein, a user can create and use one or more links to different items associated with a note-taking application. The created links can also be used in conjunction with other applications, such as word processing, e-mail, and other applications that link to items of the note taking application. The embodiments described herein can be used with a number of applications that use links to point and navigate to structured and other information.
Exemplary Operating Environment
Referring now to
Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the invention may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
Referring now to
The computer 2 further includes a mass storage device 14 for storing an operating system 32, application programs, such as a note-taking application 24, and other program modules. In one embodiment, the note-taking application 24 comprises the OneNote® note-taking application program from MICROSOFT CORPORATION of Redmond, Wash. However, the embodiments described herein may be utilized with other system, applications, modules, etc to provide resilient links to structured and/or hierarchal information. The mass storage device 14 is connected to the CPU 8 through a mass storage controller (not shown) connected to the bus 10. The mass storage device 14 and its associated computer-readable media provide non-volatile storage for the computer 2. Although the description of computer-readable media contained herein refers to a mass storage device, such as a hard disk or CD-ROM drive, it should be appreciated by those skilled in the art that computer-readable media can be any available media that can be accessed or utilized by the computer 2.
By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media. Computer storage media includes 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 includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid state 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 the computer 2.
According to various embodiments of the invention, the computer 2 may operate in a networked environment using logical connections to remote computers through a network 4, such as a local network, the Internet, etc. for example. The computer 2 may connect to the network 4 through a network interface unit 16 connected to the bus 10. It should be appreciated that the network interface unit 16 may also be utilized to connect to other types of networks and remote computing systems. The computer 2 may also include an input/output controller 22 for receiving and processing input from a number of input types, including a keyboard, mouse, pen, stylus, finger, and/or other means. Similarly, an input/output controller 22 may provide output to a display, a printer, or other type of output device. Additionally, a touch screen can serve as an input and an output mechanism.
As mentioned briefly above, a number of program modules and data files may be stored in the mass storage device 14 and RAM 18 of the computer 2, including an operating system 32 suitable for controlling the operation of a networked personal computer, such as the WINDOWS XP operating system from MICROSOFT CORPORATION of Redmond, Wash. The mass storage device 14 and RAM 18 may also store one or more program modules. In particular, the mass storage device 14 and the RAM 18 may store application programs, such as a word processing application 28, an imaging application 30, e-mail application 34, drawing application, etc.
It should be appreciated that various embodiments of the present invention can be implemented (1) as a sequence of computer implemented acts or program modules running on a computing system and/or (2) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance requirements of the computing system implementing the invention. Accordingly, logical operations including related algorithms can be referred to variously as operations, structural devices, acts or modules. It will be recognized by one skilled in the art that these operations, structural devices, acts and modules may be implemented in software, firmware, special purpose digital logic, and any combination thereof without deviating from the spirit and scope of the present invention as recited within the claims set forth herein.
Although the invention has been described in connection with various exemplary embodiments, those of ordinary skill in the art will understand that many modifications can be made thereto within the scope of the claims that follow. Accordingly, it is not intended that the scope of the invention in any way be limited by the above description, but instead be determined entirely by reference to the claims that follow.
Number | Name | Date | Kind |
---|---|---|---|
5202828 | Vertelney et al. | Apr 1993 | A |
5493692 | Theimer et al. | Feb 1996 | A |
5530794 | Luebbert | Jun 1996 | A |
5537628 | Luebbert | Jul 1996 | A |
5544321 | Theimer et al. | Aug 1996 | A |
5555376 | Theimer et al. | Sep 1996 | A |
5563996 | Tchao | Oct 1996 | A |
5596656 | Goldberg | Jan 1997 | A |
5603054 | Theimer et al. | Feb 1997 | A |
5611050 | Theimer et al. | Mar 1997 | A |
5625783 | Ezekiel et al. | Apr 1997 | A |
5625810 | Kurosu et al. | Apr 1997 | A |
5701424 | Atkinson | Dec 1997 | A |
5724595 | Gentner | Mar 1998 | A |
5734915 | Roewer | Mar 1998 | A |
5752254 | Sakairi | May 1998 | A |
5760768 | Gram | Jun 1998 | A |
5761683 | Logan et al. | Jun 1998 | A |
5765156 | Guzak et al. | Jun 1998 | A |
5778346 | Frid-Nielsen et al. | Jul 1998 | A |
5781192 | Kodimer | Jul 1998 | A |
5798760 | Vayda et al. | Aug 1998 | A |
5801693 | Bailey | Sep 1998 | A |
5812865 | Theimer et al. | Sep 1998 | A |
5838321 | Wolf | Nov 1998 | A |
5855006 | Huemoeller et al. | Dec 1998 | A |
5870552 | Dozier et al. | Feb 1999 | A |
5884306 | Bliss et al. | Mar 1999 | A |
5898434 | Small et al. | Apr 1999 | A |
5924099 | Guzak et al. | Jul 1999 | A |
5940078 | Nagarajayya et al. | Aug 1999 | A |
5958008 | Pogrebisky et al. | Sep 1999 | A |
5970455 | Wilcox et al. | Oct 1999 | A |
5970466 | Detjen et al. | Oct 1999 | A |
5999938 | Bliss et al. | Dec 1999 | A |
6002402 | Schacher | Dec 1999 | A |
6025837 | Matthews, III et al. | Feb 2000 | A |
6034686 | Lamb et al. | Mar 2000 | A |
6057845 | Dupouy | May 2000 | A |
6065012 | Balsara et al. | May 2000 | A |
6177939 | Blish et al. | Jan 2001 | B1 |
6233591 | Sherman et al. | May 2001 | B1 |
6249283 | Ur | Jun 2001 | B1 |
6262724 | Crow et al. | Jul 2001 | B1 |
6269389 | Ashe | Jul 2001 | B1 |
6275940 | Edwards et al. | Aug 2001 | B1 |
6278450 | Arcuri et al. | Aug 2001 | B1 |
6282548 | Burner et al. | Aug 2001 | B1 |
6309305 | Kraft | Oct 2001 | B1 |
6310622 | Assente | Oct 2001 | B1 |
6310634 | Bodnar et al. | Oct 2001 | B1 |
6321242 | Fogg et al. | Nov 2001 | B1 |
6389434 | Rivette et al. | May 2002 | B1 |
6411311 | Rich et al. | Jun 2002 | B1 |
6429882 | Abdelnur et al. | Aug 2002 | B1 |
6433801 | Moon et al. | Aug 2002 | B1 |
6448987 | Easty et al. | Sep 2002 | B1 |
6459441 | Perroux et al. | Oct 2002 | B1 |
6466232 | Newell et al. | Oct 2002 | B1 |
6490634 | Coiner | Dec 2002 | B2 |
6499041 | Breslau et al. | Dec 2002 | B1 |
6513046 | Abbott, III et al. | Jan 2003 | B1 |
6549219 | Selker | Apr 2003 | B2 |
6549915 | Abbott, III et al. | Apr 2003 | B2 |
6572660 | Okamoto | Jun 2003 | B1 |
6606653 | Ackermann, Jr. et al. | Aug 2003 | B1 |
6618732 | White et al. | Sep 2003 | B1 |
6651059 | Sundaresan et al. | Nov 2003 | B1 |
6686938 | Jobs et al. | Feb 2004 | B1 |
6694087 | Weaver | Feb 2004 | B1 |
6704770 | Ramakesavan | Mar 2004 | B1 |
6708202 | Shuman et al. | Mar 2004 | B1 |
6735347 | Bates et al. | May 2004 | B1 |
6747675 | Abbott et al. | Jun 2004 | B1 |
6751777 | Bates et al. | Jun 2004 | B2 |
6763496 | Hennings et al. | Jul 2004 | B1 |
6789228 | Merril et al. | Sep 2004 | B1 |
6791580 | Abbott et al. | Sep 2004 | B1 |
6801223 | Abbott et al. | Oct 2004 | B1 |
6802041 | Rehm | Oct 2004 | B1 |
6812937 | Abbott et al. | Nov 2004 | B1 |
6826729 | Giesen et al. | Nov 2004 | B1 |
6836270 | Du | Dec 2004 | B2 |
6842877 | Robarts et al. | Jan 2005 | B2 |
6848075 | Becker et al. | Jan 2005 | B1 |
6918091 | Leavitt et al. | Jul 2005 | B2 |
6924797 | MacPhail | Aug 2005 | B1 |
6925496 | Ingram et al. | Aug 2005 | B1 |
6944821 | Bates et al. | Sep 2005 | B1 |
6970867 | Hsu et al. | Nov 2005 | B1 |
7032210 | Alloing et al. | Apr 2006 | B2 |
7039234 | Geidl et al. | May 2006 | B2 |
7114128 | Koppolu et al. | Sep 2006 | B2 |
7143338 | Bauchot et al. | Nov 2006 | B2 |
7165098 | Boyer et al. | Jan 2007 | B1 |
7184955 | Obrador et al. | Feb 2007 | B2 |
7185050 | Eld et al. | Feb 2007 | B2 |
7188073 | Tam et al. | Mar 2007 | B1 |
7210107 | Wecker et al. | Apr 2007 | B2 |
7254785 | Reed | Aug 2007 | B2 |
7373603 | Yalovsky et al. | May 2008 | B1 |
7406501 | Szeto et al. | Jul 2008 | B2 |
7454763 | Veselova et al. | Nov 2008 | B2 |
7460713 | Lapstun et al. | Dec 2008 | B2 |
7555707 | Labarge et al. | Jun 2009 | B1 |
20010032214 | Bauchot et al. | Oct 2001 | A1 |
20010040590 | Abbott et al. | Nov 2001 | A1 |
20010040591 | Abbott et al. | Nov 2001 | A1 |
20010043231 | Abbott et al. | Nov 2001 | A1 |
20010043232 | Abbott et al. | Nov 2001 | A1 |
20020032689 | Abbott, III et al. | Mar 2002 | A1 |
20020044152 | Abbott, III et al. | Apr 2002 | A1 |
20020049785 | Bauchot | Apr 2002 | A1 |
20020052930 | Abbott et al. | May 2002 | A1 |
20020052963 | Abbott et al. | May 2002 | A1 |
20020054130 | Abbott, III et al. | May 2002 | A1 |
20020054174 | Abbott et al. | May 2002 | A1 |
20020078180 | Miyazawa | Jun 2002 | A1 |
20020078204 | Newell et al. | Jun 2002 | A1 |
20020080155 | Abbott et al. | Jun 2002 | A1 |
20020080156 | Abbott et al. | Jun 2002 | A1 |
20020083025 | Robarts et al. | Jun 2002 | A1 |
20020083158 | Abbott et al. | Jun 2002 | A1 |
20020087525 | Abbott et al. | Jul 2002 | A1 |
20020087534 | Blackman et al. | Jul 2002 | A1 |
20020087642 | Wei et al. | Jul 2002 | A1 |
20020091739 | Ferlitsch et al. | Jul 2002 | A1 |
20020099777 | Gupta et al. | Jul 2002 | A1 |
20020099817 | Abbott et al. | Jul 2002 | A1 |
20020120697 | Generous et al. | Aug 2002 | A1 |
20020133520 | Tanner | Sep 2002 | A1 |
20020138582 | Chandra et al. | Sep 2002 | A1 |
20020140731 | Subramaniam et al. | Oct 2002 | A1 |
20020161800 | Eld et al. | Oct 2002 | A1 |
20020161804 | Chiu et al. | Oct 2002 | A1 |
20020196293 | Suppan et al. | Dec 2002 | A1 |
20030013483 | Ausems et al. | Jan 2003 | A1 |
20030014395 | Ruvolo et al. | Jan 2003 | A1 |
20030014490 | Bates et al. | Jan 2003 | A1 |
20030020749 | Abu-Hakima et al. | Jan 2003 | A1 |
20030046401 | Abbott et al. | Mar 2003 | A1 |
20030050927 | Hussam | Mar 2003 | A1 |
20030069877 | Grefenstette et al. | Apr 2003 | A1 |
20030070143 | Maslov | Apr 2003 | A1 |
20030076352 | Uhlig et al. | Apr 2003 | A1 |
20030084104 | Salem et al. | May 2003 | A1 |
20030088534 | Kalantar et al. | May 2003 | A1 |
20030097361 | Huang et al. | May 2003 | A1 |
20030100999 | Markowitz | May 2003 | A1 |
20030135565 | Estrada | Jul 2003 | A1 |
20030154254 | Awasthi | Aug 2003 | A1 |
20030154476 | Abbott, III et al. | Aug 2003 | A1 |
20030172168 | Mak et al. | Sep 2003 | A1 |
20030172384 | Comps | Sep 2003 | A1 |
20030187930 | Ghaffar et al. | Oct 2003 | A1 |
20030196196 | Nylander et al. | Oct 2003 | A1 |
20030212680 | Bates et al. | Nov 2003 | A1 |
20030222899 | Alvesalo | Dec 2003 | A1 |
20040001093 | Sellers et al. | Jan 2004 | A1 |
20040039779 | Amstrong et al. | Feb 2004 | A1 |
20040054736 | Daniell et al. | Mar 2004 | A1 |
20040063400 | Kim | Apr 2004 | A1 |
20040073679 | Martens et al. | Apr 2004 | A1 |
20040098398 | Ahn et al. | May 2004 | A1 |
20040109033 | Vienneau et al. | Jun 2004 | A1 |
20040128613 | Sinisi | Jul 2004 | A1 |
20040153445 | Horvitz et al. | Aug 2004 | A1 |
20040158611 | Daniell et al. | Aug 2004 | A1 |
20040168119 | Liu et al. | Aug 2004 | A1 |
20040172455 | Green et al. | Sep 2004 | A1 |
20040174392 | Bjoernsen et al. | Sep 2004 | A1 |
20040177122 | Appelman et al. | Sep 2004 | A1 |
20040177319 | Horn | Sep 2004 | A1 |
20040189694 | Kurtz et al. | Sep 2004 | A1 |
20040194025 | Hubert et al. | Sep 2004 | A1 |
20040221243 | Twerdahl et al. | Nov 2004 | A1 |
20040230599 | Moore et al. | Nov 2004 | A1 |
20040243677 | Curbow et al. | Dec 2004 | A1 |
20040243941 | Fish | Dec 2004 | A1 |
20040267625 | Feng et al. | Dec 2004 | A1 |
20040267706 | Springer et al. | Dec 2004 | A1 |
20040268231 | Tunning | Dec 2004 | A1 |
20040268263 | Van Dok et al. | Dec 2004 | A1 |
20050004989 | Satterfield et al. | Jan 2005 | A1 |
20050004990 | Durazo et al. | Jan 2005 | A1 |
20050005235 | Satterfield et al. | Jan 2005 | A1 |
20050005249 | Hill et al. | Jan 2005 | A1 |
20050010871 | Ruthfield et al. | Jan 2005 | A1 |
20050034078 | Abbott et al. | Feb 2005 | A1 |
20050055424 | Smith | Mar 2005 | A1 |
20050064852 | Baldursson | Mar 2005 | A1 |
20050097465 | Giesen et al. | May 2005 | A1 |
20050102365 | Moore et al. | May 2005 | A1 |
20050102607 | Rouselle et al. | May 2005 | A1 |
20050102639 | Dove | May 2005 | A1 |
20050108619 | Theall et al. | May 2005 | A1 |
20050114521 | Lee | May 2005 | A1 |
20050119018 | Kim | Jun 2005 | A1 |
20050125717 | Segal et al. | Jun 2005 | A1 |
20050149851 | Mittal | Jul 2005 | A1 |
20050154761 | Lee et al. | Jul 2005 | A1 |
20050165795 | Myka et al. | Jul 2005 | A1 |
20050166154 | Wilson et al. | Jul 2005 | A1 |
20050175089 | Jung | Aug 2005 | A1 |
20050183008 | Crider et al. | Aug 2005 | A1 |
20050208962 | Kim | Sep 2005 | A1 |
20050233744 | Karaoguz | Oct 2005 | A1 |
20050240590 | Shimizu et al. | Oct 2005 | A1 |
20050245241 | Durand | Nov 2005 | A1 |
20050286414 | Young et al. | Dec 2005 | A1 |
20050289109 | Arrouye et al. | Dec 2005 | A1 |
20060036945 | Radtke et al. | Feb 2006 | A1 |
20060036950 | Himberger et al. | Feb 2006 | A1 |
20060036965 | Harris et al. | Feb 2006 | A1 |
20060053379 | Henderson et al. | Mar 2006 | A1 |
20060069603 | Williams et al. | Mar 2006 | A1 |
20060069604 | Leukart et al. | Mar 2006 | A1 |
20060069617 | Milener et al. | Mar 2006 | A1 |
20060074844 | Frankel | Apr 2006 | A1 |
20060075347 | Rehm | Apr 2006 | A1 |
20060095452 | Jansson et al. | May 2006 | A1 |
20060139709 | Bifano et al. | Jun 2006 | A1 |
20060150109 | Schultz et al. | Jul 2006 | A1 |
20060195461 | Lo et al. | Aug 2006 | A1 |
20070022372 | Liu et al. | Jan 2007 | A1 |
20070124325 | Moore et al. | May 2007 | A1 |
20070156627 | D'Alicandro | Jul 2007 | A1 |
20070156643 | Sareen et al. | Jul 2007 | A1 |
20070168278 | Peterson et al. | Jul 2007 | A1 |
20070168378 | Sareen et al. | Jul 2007 | A1 |
20070245223 | Siedzik et al. | Oct 2007 | A1 |
20070245229 | Siedzik et al. | Oct 2007 | A1 |
20080115048 | Veselova et al. | May 2008 | A1 |
Number | Date | Country |
---|---|---|
0569133 | Nov 1993 | EP |
0986011 | Mar 2000 | EP |
1223503 | Jul 2002 | EP |
1376337 | Feb 2004 | EP |
1630694 | Mar 2006 | EP |
2391148 | Jan 2004 | GB |
2001265753 | Sep 2001 | JP |
WO 9800787 | Aug 1998 | WO |
WO 2004038548 | May 2004 | WO |
WO 2004038548 | May 2004 | WO |
WO 2004038548 | May 2004 | WO |
WO 2004086254 | Oct 2004 | WO |
WO 2005001709 | Jan 2005 | WO |
WO 2005067328 | Jul 2005 | WO |
WO 2005110010 | Nov 2005 | WO |
WO 2007081783 | Jul 2007 | WO |
WO 2007081783 | Jul 2007 | WO |
WO 2007081786 | Jul 2007 | WO |
WO 2007081786 | Jul 2007 | WO |
Number | Date | Country | |
---|---|---|---|
20080115069 A1 | May 2008 | US |