I am at the mozilla drumbeat event, and I met some of the enthusiastic
peopel of the wikimedia there. I discussed the following idea with
The following simple idea, I think, can create a huge impact in using
wikipedia for education as well as for navigation. I seek your
A new infobox item for every page.
** What other pages the learner should read/learn before the current page?
The idea is to build a specific link between pages that will
generate a learning sequence (or you wish a teaching sequence or a
The authors of wikipedia pages will add the names of the pages that
they think the reader of the page may need to read, if they fail to
understand the content of the page.
** How to do this?
http://atlas.gnowledge.org started hacking a model that generates
dependencies between activities or topics (concepts). For example,
you may look at the page:
The top links of the node are the links the user could visit, and
the bottom links are those that the user could viist after visiting
the current page.
** How to generate a learning sequence?
The set of all the dependency links will generate a sequence or a
road map for
This paper http://gnowledge.org/~nagarjun/collaborative-LTS-published-version.pdf
introduces the idea and what are the motivations and inspirations
of doing this.
** What wikimedia can do?
Currently http://atlas.gnowledge.org supports the following format
for adding the dependency links between the nodes.
factors < multiplication;
subtraction < difference;
product < multiplication;
factors < product;
division < factors; product;
fraction < division; multiplication;
division > remainder; divisor; quotient; dividend;
brackets > order of operations;
* '<' indicates 'dependson' whereas '>' indicates 'isrequiredfor'.
* Multiple relations in a single line are separated by semicolons ';'.
* Do not use word processors for creating the files. Use text
editors like notepad, emacs, gedit, vi etc.
The proposal is to introduce a similar encoding that is easy for the
authors of wikipedia to suggest while they edit or create a page.
I have a mediawiki installation at:
I would like to share documents like .doc, .ppt, .pdf, .xls file with my
clients through the "upload File" section. This is what I am looking for:
1. Each client will have separate permissions i.e. a file uploaded by client
1 cannot be accessed (view/modify/delete) by client 2.
2. As an Administrator if I upload a file I can specifically assign which
client has access to the file.
3. A client can also see what files are uploaded on the wiki to which they
have access only.
4. Not anybody can register on the wiki. I specifically create user accounts
for my clients and send them their login info.
5. Similarly for the pages on the wiki, I would like to assign specific
permission to my clients to access them. I guess the best thing would be to
create a separate ground for each client?
What all extensions will I need in order to achive the above? Is there any
best practice for this kind of a scenario?
Your thoughts/inputs are highly appreciated.
So, I created a wiki and installed the Semantic Bundle. The last
step involved announcing my wiki, which I did. I don't see it anywhere in
any list though. It just started so there isn't much to see but I am
curious about the smw submission process and how to get listed.