Automatic Code generation of ontologies

[amedranogil]

Enhance the Protege Code Generation plugin to create output based on the Apache Velocity Engine.

• Create templates for classes, factories, ontologies, and all the other nedded files.
• Templates will use the OWLAPI ontology or ontology class instances, along other custom properties
• An XML schema defining the custom properties and variables, as well as coordinating which templates are runned against what, defining output schemes too. initially 2 modes:
  • Once per ontology, ontology class as input (e.g., Ontology Velocity Macro is runned using the ontology instance to create Ontology.java )
  • Once per ontology class, using ontology class instance (e.g.2, Class Velocity Macro is runned for each ontology class outputed as <ClassName>.java)
• Templates and XML are bundled into _Template System_s, providing an easy mechanism to switch output (this will allow for generating OWLAPI java code, c code, SQL, or universAAL ontology code using the same implementation, only the template system changes)

Enhance the Maven plugin so it can be configured for:

• generating output for all owl files found in {$project.build.sourceDirectory}/main/owl
• generating output for a single owl file through URI (used for generating dependencies from web)
• triggering transitive generation, previous options will only generate the given ontology, this option will allow to generate all the imported ontologies recurvively as well.
• goal attached to the process-resources phase so the (Java) output is generated in {$project.build.outputDirectory} in, this will cause the output source to be interpreted as the code it self for compilation.
• If the output code needs to be customized, it can be generated in {$project.build.sourceDirectory}/main/java through another goal.

This way we can import standard ontologies directly as universAAL code. As well as creating and maintaining our ontologies only in turtle serialization in the version control, using protege or other ontology tools. Legacy implementation will still be supported (but only for ontologies with custom non-OWL code).