UseCase Template

This page contains a template for the use case/requirement corpus.

Each use case is added as a separate wiki page, and the linked to from the TOC page.

Template

(ID/title of page)

Use case

Plain english scenario which specifies relevant actors and intended/desired flow of events

Requirement(s)

List of requirements drawn from the above use case

Stakeholder(s)

Always uses one of the predefined values PUBLISHERS-ALL, PUBLISHERS-STEM, USERS-ALL, USERS-A11Y, RETAILERS, IMPLEMENTERS. New values will be added to this space as they are needed.

Ranking

Ranking will be done as a separate activity later. For now, leave this field as 'TBD'

Relations/dependencies

Optional, links to other entries in the corpus

Relevant W3C group(s)/specification(s)

Where the target WG/spec is obvious, specify it

External relevant group(s)/specification(s)

Where there are external groups/specifications that address on this problem in whole or part

Comments

Any additional info (clarifications, etc)

Submitted by

name of author of the use case

Status

Always uses one of the values NEW | REJECTED | ACCEPTED

Examples

ANNO-1234

Use case

A publisher of geography books in education supplies an online repository of annotations for their content. Users are able to import these annotations for use in their Reading System, and can at import time supply information about their preferences so that the supplied annotations can be personalized, e.g. for a person with low vision or dyslexia, an annotation of a complex map would have detailed textual information about regions in the map; another person might instead import annotations that contain extra-curricular information about the regions in the map.

Requirement(s)

1) Annotations are able to target spatial regions of objects

2) There is a standardized way to encode and exchange user preferences for personalization purposes

Stakeholder(s)

PUBLISHERS-ALL, USERS-A11Y

Ranking

TBD

Relations/dependencies

FOO-001 and BAR-007 also relate to personalization.

Relevant W3C group(s)/specification(s)

PF, OA

Comments

Submitted by

Joe

Status

NEW

ADPT-1234

Use case

A publisher of high design magazines supplies multiple renditions/facets of the same publication as one unit, and has the content and layout of these vary depending on device characteristics and/or user preferences. For example, a magazine publisher provides one publication in which the default rendition is fixed-layout/pre-paginated and includes lots of graphical material, and a secondary rendition which is reflowable and excludes most of the image material.

Requirement(s)

1) There is a way at runtime to reuse documents and fragments of documents through transclusion.

2) There is a way to at runtime have transclusions depend on conditions such as device characteristics and user preferences

Stakeholder(s)

PUBLISHERS-ALL

Ranking

TBD

Relations/dependencies

N/A

Relevant W3C group(s)/specification(s)

HTML5, SVG2, CSS

Comments

Submitted by

Joe

Status

NEW