| Course
|
UNIK4710, UNIK9710
|
| Title
|
Context-aware Scenarios
|
| Lecture date
|
2012/02/03
|
| Lecturer(s), (users)
|
Josef.Noll
|
| Objective
|
During this lecture you will present to your colleagues the scenario which you would like to work with.
|
| Learning outcomes
|
Having joined this lecture and prepared your scenario description, you
- have a basic understanding of "tripple store" (.rdf) and ontologies (.owl)
- will be able to describe a scenario based on
- define some hierarchical overview on "classes" being involved in your scenario
- prepare for the .owl implemenation of your classes
|
| Pensum (read before)
|
"What is a scenario"
- Create a powerpoint (3-6 slides) of your envisaged scenario
- Create the relations for the major items, e.g. Context, Preferences, ...
- See the YouTube videos listed under References
|
| References (further info)
|
See examples of Scenarios from earlier courses
Video
|
| Keywords
|
Scenario, Context, Location, Profile, RDF, Ontology, Semantic Technologies
|
this page was created by Special:FormEdit/Lecture, and can be edited by Special:FormEdit/Lecture/Context-aware Scenarios.
Test yourself, answer these questions
- How do I start to build a Semantic Web?
- What is the role of Ontologies in the Semantic Web?
- What is RDF and what is it good for?
- Why RDF model is different from the XML model?
- What is OWL?
Scenarios
Semantics
- .xml realtion between subject & object
- .rdf subject, predict, object
- .rdfs vocabulary for properties
- ontologies as data models of a domain
- describe through rdf or owl
- owl is more expressive
- Extension of semantics through rules
- Rules might replace ontologies
Challenges with ontologies
- ontologies describe the data on a Web
- very good suited as a knowledge base, e.g. medical history, interworking of medicine, oil drilling
- when using a semantic model in the real world, the challenge is to get changes (updates) to the ontologies. Example: car industry, where cars are produced under the same header with slightly different outfit, where manufacturers change frequently,...
Summary on Ontologies
- cover only limited area (specific area, "swamps of ontologies")
- have a "creation date" (timestamp) in mind
- upgradability?
- consistency when upgrading one ontology
- are good for knowledge management
- interface between knowledge management and processes is not clear
Lecture Notes & Scenarios
Media:UNIK4710-L3-v12-LectureNotes.pdf