0
Designing a GUI Description
 Language with Topic Maps
       Lukas.Georgieff@hotmail.com
 University of Applied Sciences W...
Topic Maps (1)
• “Information wants to be free“
• “Information wants to be a topic map“




30/09/2010          Lukas Geor...
Topic Maps (2)
• “Information wants to be free“
• “Information wants to be a topic map“




30/09/2010          Lukas Geor...
Topic Maps (3)
• “Information wants to be free“
• “Information wants to be a topic map“




30/09/2010          Lukas Geor...
Topic Maps (4)
• “Information wants to be free“
• “Information wants to be a topic map“
       Why?
       – TM models arb...
Topic Maps (5)
       What to do?




30/09/2010           Lukas Georgieff - TMRA 2010 - GDL   6
GDL (1)
 GUI Description Language, a TM ontology


• Goals
       –     Generic UI adapted to a specific domain
       – ...
GDL (2)




30/09/2010   Lukas Georgieff - TMRA 2010 - GDL   8
GDL – Features (1)
• Defines default values
             e.g. PSIs regexp: “http://some.where/psis/author/.+“
• Allows to ...
GDL – Features (2)
• Allows individual layout of TM-constructs
  corresponding to semantic meaning/domain
             e.g...
GDL – Features (3)




30/09/2010      Lukas Georgieff - TMRA 2010 - GDL   11
GDL – Features (4)




30/09/2010     Lukas Georgieff - TMRA 2010 - GDL   12
GDL – Features (5)




30/09/2010     Lukas Georgieff - TMRA 2010 - GDL   13
GDL - Problems
• GDL inserts a new layer between the end user and
  the TM-engine
       –     Additional processing of th...
Conclusions
• GDL builds a bridge between the end-user and the
  TM-internals
• GDL does not limit TM/ontology
• GUI is no...
Thank you for your attention!




30/09/2010             Lukas Georgieff - TMRA 2010 - GDL   16
Upcoming SlideShare
Loading in...5
×

Designing a GUI Description Language with Topic Maps

780

Published on

This paper presents the concepts of a description language to be created to design a graphical user interface (GUI) for specific ontologies defined in Topic Maps.

Published in: Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
780
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Designing a GUI Description Language with Topic Maps"

  1. 1. Designing a GUI Description Language with Topic Maps Lukas.Georgieff@hotmail.com University of Applied Sciences Worms
  2. 2. Topic Maps (1) • “Information wants to be free“ • “Information wants to be a topic map“ 30/09/2010 Lukas Georgieff - TMRA 2010 - GDL 2
  3. 3. Topic Maps (2) • “Information wants to be free“ • “Information wants to be a topic map“ 30/09/2010 Lukas Georgieff - TMRA 2010 - GDL 3
  4. 4. Topic Maps (3) • “Information wants to be free“ • “Information wants to be a topic map“ 30/09/2010 Lukas Georgieff - TMRA 2010 - GDL 4
  5. 5. Topic Maps (4) • “Information wants to be free“ • “Information wants to be a topic map“ Why? – TM models arbitrary real world scenarios – TM knows no limits for users But users must be familiar with TM-internals 30/09/2010 Lukas Georgieff - TMRA 2010 - GDL 5
  6. 6. Topic Maps (5) What to do? 30/09/2010 Lukas Georgieff - TMRA 2010 - GDL 6
  7. 7. GDL (1)  GUI Description Language, a TM ontology • Goals – Generic UI adapted to a specific domain – Configurable UI – Plattform independency – “Semantic based“ – Non-limitting for TM – Simplifying TM for end users 30/09/2010 Lukas Georgieff - TMRA 2010 - GDL 7
  8. 8. GDL (2) 30/09/2010 Lukas Georgieff - TMRA 2010 - GDL 8
  9. 9. GDL – Features (1) • Defines default values e.g. PSIs regexp: “http://some.where/psis/author/.+“ • Allows to hide fields e.g. item identifiers • Auto-generates (sub-)values e.g. item identifiers a predifened prefix with an auto- generated suffix • Defines restrictions for end users e.g. no creation of elements, just a choice of elements 30/09/2010 Lukas Georgieff - TMRA 2010 - GDL 9
  10. 10. GDL – Features (2) • Allows individual layout of TM-constructs corresponding to semantic meaning/domain e.g. placing, naming, visual construction of elements on screen, using of css • Binds/displays partial modelled data at one glance e.g. displaying topics related via associations • Generates context depending GUIs e.g. visualisation depends on the area of interest 30/09/2010 Lukas Georgieff - TMRA 2010 - GDL 10
  11. 11. GDL – Features (3) 30/09/2010 Lukas Georgieff - TMRA 2010 - GDL 11
  12. 12. GDL – Features (4) 30/09/2010 Lukas Georgieff - TMRA 2010 - GDL 12
  13. 13. GDL – Features (5) 30/09/2010 Lukas Georgieff - TMRA 2010 - GDL 13
  14. 14. GDL - Problems • GDL inserts a new layer between the end user and the TM-engine – Additional processing of the GDL-data – GDL-file must be created – Many GUI-systems exist – GDL exists in parallel with TMCL 30/09/2010 Lukas Georgieff - TMRA 2010 - GDL 14
  15. 15. Conclusions • GDL builds a bridge between the end-user and the TM-internals • GDL does not limit TM/ontology • GUI is not hard-coded but still configurable • GDL is not plattform/TM dependent  defines just the semantics 30/09/2010 Lukas Georgieff - TMRA 2010 - GDL 15
  16. 16. Thank you for your attention! 30/09/2010 Lukas Georgieff - TMRA 2010 - GDL 16
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×