That's right! At the Wikimedia Developer Summit, we decided to organize a
Developer Wishlist Survey, and here we go:
https://www.mediawiki.org/wiki/Developer_Wishlist
The Wikimedia technical community seeks input from developers for
developers, to create a high-profile list of desired improvements. The
scope of the survey includes the MediaWiki platform (core software, APIs,
developer environment, enablers for extensions, gadgets, templates, bots,
dumps), the Wikimedia server infrastructure, the contribution process, and
documentation.
The best part: we want to have the results published by Wednesday, February
15. Yes, in a month, to have a higher chance to influence the
Wikimedia Foundation annual plan FY 2017-18.
There's no time to lose. *Propose your ideas before the end of January, *
either by pushing existing tasks in Phabricator or by creating new ones.
You can find instructions on the wiki page
<https://www.mediawiki.org/wiki/Developer_Wishlist>. Questions and feedback
are welcome especially on the related Talk page.
The voting phase is expected to start on February 6 (tentative). Watch this
space (or even better, the wiki page).
Cheers,
Srishti Sethi
Developer Advocate, Technical Collaboration team
Wikimedia Foundation
https://www.mediawiki.org/wiki/User:SSethi_(WMF)
I can confirm that, just had a chat at RDF4JUsers
<https://groups.google.com/forum/#%21topic/rdf4j-users/p-uqdjgGMHs>
where I was told that:
"In terms of getting the query to parse, why not just reorder the
BIND() to the front of the group? This is what blazegraph is doing
internally. "
So you guessed right (and we are going to treat those queries the same way).
Thanks and greetings,
Adrian
> Hi!
>
> On 1/14/17 9:23 AM, Adrian Bielefeldt wrote:
>> I was wondering if anybody could help me understand why (and how) this
>> query:
>>
>> SELECT DISTINCT ?item
>> WHERE
>> { ?tree0 wdt:P31 ?item . BIND (wd:Q146 AS ?tree0) }
>>
>> is being accepted by query.wikidata.org.
> Probably Blazegraph engine considers it analogous with the query having
> the bind in front, or maybe optimization reorders it.
>
>> At the moment we are parsing them using OpenRDF, which fails (as far
> as I can see understandably) at parsing this query.
>
> Well, the standard does say you can not use a variable in BIND that was
> previously used, and I guess OpenRDF parser chooses to be more strict
> than Blazegraph.
Hello everyone,
I'm writing on behalf of a Wikidata Research Project
<https://meta.wikimedia.org/wiki/Research:Understanding_Wikidata_Queries>
into
SPARQL-Queries.
I was wondering if anybody could help me understand why (and how) this
query:
SELECT DISTINCT ?item
WHERE
{ ?tree0 wdt:P31 ?item . BIND (wd:Q146 AS ?tree0) }
is being accepted by query.wikidata.org.
The reason I'm asking is that we are trying to parse the queries from
the wikidata logs and analyze them for different features. At the moment
we are parsing them using OpenRDF, which fails (as far as I can see
understandably) at parsing this query.
Greetings,
Adrian
Hi,
I found that if I have items, the first one matching the alias is found,
instead of a later one which matches the label.
Example:
Q1 Label=SomethingElse, Alias=ABC
Q2 Label=ABC
Would it be possible to make Q2 appear first?
This is most useful if I only ask for one entity, thus this would be the
best match.
Thanks!
Cheers
Miguel
Hi!
I'm starting to build my own Wikidata installation. Thanks for the great
work on this project!
One of my needs is to do a search and match ignoring diacritic marks.
For example: a search for "Comite" matching "Comité".
Is it feasible to change the Wikidata code to support this as an option?
Could you point me to the right place to make the change?
Thanks!
Regards,
Miguel