SWiM/services


 * Which services are already there?
 * Which ones can be integrated into SWiM?
 * Which ones need to be developed?
 * Which interface (service API) is needed?

Implemented services

 * ../Subversion client

More possible services

 * living documents (cf. Lectora)
 * If SWiM by itself is not “alive” enough, integrate external services (i.e. visualization) where appropriate.
 * QMath editing
 * metadata editing
 * ../stepwise formalisation
 * ../added-value analysis

Classification

 * based on notation?
 * Some services only rely on the system ontology
 * others rely on system ontology plus data format (aka notation), e.g. OMDoc/XML – can you call that “data model”?
 * different approach (Michael): model ontology of data format, refine OMDoc's document ontology by data format's ontology, giving e.g. an OMDoc+XML system ontology.
 * number of steps
 * some services are more interactive than others

Customization
Assume there is a set S of all services. Let the user choose any $$P\subset S$$ he wants to have enabled.