On Sun, Jan 17, 2010 at 11:32 AM, Denny Vrandecic
<denny.vrandecic(a)kit.edu> wrote:
I was not talking about WIkipedia -- even though our
scalability tests suggest that it could work there, but it is hard to say in advance
without testing on the actual WMF server farm. I am merely talking about Wikisource, and
wondering if it could be used to solve the problems they have, right now.
The code still must undergo security review to be enabled on any
Wikimedia site. As I said, we don't even have enough reviewers right
now to review core code, let alone large new extensions, so it's
really not likely in the near future. Even small extensions would
probably have a hard time getting enabled right now.
On Sun, Jan 17, 2010 at 11:40 AM, Dmitriy Sintsov <questpc(a)rambler.ru> wrote:
Intersections probably are inefficient when someone
needs a range search
between, let's say 1944 and 1965. SMW has probably right approach that
something sequental and numerical like date, mass, speed should not be a
Category but a Property..
Yes, that would be awkward to phrase in Lucene search. The point is,
anyway, that enabling something like SMW (probably with fewer
features) is orthogonal to RDFa/microdata/RDF support -- the extension
could incidentally output RDF or whatnot, but it doesn't matter for
internal use.
Also, it's a bit sad that so many toolserver tools
are standalone and
are not a part of MediaWiki distribution. That tool should be a part of
Special:Search.
Most toolserver tool authors just don't bother applying for commit
access for whatever reason. Most tools also either perform badly
and/or would need to be rewritten to meet coding standards.
Toolserver roots routinely have to kill processes for using up
unreasonable amounts of resources.
When comes to subcategories, I always wondered why
they have to include
the name of parent category:
http://en.wikipedia.org/wiki/Category:Books
The word "Books" is repeated many times through the nested categories,
although we already know these are the "Books".
Because categories in MediaWiki form a directed graph, not a tree.
Categories don't have a unique parent. Whether this is good or bad is
debatable.