I agree that for some wikis it's not a problem, but the default
behavior in SMW is to treat them as equivalents, so I assume that
many wikis would like to treat redirects as equivalents. However,
wikis like mine that are catered towards searching can't afford to
have $smwgQEqualitySupport set to true, because it makes searches
much more resource intensive--redirect equivalency is the most
expensive component in a search. If you want the numbers for some of
my benchmarks that demonstrate this:
One property search ( [[property::object]] ) --
redirect equiv on: .05 sec, off: .00 sec
Two different properties search ( [[property1::object1]]
[[property2::object2]] ) --
redirect equiv on: .06 sec, off: .00 sec
Small simple subquery ( [[property::<q>[[Category:Small]]</q>]] ) --
redirect equiv on: .09 sec, off: .00 sec
Small category disambiguation ([[property::<q>[[Category:Small1||
Small2]]</q>]]) --
redirect equiv on: .16 sec, off: .00 sec
Two relatively small simple subqueries ([[property::<q>
[[Category:Small1]]</q>]] [[property::<q>[[Category:Medium1]]</q>]] --
redirect equiv on: .50 sec, off: .01 sec
Large three simple subqueries ([[property::<q>[[Category:Hefty1]]</
q>]] [[property::<q>[[Category:Hefty2]]</q>]] [[note::<q>
[[Category:Hefty3]]</q>]]) --
redirect equiv on: 34 in 48 sec, off: .3 sec
For the last one, it's a difference between a search that looks like
this:
SELECT DISTINCT `page`.page_title as title, `page`.page_namespace as
namespace, `page`.page_id as id
FROM `cats17`, `prop13`, `cats11`, `prop7`, `cats5`, `prop1`, `page`
INNER JOIN `smw_relations` AS rel0 ON rel0.subject_id=`page`.page_id
LEFT JOIN `redirect` AS rd3 ON rd3.rd_from=rel0.object_id
LEFT JOIN `page` AS rp4 ON (rd3.rd_title=rp4.page_title AND
rd3.rd_namespace=rp4.page_namespace)
INNER JOIN `categorylinks` AS cl2 ON ((cl2.cl_from=rel0.object_id)
OR (rp4.page_id=cl2.cl_from))
INNER JOIN `smw_relations` AS rel6 ON rel6.subject_id=`page`.page_id
LEFT JOIN `redirect` AS rd9 ON rd9.rd_from=rel6.object_id
LEFT JOIN `page` AS rp10 ON (rd9.rd_title=rp10.page_title AND
rd9.rd_namespace=rp10.page_namespace)
INNER JOIN `categorylinks` AS cl8 ON ((cl8.cl_from=rel6.object_id)
OR (rp10.page_id=cl8.cl_from))
INNER JOIN `smw_relations` AS rel12 ON
rel12.subject_id=`page`.page_id
LEFT JOIN `redirect` AS rd15 ON rd15.rd_from=rel12.object_id
LEFT JOIN `page` AS rp16 ON (rd15.rd_title=rp16.page_title AND
rd15.rd_namespace=rp16.page_namespace)
INNER JOIN `categorylinks` AS cl14 ON
((cl14.cl_from=rel12.object_id) OR (rp16.page_id=cl14.cl_from))
WHERE (prop1.title=rel0.relation_title AND
(cats5.title=cl2.cl_to)) AND (prop7.title=rel6.relation_title
AND (cats11.title=cl8.cl_to)) AND
(prop13.title=rel12.relation_title AND (cats17.title=cl14.cl_to))
ORDER BY `page`.page_title ASC LIMIT 21;
And a search that looks like this:
SELECT DISTINCT `page`.page_title as title, `page`.page_namespace as
namespace, `page`.page_id as id
FROM `cats17`, `prop13`, `cats11`, `prop7`, `cats5`, `prop1`, `page`
INNER JOIN `smw_relations` AS rel0 ON rel0.subject_id=`page`.page_id
INNER JOIN `categorylinks` AS cl2 ON ((cl2.cl_from=rel0.object_id))
INNER JOIN `smw_relations` AS rel6 ON rel6.subject_id=`page`.page_id
INNER JOIN `categorylinks` AS cl8 ON ((cl8.cl_from=rel6.object_id))
INNER JOIN `smw_relations` AS rel12 ON rel12.subject_id=`page`.page_id
INNER JOIN `categorylinks` AS cl14 ON ((cl14.cl_from=rel12.object_id))
WHERE (prop1.title=rel0.relation_title AND (cats5.title=cl2.cl_to))
AND (prop7.title=rel6.relation_title
AND (cats11.title=cl8.cl_to)) AND
(prop13.title=rel12.relation_title AND (cats17.title=cl14.cl_to))
ORDER BY `page`.page_title ASC LIMIT 21;
So, some wikis might like to annotate redirect pages and have them
not be equivalent to what they redirect to, like what you describe.
But others might need to turn redirect equivalencies off for
performance reasons and then a redirected annotations page to see
which annotations need changing so they can be included in searches
again would come in handy.
--Audra
On Nov 19, 2007, at 7:23 AM, Mov GP 0 wrote:
> Hi,
> I don't think that its a problem, because you can annotate
> Redirection-Pages too. This makes sense, because in the Wikipedia, not
> all information is stored atomically. Instead, Redirects are often
> redirecting to subsections of bigger articles. It is also possible to
> categorize or translate Redirection-Pages, so why not semantically
> annotate them? I think this makes sense.
>
> If there would not be this possible, the Articles in the Wikipedia
> would need to get rewritten so the information becomes more atomic.
>
> ys, MovGP0
>
>
> On Nov 19, 2007 1:05 AM, Audra Johnson <[EMAIL PROTECTED]> wrote:
>> A few weeks ago, I discovered that searches with a few subqueries
>> were dreadfully slow and found the cause to be making annotated
>> redirects equivalent to their targets. I suggested making redirect
>> equivalency a SMW option--but when I went scanning for how to
>> implement it, I gleefully found that it was already included! The
>> setting is:
>>
>> $smwgQEqualitySupport = true; // Should #redirects be evaluated as
>> equality between page names?
>>
>> (It should probably include a note about efficiency for its comment,
>> just like the one for $smwgQDefaultNamespaces--taking out redirect
>> equality support can make a HUGE difference for more complex
>> queries. HUGE being the difference between a three subquery search
>> taking 34 minutes with redirect equivalency and .3 seconds without.)
>>
>> In any case, my semantic wiki has been happily humming and searching
>> along since I set $smwgQEqualitySupport to false. But I also need
>> a way to tell where annotations in the wiki are pointing to
>> redirected pages, so they can be fixed.
>>
>> So I've made a special page for redirected annotations that extends
>> SMWQueryPage. This will make it easy for people to find where
>> annotations are pointing to redirected pages and fix them to point at
>> the right ones.
>>
>> Messages that would are added for this page:
>>
>> // Messages for Redirected Annotations Special
>> 'redirectedannotations' => 'Redirected annotations',
>> 'smw_redirectedannotations_docu' => 'The object of these
>> annotations
>> points to a redirected page.',
>> 'smw_redirectedannotations_template' => 'On page $1, the
>> annotation
>> $2::$3 redirects to $4.',
>>
>> It required one additional function to SMW_SQLStore in the "Special
>> page functions" section:
>>
>> function getRedirectedAnnotationsSpecial($requestoptions = NULL) {
>> wfProfileIn
>> ("SMWSQLStore::getRedirectedAnnotationsSpecial (SMW)");
>> $db =& wfGetDB( DB_SLAVE );
>> $options = ' ORDER BY subject_title';
>>
>> if ($requestoptions->limit > 0) {
>> $options .= ' LIMIT ' . $requestoptions-
>> >limit;
>> }
>> if ($requestoptions->offset > 0) {
>> $options .= ' OFFSET ' . $requestoptions-
>> >offset;
>> }
>>
>> extract( $db->tableNames('smw_relations',
>> 'redirect') );
>>
>> $res = $db->query("SELECT subject_title,
>> subject_namespace,
>> relation_title, object_title, object_namespace, rd_title,
>> rd_namespace FROM $smw_relations "
>> . "INNER JOIN $redirect ON
>> $smw_relations.object_id =
>> $redirect.rd_from"
>> . $options,
>> 'SMW::getRedirectedAnnotationsSpecial');
>> $result = array();
>>
>> while($row = $db->fetchObject($res)) {
>> $subject_page = Title::newFromText($row-
>> >subject_title, $row-
>>> subject_namespace);
>> $relation_page = Title::newFromText($row-
>> >relation_title,
>> SMW_NS_PROPERTY);
>> $object_page = Title::newFromText($row-
>> >object_title, $row-
>>> object_namespace);
>> $rd_page = Title::newFromText($row-
>> >rd_title, $row->rd_namespace);
>> $result[] = array($subject_page,
>> $relation_page, $object_page,
>> $rd_page);
>> }
>>
>> wfProfileOut
>> ("SMWSQLStore::getRedirectedAnnotationsSpecial (SMW)");
>> return $result;
>> }
>>
>> And it needs to be added in the enableSemantics() function in
>> SMW_GlobalFunctions.php:
>>
>> $wgSpecialPages['RedirectedAnnotations'] = array
>> ('SMWSpecialPage','RedirectedAnnotations',
>> 'smwfDoSpecialRedirectedAnnotations', $smwgIP . '/specials/
>> QueryPages/
>> SMW_SpecialRedirectedAnnotations.php');
>>
>> I've attached the PHP code for the page itself.
>>
>> Am looking for input on:
>>
>> * Whether the special page should be initialized and included only if
>> $smwgQEqualitySupport = false
>> * Whether the page name RedirectedAnnotations is an adequate name
>> * Other wording that should be changed or tweaked. For example, in
>> the smw_redirctedannotations_temp:
>> * Message text: "the annotation Similar to::X redirects to Y." or
>> "the relation Similar to::X redirects to Y.", since this only happens
>> to relation annotations? "The object of these annotations points to a
>> redirected page." or "The object of these relations points to a
>> redirected page." ?
>> * Coding style
>>
>>
>>
>> ---------------------------------------------------------------------
>> ----
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2005.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Semediawiki-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
>>
>>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Semediawiki-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
