Hello everyone,
One of the main problems of under-resourced Wikipedias is the lack of
content in their languages. We want to tackle this problem by supporting
editors in creating more content in their languages easily.
We are working on a tool to support editors in creating new articles. The
editing tool (Scribe) will display a structure of the new article and
references (with their most important points) for each section, supported
by the information on Wikidata. The project is based on recent research in
document planning, reference discovery and collection, and document
summarization. One of the emphasizes of our project is to keep the
community involved in every step of the development to ensure that we are
serving their needs.
We are currently applying for a Wikimedia project grant and would like to
hear your feedback:
https://meta.wikimedia.org/wiki/Grants:Project/Scribe:_Supporting_Under-res…
Looking forward to hearing from you!
Best,
Lucie
--
Lucie-Aimée Kaffee
Hi,
I am puzzled by the behaviour of a SPARQL query. Maybe there is an error
with BlazeGraph here, but hopefully I am just overlooking something.
The query is as follows: http://tinyurl.com/y95jpmhq
SELECT ?item ?birthdate ?spouse
WHERE
{
{ ?item wdt:P569 ?birthdate
FILTER (year(?birthdate)>1900)
?item wdt:P26 []
} OPTIONAL {
?item wdt:P26 ?spouse
FILTER (year(?birthdate) = 1947)
}
# FILTER (year(?birthdate) = 1947) ## For testing: works correctly
} LIMIT 1000
What this should do: "Select married people born after 1900, and,
optionally, also select their spouses, but only for people born in
1947." What BlazeGraph does is: "Select married people born after 1900;
never select any spouses, even if the person is born in 1947".
The 1000 results should contain lines for 1947 births, so you can see
they have no spouse. The commented out filter at the bottom can be used
instead of the inner filter to verify that the condition has no typos
and really matches some of the items.
It seems that BlazeGraph gets the scope of ?birthdate wrong here, and
rather processes the whole query inside out, applying the FILTER to the
optional pattern (where ?birthdate is not bound) and then using the
(empty) result in a binary LeftJoin operation. In reality, LeftJoin in
the SPARQL algebra is a ternary operator that applies the FILTER to the
Join of both sides to determine if we have an optional match or not:
* See "Definition: LeftJoin" in Section 18.5 of the spec [1].
Filters within optional patterns become the third parameter in the
LeftJoin operation when translating queries as in my example:
* See example "{ ?s :p1 ?v1 OPTIONAL {?s :p2 ?v2 FILTER(?v1<3) } }" in
Section 18.2.3 of the spec [1].
Is my interpretation correct or did I overlook something? Is this a
known problem?
Cheers,
Markus
[1] https://www.w3.org/TR/sparql11-query
--
Prof. Dr. Markus Kroetzsch
Knowledge-Based Systems Group
Center for Advancing Electronics Dresden (cfaed)
Faculty of Computer Science
TU Dresden
+49 351 463 38486
https://kbs.inf.tu-dresden.de/
Forwarding to the Discovery list and more project email lists so that
people know that this feature change is coming.
Pine
( https://meta.wikimedia.org/wiki/User:Pine )
---------- Forwarded message ---------
From: Johanna Strodt <johanna.strodt(a)wikimedia.de>
Date: Wed, Nov 21, 2018 at 12:14 PM
Subject: [Translators-l] Fwd: AdvancedSearch announcement: looking for
translation support
To: <translators-l(a)lists.wikimedia.org>
Dear all,
the Advanced Search interface will soon become a default feature on
all wikis. Its deployment is planned for November 28.
The feature adds an advanced parameter form to the Special:Search page
in order to make already existing advanced search options such as
"intitle" or "subpageof" more visible and accessible for everyone. It
also changes the way namespaces can be selected.
We want to announce the upcoming deployment on village pumps with this
short message: https://meta.wikimedia.org/wiki/User:Johanna_Strodt_(WMDE)/Advanced_Search_…
The feature has already been deployed to deWP, arWP, faWP and huWP, so
we're now looking for translations in other languages.
We're planning to publish the message on Monday, Nov 26, around 11 am
UTC. Therefore it would be great to have the translations ready by
Monday November 26, 7 am UTC.
Thanks a lot. Any support is very appreciated!
Johanna
--
Johanna Strodt
Project Manager Community Communications Technical Wishlist
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0)30 219 158 26-0https://wikimedia.de
Imagine a world, in which every single human being can freely share in
the sum of all knowledge. That‘s our commitment.
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.
V. Eingetragen im Vereinsregister des Amtsgerichts
Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig
anerkannt durch das Finanzamt für Körperschaften I Berlin,
Steuernummer 27/029/42207.
_______________________________________________
Translators-l mailing list
Translators-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/translators-l
Greetings!
Thank you very much to those who have signed up to participate in the Months of African Cinema<https://en.wikipedia.org/wiki/Wikipedia:WikiProject_AfroCine/Months_of_Afri…> global contest/edit-a-thon, and thank you for your contributions so far.
We are moving towards the conclusion of the contest and a lot have been achieved already! We have been able to get over about 300 articles created in over eight (8) languages! The figures soars to up to a thousand, if Wikidata entries are included. Furthermore, there have been about 6 in-person gatherings of Wikipedians in different countries across the world to create articles about African(a) cinema!
We are very excited about what has been achieved so far, but your contributions are still needed to further exceed all expectations! Let’s create more articles before the end of this contest, which is this November!!!
* Article suggestions can be found here<https://en.wikipedia.org/wiki/Wikipedia:WikiProject_AfroCine/Article_Sugges…>. You can also add to this list.
* Some notable reliable sources for African cinema can be found here<https://en.wikipedia.org/wiki/Wikipedia:WikiProject_AfroCine/Reliable_Sourc…>. Again, this list needs expansion.
* Interested in Wikidata translation? check out the Occupation Drive<https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Wiki_Loves_Women/Occupa…>, which is being led by Wiki Loves Women, in support of the contest and the project!
* Please remember to list articles you have created or improved in the Article Achievements<https://en.wikipedia.org/wiki/Wikipedia:WikiProject_AfroCine/Months_of_Afri…> section of the contest page, so that they can be easily tracked.
Thank you once again for being part of this global event!
Kindly,
Sam Oyeyele.
Hi!
We are planning to change the prefix and associated URIs in RDF
representation for Wikidata from:
PREFIX wikibase: <http://wikiba.se/ontology-beta#>
to:
PREFIX wikibase: <http://wikiba.se/ontology#>
If you are using Wikidata Query Service, you do not have to do anything,
as WDQS already is using the new definition.
However, if you consume RDF exports from Wikidata or RDF dumps directly,
you will need to change your clients to expect the new URI scheme for
Wikibase ontology.
Also, if you're using Wikibase extension in your project, please be
aware that the RDF URIs generated by it will use this prefix after the
change. This is defined in repo/includes/Rdf/RdfVocabulary.php around
line 175:
self::NS_ONTOLOGY => self::ONTOLOGY_BASE_URI . "#",
The new data will have schema:softwareVersion "1.0.0" triple on the
dataset node[1], which will allow your software to distinguish the new
data format from the old one.
The task tracking the change is
https://phabricator.wikimedia.org/T112127. I will make another
announcement when the change is merged and deployed and the data
produced by Wikidata is going to change.
Please contact me (or comment in the task) if you have any questions or
concerns.
[1] https://www.mediawiki.org/wiki/Wikibase/Indexing/RDF_Dump_Format#Header
--
Stas Malyshev
smalyshev(a)wikimedia.org
Hi,
I just came across the English Wikipedia article on Wikidata. Parts of
it are very incomplete and outdated. The section "Reception" offers
three sentences that reflect the all-but-neutral POV of a single source,
weasel-wording around actually naming the person whose opinion was
reproduced here [1].
I feel too involved to edit this, but it would be nice if people who are
active in both communities could at least try to cover all relevant
aspects of this topic (e.g., awards won by Wikidata, views offered in
the media, actual usage with references, updated statistics about
statement references with pointers on where to get current numbers). A
full section on relevant critique could also be of interest. What is
currently there cannot even do this goal any justice, since it only
mentions concerns that are generic problems of all Wikimedia projects
alike (though not all of them can claim the same rate of citation
support ;-).
Cheers,
Markus
[1]
"""
Reception
There is concern that the project is being influenced by lobbying
companies, PR professionals and search engine optimizers.[27]
As of December 2015, according to Wikimedia statistics, half of the
information in Wikidata is unsourced.[27] Another 30% is labeled as
having come from Wikipedia.[27]
"""
I read through the current documentation and Talk pages, but didn't find
any cases for Aliases on Sense Statements.
But this seems useful. Let me explain...
https://www.wikidata.org/wiki/Lexeme:L36454
Verb: mistype
alias: fat finger
How to get that alias on L36454-S1 ?
"fat finger" would be a synonym phrase for the verb sense L36454-S1 of
"mistype".
I see this being extremely useful for building out "urban dictionaries",
etc. in the future.
-Thad
FYI: the annual Community Wishlist Survey from the Wikimedia Foundation is
now open for proposals. As usual, it has a Wikidata category.
---------- Forwarded message ---------
From: Johan Jönsson <jjonsson(a)wikimedia.org>
Date: Tue, 30 Oct 2018 at 12:36
Subject: [Wikimedia-l] The annual Community Wishlist Survey now open for
proposals
To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>, Wikimedia
developers <wikitech-l(a)lists.wikimedia.org>
Hey everyone,
The Community Wishlist Survey is now open, and you can post proposals
for projects that you would like the Wikimedia Foundation's Community
Tech team to work on:
https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2019
The Community Tech team builds features and makes changes that active
Wikimedia contributors want, and the Wishlist Survey sets the team's
agenda for the next year.
The Wishlist Survey starts with a two-week proposal period, when
contributors from all Wikimedia projects are invited to post, discuss
and improve proposals. After that, there's a two-week voting period,
when everyone can post support-votes on the proposals.
You can post technical proposals until 11 November.
You can vote on proposals from 16 November to 30 November.
The Community Tech team is responsible for addressing the top ten
wishes on the list. If they, after investigating it, find that
something isn't feasible, they need to explain why to the community.
The Wishlist can also be used by volunteer developers and other teams,
who want to find projects to work on that the community really wants.
//Johan Jönsson
--
_______________________________________________
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l(a)lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
<mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
--
Léa Lacroix
Project Manager Community Communication for Wikidata
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
10963 Berlin
www.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.