From MathWeb

This is an added-value analysis for SWiM.

Trigger	Core Problem	Solution	Benefits	Sacrifices
Core
(initial)	collaborative work environment…	social (web) software	joint development easy publishing	keeping track of others' contributions
	…for scientific knowledge…	semantic markup	stepwise formalization can be narrative machine-understandable	hard to write not directly usable for automated deduction
	…management	semantic work environment	reusable knowledge “atoms” explicitly typed links (e.g. depends, exemplifies)	making knowledge explicit
stepwise formalization	incremental editing based on division of labour	wiki	easy linking	danger of spam
Auto-completion
easy linking	find possible targets	naïve auto-completion	no more link typos	too many inappropriate targets
too many inappropriate targets	recommend allowed targets only	ontology-based auto-completion	concise list of appropriate targets
Learning assistance
explicitly typed links	help users to understand topics	display facetted incoming/outgoing links (i.e. grouped by type; offered for free by IkeWiki)	concise overview of direct prerequisites/examples/…	other links (e.g. instance of) also shown indirect prerequisites not accessible
indirect prerequisites not accessible	interactively exploring indirect prerequisites	compute all prerequisites, offer exploring direct/indirect ones	indirect prerequisites accessible with one click	need to decide between direct/all prerequisites too many irrelevant prerequisites in overall list
need to decide between direct/all prerequisites	offer exploring “reasonable” prerequisite selection	depth of prerequisites suggested depends on difficulty of concept as perceived by the community	community-specific level of explanation	how to configure the perceived difficulty of a concept? user might not be a “default case”
how to configure the perceived difficulty of a concept?	measure the perceived difficulty of a concept	learn depth of prerequisites requested by all users
how to configure the perceived difficulty of a concept?	measure the perceived difficulty of a concept	count questions regarding that concept (marked up on discussion page)
too many irrelevant prerequisites	only show relevant prerequisites user doesn't know already	let user acknowledge “I know this”; maintain user model
too many irrelevant prerequisites	rank prerequisites by relevance	Lectora?
Change management
explicit dependency links	preserve dependencies upon editing	change management	less conflicts improved consistency
Import/export
hard to write	support the user's preferred editor	external editor interface	…
not directly usable for automated deduction	extract logical structure