You are on page 1of 1

Assigned: 29.12.2011 Due: 13.01.

2012

KRR Written Assignment PROJECT No. 2

Task For this project you have to choose one of the following assignments. All required files are to be uploaded on curs.cs.pub.ro as a .zip archive named SOAR_LastName_First_Names.zip or Protege_LastName_First_Names.zip. Assignment 1 SOAR You are to implement an advanced eater in SOAR, starting either from scratch or from one of the implementations provided in the SOAR tutorial. Your eater should (at least): remember (the coordinates of) all seen cells (an eater can see a 5x5 grid of cells around its current position) and their content always move to (or in the direction of) the closest seen cell that contains food or has contained food at the moment the agent has seen it; in case of a tie, bonus food is to be preferred Additional features may be added and will earn you bonus points. Your submission should include: the whole source code in a single .soar file. If you use VisualSoar during development, make sure you submit the right file. It is best to test your eater right before submission. a .pdf document containing: details about how you implemented each feature a comparison of your eater with the other eaters from the tutorial, at least with respect to the number of steps needed for clearing all food and with respect to its behavior when surrounded by empty cells Assignment 2 Protege You are to design an OWL ontology using Protege version 4.1.0. The ontology should be more complex than the Pizza ontology created during the labs and use as many of the features of Protege discussed in the tutorial as possible. Be creative, your ontologies are expected to be very different from one another. Pizza and wine ontologies are not allowed. Here are some possible topics: music, movies, TV series sports (teams, coaches, awards, players etc): football, tennis etc. cars, planes family relationships (with individuals from history, movies or books) domain specific ontology: geography, medicine, law, economy etc Your ontology must satisfy the following requirements: it should contain at least 25 classes nested to a depth at least 4 it should contain at least 10 object properties; there should be some nested properties and also relations between them (inverse) it should contain at least 3 data properties it should contain at least 25 individuals it should contain at least 5 inferred classes and their definitions should be as diverse as possible; you should use both object and data properties and define the inferred classes in such a way as to have some subclasses and individuals inferred at runtime the whole ontology must be meaningful Your submission should include: the .xml file generated by Protege. Copy this file to a different location and try opening it with Protege before submission. a .pdf file describing your ongology, with details about the inferred classes.

You might also like