Denny and Markus,
 
I just read your paper, "Reusing Ontological Background Knowledge in Semantic Wikis".
 
I have a few comments.
 
You make assumptions that will hold in some usage scenarios: e.g.
* that the ontology is relatively fixed, so that data can be uploaded etc
* collaborative ontology engineering may be best left to separate ontology editors
 
Yet there are also usage scenarios where you want everything tightly integrated. Or at least I do!
 
The reason is that there are high costs of keeping the ontology development and evolution separate from the wiki. Things go out of synch, or have to be manually kept in synch, which is expensive and error-prone.  This is analogous to the problem with models and software requirements getting out of synch with the software.
 
This is the kind of thing I want to do:
* start building an ontology any which way I like e.g.
   a.  in my preferred [perhaps collaborative] ontology editor
   b.  in a suitably enhanced semantic wiki editor
 
* be able to import ontologies and data into the wiki,
 
* be able to enter more information in the wiki using the imported ontologies
 
* be able to continue to edit and modify the ontology from the wiki itself for small changes(*)
 
* be able to export the ontology and data from the wiki into my favorite ontology editor for major revisions
 
* be able to re-import the updated ontology, with some automated assistance in keeping old versions and making new versions of the pages and the semantic annotations
 
 
I may be asking for a lot, and it may not happen next month or next year, but I think this vision has powerful functionality that would be very useful for many situations.
 
 
(*) yes i agree with you that you may want to limit the people who can make ontology changes.
 
Thanks,
Michael
 
==========================
Michael Uschold
M&CT, Phantom Works
425 373-2845
michael.f.uschold@boeing.com 
==========================