

![0_image_0.png](0_image_0.png)

Figure 1 shows a typical workflow: the processing and description of a specimen. It involves three actors: a field trip participant who describes the finding of the specimen, a taxonomist who performs the taxonomical identification and a curator who is responsible for the final curation of the descriptions. First, somebody in the role of a *field work* participant triggers the start of the process 1and describes the discovery of a new specimen through an associated task form in the user console, whereby a new Wiki page is created from a template. This template contains enhanced Wiki syntax with placeholders for subjects of statements, which are replaced with corresponding user input. User input consists of literals (e.g. from text area and input fields) as well as URIs of concepts and instances. Predicates used in the template are taken from existing ontologies.2 Notification by email is sent to somebody in the *taxonomist* swimlane to inform him/her that he/she is due to perform a taxonomic identification of this specimen. Again, the results are committed to the workflow engine through a Wiki task form. Upon completion a new page with the results of the taxonomic identification is created, and a typed link to it is inserted on the discovery page. A last action must be taken by somebody in the role of a *curator*. The automated expert selection is based on semantic description of curators' responsibilities and the results of the taxonomist's identification. and user resources.

Further on, Process Makna's click-searches which are provided with every resource in 1 Workflow related functionality (e.g. listing and starting of processes) is provided by JSPWiki plugins in Makna which use RMI to interact with the jBPM engine.

2In our example we reuse the FungalWeb ontology [SNBHB05] for mycological classifications and TDWG's LSID ontologies for taxonomic data.