Diagrams and Graphing UC

From Digital Publishing Interest Group
Jump to: navigation, search

Diagrams 1

Use case
A publisher wants to provide diagrammatic content. For example, an electrical engineering publisher wants to provide electrical diagrams, a computer-science publisher wants to provide UML diagrams, a physics publisher wants to provide Feynman diagrams. A user wants to access this content on all screen sizes and via accessibility tools.
Requirement(s)
1) There is a way to render diagrammatic content
2) There is a way to script interactive elements
3) There is a way to connect to server for computational enhancements
4) There is a way to embed the underlying semantics
5) There is a way for accessibility tools to access the embedded semantics
Stakeholder(s)
PUBLISHERS-STEM, USERS-ALL, USERS-A11Y
Ranking
TBD
Relations/dependencies
N/A
Relevant W3C group(s)/specification(s)
SVG, HTML, CSS, WebApps
Comments
Submitted by
Peter Krautzberger
Status
NEW


Data Plots 1

Use case
A publisher wants to provide content represented as data plots. For example, a life science publisher wants to provide rendering of experimental data. A mathematical publisher wants to provide plots of basic mathematical functions. A user wants to access this content on all screen sizes and via accessibility tools.
Requirement(s)
1) There is a way to embed and plot the data.
2) There is a way for the user to switch rendering modes (e.g. box plot to scatter plot)
3) There is a way for accessibility tools to access the embedded semantics
Stakeholder(s)
PUBLISHERS-STEM, USERS-ALL, USERS-A11Y
Ranking
TBD
Relations/dependencies
N/A
Relevant W3C group(s)/specification(s)
SVG, HTML, CSS, WebApps
Comments
Submitted by
Peter Krautzberger
Status
NEW

Graphs 1

Use case
A publisher wants to provide content represented as graphs. For example, a life science publisher wants to provide rendering of protein-DNA/protein-portein interaction graphs, regulatory networks etc. An informatics publisher wants to provide rendering of database structures, computational networks etc. A user wants to access this content on all screen sizes and via accessibility tools.
Requirement(s)
1) There is a way to encode graphs (e.g., [1]).
2) There is a way to embed the underlying semantics
3) There is a way for accessibility tools to access the embedded semantics
Stakeholder(s)
PUBLISHERS-STEM, USERS-ALL, USERS-A11Y
Ranking
TBD
Relations/dependencies
N/A
Relevant W3C group(s)/specification(s)
SVG, HTML, CSS
Comments
Submitted by
Peter Krautzberger
Status
NEW