Your SlideShare is downloading. ×
0
myUI Ontology
myUI Ontology
myUI Ontology
myUI Ontology
myUI Ontology
myUI Ontology
myUI Ontology
myUI Ontology
myUI Ontology
myUI Ontology
myUI Ontology
myUI Ontology
myUI Ontology
myUI Ontology
myUI Ontology
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

myUI Ontology

1,720

Published on

Review meeting

Review meeting

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

  • Be the first to like this

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

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. MyUI Ontology Draft<br />Andreas Schmidt, Heiko Haller<br />FZI Research Center for Information Technologies Karlsruhe, Germany<br />Review Meeting, Brussels, July 14, 2010<br />
  • 2. Ontologiesandtheiruse<br />Twoperspectives:<br />sharedunderstandingof a domainofinterest(Uschold & Grüninger 1996)<br />explicit specificationof a conceptualization(Gruber 1993)<br />Ontology-centereddesign<br />2<br />
  • 3. Ontologies in myUI<br /> In myUI:<br />describingpreferences, impairments etc. ofthe end user („user model“)<br />describingcapabilitiesofdevices (withrespectto UI adaptation)<br />describing environmental andothercontextualfactor<br />Purpose<br />enablerun-time adaptation<br />guide design-time activities<br />3<br />
  • 4. Iterative Approach<br />4<br />Standards<br />Wouldthisinformationchangethewaywewouldliketoadaptthe UI?<br />adaptation<br />requirements &<br />strategies<br />device UIdesign<br />sensors<br />SCENARIOS<br />Whataredevicerequirements/constraints?<br />Whatarewelikelyabletocapture?<br />Standards<br />Standards<br />
  • 5. Startingpoint<br />5<br />reusing<br />
  • 6. Ontology Overview: Preferences and Impairment<br />
  • 7. Ontology: Hierarchy of Disabilities<br />
  • 8. Hierarchy of Disabilities (Detail)<br />
  • 9. Additional contextualfactorsidentified (smallsubset)<br />9<br />
  • 10. Disability Profiles<br />Doris mobility impairment 0.8<br />Doris right hand weakness 0.9<br />Doris presbyopia 0.6<br />Arthur mobility impairment 0.7<br />Arthur manual impairment 0.4<br />Arthur visual impairment 0.8<br />Arthur myopia 0.5<br />Thomas h.f. hearing impairment 0.8<br />Thomas colour blindness 1.0<br />
  • 11. Personal Preferences<br />Doris preferred text angle 0.024*<br />Doris preferred input device big-button remote<br />Doris preferred volume 0.2<br />Arthur preferred text angle 0.07*<br />Arthur preferred input device voice<br />Arthur preferred volume 0.7<br />Thomas preferred input device keyboard<br />Thomas preferred text angle 0.01*<br />*) fraction of vertical visual angle (0.01 ≈ 28pt at a distance of 50cm).<br />
  • 12. Interface Profiles<br />Profile1 (default colour based visual with limited text scaling)<br />max. visual impairment 0.4 (relies mainly on visual interaction)<br />max. font size 80 <br />max. color blindness 0.2 (uses color as vital part of design)<br />Profile2 (voice feedback)<br />max. hearing impairment 0.3 (relies on audio feedback)<br />max. anterograde amnesia 0.7 (AP needs to remember question)<br />max. slow reactions 0.4 (AP needs to react sequentially)<br />Profile3 (very large buttons)<br />max. visual impairment 0.8 (compatible with very weak vision)<br />max. font size 300 (huge letters)<br />max. anterograde amnesia 0.9 (AP needs to remember context)<br />
  • 13. Preliminary Interaction Scenario Doris<br />Device encounters Doris at 50cm distance<br />System checks device’s interaction profiles for compatibility with user disabilities and preferences<br />System tells device to use the best fitting profile (no. 1) of the possible profiles (1,2,3)<br />System tells device to set preferred text size to 67pt (0.024 at 50 cm)<br />Device adapts accordingly<br /> […later…]<br />Device detects Doris has moved to armchair at 250cm distance<br />System re-calculates required font size to maintain text viewing angle (335pt).<br />System checks device’s interaction profiles for compatibility with updated requirement (Profile1 cannot handle font sizes > 80pt). <br />System tells device to use the best fitting profile (no. 2) of the possible profiles (no. 2,3)<br />Device switches to audio output, adjusts the volume according to the ambient noise level<br />
  • 14. Summary<br />Iterative approachtoontologymodelingfollowingtheontology-centered design methodology<br />First phase: „ontologyasmediatingartefact“<br />(Second phase: ontology a formal specificationforautomation)<br />Currentstatus: First iterationscompletedwith afirstdraftoftheontology<br />Mainlyfocused on theuserprofileandimpairments<br />Reusingthevocabularyfromthe SOPRANO/openAALontology<br />Next steps<br />closerinvestigationintoadaptivityrequirements<br />14<br />
  • 15. Questions?<br />andreas.schmidt@fzi.de<br />heiko.haller@fzi.de<br />
  • 16. Existing OpenAALOntology<br />

×