Locations within books have traditionally been indicated by page and line numbers. However, the concept of a “page” is not as meaningful in the context of electronic books, in which page divisions may be calculated dynamically, as a function of page and font size. Different book reader devices have different display sizes, and even within a particular device, a user may change viewing options to result in different effective page sizes.
Because of this, locations within electronic books are often specified in terms of an index that relates to a smaller unit of measure, such as by a byte/character index or a word index. For example, a particular word might be specified in terms of its starting and ending character indexes, relative to the beginning of the electronic book.
However, a further complication arises when dealing with multiple versions of an electronic book. When publishing electronically, revisions are very easy to implement, and publishers often submit new versions to correct relatively minor things such as typographical errors, as well as to make more significant revisions. More specifically, different versions may arise because of updates from the original publisher, because different publishers might submit versions of the same book, because of differences in electronic formats, because of differences in media (such as electronic vs. audio), and so forth.
Even small changes between versions can disrupt a position indexing scheme, making it difficult to correlate locations across versions.
The detailed description is set forth with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different figures indicates similar or identical items.
This disclosure describes systems, devices, and techniques in which services that rely on content position can be used with different versions of an electronic book, even when the different versions use different indexing schemes or have revised content from one version to another. When providing position-dependent services or information, a position mapping service can be queried to obtain an equivalent position within a different version of an electronic book.
Example Architecture
Each electronic reader 104 has a display upon which electronic content such as electronic books (eBooks) may be rendered. The terms content, content item, and “eBook” include essentially any form of electronic data that may be consumed on a device, including textual and verbal works comprising sequences of words such as digital books, audio books, electronic magazines, papers, journals, periodicals, documents, instructional materials, course content, music, movies, and so on.
The electronic readers 104 may be handheld devices or other small, light-weight, portable devices upon which eBooks and other content can be rendered and conveniently viewed in a manner similar to viewing a paper book. Examples of handheld electronic readers include flat form-factor devices such as tablets, pads, smartphones, personal digital assistants (PDAs), etc. The electronic readers 104 may also comprise more traditional computing devices, such as desktop computers, laptop computers, and so forth.
In some embodiments, the electronic readers 104 may comprise dedicated-purpose eBook reader devices, having flat-panel displays and other characteristics that mimic the look, feel, and experience offered by paper-based books. For example, such eBook reader devices may have high-contrast flat-panel displays that appear similar to a printed page and that persist without frequent refreshing. Such displays may consume very negligible amounts of power, so that the eBook reader devices may be used for long periods without recharging or replacing batteries. In some instances, these readers may employ electrophoretic displays.
In the example of
The network 106 may be any type of communication network, including a local-area network, a wide-area network, the Internet, a wireless network, a wide-area network (WAN), a cable television network, a telephone network, a cellular communications network, combinations of the foregoing, etc. Services, sometimes referred to as “cloud-based” services, may be provided from the network 106. In
In the described embodiment, the electronic readers 104 include nonvolatile storage capabilities so that electronic content items can be downloaded and stored in their entirety on the electronic readers. Once an eBook has been stored by an electronic reader, it can be displayed and read at any time, whether or not the electronic reader is connected to a network.
Each electronic reader 104 may be configured with account information corresponding to a particular user 102. Each user may have multiple electronic readers, which may synchronize with each other so that a user may stop reading on a first device and continue reading on a second device, at the same location that the user left off in the first device.
In the configuration illustrated by
In
Various applications and user interfaces may be used in conjunction with the electronic readers 104 to interact with the reader service 108, such as Internet browser programs that allow a user to interactively engage different online services. In addition, the reader service 108 may expose lower-level interfaces or APIs (application programming interfaces) through the network 106, through which devices and programs can access the underlying functionality of the reader service 108 without direct user interaction. For example a user may interactively purchase an eBook or other content item using a personal computer or some device other than the electronic reader device 104. The electronic reader 104 may periodically communicate with the reader service 108 to perform background synchronization or other housekeeping, and may automatically (without specific user intervention) download any content that has been purchased.
The reader service 108 might be implemented in some embodiments by an online merchant or vendor. Electronic books and other electronic content might be offered for sale by such an online merchant, or might be available to members or subscribers for some type of periodic or one-time fee. In some circumstances, eBooks or other content might be made available without charge.
The reader service 108 may in some embodiments include a client interface 110 through which electronic readers 104 and other clients interact with the reader service 108. The client interface 110 may include a virtual storefront or other type of online interface for interaction with consumers and/or devices. The client interface 110 may expose a graphical, web-based user interface that can be accessed by human users to browse and obtain (e.g., purchase, rent, lease, etc.) content items such as eBooks. The client interface may also expose programmatic interfaces or APIs that entities and devices can use to obtain digital content items and related services.
In the described embodiment, the reader service 108 provides one or more of the following services: a content service 112, an annotation service 114, and a position synchronization service 116. Clients such as electronic readers 104 may access or utilize these services through the client interface 110. The reader service 108 may also support additional services, which may also be accessible through client interface 110.
In addition, the reader service 108 provides and/or has access to support services, including storage 118 and a position mapping service 120. The storage 118 may include repositories, databases, cloud-based storage services, electronic memory, and other forms of computer-readable memory. The storage 118 may be utilized by the content service 112 as a content repository to store eBooks and other electronic content for consumption on the reader devices 104. The storage 118 may also be utilized by other services, including the annotation service 114, the position synchronization service 116, and the position mapping service 120.
The annotation service 114 can be accessed through the client interface 110 to provide various types of annotations services to users 102. Depending on the capabilities of the electronic readers 104, users may annotate different items of electronic content. Annotations may include highlights, underlining, comments, ratings, tags, corrections, and other items of information relating to specific locations within the electronic content. The annotations can be stored locally on the electronic readers, but may also be transmitted to the annotation service 114 of the reader service 108. User annotations might be archived by the reader service 108 for various reasons, such as for backup and sharing. For example, a user may at some point delete an annotated eBook from his or her electronic reader 104, and at some later time may re-obtain the same eBook from the reader service 108. Using the annotation service 114, the annotations may have been archived, and may be available for restoration when the user re-obtains the eBook or reloads the eBook onto his or her electronic reader 104. As another example, the annotation service 114 may implement annotation sharing, where annotations from one or more users are shared with one or more other users.
The position synchronization service 116 may be utilized when a user reads a content item on more than one electronic reader 104. For example, a user may begin reading a particular eBook on a first electronic reader, and then move to a second electronic reader to continue reading the same eBook. The position synchronization service 116 can be configured to receive updates from the first electronic reader regarding the last or furthest location accessed by the user within the eBook. When the user opens the same eBook on the second electronic reader, the second electronic reader may query the position synchronization service 116 for this information, and may then automatically navigate within the eBook to the last or furthest location in the eBook that was previously accessed from the first electronic reader.
The position mapping service 120 may be used by the annotation service 114 and the position synchronization service to cross-reference locations between different versions of electronic content. The operation and functionality of position mapping service 120 will be described in more detail below.
Position Mapping
The annotation service 114, the position synchronization service 116, and possibly other types of services deal with information that references particular positions within items of electronic content. Location or position within a particular content item can be indicated in different ways, and different eBook formats often use different metrics to indicate position. In paper-based books, location is usually indicated by page number, and possibly by a line number relative to a page. In eBooks, however, page boundaries are generally undefined, and page divisions vary based on the rendering capabilities and/or settings of the device upon which the eBooks are being rendered. Accordingly, some eBook formats may indicate position in terms of a character or byte index, such as the number of characters or bytes from the beginning of the eBook. Other eBook formats may indicate position in terms of a word index, such as the number of words from the beginning of the eBook. Other measurement quantities can also be used, such as a sentence index, a line index, or a paragraph index. In audio eBooks, location or position may be indicated by a time index—the length of elapsed time from the beginning of an audio eBook.
Other electronic formats may indicate location in more complex ways. For example, in electronic formats utilizing a markup language, location may be specified in terms of markup elements or with respect to unique markup identifiers within the content. For example, location might be specified as an offset from a particular unique identifier within the electronically formatted content. Similarly, in hierarchically arranged content, location might be specified in terms of nodes within the data structures representing the content.
For purposes of discussion, the various methods of indicating location, described above, will be referred to as indexing methods or metrics.
Different versions of a particular eBook can have discrepancies in location indexing, even within a single eBook format. In particular, the addition, deletion, or modification of words, characters, sentences, and paragraphs between versions of an eBook may result in the same word or passage having different position indexes within the respective versions. Furthermore, even versions having seemingly identical content may have differences in location indexing, due to arbitrary file structure differences that are invisible to end users.
The position mapping service 120 can be accessed by other services, such as by the annotation service 114 and the position synchronization service 116, to resolve location indexing discrepancies between different formats and versions. This allows the annotation service 114 and the position synchronization service 116 to correctly specify content positions to electronic readers 104, allowing for different eBook formats and different versions that might be in use on each particular electronic reader 104.
In particular, a component such as the annotation service 114 can submit a query to the position mapping service 120. The query may identify a particular content item, the version of the content item, and a position within the content item. The position mapping service 120 may respond by identifying a list of other versions of the same content item, and the positions within those versions corresponding to the specific position within the specified version/format.
Note that for purposes of explanation, the term “version” will be used herein to indicate a specific revision and eBook format of an electronic content item. Thus, two different “versions” of an electronic content item may vary from each other by content and/or by format. As an example, two different versions may be formatted using the same eBook format, but may have slightly different words or text. Alternatively, two different versions may have identical textual content, but may be formatted in two different eBook formats. For example, one version may be text-based, while another version may be audio-based. As another example, two different versions may comprise the same eBook in different languages.
At 202, the reader service 108 receives a new version 204 of an electronic content item. The new version 204 may be submitted by an author or publisher, using existing procedures implemented by the reader service 108. The version 204 is stored by the reader service 108 in a content repository, which may be implemented using the storage 118.
The new version 204 may be an updated or modified version of an existing version of a content item. It may thus differ from one or more existing versions of the same content item in terms of content, storage format, or both. Content differences between two versions of the same work may range from very minor to relatively significant. For example, differences may consist of mere spelling corrections. More significant differences may involve significant editing or the addition/deletion of entire phrases, sentences, paragraphs, chapters, introductory materials, afterwards, etc. Versions may also differ in format. For example, one version might be formatted as a PDF (portable document format) document, while another is formed as a MOBI (Mobipocket) file. Versions may also vary by language or media. Thus, one version might be in a different language than another version. As another example, one version might comprise a written or text-based eBook, while another version might comprise an audio performance of the same eBook.
At 206, upon receiving the new version 204 of a content item, the position mapping service 120 indexes the words of the new version to indicate positions of words within the new version. More specifically, the position mapping service 120 creates a version-specific word-to-position map 208 corresponding to the new version 204. The word-to-position map 208 is a data object that lists renderable components of the version 204. Renderable components include words and other visual or audio entities such as photographs, tunes, sounds, glyphs, equations, symbols, graphics, charts, and so forth. White-space may be ignored, and omitted from the word-to-position map 208. Formatting characters and strings may also be ignored and omitted.
For each renderable component of the version 204, the word-to-position map 208 also indicates the position of that component relative to the entire version. Position is indicated in accordance with the protocol or format of the version 204, using the index metric specified by the protocol or format of the version 204. For example, some versions may use a format that indicates position by character or byte index, while other versions may use a format that indicates position by word index.
Below version 302 is a corresponding word-to-position map 306. It has a first column 308 that lists the words occurring in version 302. It has a second column 310 that indicates the position of each word. Position is indicated in this example by starting and ending character indexes. Note that the positions may in some cases be discontinuous due to non-renderable characters that have been ignored.
Below version 304 is a corresponding word-to-position map 312. It has a first column 314 that lists the words occurring in version 304. It has a second column 316 that indicates the position within version 304 of every word. Again, position is indicated by starting and ending character indexes.
Returning to
Within the version-to-version position map 320, the positions of words in version 302 are indicated in a left column 322. The positions of corresponding words in version 304 are indicated in a right column 324.
A middle column indicates change metadata, such as correspondence types between the left and right columns. In this example, an “R” indicates that one word has been replaced by another (such as “quick” being replaced by “fast”). An “X” indicates that the word has been deleted from the version 304. An “I” indicates that version 304 contains an inserted or new word. An “M” indicates that there was a match—that the word of the version 302 was matched with a word from the version 304. For words that are simply deleted, the right column 324 is blank. For words that are inserted, the left column 322 is blank.
In some implementations, additional change metadata might be included. In particular, each type of change metadata described above might be accompanied by a confidence factor (“CF”), indicating the confidence with which the determination was made. This indicator might be used for various purposes. For example, if a match or “M” entry has a relatively low CF, human-based analysis might be performed to confirm the match.
For purposes of illustration,
Returning again to
The process of
At 404, the position mapping service 120 locates and accesses a version-to-version position map that corresponds to the first and second specified versions. In particular, the mapping service 120 accesses a version-to-version position map that translates or maps word positions from the first version to the second version. This version-to-version position map may be one of numerous maps that are generated in the procedure 200 of
At 406, the position mapping service uses the appropriate version-to-version position map to find or determine the position in the second version that corresponds to the specified position in the first version. When using a format such as that shown in
At 408, the position mapping service responds to the query by returning the position in the second version that corresponds to the specified position in the first version. The position mapping service may also return any available change metadata, which may comprise a CF indicating the nature of the correspondence indicated by the mapping and the confidence with which the mapping was obtained.
Position-Based Annotation Services
The annotation 504 may be in various formats, and may indicate a variety of information. For example, the annotation may indicate a comment as shown: “Let sleeping dogs lie.” Alternatively, the annotation may indicate some type of action or characteristic, such as a highlight. In addition, the annotation 506 indicates a word position or a range of word positions. The annotation may also indicate the version number of a particular electronic book to which the annotation applies.
At 508, the annotation service 114 submits one or more queries to the position mapping service 120. Each query may specify an electronic book, a particular version of that book, a position within that version, and a target version to which the specified position is to be mapped. The position mapping service 120 responds as described above with reference to
At 510, the annotation servicer 114 associates the received annotations with their corresponding positions within the target version of the electronic book. In some embodiments, the original annotations can be modified by replacing the original position indicator with a new position indicator, specifying position in terms of the target version.
As mentioned, annotations may be formatted in various ways. As one example, a single annotation might be modified to include position indicators for two or more different versions. Thus, rather than replacing the position indicator of an annotation, a second position identifier might be added.
The annotation service 114 may use received annotations in various ways at 516. In some embodiments, annotations may be archived for users of electronic readers. Archived annotations may be restored to the electronic readers from which they were received, or may be restored to other electronic readers. In some situations, the electronic book to which the annotations pertain may exist on a new electronic reader in a version different than the version in which the annotations were originally made. In other situations, the electronic book reader may utilize a different eBook format. The annotation service 114, as described above, may modify the annotations or create new annotations, so that they correspond to the version and format in use on the reader to which the annotations are being supplied.
Annotations received from a particular electronic reader may also be shared with different electronic readers, including readers belonging to other users. Annotations may be received from a plurality of users and electronic readers, and shared collectively with the same users and electronic readers and/or with additional users and electronic readers. The annotation service may also compile statistics or other indirect information from received annotations, and may utilize such information in various ways such as by indicating popular annotations to users who desire to see them.
Position Synchronization Services
At 608, the position synchronization service 116 receives synchronization information from the first electronic reader 604. The synchronization may include various information, including a position indicator corresponding to the furthest or most recent position accessed by the user 602 when reading a particular version of an electronic book using the electronic reader 604. The position indicator uses the indexing method of the first electronic reader 604 and specifies position in terms of the version of the electronic book that is being used on the first electronic reader 604.
Assuming that the second electronic reader 606 has a different version of the electronic book, at 610 the position synchronization service 116 queries the position mapping service 120 to find the position within the second version that corresponds to the last-accessed position in the first version. At 612, this information is sent or provided to the second electronic reader 606. The second electronic reader 606 may then navigate based on this information, and the user can resume reading at the synchronized location.
Example Electronic Reader
In a very basic configuration, the electronic reader 104 includes a processing unit 702 composed of one or more processors, and memory 704. Depending on the configuration of the eBook reader 104, the memory 704 may be a type of computer storage media and may include volatile and nonvolatile memory. Thus, the memory 704 may include, but is not limited to, RAM, ROM, EEPROM, flash memory, or other memory technology, or any other medium which can be used to store media items or applications and data which can be accessed by the electronic reader 104.
The memory 704 may be used to store any number of functional components that are executable on the processing unit 702. In many embodiments, these functional components comprise instructions or programs that are executable by the processing unit 702, and that implement operational logic for performing the actions attributed above to the electronic reader 104. In addition, the memory 704 may store various types of data that are referenced by executable programs.
The memory 704 may store an operating system 706 and content storage 708 to store one or more content items. A user interface module 710 may also be provided in the memory 704 and executed on the processing unit 702 to provide for user operation of the electronic reader 104. The UI module 710 may provide menus and other navigational tools to facilitate selection and rendering of content items. The UI module 710 may further include a browser or other application that facilitates access to sites over a network, such as websites or online merchants, or other sources of electronic content items or other products.
A communication and synchronization module 712 is stored in the memory 704 and executed on the processing unit 702 to perform management functions in conjunction with one or more content sources, such as the content service 108 discussed above. In some embodiments, the communication and synchronization module 712 communicates with the content service 108 to receive eBooks and other content items.
The electronic reader 104 may also include an annotation module 714 allowing a user to enter annotations and to communicate annotations with the annotation service 114, in accordance with the techniques described above. Similarly, the electronic reader 104 may include a position synchronization module 716 that communications with the position synchronization service 116 as described above, to synchronize last-read positions between different electronic readers.
The electronic reader 104 may further include a display 718 upon which electronic books are rendered. In one implementation, the display 718 uses electronic paper display technology. In general, an electronic paper display is one that has a high resolution (150 dpi or better) and is bi-stable, meaning that it is capable of holding text or other rendered images even when very little or no power is supplied to the display. The electronic paper display technology may also exhibit high contrast substantially equal to that of print on paper. Some exemplary electronic paper displays that may be used with the implementations described herein include bi-stable LCDs, MEMS, cholesteric, pigmented electrophoretic, and others. One exemplary electronic paper display that may be used is an E Ink-brand display. Touch sensitive technology may be overlaid or integrated with the electronic paper display technology to enable user input via contact or proximity to the screen.
The electronic reader 104 may further be equipped with various input/output (I/O) components 720. Such components may include various user interface controls (e.g., buttons, joystick, keyboard, etc.), audio speaker, connection ports, and so forth.
A network interface 722 may support both wired and wireless connection to various networks, such as cellular networks, radio, WiFi networks, short range networks (e.g., Bluetooth), IR, and so forth. The network interface 722 facilitates receiving electronic books and other content as described herein.
The electronic reader 104 may also include a battery and power control unit 724. The power control unit operatively controls an amount of power, or electrical energy, consumed by the electronic reader. Actively controlling the amount of power consumed by the electronic reader may achieve more efficient use of electrical energy stored by the battery.
The electronic reader 104 may have additional features or functionality. For example, the electronic reader 104 may also include additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. The additional data storage media may include volatile and nonvolatile, 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.
Example Server
In a very basic configuration, an example server 800 may comprise a processing unit 802 composed of one or more processors, and memory 804. Depending on the configuration of the server 800, the memory 804 may be a type of computer storage media and may include volatile and nonvolatile memory. Thus, the memory 804 may include, but is not limited to, RAM, ROM, EEPROM, flash memory, or other memory technology.
The memory 804 may be used to store any number of functional components that are executable by the processing unit 802. In many embodiments, these functional components comprise instructions or programs that are executable by the processing unit 802, and that when executed implement operational logic for performing the actions attributed above to the content service 108. In addition, the memory 804 may store various types of data that are referenced by executable programs, including content items that are supplied to consuming devices such as electronic reader 104.
Functional components stored in the memory 804 may include an operating system 806 and a database 808 to store content items, annotations, maps, etc. Functional components of the server 800 may also comprise a web service component 810 that interacts with remote devices such as computers and media consumption devices.
The server 800 may of course include many other logical, programmatic, and physical components, generally referenced by numeral 812, of which those described above are merely examples that are related to the discussion herein.
Note that the various techniques described above are assumed in the given examples to be implemented in the general context of computer-executable instructions or software, such as program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. for performing particular tasks or implement particular abstract data types.
Other architectures may be used to implement the described functionality, and are intended to be within the scope of this disclosure. Furthermore, although specific distributions of responsibilities are defined above for purposes of discussion, the various functions and responsibilities might be distributed and divided in different ways, depending on particular circumstances.
Similarly, software may be stored and distributed in various ways and using different means, and the particular software storage and execution configurations described above may be varied in many different ways. Thus, software implementing the techniques described above may be distributed on various types of computer-readable media, not limited to the forms of memory that are specifically described.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as illustrative forms of implementing the claims. For example, the methodological acts need not be performed in the order or combinations described herein, and may be performed in any combination of one or more acts.
This is a continuation application which claims priority to commonly assigned, co-pending U.S. patent application Ser. No. 12/980,015, filed Dec. 28, 2010. Application Ser. No. 12/980,015 is fully incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
4884974 | DeSmet | Dec 1989 | A |
5166664 | Fish | Nov 1992 | A |
5802204 | Basehore | Sep 1998 | A |
5907845 | Cox et al. | May 1999 | A |
5960464 | Lam | Sep 1999 | A |
5986690 | Hendricks | Nov 1999 | A |
6047093 | Lopresti et al. | Apr 2000 | A |
6074093 | Anderson | Jun 2000 | A |
6108688 | Nielsen | Aug 2000 | A |
6138129 | Combs | Oct 2000 | A |
6173251 | Ito et al. | Jan 2001 | B1 |
6218982 | Shirai et al. | Apr 2001 | B1 |
6377945 | Risvik | Apr 2002 | B1 |
6480838 | Peterman | Nov 2002 | B1 |
6622624 | Divine et al. | Sep 2003 | B1 |
6658626 | Aiken | Dec 2003 | B1 |
6704733 | Clark et al. | Mar 2004 | B2 |
6741985 | Green | May 2004 | B2 |
6898307 | Harrington | May 2005 | B1 |
7020654 | Najmi | Mar 2006 | B1 |
7020663 | Hay et al. | Mar 2006 | B2 |
7028258 | Thacker et al. | Apr 2006 | B1 |
7350143 | Elazar et al. | Mar 2008 | B2 |
7702655 | Panelli et al. | Apr 2010 | B1 |
7823127 | Zeidman | Oct 2010 | B2 |
8051088 | Tibbetts et al. | Nov 2011 | B1 |
8149217 | Yeung et al. | Apr 2012 | B2 |
8229912 | Downum et al. | Jul 2012 | B2 |
8250065 | Chambers et al. | Aug 2012 | B1 |
8266115 | Park et al. | Sep 2012 | B1 |
8280640 | Levin et al. | Oct 2012 | B2 |
8316032 | Baluja et al. | Nov 2012 | B1 |
8463790 | Joshi et al. | Jun 2013 | B1 |
8495061 | Lifantsev | Jul 2013 | B1 |
8510312 | Thibaux et al. | Aug 2013 | B1 |
8798366 | Jones et al. | Aug 2014 | B1 |
9049398 | Moscovich et al. | Jun 2015 | B1 |
9058067 | Van Schaack et al. | Jun 2015 | B2 |
9286392 | Downum et al. | Mar 2016 | B2 |
9690758 | Pyo | Jun 2017 | B2 |
20020021838 | Richardson et al. | Feb 2002 | A1 |
20020049781 | Bengtson | Apr 2002 | A1 |
20020091584 | Clark et al. | Jul 2002 | A1 |
20020107735 | Henkin et al. | Aug 2002 | A1 |
20020123994 | Schabes et al. | Sep 2002 | A1 |
20030032010 | Selifonov et al. | Feb 2003 | A1 |
20030093427 | Hsu et al. | May 2003 | A1 |
20030103238 | MacLean et al. | Jun 2003 | A1 |
20030130994 | Singh et al. | Jul 2003 | A1 |
20040068471 | Kato | Apr 2004 | A1 |
20040088165 | Okutani et al. | May 2004 | A1 |
20040090390 | Mason et al. | May 2004 | A1 |
20040194021 | Marshall | Sep 2004 | A1 |
20040205540 | Vulpe et al. | Oct 2004 | A1 |
20040218205 | Irwin et al. | Nov 2004 | A1 |
20050060273 | Andersen et al. | Mar 2005 | A1 |
20050096938 | Slomkowski et al. | May 2005 | A1 |
20050097007 | Alger et al. | May 2005 | A1 |
20050131932 | Weare | Jun 2005 | A1 |
20050138551 | Elazar et al. | Jun 2005 | A1 |
20050160355 | Cragun | Jul 2005 | A1 |
20050160356 | Albornoz et al. | Jul 2005 | A1 |
20050190397 | Ferlitsch | Sep 2005 | A1 |
20050192955 | Farrell | Sep 2005 | A1 |
20050196074 | Deere | Sep 2005 | A1 |
20050198070 | Lowry | Sep 2005 | A1 |
20050209989 | Albornoz et al. | Sep 2005 | A1 |
20060036593 | Dean et al. | Feb 2006 | A1 |
20060036934 | Fujiwara | Feb 2006 | A1 |
20060041590 | King et al. | Feb 2006 | A1 |
20060064435 | Firstbrook et al. | Mar 2006 | A1 |
20060150096 | Thacker et al. | Jul 2006 | A1 |
20060156226 | Dejean et al. | Jul 2006 | A1 |
20060173818 | Berstis et al. | Aug 2006 | A1 |
20060262340 | Lee | Nov 2006 | A1 |
20060277167 | Gross et al. | Dec 2006 | A1 |
20060294094 | King et al. | Dec 2006 | A1 |
20070061582 | Ohmori et al. | Mar 2007 | A1 |
20070061755 | Taboada et al. | Mar 2007 | A1 |
20070150443 | Bergholz | Jun 2007 | A1 |
20070180381 | Rice et al. | Aug 2007 | A1 |
20070196015 | Meunier et al. | Aug 2007 | A1 |
20070217692 | Newcomer et al. | Sep 2007 | A1 |
20070217715 | Newcomer et al. | Sep 2007 | A1 |
20070274704 | Nakajima et al. | Nov 2007 | A1 |
20070280072 | Hsieh et al. | Dec 2007 | A1 |
20070286465 | Takahashi et al. | Dec 2007 | A1 |
20080019430 | Suzuki et al. | Jan 2008 | A1 |
20080021880 | Ren et al. | Jan 2008 | A1 |
20080027916 | Asai et al. | Jan 2008 | A1 |
20080077570 | Tang et al. | Mar 2008 | A1 |
20080114757 | Dejean et al. | May 2008 | A1 |
20080126335 | Gandhi et al. | May 2008 | A1 |
20080134023 | Aizawa | Jun 2008 | A1 |
20080141117 | King et al. | Jun 2008 | A1 |
20080154943 | Dreyer et al. | Jun 2008 | A1 |
20080163039 | Ryan et al. | Jul 2008 | A1 |
20080209314 | Sylthe et al. | Aug 2008 | A1 |
20080229182 | Hendricks et al. | Sep 2008 | A1 |
20080235579 | Champion et al. | Sep 2008 | A1 |
20080243842 | Liang et al. | Oct 2008 | A1 |
20080275871 | Berstis et al. | Nov 2008 | A1 |
20080279416 | Lo et al. | Nov 2008 | A1 |
20080294453 | Baird-Smith et al. | Nov 2008 | A1 |
20090012984 | Ravid et al. | Jan 2009 | A1 |
20090027419 | Kondo et al. | Jan 2009 | A1 |
20090049026 | Ohguro | Feb 2009 | A1 |
20090063557 | MacPherson | Mar 2009 | A1 |
20090144277 | Trutner et al. | Jun 2009 | A1 |
20090164312 | Nadig | Jun 2009 | A1 |
20090182728 | Anderson | Jul 2009 | A1 |
20090204893 | Nguyen et al. | Aug 2009 | A1 |
20090241054 | Hendricks | Sep 2009 | A1 |
20090254810 | Mitsui | Oct 2009 | A1 |
20090265321 | Grubb et al. | Oct 2009 | A1 |
20090267923 | Van Schaack et al. | Oct 2009 | A1 |
20090310408 | Lee et al. | Dec 2009 | A1 |
20090313539 | Ota et al. | Dec 2009 | A1 |
20090324096 | Megawa | Dec 2009 | A1 |
20100088584 | Pangrazio, III et al. | Apr 2010 | A1 |
20100114827 | Pearce | May 2010 | A1 |
20100166309 | Hull | Jul 2010 | A1 |
20100198864 | Ravid et al. | Aug 2010 | A1 |
20100205160 | Kumar et al. | Aug 2010 | A1 |
20100220216 | Fishman et al. | Sep 2010 | A1 |
20100251089 | Cole et al. | Sep 2010 | A1 |
20100262454 | Sommer et al. | Oct 2010 | A1 |
20100287150 | Downum et al. | Nov 2010 | A1 |
20110029491 | Joshi et al. | Feb 2011 | A1 |
20110078152 | Forman et al. | Mar 2011 | A1 |
20110119240 | Shapira | May 2011 | A1 |
20110153330 | Yazdani | Jun 2011 | A1 |
20110173445 | Yami et al. | Jul 2011 | A1 |
20110231474 | Locker et al. | Sep 2011 | A1 |
20120036431 | Ito et al. | Feb 2012 | A1 |
20120060082 | Edala et al. | Mar 2012 | A1 |
20120121195 | Yadid et al. | May 2012 | A1 |
20120198330 | Koppel et al. | Aug 2012 | A1 |
20120284250 | Downum et al. | Nov 2012 | A1 |
20140298167 | Jones et al. | Oct 2014 | A1 |
Number | Date | Country |
---|---|---|
2009205248 | Sep 2009 | JP |
Entry |
---|
“How do I use the Migrate Comments Command?”, The Same Page, Retrieved Feb. 17, 2017 from http://blogs.adobe.com/thesamepage/2009/05/how_do_i_use_the_migrate_comme.html, 2 pgs. |
Office action for U.S. Appl. No. 13/048,426, dated Jan. 14, 2016, Weight et al., “Identifying Book Title Sets”, 26 pages. |
Office action for U.S. Appl. No. 12/980,015, dated Jan. 21, 2016, Weight et al., “Book Version Mapping”, 40 pages. |
Office action for U.S. Appl. No. 12/980,015, dated Nov. 17, 2016, Weight et al., “Book Version Mapping”, 27 pages. |
Office action for U.S. Appl. No. 13/048,426, dated Nov. 18, 2013, Weight, et al., “Identifying Book Title Sets”, 18 pages. |
Office action for U.S. Appl. No. 13/050,829, dated Nov. 29, 2012, Hamaker et al.,“Aligning Content Items to Identify Differences”, 24 pages. |
Office Action for U.S. Appl. No. 12/979,971, dated Dec. 6, 2013, Derek T. Jones, “Electronic Book Pagination”, 13 pages. |
Office Action for U.S. Appl. No. 14/308,914 dated Mar. 6, 2017, Jones et al, “Electronic Book Pagination”, 18 pages. |
Office action for U.S. Appl. No. 13/048,426, dated Mar. 7, 2017, Weight et al., “Identifying Book Title Sets”, 7 pages. |
Office action for U.S. Appl. No. 13/048,426, dated Apr. 1, 2013, Weight et al., “Identifying Book Title Sets”, 23 pages. |
Office action for U.S. Appl. No. 12/979,971, dated Apr. 18, 2013, Jones et al., “Electronic Book Pagination”, 30 pages. |
Final Office Action for U.S. Appl. No. 12/980,015, dated May 19, 2017, Christopher F. Weight, “Book Version Mapping”, 30 pages. |
Non-Final Office Action for U.S. Appl. No. 13/050,829, dated May 8, 2012, Janna Hamaker et al., “Aligning Content Items to Identify Differences”, 20 pages. |
Final Office Action for U.S. Appl. No. 12/980,015, dated May 9, 2014, Christopher F. Weight, “Book Version Mapping”, 30 pages. |
Office action for U.S. Appl. No. 13/048,426, dated Jun. 19, 2014, Weight et al., “Identifying Book Title Sets”, 23 pages. |
Office Action for U.S. Appl. No. 14/308,914 dated Jul. 14, 2017, Jones et al, “Electronic Book Pagination”, 22 pages. |
Office Action for U.S. Appl. No. 12/980,015, dated Jul. 7, 2015, Christopher F. Weight, “Book Version Mapping”, 32 pages. |
Office action for U.S. Appl. No. 12/979,971, dated Aug. 8, 2013, Jones et al., “Electronic Book Pagination”, 32 pages. |
Office action for U.S. Appl. No. 12/980,015, dated Sep. 10, 2013, Weight et al., “Book Version Mapping”, 27 pages. |
Office action for U.S. Appl. No. 13/050,829, dated Sep. 30, 2014, Hamaker et al., “Aligning Content Items to Identify Differences”, 30 pages. |
Office action for U.S. Appl. No. 13/048,426, dated Sep. 8, 2016, Weight et al., “Identifying Book Title Sets”, 8 pages. |
Wikipedia, “Lookuptable”, at http://en.wikipedia.org/w/index.php?title=Lookup_table&oldid_333018082, retrieved on Aug. 2, 2013, 2009, 7 pages. |
Wikipedia, “Metadata”, at http://en.wikipedia.org/w/index.php?title=Metadata&oldid=333583065, retrieved on Aug. 2, 2013, 2009, 17 pages. |
Number | Date | Country | |
---|---|---|---|
Parent | 12980015 | Dec 2010 | US |
Child | 15810510 | US |