[Tagging] The current problem with tagging

Tobias Knerr osm at tobias-knerr.de
Mon Oct 19 12:31:30 BST 2009

John Smith:
> 2009/10/19 Tobias Knerr <osm at tobias-knerr.de>:
>> I'd strongly recommend to use the
>> wiki as your backend for most of the information.
> It doesn't matter how I look at the problem there will need to be a
> lot of effort exerted to be useful.

When I look at the problem, reimplementing all those features I've
mentioned is a lot more effort than writing a wiki text parser.

> The users need to spend a lot of time/effort getting the wiki up to
> scratch, even then there is no guarantee that will be good enough
> because there is no code at present to enforce some sort of
> consistency needed to build a useful/encompassing index.

If you offer a template, people tend to use it in a way that makes
sense. Of course you cannot strictly enforce it, but that doesn't mean
it wouldn't work. You still could use automated validation to spot for
potential problems if you think that's required.

> Which is the
> point of this thread to make is as simple for people to use and keep
> up to date as possible with the least amount of effort as possible.

How does the backend used by a web app or editor feature determine
whether it's easy to use? Why is it harder to use a form whose results
are stored as a wiki template than a form whose results are written to
some database?

> You can't do that with a wiki, and as I see it the amount of effort to
> get the wiki to contort into something useful is about the same as
> doing something new, although the learning curve to integrate with the
> wiki might actually make it more effort to use a wiki for something as
> sophisticated as what I'm proposing.

That doesn't matter unless you manage to convince everyone to not use
the wiki at all but switch to your solution. If this doesn't work (which
isn't that unlikely, is it?) information has to be copied from and to
the wiki - suddenly the effort required is the added effort of both

Which features of your sophisticated solution can NOT be properly
implemented with a wiki backend? I don't see any except maybe the
"voting" feature, and even if some data is best stored outside the wiki,
that doesn't mean you cannot use the wiki for the rest.

Tobias Knerr

More information about the Tagging mailing list