This workshop may be seen as an heir to the past versions of MASPEGHI (at OOIS
2002 and ASE
2003) and of the Inheritance Workshop (at ECOOP
2002). This is multiple inheritance between workshops, and so we intend
to apply the results of the previous workshops to the organization of this one,
while at the same time making it possible to reuse the results of this workshop
in the next one (MASPEGHI 2005). MASPEGHI 2004 will continue the discussion
about mechanisms for managing specialization and generalization of programming
language components: inheritance and reverse inheritance, specialization and
generalization, and other forms of inheritance, multiple, single, mixin or trait-based.
The scope of the workshop reflects two main concerns: (i) the various uses of
inheritance, and (ii) the difficulties of implementation and control of inheritance
in practical applications. Different communities, such as the design methods,
database, knowledge representation, data mining, object programming language
and modeling communities, address these concerns in different ways. Thus, one
of our goals is to bring together a diverse set of participants to compare and
contrast the use, implementation and control of inheritance as practiced in
MASPEGHI 2004 will continue the discussion about mechanisms for managing and
manipulating specialization and generalization hierarchies: inheritance and
reverse inheritance, specialization and generalization, interface and implementation
inheritance, multiple, single, mixin and trait-based inheritance, etc. We are
concerned with both the uses of inheritance, and the difficulties of implementing
and controlling it.
These concerns are reflected differently by disciplines such as databases, knowledge discovery and representation, modeling and design methods, object programming languages, with emphasis put either on problem domain modeling or on organizing the computational artifacts that simulate the domain. For example, in knowledge representation, the modeling role of classes prevails: hierarchies are repositories of validated knowledge, which support the acquisition of new knowledge. In analysis and design, the purpose of the hierarchy shifts as the design matures from modeling to organizing. Hence, modern OOA&D methods support the gradual evolution of class hierarchies from one use to the other.
Despite the wide use of specialization hierarchies, there is no standard methodology for constructing and maintaining them independently from the domains that they represent and the artifacts that they organize. This workshop will provide a forum for researchers from a variety of domains to learn from each other and work together to develop such a methodology.
Prospective participants are invited to submit high-quality position papers.
Papers may be at most 5 pages long, but shorter papers are preferred. Papers
should cover one or several topics according to the objectives and scope mentioned
previously. Submissions should preferably be in the ECOOP
paper format (Springer
LNCS). They should be sent electronically in PDF or Postscript format if
possible, to maspeghi2004@#REMOVE-THIS#i3s.unice.fr
(*). Final versions of accepted position papers will be made available
in the Papers section of the workshop web-site and published as a research report
by the I3S laboratory. However, a paper can be distributed only to the workshop
participants if the authors wish so for some reason. Papers will be selected
according to the following criteria :
To encourage fruitful discussions, the selected participants must be able to focus on a small set of related subjects. Too large a set of widely divergent interests will not encourage useful discussion. Thus, in addition to these criteria, the selection of position papers will be influenced by the need to keep the workshop focused. Please, note that a paper will not be considered in the proceedings, on the web-site, and even referenced in the workshop reader, unless at least one of the coauthors attend to the workshop.
(*) Menu is identical to the "flash" one
This page was updated on 06/21/2004
Maintainer : Philippe Lahire (lahire@#REMOVE-THIS#unice.fr) Do not forget to remove #REMOVE-THIS# from the electronic address