Capturing Multi-Level Models in a Two-Level Formal Modeling Technique
By Joao Paulo Almeida, Fernando Musso, Victorio Albani Carvalho, Claudenir Fonseca and Giancarlo Guizzardi
Traditional Modeling prescribe two-level schemes. However, real world domains challenge this model, by having entities that are classes of classes (i.e. higher order types).
Two level Workaround: Powertypes
- Both powertype and basetype are regular classes.
- Regular user-defined association
The problem is not being able to constrain the instantiation relations.
Using a Proper Multi-level Language
He showed that using MLL, you may define properties for the specialization classes themselves, which help providing the information missing in the pre-existing languages.
Fitting Multi-level into Two
They provide some design transformation principles
They implemented the principles in an Alloy-based tool that allow the ontology engineer to define and simulate the model, thus helping him/her to specify and verify ontologies.
He showed some examples of simulation, showing a mistake in the original model. This way, one can constraint the model to fix the problem.
The idea is to provide the constraints on the knowledge in a class level in a way that even not knowing before hand what you will classify, this is done consistently. And then run Alloy so that you can still note some inconsistencies (holes) in your model and provide extra contrains before actually deploying the model in a real setting.
Q&A
Comment from Ulrich: he should choose examples that are more meaningful for people than the texbook biology examples.
By Joao Paulo Almeida, Fernando Musso, Victorio Albani Carvalho, Claudenir Fonseca and Giancarlo Guizzardi
Traditional Modeling prescribe two-level schemes. However, real world domains challenge this model, by having entities that are classes of classes (i.e. higher order types).
Two level Workaround: Powertypes
- Both powertype and basetype are regular classes.
- Regular user-defined association
The problem is not being able to constrain the instantiation relations.
Using a Proper Multi-level Language
He showed that using MLL, you may define properties for the specialization classes themselves, which help providing the information missing in the pre-existing languages.
Fitting Multi-level into Two
They provide some design transformation principles
They implemented the principles in an Alloy-based tool that allow the ontology engineer to define and simulate the model, thus helping him/her to specify and verify ontologies.
He showed some examples of simulation, showing a mistake in the original model. This way, one can constraint the model to fix the problem.
The idea is to provide the constraints on the knowledge in a class level in a way that even not knowing before hand what you will classify, this is done consistently. And then run Alloy so that you can still note some inconsistencies (holes) in your model and provide extra contrains before actually deploying the model in a real setting.
Q&A
Comment from Ulrich: he should choose examples that are more meaningful for people than the texbook biology examples.
Nenhum comentário:
Postar um comentário