> /comments/wishlist
> ../Q1
> ../A1
> ../A2
> ../A3
> ../Q2
> ../A1
> ../A2
> ../Q3
> ../A1
> ../A2
> ...
>
> etc. Right?
Yeah, that looks good. But instead of Qn1/An1/An2/An3...,
how about just Qn/An ; i.e., just a single article for a
question and an answer. So instead of generating
another unmerged response, anyone who has something
to add to the answer to 'Qn' would edit the single 'An'
field. A true, albeit crude, collaborative authoring
environment. Some level of security would be needed
for this, I suppose, to guard against vandalism.
An alternative would be Qn1/An1/An2/An3... with
editing by a restricted person/group authorized to sythesize
Qn/An . The problem would be that the time resource
limits of the restricted authorized person/group becomes
the bottleneck, as usual.
A third possibility is that An1/An2/An3... are progressively
edited and refined copies of the answer, so all the authorized
person/group needs to do is sanity-check the most recent
version, then dump it into An1 and get rid of An2/An3...
That more or less takes care of the security issue, and
might minimize the workload of the authorized person/group.
Comments?
Paul N.
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
