The current extensions of BPM languages such as BPEL4People [BPEL4P] are purely syntactic and introduce "Peoplelinks", "Partnerlinks", "Exceptions", "Compensations",
"HumanTasks" etc. They do not address the semantics of these interactions and do not investigate the combination of social software + semantic technology (=Web 3.0) for scientific workflows. 

## 5. Conclusion

Manifold rigorous and industry-strength BPM languages 7 and tools have been developed. Typically these tools are applied in repetitive, high-volume production or administrative workflows where a central orchestration process definition can be created, optimized, and then used as a prescriptive, standardized model for process enactors or for workflow automation. However, practical experiences have shown that scientific workflows process are often weakly-structured, agile / change quickly, and need to dynamically integrate heterogeneous information resources and services as well as collaborative human knowledge and tasks. 

We have considered in this paper how the limited coordination, collaboration and (human) integration support of BPM approaches could be improved for scientific workflows by a Web 3.0 semantic process Wikis and have presented a solution based on integration with a BPM workflow system. We see two major advantages of our proposal:

1. decentral, lightweight dynamic acquisition of required process knowledge –
(human) end users bring in their process knowledge in a simple, effortless, manner - the low-barrier Wiki approach provides and intuitive interface to collect knowledge from humans.

2. the ongoing collaborative (conversation-based) human interaction may be very simple, yet powerful, instrument to execute rule-based agile scientific workflows processes.
Initial evaluation of our implementation in a HCLS e-Science infrastructure
[Paschke2008] has demonstrated promising improvements in these aspects. Guided by the scenario, described in section 3, several tests were run to ensure that the prototype mainly performs correctly and stable in the expected behavior. In particular, a set of defined use cases covering the main functionalities have been performed. Additionally, during the development of the prototype several unit tests have been run to check the correct implementation of the various methods. Thus, it can be stated that the prototype generally performs correctly and in the authors' view, the evaluated use cases can prove the importance of the future uptake of semantic Wiki systems as user-friendly interface for human interaction during scientific workflow execution, particularly in corporate environments.