UseCase Directory

Note: This is a dated set of use cases. Please see Portable Web Publications Use Cases and Requirements for the latest version of use cases. This page is the TOC of the use case collection. All uses cases added are linked to from this page.

If you are about to add a new use case, start by creating a new page, and then clone the template as a starting point.

Use cases that are in need of further analysis and/or expert input are marked below with a INPUT NEEDED suffix. If you are an expert in the area, you should help us out!

Styling and Layout

Lists

Lists

Pagination

Tables_1

Adaptive Layout

Device Adaption

Tables_1

User Adaption

Positioning

• NakaTobira_01 INPUT NEEDED

Domain-Specific Content Types

STEM

• MathML use cases: MathML 1, MathML 2, MathML 3, Computational MathML
• Chemistry UC
• Diagrams and Graphing UC
• Tables_1
• Lists

Assessments

Infographics

Comics/Manga

Identifiers

Metadata

Publication-level

• Discovery of accessible EPUBs
• Provenance of Digital Publications

Resource/fragment-level

• Book Semantics 1

Content & Markup

Structural Semantics

• Index1
• Index2
• Index3
• Notes1
• User added dictionary

Other

• MediaSpecificMarkup
• ScrollDirection
• ContinuousSound
• Tables_1
• User directed styling modifications (font family)

Interaction

• MathML 2
• MathML 3

Accessibility and Personalization

WCAG 2.0 & Education Environment / Educational Publishing

• Timed Tests and Activities
• Mirroring Source Materials
• Still View of Moving Content
• What is "Loss of functionality" for a reading experience (need to scroll horizontally)

Pre-School through Middle School

• Captions & Early Readers
• When students are too young to judge how much additional time they might need (or the activity is too new/innovative)

Specialized Subject Areas (e.g. Chemistry, Grammar, Poetry)

(Can include providing authors with ability to polish pronunciations, pauses and stresses, as well as solutions such as subject-specific markup.)

• When implementations are tested, they might be tested with simpler content than what publishers need to use. Publishers should be able to submit samples to a test suite for verifying subject-specific readiness.

Allowing Versions

(versions & third-party, second-party or first-party patches.)

• Allow Different Math Pronunciations
• Facilitate Post Production Crowdsourcing of SVG Descriptions
• A publisher uses the latest WAI-ARIA and good semantics to make an interactive widget accessible on many assistive technologies, but there's a catch 22 as a key technology has a bug. (For example, VoiceOver doesn't handle merged table cells well currently.) Having identified the issue, a publisher wants to easily send a different version to the problematic assistive technology.
• A 3rd party wants to provide improve the accessibility of an interactive widget
  • https://github.com/idpf/widgets
• In an environment where accessibility has been customized, a publisher's customer support technical team needs to quickly identify the version in use and get detail on the reasons for the version, where it was tested, etc.
• In an environment where content is generated through crowdsourcing, a graduate student (for example) who uses assistive technology needs clear identification of the source of the content they receive and to be able to allow/disallow content depending on the source, at their own discretion.

General Accessibility Use Cases (including Math)

• Contextual Vocabulary for Augmentative and Alternative Communication Users
• Highlighting Text: Accessibility & Find-ability in Long Works (was Accessing Highlights and Related Notes with a Screen Reader or Using a Small Screen)
• Rendering of Accessible Mathematics with SVG as an Alternative to MathML
• Sonification of SVG Graphs
• Structural Descriptions in SVG
• Media-Query Print Stylesheet Like Functionality for SVG
• SVG reuse within pages, across pages and across titles
• Support for multiple languages or versions for image descriptions
• Publishers and content remixers would like to keep image descriptions and pointers to alternatives packaged together with images regardless of image format (e.g. PNG) for portability and reuse reasons
• A user wants to be able to find the simplified language version of an image description
• A users wants to read a short image description prior to listening to a longer and more detailed description
• A user wants a tour of a tactile graphic
• A user wants high quality braille transcription of the content of a publication
• Dyslexic users want synchronized word-level highlighting and TTS for text, structured content and math without having to use traditional assistive technology
  • Need to look at media overlays EPUB use cases and features
• A user wants to be able to search for accessible content based on their needs and preferences and reading system requirements.
• A users wants to know if a reading system supports the accessibility features provided by the content they are trying to access.
• Standard Alternative Text Templates for Image Types: Consider that students learn what, for example, a pie chart is in class and later use pie charts. For sighted students, there are standard elements in these images.

Personalization

• Adjustable Fonts
• Adjustable Line Height and Length
• Adjustable Text Alignment
• Adjustable Background and Contrast
• Zoom Control
• Rendition Control
• Initial Collection of Existing Efforts

User Descriptions

• ReadingDisorder
• Dyslexia
• CerebralPalsy

Internationalization

Layout

• NakaTobira_01 INPUT NEEDED

Social Reading and Annotations

Use Cases Targeting Full Publication

• Comment on Publication Title
• Tagging a Publication
• Structured Review of a Publication
• Private Comment on Publication Title
• Comment separate from Annotation

Use Cases Targeting Specific Segments

• Bookmarking current reading position
• Highlighting a span of text
• Commenting on a span of text
• Annotating embedded resources
• Annotating parts of embedded resources
• Annotating alt text of embedded resources
• Comparison annotations within a publication
• Comparison annotations between publications

Advanced Use Cases

• Cross format annotations
• Cross version annotations
• Maintaining annotation style
• Maintaining annotation layout
• Recording State of dynamic resources
• Recording State of user manipulated resources
• Annotation has multiple, independent bodies
• Annotation has a choice of multiple, dependent bodies
• Annotation relevance after target is modified

Annotation Packages

• Annotations supplied with publication
• Third party commentary

Annotation Publication

• Persistence of Annotations
• User or System Initiated Transfers between systems
• Annotation (or part) is not published openly
• Publication (or part) is not published openly

Other Use Cases

• Specifying target audience for annotation (or part)
• Using annotation for contributing accessibility information
• Making sure the annotations can be found
• Making sure the annotations can be categorized

Packaging and Distribution

• Publication with Data
• Publication with Interactive Data
• Publication plus Annotations
• Items with Shared Resources
• Streamlined Access to Disjoint Package Components
• Manifest Includes Information about New Content
• Overview of OCF Functionality
• Access Control and selective encryption
• Functional Requirements

Publishing Workflow Effectiveness

• Transclusion_01

DRM

• DRM-1
• DRM-2

Security

Pagination/DOM interaction

• Page representation in the DOM
• Showing a specific page of content
• Showing more than one page of content
• Determine what page a particular element appears on
• Specify how pages are referenced
• Define events to notify when a page is ready/visible
• Functional Requirements for Pagination