this is why i suggested making semantic mediawiki extensible. it will allow to give everyone their desired functionality, without needing to find a common set for everybody. anyone will be able to get the functionality he/she wants, but not those that are not interesting to him. with a small set of functionality, things should be simpler. this is what is so successful about mediawiki, firefox, eclipse etc. - you get something very basic and simple, but can extend it (by packages others create) to your desired taste.


ittay

Michael Cysouw wrote on 05/10/07 09:21:

On 9 May 2007, at 19:40, Yaron Koren wrote:

  
 I think one of
the big strengths of SMW is that it's a relatively simple concept -
there's only one way to declare a relation or attribute, and there's
only one place (that is, one page) where you can store any specific
relation or attribute.
    

I completely agree that this simplicitly is an important design  
principle, as wikis are supposed to be as easy as possible.

However, I'm still struggling with the problems posed by symmetric  
relations, and by pairs of inverse relations. In both cases, the same  
link (semantically speaking) can be added in two different places,  
actually duplicating information (which I think is unwanted) and  
making it more difficult for inline queries to find the information

For example, on the Amterdam page, one could say:

	[[capital of::Netherlands]]

And likewise, on the Netherlands page, one could state:

	[[has capital::Amsterdam]]

The information content of the two links is identical. SMW should  
ideally find such alternatives in inline queries, thus showing users  
that a particular piece of information is already present in the wiki  
(though on a different page than they might have envisioned it).

The basic idea would be, for example, to declare on the page  
{{Relation:capital of}} that it [[has inverse:has capital]]. This  
then should automatically lead to broaden the search of an inline  
query like:

	<ask>[[has capital::{{PAGENAME}}]]</ask>

to also do the inverse question:

	<ask>{{PAGENAME}} [[capital of::*]]</ask>

and merge the results into one table.

best
michael

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Semediawiki-user mailing list
Semediawiki-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-user

  

--
Ittay Dror
Chief Architect,
R&D, Qlusters Inc.
Web: qlusters.com
Email: [EMAIL PROTECTED]
Phone: +972-3-6081994

openQRM - Data Center Provisioning
------
I own this number: D0E008A921FF04A9DB8C12668E4315F4. Get your own at http://www.freedom-to-tinker.com
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Semediawiki-user mailing list
Semediawiki-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-user

Reply via email to