Hey :)
We are currently discussing if we should also offer .nt dumps:
https://phabricator.wikimedia.org/T144103
Since we'd need to set that up and maintain it I want to make sure
there is actually demand for it. So if you'd like to have it and use
it please let me know.
Cheers
Lydia
--
Lydia Pintscher - http://about.me/lydia.pintscher
Product Manager 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.
Hi all!
This is an announcement for a breaking change to the Wikidata API, JSON and RDF
binding, to go live on 2016-11-15. It affects all clients that process quantity
values.
As Lydia explained in the mail she just sent to the Wikidata list, we have been
working on improving our handling of quantity values. In particular, we are
making upper- and lower bounds optional: When the uncertainty of a quantity
measurement is not explicitly known, we no longer require the bounds to somehow
be specified anyway, but allow them to be omitted.
This means that the upperBound and lowerBound fields of quantity values become
optional in all API input and output, as well as the JSON dumps and the RDF mapping.
Clients that import quantities should now omit the bounds if they do not have
explicit information on the uncertainty of a quantity value.
Clients that process quantity values must be prepared to process such values
without any upper and lower bound set.
That is, instead of this
"datavalue":{
"value":{
"amount":"+700",
"unit":"1",
"upperBound":"+710",
"lowerBound":"+690"
},
"type":"quantity"
},
clients may now also encounter this:
"datavalue":{
"value":{
"amount":"+700",
"unit":"1"
},
"type":"quantity"
},
The intended semantics is that the uncertainty is unspecified if not bounds are
present in the XML, JSON or RDF representation. If they are given, the
interpretation is as before.
For more information, see the JSON model documentation [1]. Note that quantity
bounds have been marked as optional in the documentation since August. The RDF
mapping spec [2] has been adjusted accordingly.
This change is scheduled for deployment on November 15.
Please let us know if you have any comments or objections.
-- daniel
[1] https://www.mediawiki.org/wiki/Wikibase/DataModel/JSON
[2] https://www.mediawiki.org/wiki/Wikibase/Indexing/RDF_Dump_Format#Quantity
Relevant tickets:
* <https://phabricator.wikimedia.org/T115269>
Relevant patches:
* <https://gerrit.wikimedia.org/r/#/c/302248>
*
<https://github.com/DataValues/Number/commit/2e126eee1c0067c6c0f35b4fae0388f…>
--
Daniel Kinzler
Senior Software Developer
Wikimedia Deutschland
Gesellschaft zur Förderung Freien Wissens e.V.
Hi all!
I plan to add the wikibase (SQL) database schema as a stable interface.
Typically, a database schema is considered internal, but since we have tools on
labs that may rely on the current schema, breaking changes to the schema should
be announced as such. To address this, I plan to add the following paragraph to
the Stable Public APIs section:
The database schema as exposed on Wikimedia Labs is considered a stable
interface. Changes to the available tables and fields are subject to the
above notification policy.
In addition, I plan to add the following paragraph to the Extensibility section:
In a tabular data representation, such as a relational database schema, the
addition of fields is not considered a breaking change. Any change to the
interpretation of a field, as well as the removal of fields, are considered
breaking. Changes to existing unique indexes or primary keys are breaking
changes; changes to other indexes as well as the addition of new unique
indexes are not breaking changes.
If you have any thoughts ob objections, please let me know at
<https://www.wikidata.org/wiki/Wikidata_talk:Stable_Interface_Policy#Databas…>
--
Daniel Kinzler
Senior Software Developer
Wikimedia Deutschland
Gesellschaft zur Förderung Freien Wissens e.V.
Hello all,
This is the last day of our birthday week. Today, let's play a very nice
puzzle game created by Denny. It's based on Wikidata items and properties,
and the goal is to organize the elements in the grid and figure out how
they fit together. You will see, it's not always easy... You can *play the
game here <https://tools.wmflabs.org/everythingisconnected/index.html>*,
discover
other levels
<https://www.wikidata.org/wiki/Wikidata:Everything_is_connected> and even
create you own levels.
Thanks to the contributors: YULdigitalpreservation, ThurnerRupert, Tobijat,
Bináris, Maxlath, Incabell for adding levels!
The story of the day is *You know you're a Wikidata editor when...
<https://www.wikidata.org/wiki/Wikidata:Fourth_Birthday/Stories/You_know_you…...>*
inspired from ideas by VIGNERON, Harmonia Amanda, Ash_Crow... and modestly
drawn by me. Feel free to translate it in your own language!
Tonight is the birthday meetup in Berlin
<https://www.wikidata.org/wiki/Wikidata:Fourth_Birthday/Events/Berlin>. I
can't wait too meet some of you there :)
Thanks to everyone who participated by offering a present, a story, or
letting a message on the birthday page
<https://www.wikidata.org/wiki/Wikidata:Fourth_Birthday>!
Cheers,
--
Léa Lacroix
Community Communication Manager 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.
Hello all,
Only two days of birthday announcements remaining, and today's a pretty
cool one :)
We integrated the *graph builder tool into the query service*. It's a
lightweight tableau-style interface for visual analysis, built on Vega-lite
<http://vega.github.io/polestar/>, that's allows you to create and
personalize your graph, based on the query results. Once it's done, you can
also integrate it in Wikidata or Wikipedia, using the graph extension
<https://www.mediawiki.org/wiki/Extension:Graph>!
For now, the tool encounter some problems in Firefox, but works well with
Chrome or Chromium. We'll try to fix is as soon as possible. Thanks a lot
to Jonas and Smalyshev for your work!
Check out the demo video
<https://commons.wikimedia.org/wiki/File:WDQS_GUI_graph_builder_demo.webm>
to see how it works, and try it with your favorite query ;)
The story of the day has been shared by Denny. *Everything starts when you
click on the "random item" link
<https://lists.wikimedia.org/pipermail/wikidata/2016-May/008711.html>...*
Check also the nice gift from TomT0m: Module:PropertyPath
<https://www.wikidata.org/wiki/Wikidata:Project_chat#My_little_gift_for_Wiki…>
!
Cheers,
--
Léa Lacroix
Community Communication Manager 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.
Hello!
I'd like to draw your attention to a request-for-comment that we started
recently:
https://www.wikidata.org/wiki/Wikidata:Requests_for_comment/Editing_descrip…
tldr: We'd like to allow our Android users to edit Wikidata descriptions
directly from the app, and we'd like your input and feedback on our
proposed workflow, as well as any potential pitfalls that we should
consider.
Looking forward to your comments!
--
Dmitry Brant
Senior Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
ESWC2017 – 2nd CALL FOR PAPERS
conference: 28 May to 1 June 2017 in Portorož, Slovenia
submission: 7 December (abstract) and 14 December 2016 (paper)
details: http://2017.eswc-conferences.org/call-papers
ESWC is a major venue for discussing scientific results and innovations around semantic technologies. ESWC 2017 welcomes original research and application papers dealing with all aspects of semantics on the Web. We encourage theoretical, methodological, empirical, and applications papers. Papers should describe original work, present significant results, and provide rigorous, principled, and repeatable evaluation.
1) ESWC2017 PHD SYMPOSIUM (details: http://2017.eswc-conferences.org/call-phd)
Early-stage or late-stage PhD students in all areas of the Semantic Web can submit a paper describing their PhD research. Submissions need to follow the template on the website.
2) ESWC2017 SPECIAL TRACKS (details: http://2017.eswc-conferences.org/call-papers/)
The 2017 edition introduces two new tracks:
– Multilinguality
– Semantic Web and Transparency
Managing multilingual data requires semantic normalization and reconciliation to make the Semantic Web reach people around the world. Transparency concerns relationships between people and both commercial and authoritative entities, using semantic technologies with objectives varying from enabling trust to ensuring accountability.
3) ESWC2017 IN USE AND INDUSTRIAL TRACK (details: http://2017.eswc-conferences.org/call-papers#12)
This track demonstrates the impact of Semantic Web Technologies in concrete applications and in industry.
4) ESWC2017 RESEARCH TRACKS (details: http://2017.eswc-conferences.org/call-papers/)
The 9 research tracks cover major current Semantic Web subdomains:
– Vocabularies, Schemas, Ontologies
– Reasoning
– Linked Data
– Social Web and Web Science
– Semantic Data Management, Big data, Scalability
– Natural Language Processing and Information Retrieval
– Machine Learning
– Mobile Web, Sensors and Semantic Streams
– Services, APIs, Processes and Cloud Computing
DATES
– abstract: 7 December 2016 (required, except PhD symposium)
– paper: 14 December 2016
– notification: 20 February 2017 (20 January for PhD symposium)
PAPER SUBMISSION
– full details: http://2017.eswc-conferences.org/call-papers / http://2017.eswc-conferences.org/call-phd
– template: LNCS
– limit: 15 pages (5–10 pages for PhD symposium)
– format: PDF, or zipped HTML (RASH, dokieli, …)
– submission: https://easychair.org/conferences/?conf=eswc2017 and https://easychair.org/conferences/?conf=eswc2017phd
– We encourage links to datasets and other evaluation material, as well as to live demos and source code.
– Springer will publish the proceedings in its Lecture Notes in Computer Science series.
ABOUT ESWC2017
ESWC is one of the key academic conferences to present research results and new developments in the area of the Semantic Web. This endeavour naturally draws from and impacts on many disciplines of computing (and connected areas), related to data and information management, knowledge engineering, machine intelligence, human knowledge and languages, software services and applications. We are therefore seeking contribution to research at the intersection of the Semantic Web and these areas, as described in the 9 core research tracks of the conferences, as well as demonstration of the impact of Semantic Web Technologies in concrete applications and in industry, through the “In Use and Industrial” Track.
GENERAL CHAIR: Eva Blomqvist, Linköping University, Sweden – eva.blomqvist(a)liu.se
PROGRAM CHAIRS: Diana Maynard, University of Sheffield, UK – d.maynard(a)sheffield.ac.uk
and Aldo Gangemi, Paris Nord University, France – gangemi(a)lipn.univ-paris13.fr
ESWC will not accept research papers that, at the time of submission, are under review for or have already been published in or accepted for publication in a journal or another conference.
