It is possible (while maybe a bit awkward) to convert other ontologies to be used with the Beanynizer. To convert an existing ontology perform the following steps (note, this process has only been tested with Protégé 2.1 and might not work with 3.0):
Load the old ontology and save it under a new name (to keep the original file untouched).
Use the
→ option to remove references to other external ontologies.Include the Beanynizer default ontology as described above. If your
original ontology was also designed for use with
a FIPA-compliant agent platform, ignore any errors, e.g., complaining about
duplicate definition of classes like AgentAction
,
etc.
If your original ontology did contain FIPA classes with different names (e.g., AID
for agent identifiers)
change all references to these classes (if any) to now refer to the Beanynizer classes (e.g., agent-identifier
).
Afterwards remove the original FIPA classes.
When your original ontology was not designed to be used with FIPA, you might have to rearrange the class hierarchy, such that all your classes are derived from the appropriate classes (such as AgentAction).
Now the awkward part: Make sure that all your classes and slots are
instances of the Beanynizer metaclasses. The required metaclass is called
BEANYNIZER-CLASS
and is a subclass of the
:STANDARD-CLASS
. You change the metaclass by selecting
each single class and using the option from the popup menu, but a much faster way
is to change to the instance tab, and use drag and drop. The same procedure
should be done for your slots, which should be instances of the
BEANYNIZER-SLOT
. Finally, you should make the
Beanynizer class and the Beanynizer slot the default metaclasses by using
the option
from the popup menu.
You're done! You can now start to generate code, or to adjust code generation options as described above.