SWiM/services

From MathWeb

Jump to: navigation, search
  • Which services are already there?
  • Which ones can be integrated into SWiM?
  • Which ones need to be developed?
  • Which interface (service API) is needed?

Contents

Implemented services

Specified services

service internal setting semantic-based notation-dependent domain-specific steps added value status
faceted navigation yes any view/edit mode yes no no 1 better overview, saves searching in many cases implemented, still needs improvement
auto-completion yes source editing mostly (for link targets, not for XML) yes (XML) no 1 easier editing, more correct editing fully specified, easy test case
edit-in-place yes presentation-like editing mode
or enhanced presentation mode
partly yes no 3 easier editing, better overview of the content structure fully specified
learning assistance yes any view mode yes no no 2
  • user: learning
  • community: social bookmarking
partly specified
Sentido editing no ? not yet maybe yes 1 easier editing, nicer browsing nothing so far
MoC assistance yes any edit partly (for dependencies covered by the system ontology, not for other link targets) yes (XML) no 2 consistency partly specified
Change warner yes any edit yes (w/ reasoning, maybe) no no 1 consistency partly specified

More possible services

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.

Personal tools
MathWeb
Structures