The document discusses the design of a declarative language called RVL for visualizing RDFS/OWL data. It summarizes an analysis of visualization literature and 7 ontologies across 3 domains that identified common graphic representations and 12 visualization cases. From this, 14 language requirements for RVL were deduced, such as allowing multiple visual structures and ensuring platform independence. The key constructs of RVL are then described, including property mappings and value mappings to define how ontology properties and values are mapped to graphic properties and values.
Unleash Your Potential - Namagunga Girls Coding Club
RVL language for visualizing RDFS/OWL data
1. HTWK Leipzig / IMN ; TU Dresden / SMT / Softwaretechnology Group
Towards RVL: a Declarative Language
for Visualizing RDFS/OWL Data
HSWI Workshop at WIMS ‘13, June 14th 2013
Jan Polowinski (jan dot polowinski at tu-dresden dot de)
2. Clarification – What do we mean by „Visualizing“?
• Not: Structuring data into
textual documents +
Formatting / Styling
2/30
• But: Visual encoding:
Define what data relations
correspond to what graphic
relations
Source: http://www.w3.org/2005/04/
fresnel-info/manual/#foafExample
3. Overall Goal: Reusable, Shareable Visual Mappings
3/30
Visualization authors can
share and reuse „good“
visualization settings and
take their settings to other
tools!
Visualization
Author
Author of a domain ontology (just finished modelling)
Domain ontology authors can
propose visualization settings!
4. 4/30
Outline
• Principle of RVL
• Analysis: Requirements of RVL (Summary)
• Main constructs
• Composition
• Open Issues
• (Prototype RVL editors)
5. The Principle of RVL
Based on RDFS/OWL
itself
WIMS '13, Madrid, 28.06.13 RVL: A Language for RDFS/OWL Visualisation 5/30
6. Summary of the Analysis Preceeding the
Design of RVL
6/30
Analysis of
• 3 domains: Life sciences, software requirements, publication
• 7 ontologies
• Frequently used concepts
7. Summary of the Analysis Preceeding the
Design of RVL
7/30
Analysis of Visualisation Literature ..
• Graphic concepts + relations
• Formalized as ontology:
http://purl.org/viso/graphic/
8. Summary of the Analysis Preceeding the
Design of RVL
8/30
Analysis for ...
• Common graphic
representations
• Identification of 12
Visualisation Cases (VC)
9. Summary of the Analysis Preceeding the
Design of RVL
9/30
Examples for Visualization Cases:
• VC1 - Create a graphic object per resource.
• VC2 - Map to Graphic Attributes.
• VC5 - Define simple interactions.
• VC10 - Draw legends and labeled axes.
• VC11 - Define styles.
10. Summary of the Analysis Preceeding the
Design of RVL
10/30
Deduction of 14 Language Requirements (LR)
• Examples ...
11. • LR-2: Multiple Visual Structures
11/30
Examples of Concrete Language Requirements:
WIMS '13, Madrid, 28.06.13 RVL: A Language for RDFS/OWL Visualisation
12. • LR-2: Multiple Visual Structures
• LR-6: Platform Independence
12/30
Examples of Concrete Language Requirements:
WIMS '13, Madrid, 28.06.13 RVL: A Language for RDFS/OWL Visualisation
13. • LR-2: Multiple Visual Structures
• LR-6: Platform Independence
• LR-12: Composability of Mappings
13/30
Examples of Concrete Language Requirements:
29. Value Mappings
• Simple case: 1-to-1 explicit,
manual mapping of discrete
values
• Calculated value mappings
• Default: map whole range of
source values to the whole range
of target values
• Source and target values can be
refined ...
1
00
44. Value Mappings
• Simple case: 1-to-1 explicit,
manual mapping of discrete
values
• Calculated value mappings
• Default: map whole range of
source values to the whole range
of target values
• Source and target values can be
refined ...
• Order / Scale of measurement
can be re(de)fined ...
1
00
59. RVL – Main Constructs
UML-Style Class Diagramm (simplified)
20/30
60. WIMS '13, Madrid, 28.06.13 RVL: A Language for RDFS/OWL Visualisation
61. Composition of Visual Mappings
21/30
• Simultaneous Composition
• Mappings all applied independently
• Trivial, except perceptional constraints (!)
• Context Composition
• Mapping only applies for a specific context
• Created by another mapping
WIMS '13, Madrid, 28.06.13 RVL: A Language for RDFS/OWL Visualisation
80. Which Visualisation Cases are Covered?
Most, except:
• Interaction
Ideas exist
• Complex „Standard“ Graphics
• Example: How to describe a TreeMap and the associated
algorithms?
• Reference a concept „TreeMap“?
• Keep flexibility of composition Current focus
• Integration of Formatting and Styling
Fresnel + CSS
WIMS '13, Madrid, 28.06.13 RVL: A Language for RDFS/OWL Visualisation 34/30
81. Summary
• We introduced a novel Language for visualizing RDFS/OWL data
• Rich capabilities to describe visual encodings
• Itself based on Semantic web standards
à Mappings have URIs
• Defaults allow for quickly handling common situations
• Design driven by concrete mapping situations
• Many mapping situations already covered
• Multitude of domains suggests some universality
WIMS '13, Madrid, 28.06.13 RVL: A Language for RDFS/OWL Visualisation 35/30
82. Future Work
• Further evaluate RVL
Tooling
WIMS '13, Madrid, 28.06.13 RVL: A Language for RDFS/OWL Visualisation 36/30
83. Two Prototypes for RVL Editing ...
WIMS '13, Madrid, 28.06.13 RVL: A Language for RDFS/OWL Visualisation 37/30
86. Future Work
• Further evaluate RVL
Tooling
• Cover remaining visualisation cases
40/30
87. Thank you for your attention!
http://purl.org/rvl/
jan dot polowinski at tu-dresden dot de
PLEASE DISCUSS HERE OR
OFFLINE:
Schema of RVL
Relation to Fresnel
Advanced mapping compositions
41/30
BACKUP SLIDES à
88. Acknowledgements
• This research has been co-funded by the European Social Fond / Free State of Saxony,
contract no. 80937064 and 1330674013 (eScience – network).
42/26
BACKUP SLIDES à
91. Graphic Attributes and Graphic-Object-to-Object-
Relations
Graphic Attributes (GA)
• Lightness, Shape, Size, Named Colors
Graphic-Object-to-Object-
Relations (GOTOR)
• Linking Undirected
• Relative Position
• Separation by a Separator
à Formalised as
VISO Ontology
http://purl.org/viso/ 45/30
92. B0#-!)E.;(=(
I'-*!***(DJ(
How to visualise beyond node-link diagrams?
Types
B0#-!)E.;(
F(
B0#-!)E.;(
G(
B0#-!)E.;(
H(
B0#-!)E.;(D(
B0#-!)E.;(
C(
B0#-!)E.;(=(
A builds on B …
B0#-!)E.;(D(
B0#-!)E.;(C(
I!.;K%+*(=L(
!%-EM*(DJ(
can be seen as an area
connector
46/30
C#)**( D../(=(
D../(=(
115. RVL Schema
• What is a valid Mapping in RVL?
• SPIN Constraints used to describe Attributes, Defaults, ...
• Cardinality CS
• Type CS
• What is an effective mapping?
• Consistent handling of constraints which are based on VISO/facts is possible
49/30