https://bugzilla.wikimedia.org/show_bug.cgi?id=20620

--- Comment #3 from Markus Krötzsch <[email protected]> 2012-11-20 
18:42:04 UTC ---
Revisiting this request, I have to say that this is very hard to handle in the
current implementation. All query answering is fundamentally based on the
notion that each (potential) result has only one title string. This is correct
for sorting and exact matching. To allow queries to even consider other
alternative titles, one would need to JOIN this information into all queries.
This is a major performance threat (we had a similar system of joining in all
redirects in early versions of SMW).

It is also not clear if this behaviour corresponds to the meaning of redirects,
which by definition *refer to* something else. In your example, the information
stored by SMW is [[Symptom::Makroglossie]] and nothing else. What you are
asking for is that SMW retracts incoming redirects, i.e., evaluates redirects
*backwards* to find that this *could* be stated by typing
[[Symptom::Zungenvergrößerung]], and takes all of the potential spellings thus
obtained into account for pattern matching. This would be a new interpretation
of redirects. Currently the pattern search performs string matching over the
data that is really stored, and this data does not involve anything that would
match [[Symptom::~*Zunge*]].

I leave it open whether we should address this at some point (should we then
also do this for sorting comparators? what about {{#ask:[[Symptom::>Z]]}}?). If
this ever gets implemented, it should be configurable and probably switched off
by default. I think my suggestion of storing synonyms in another way, e.g.,
using a string property "Synonym", is still a valid workaround.

-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to