Reading PDDL, Writing an Object-Oriented Model
There are many efforts towards a combination of planning systems and real world applications. Although the PDDL is in constant evolution, which improves its capability to describe real domains, it is still a declarative language that is not so simple to be used by the non-planning community. This paper describes a translation process that reads a domain specification in PDDL and transforms it into an object-oriented model, more specifically into a version of UML for planning approaches. This translation process can let a designer read PDDL domains and verify it with some powerful tool like itSIMPLE or GIPO, or it can allow a planning system that only reads object-oriented models to run in domains described in PDDL originally.
KeywordsUnify Modeling Language Class Diagram Translation Process Planning Domain Action Definition
Unable to display preview. Download preview PDF.
- 2.D’Souza, F.D., Wills, A.C.: Object, Components, and Frameworks with UML – The Catalysis Approach. Addison-Wesley, USA (1999)Google Scholar
- 3.McDermott, D., et al.: The PDDL Planning Domain Definition Language. In: The AIPS 1998 Planning Competition Committee (1998)Google Scholar
- 4.OMG - Object Management Group. Unified modeling language specification: version 1.4 (2001), http://www.omg.org/uml
- 5.Simpson, R.M., McCluskey, T.L., Zhao, W., Aylett, R.S., Doniat, C.: An Integrated Graphical Tool to support Knowledge Engineering in AI Planning. In: Proceedings, 2001 European Conference on Planning, Toledo, Spain (2001)Google Scholar
- 7.Vaquero, T.S., Tonidandel, F., Silva, J.R.: The itSIMPLE tool for Modeling Planning Domains. In: ICAPS 2005 Competition on Knowledge Engineering for Planning and Scheduling, Monterey, California, USA (2005)Google Scholar