Sequence diagrams
This diagram shows the sequence of actions ending with encrypted content stored in a file system, with a notification sent to the License Server.
The main corresponding use case is a reading system (e.g. a mobile app) interacting with a frontend REST API.
This diagram shows the sequence of actions starting from a user transaction (a loan for instance) and ending with the opening of the downloaded ebook by the device. A Readium LCP license is loaded first, then the corresponding encrypted epub content is downloaded silently, the license is included in the epub archive and the resulting licensed publication is saved by the app. The epub content can then be read, after the user passphrase has been entered (not shown in the diagram).
The main corresponding use case is a user interacting with a frontend Web interface.
This diagram shows the sequence of actions starting from a user transaction (a loan for instance) and ending with the opening of the downloaded ebook by the device.
This diagram shows the sequence of actions necessary to register a device for a given license, if the device has not been registered before. In this sequence, we suppose the the initial status is "ready", meaning that no device has been registered. Once the first device is registered, the status becomes "active".
This diagram shows the update of a license, after the user device has checked that the date of update of the license in the status document is more recent than the value saved locally.
This diagram shows the sequence of actions necessary when a user wants to return an ebook to a public library.
The same sequence applies to loan extension.
This diagram illustrates what happens when a provider decides to revoke a license. Once again, this should only happen if the license has been clearly overshared by the user (e.g. with more than 100 devices registered for the license in a short period).
