Jim Stuttard a écrit :
On Tue, 07 Jun 2005 09:54:21 +0200, Ludovic Dubost
<ludovic(a)xwiki.com> wrote:
XWiki and CMS are mailing differentiate by the role you give your
visitors..
With CMS there is a distinctions between writer and reader and they get
different user interfaces.
In XWiki (and Wiki in general) it's the same interface and writing is
considered as important as reading.
Agreed.
So the more your subject requires or takes
advantage of the implications
of your users, the better XWiki is. The more the writers want to
"control" the publishing process, the better CMSs are.
That's perhaps why in a more democratic knowledge base the divisions
between a wiki, a wikipedia, a wikiblog and a content management
system are getting blurred.
For example an academic department where I've just done some mentoring
has selected Plone for its CMS. They also want to show student work.
I have a current interest in ontologies for process modelling of
healthcare pathways and protocols. UML-enabled clinicians are drawing
up the protocols and everybody needs to see them. So there does seems
a democratising trend.
There would be a problem if this was just another turn of the
"end-user programming", 4GL cycle. IMHO lightweight tools for all is
how things are likely to be. But remember the blight of
badly-designed Filemaker Pro databases produced by scientists,
academics and clinicians or the study showing >5% London city
financial institution spreadsheets contained for mula errors. It's
got to be a horses for courses future.
Yes it's a problem.. End user design leaves always room for errors...
But a way to see this is that it wouldn't be done at all if there wasn't
end use tools.. So the 5% errors is not that bad.. With network tools I
think we can improve the model. The good thing about programming in
XWiki is that you can have much more easily experienced people review
what end-users have done. People that have the content knowledge can
more easily share the work with people that are the programmers. They
can work together in the same tool.. This is not the case of the more
classical approach of separating application design from application usage.
Wikis
don't have advanced features for validations
I'm not quite sure what you mean specifically. But, say, an academic
results or clinical wiki needs guaranteed authentification and
validated information __and__ robustness. Won't lots more
'technical', as it were, validation have to occur on an extended
XWiki when it provides, say, streaming video.
Taking on board what you say then perhaps what might be good is for
Lenya to become more like XWiki or have an XWiki interface and
receive a coplet/portlet web service through the Lenya api?
Not sure what you mean here.. Integration is always interesting..
Well that's were CMS is different and complementary to Wikis.. Now you
can do it both ways.. Implement some sort of validation in a Wiki..
Implement soem sort of Wiki in a CMS.. You can also keep the tools
separate.. and integrate them using a portal (XWiki can be integrated in
eXo and soon JBoss Portal).
you want
everybody to be equal..
so there is not reason to why they would not see an incomplete document.
We already have selective access rights so it's not that we always
want everybody to have equal access.
Right.. but we encourage to use viewing rights more than editing rights..
XWiki is such a large project, it's the consensus
road map statement
I'm trying to get. The Google project list is an excellent start and
a statement of how these are going to integrate should keep folks
busy for many hackathons.
Yes.. I've been relunctant to build a roadmap because there wasn't the
actual critical mass to implement it.. I tend to view a roadmap
something on whcih we would commit.. Now we could do some sort of
tentative roadmap without dates showing our priorities..
Hope you don't mind the not-apparently-productive
rambles.
Not at all.. we need to know how we can help getting more people on board..
Ludovic
Cheers
Jim
------------------------------------------------------------------------
--
You receive this message as a subscriber of the xwiki-dev(a)objectweb.org mailing list.
To unsubscribe: mailto:xwiki-dev-unsubscribe@objectweb.org
For general help: mailto:sympa@objectweb.org?subject=help
ObjectWeb mailing lists service home page:
http://www.objectweb.org/wws
--
Ludovic Dubost
XPertNet:
http://www.xpertnet.fr/
Blog:
http://www.ludovic.org/blog/
XWiki:
http://www.xwiki.com
Skype: ldubost AIM: nvludo Yahoo: ludovic