Menu
▾
▴
Re: [Semediawiki-user] Extensible semantic mediawiki?
|
From: Ittay D. <it...@ql...> - 2007-05-10 08:35:56
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body dir="ltr" bgcolor="#ffffff" text="#000000">
<p style="margin-bottom: 0cm; margin-top: 0pt;">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.</p>
<p style="margin-bottom: 0cm; margin-top: 0pt;"><br>
</p>
<p style="margin-bottom: 0cm; margin-top: 0pt;">ittay<br>
</p>
<p style="margin-bottom: 0cm; margin-top: 0pt;">Michael Cysouw wrote on
05/10/07 09:21:<br>
</p>
<blockquote cite="mid:66B...@ev..."
type="cite">
<pre wrap="">On 9 May 2007, at 19:40, Yaron Koren wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> 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.
</pre>
</blockquote>
<pre wrap=""><!---->
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.
<a class="moz-txt-link-freetext" href="http://sourceforge.net/powerbar/db2/">http://sourceforge.net/powerbar/db2/</a>
_______________________________________________
Semediawiki-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Sem...@li...">Sem...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/semediawiki-user">https://lists.sourceforge.net/lists/listinfo/semediawiki-user</a>
</pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<b>Ittay Dror</b>
<br>
Chief Architect,
<br>
R&D, Qlusters Inc.
<br>
Web: <a href="http://www.qlusters.com/">qlusters.com</a>
<br>
Email: <a href="mailto:it...@ql...">it...@ql...</a>
<br>
Phone: +972-3-6081994 <br>
<br>
<a href="www.openqrm.org">openQRM</a> - Data Center Provisioning
<br>
------
<br>
I own this number: D0E008A921FF04A9DB8C12668E4315F4. Get your own at
<a class="moz-txt-link-freetext" href="http://www.freedom-to-tinker.com">http://www.freedom-to-tinker.com</a>
</div>
</body>
</html>
|