Ideas from Thilo 'vinci' Pfennig

Licenses for sections

I would suggest to copy the Tikiwiki feature to enable to select a license for each content that is added. The licenses could be preselected or the user could make a link.

licenses should be at minimum:

• public domain
• GFDL

This should be in the version system. This could enable to change licenses of all texts at once. This could become complicated, but I think this is how it really should be done. So it culd be clear that some parts of a page are under a restrictive license and some are not. If a user wants to edit the whole page with different licenses he should be warned. Maybe this can be added with the options of "section editing" that are planned. Allthough this can be "messy" from a programmers perspective it ios highly desirable, because there are different authors and licenses

ThirdPartyApplications

Just got that idea as I looked at my mail client: What about an application that is like newsfeed readers, blog posters or mail clients, but it is used to communicate with a wiki or wikis? You then could use the wiki not by clicking on html links, but you use pull-down menus. And you can connect to one or more wikis. You can refresh at specific times You might then get a message if a page that you watch has changed (the application looks at RecentChanges or RDF to find out). You could Select File->New Page or File->New Page from Template - one might even think about sharing of templates, so that I can use a template of Apache wiki for this wiki here. It should also be possible top copy or move pages from one wiki to the other or to sync different pages. Certainly people could use the normal GUI tools of their OS to edit the pages. Those applications also could play around with some graphics without having the wiki engine doing that. If people edit wikis with this tool online CPU can sleep more often.

Ideas to structure data

I got an interesting idea. Why not put all normal pages in a pseudo namespace:

• /Pages/

And hen also have possible something like:

• /System/ or

• `/Help/'

This way one could more easily speperate content. This would allow to cleary handle request differently by URL. And you always no if you are looking at a system page, a help page, or a created page.