From NeOn Wiki

As you already know within WP5 we are developing the gOntt plug-in.

gOntt helps to schedule an ontology network development and is supposed to be a NeOn Meta-tool for informing about methodological guidelines and NeOn plug-ins for each process and activity.

gOntt generates a Gantt diagram with processes and activities involved in the ontology network development. The idea is to allow, just by clicking in a process or an activity, starting the corresponding NeOn Toolkit plug-in to carry out such a process or an activity. That is, the associated plug-in will be activated by showing its associated perspective. That means that gOntt provides access to the different NeOn plug-ins.

gOntt has its own extension point that should be extended by your NeOn plug-ins to allow the activation of such plug-ins when the user is working in gOntt. In order to make the functionality of your plug-in available from within gOntt no additional code needs to be created. Simply add a few lines to the plugin.xml providing only a small amount of information. gOntt just needs to know:

  • plug-in name
  • id of the perspective the plug-in works with. The perspective to show when you launch the plugin.
  • id of the view the plug-in works in
  • id of the activity that is associated to the plug-in.
    • A list of activities can be found in: glossary of activities.
    • Activity ids should be the activity name without spaces, first word lowercase, and the rest beginning uppercase. For example: “Non Ontological Resource Reverse Engineering” would have as id “nonOntologicalResourceReverseEngineering”.
  • pluginHelpId showing how to start the plug-in. This help should be in the form of Eclipse Cheat Sheet.
    • If you don't have a cheat sheet leave it empty.
    • However, it is important to provide this help to the user and this action is to easy for you. Here you can find a simple example of a cheat sheet. You can create a similar cheat sheet for your plug-in.

Here you have also two examples of how the gOntt extension point should be implemented. 

<extension point="org.neontoolkit.upm.gontt">
  <plugin
    name= "Watson Plugin"
    perspectiveId="com.ontoprise.ontostudio.owl.perspectives.OWLPerspective"
    viewId="uk.ac.open.kmi.watson.neontoolkitplugin.WatsonResultsView"
    activityId="ontologyReuse">
  </plugin>
</extension>

<extension point="org.neontoolkit.upm.gontt">
  <plugin
    name= "Label Translator"
    perspectiveId="com.ontoprise.ontostudio.perspectives.Schema"
    viewId="com.ontoprise.ontostudio.views.navigator"
    activityId="ontologyLocalization"
    pluginHelpId= "org.neontoolkit.xxx.cheatsheet.ontologyLocalizationIntro" >
  </plugin>
</extension>

Important note: In order to extend/implement an extension point it is not required to define a dependency to the plug-in defining it. This will give a warning in your plug-in.xml, but that will neither harm the build nor the deploy process. At runtime it is not a problem if gOntt is not present. But if it is present, your plug-in will be "discovered".

The aforementioned information is required to switch to the right perspective and make sure the proper view is visible to continue with the process or activity selected while the user is using gOntt plug-in.

For this reason, we would like to encourage NeOn plug-in developers to implement this easy extension point in order to have such plug-ins already integrated in the meta-tool gOntt. This little action will have benefits in the whole NTK that will have a complete meta-tool based on the NeOn Methodology with the associated advantages for the final users of the NTK.

Please contact Mari Carmen Suárez-Figueroa ([1]) and Oscar Muñoz ([2])

  • to inform us that you implement the gOntt extension point
  • to ask questions or provide suggestions.
Retrieved from "http://neon-toolkit.org/wiki/GOntt_Integration"