Description Logics Extensions
A fuzzy description logics temporal extension
| |
Short Description: | This is a research about a new temporal extension for description logics - valid for fuzzy logics but for crisp ones as well, as a restriction (so it always should be). We give new definitions for some temporal operators already present in literature and introduce some new temporal operators, called "tendency operators", whose semantics describes the temporal tendency - increasing, decreasing or constant - for the membership degree concerning a given concept. In addition, we define the new "temporal quantifiers", corresponding to some natural language's temporal adverbs, as usually, often, 3 times out of 5, etc. |
Coordinator: | |
Tutor: | MarcoColombetti (colombet@elet.polimi.it), DavideEynard (eynard@elet.polimi.it) |
Collaborator: | |
Students: | MarcoFurlan () |
Research Area: | Social Software and Semantic Web |
Research Topic: | Description Logics |
Start: | 2007/04/01 |
End: | 2008/04/24 |
Status: | Closed |
Level: | Ms |
Type: | Thesis |
Contents
Part 1: project profile
Project name
A fuzzy description logics temporal extension
Project short description
This is a research about a new temporal extension for description logics - valid for fuzzy logics but for crisp ones as well, as a restriction (so it always should be). We give new definitions for some temporal operators already present in literature and introduce some new temporal operators, called "tendency operators", whose semantics describes the temporal tendency - increasing, decreasing or constant - for the membership degree concerning a given concept. In addition, we define the new "temporal quantifiers", corresponding to some natural language's temporal adverbs, as usually, often, 3 times out of 5, etc.
Dates
- Start date: 2007/04/01
- End date: 2008/04/24
People involved
Project head(s)
- Prof. Marco Colombetti
Other Politecnico di Milano people
- Ing. Davide Eynard
Students
- Marco Furlan – marcofurl (at) gmail (dot) com
Laboratory work and risk analysis
I used an AIRLab computer only to write the source code and the documentation by various editors, so the risk analysis wasn’t required.