Apologies for cross-posting
Call for Posters & Demos
SEMANTiCS 2017 - The Linked Data Conference
13th International Conference on Semantic Systems
Amsterdam, Netherlands
September 11 -14, 2017
http://2017.semantics.cc
For details please go to: https://2017.semantics.cc/calls
Important Dates (Posters & Demos Track):
*Submission Deadline: July 10, 2017 (11:59 pm, Hawaii time)
*Notification of Acceptance: August 10, 2017 (11:59 pm, Hawaii time)
*Camera-Ready Paper: August 18, 2017 (11:59 pm, Hawaii time)
As in the previous years, SEMANTiCS’17 proceedings will be published by
ACM ICPS (pending) and CEUR WS proceedings.
This year, SEMANTiCS features a special Data Science track, which is an
opportunity to bring together researchers and practitioners interested
in data science and its intersection with Linked Data to present their
ideas and discuss the most important scientific, technical and
socio-economical challenges of this emerging field.
SEMANTiCS 2017 will especially welcome submissions for the following hot
topics:
*Metadata, Versioning and Data Quality Management
*Semantics for Safety, Security & Privacy
*Web Semantics, Linked (Open) Data & schema.org
*Corporate Knowledge Graphs
*Knowledge Integration and Language Technologies
*Economics of Data, Data Services and Data Ecosystems
Special Track (please check appropriate topic in submission system)
*Data Science
Following the success of previous years, we welcome any submissions
related but not limited to the following ‘horizontal’ (research) and
‘vertical’ (industries) topics:
Horizontals:
*Enterprise Linked Data & Data Integration
*Knowledge Discovery & Intelligent Search
*Business Models, Governance & Data Strategies
*Semantics in Big Data
*Text Analytics
*Data Portals & Knowledge Visualization
*Semantic Information Management
*Document Management & Content Management
*Terminology, Thesaurus & Ontology Management
*Smart Connectivity, Networking & Interlinking
*Smart Data & Semantics in IoT
*Semantics for IT Safety & Security
*Semantic Rules, Policies & Licensing
*Community, Social & Societal Aspects
Data Science Special Track Horizontals:
*Large-Scale Data Processing (stream processing, handling large-scale
graphs)
*Data Analytics (Machine Learning, Predictive Analytics, Network Analytics)
*Communicating Data (Data Visualization, UX & Interaction Design,
Crowdsourcing)
*Cross-cutting Issues (Ethics, Privacy, Security, Provenance)
Verticals:
*Industry & Engineering
*Life Sciences & Health Care
*Public Administration
*e-Science
*Digital Humanities
*Galleries, Libraries, Archives & Museums (GLAM)
*Education & eLearning
*Media & Data Journalism
*Publishing, Marketing & Advertising
*Tourism & Recreation
*Financial & Insurance Industry
*Telecommunication & Mobile Services
*Sustainable Development: Climate, Water, Air, Ecology
*Energy, Smart Homes & Smart Grids
*Food, Agriculture & Farming
*Safety, Security & Privacy
*Transport, Environment & Geospatial
Posters & Demos Track
The Posters & Demonstrations Track invites innovative work in progress,
late-breaking research and innovation results, and smaller contributions
in all fields related to the broadly understood Semantic Web. These
include submissions on innovative applications with impact on end users
such as demos of solutions that users may test or that are yet in the
conceptual phase, but are worth discussing, and also applications, use
cases or pieces of code that may attract developers and potential
research or business partners. This also concerns new data sets made
publicly available.
The informal setting of the Posters & Demonstrations Track encourages
participants to present innovations to the research community, business
users and find new partners or clients and engage in discussions about
the presented work. Such discussions can be invaluable inputs for the
future work of the presenters, while offering conference participants an
effective way to broaden their knowledge of the emerging research trends
and to network with other researchers.
Poster and demo submissions should consist of a paper that describe the
work, its contribution to the field or novelty aspects. Submissions must
be original and must not have been submitted for publication elsewhere.
Accepted papers will be published in HTML (RASH) in CEUR and, as such,
the camera-ready version of the papers will be required in HTML,
following the poster and demo guidelines (https://goo.gl/3BEpV7). Papers
should be submitted through EasyChair
(https://easychair.org/conferences/?conf=semantics2017 and should be
less than 2200 words in length (equivalent to 4 pages), including the
whole content of the paper.
For the initial reviewing phase, authors may submit a PDF version of the
paper following any layout. After acceptance, authors are required to
submit the camera-ready in HTML (RASH).
Submissions will be reviewed by experienced and knowledgeable
researchers and practitioners; each submission will receive detailed
feedback. For demos, we encourage authors to include links enabling the
reviewers to test the application or review the component.
For details please go to: https://2017.semantics.cc/calls
*https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-06-28
<https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-06-28>*
*= 2017-06-28 =*
*contact: https://www.mediawiki.org/wiki/Wikimedia_Engineering
<https://www.mediawiki.org/wiki/Wikimedia_Engineering>*
== Callouts ==
* Ops: +2 needed on https://gerrit.wikimedia.org/r/359417 to remove
disabled image handling from VCL
* RelEng: Potential widespread thumbnail problems on beta cluster
https://phabricator.wikimedia.org/T169114
* Thursday 29th, codfw row A switch upgrade:
https://phabricator.wikimedia.org/T168462 : expect ~10min downtime per rack
== Audiences ==
=== Readers ===
==== iOS native app ====
* Blocked by: None
* Blocking: None
* Updates: 5.5.0 released, 5.5.1 pending
==== Android native app ====
* Blocked by: n/a
* Blocking: n/a
* Updates: (all ongoing)
** working on reading list syncing UI, eagerly awaiting the backend service
** Stephen working on cross-platform CSS/JS consolidation
** working on hiring an engineer, about to kick off hiring a PM
==== Reading Web ====
* Blocked by:
i18n/parsing: Your guidance is requested on Translate tag doesn't get
parsed on action=parse[https://phabricator.wikimedia.org/T168743 ]
Release engineering team: More an FYI, ee'd like to switch all our browser
tests to Node.js. Not clear of timeline for
https://phabricator.wikimedia.org/T164721 Run WebdriverIO tests in CI for
extensions for planning purposes.
Ops: +2 needed on https://gerrit.wikimedia.org/r/359417 to remove disabled
image handling from VCL
* Blocking: n/a (please let us know)
* Updates:
** Working with services team to spec out a new HTML summary endpoint
service. (https://phabricator.wikimedia.org/T113094) - if you are using
TextExtracts you may want to keep an eye on changes. Bug fixes are coming.
** Starting to prepare for some updates to desktop print styles and
sunsetting OCG
==== Reading Infrastructure ====
* Blocked by:
* Blocking:
* Updates:
** working on OCG replacement (current approach: Electron with PDF
post-processing - T168871)
** starting work on Reading List Service
** measuring payload size changes from Parsoid to read-html - T164033
** stripping reference list contents - T168875
==== Multimedia ====
* Blocked by: Potential widespread thumbnail problems on beta cluster -
RelEng? https://phabricator.wikimedia.org/T169114
* Blocking: N/A
* Updates: 3D mass-upload test went well - but see above re: thumbnails.
Not currently sure what a large number of 3d2png runs will do to
performance.
==== Discovery ====
* Blocked by: n/a
* Blocking: n/a
* Updates: Working on 'explore similar' feature for SRP :
https://www.mediawiki.org/wiki/Cross-wiki_Search_Result_Improvements/explor…
- instrumenting this feature for an upcoming AB test.
=== Community Tech ===
* Blocked by: No blockers
* Blocking: N/A
* Updates:
- * XTools rewrite ongoing (http://xtools.wmflabs.org/)
- * LoginNotify roll-out ongoing
- * CodeMirror beta feature rolling out to Test Wikipedia next week (
https://www.mediawiki.org/wiki/Extension:CodeMirror)
- * Ongoing work on RangeContributions
=== Contributors ===
==== Editing ====
* Blocked by:
* Blocking:
* Updates:
==== Parsing ====
* Updates:
** Redlinks, disambig links, and redirect links are now handled in Parsoid
as well -- went live on Monday. Also bumped HTML version to 1.5.0.
** Linter went live on all wikis last week and now we are working on an
announcement to use this to get wikis to start fixing pages that would
break when Tidy is replaced. High priority issues (
https://www.mediawiki.org/wiki/Help:Extension:Linter#High-priority_lint_iss…
)
should be addressed.
** Parsoid language variants patch is getting final reviews and tweaks
before it is merged for RT testing. A followup patch will address rendering
a page in the requested variant.
==== Collaboration ====
* Blocked by: None
* Blocking: Ops on Flow dumps (is this
https://phabricator.wikimedia.org/T164262 ?)
* Updates:
** We will soon merge changes to make HTMLUsersMultiselectWidget work
properly, see https://gerrit.wikimedia.org/r/#/c/357963/
** This will be used for the Echo blacklist feature:
https://phabricator.wikimedia.org/T150419
** Work on RCFilters beta feature improvements continues
==== Language ====
* Blocked by: None
* Blocking: None
* Updates:
** Work on CX migration to OOjs + fixes continue.
** Minor updates to Apertium spa-cat language pair deployed.
** Kartik working with Services for new CX API end points.
==== Contributors Design ====
* Blocked by:
* Blocking:
* Updates:
== Technology ==
=== Analytics ===
* Blocked by:
* Blocking:
* Updates:
** Add cummulative fields to MediaWiki history data set (user revision
count, seconds elapsed since last revision) and improve format of timestamp
** Fixing a couple inconsistencies in webrequest tagging code
** Continuing work on Wikistats2 front-end, we got a repository in
Differential, we will push an initial version to it in short.
** Renaming of unique devices project wide metric to unique devices per
project family
** Getting ready for execution of EL purging script, (finalizing
white-list, making columns on EL DB nullable, bug fixes for the script)
=== Cloud Services ===
* Blocked by:
* Blocking:
* Updates:
=== Fundraising Tech ===
* Blocked by: -
* Blocking: -
* Updates:
* Minor CentralNotice features to improve Fundraising workflow
* Minor CiviCRM issues
* Usual onslaught of payment processor integration maintenance
* Slow week because a few team are members away
=== MediaWiki Platform ===
* Blocked by:
* Blocking:
* Updates:
=== Performance ===
* Blocked by:
* Blocking:
* Updates:
=== Release Engineering ===
* Blocked by:
* Blocking:
* Updates:
=== Research ===
* Blocked by:
* Blocking:
* Updates:
=== Scoring Platform ===
* Blocked by:
* Blocking:
* Updates:
** ORES intermittently unavailable for around 7 hours on 2017-06-23
*** https://wikitech.wikimedia.org/wiki/Incident_documentation/20170623-ORES
=== Search Platform ===
* Blocked by: none
* Blocking: none
* Updates:
** Continuing work on ML-assistend ranking. xgboost selected as modeling
library (https://phabricator.wikimedia.org/T162061)
** Working on fixing breakage in non-Cirrus phrase search (
https://phabricator.wikimedia.org/T167798)
** Working on Q1 goals
=== Security ===
* Blocked by:
* Blocking:
* Updates:
=== Services ===
* Blocked by: none
* Blocking: none as far as we know
* Updates:
** Automatic rerendering of HTML to bump the version to 1.5.0 -
elevated VE latencies for a while
** Red links support in Change Propagation
=== Technical Operations ===
* Blocked by: Flow dumps blocked on Collab Team, they are already aware
* Blocking: none
* Updates:
** ORES had intermittent issues on the 23rd. Long debugging session with
multiple teams. Many thanks to Subbu for figuring out the root cause!!
** Goals are being wrapped up
** Thursday 29th, codfw row A switch upgrade:
https://phabricator.wikimedia.org/T168462 : expect ~10min downtime per rack
== Wikidata ==
* No blockers.
* Wikidata is finally in the "enhanced" versions of recent changes and
watchlist! https://phabricator.wikimedia.org/T46874
* Creating Special:PageData as a canonical entry point for machine readable
page data: https://phabricator.wikimedia.org/T163923
* More work on the Lexeme UI: https://phabricator.wikimedia.org/T165567
* Working on replacing deprecated ApiErrorReporting code.
== German Technical Wishlist ==
* No blockers (as I'm aware of).
* Sneak-peak at currently running survey: http://tools.wmflabs.org/twl17/
Hello,
Jenkins jobs relying on HHVM had troubles today exiting with:
/usr/lib/x86_64-linux-gnu/hhvm/extensions/20150212/tidy.so:
cannot open shared object file: No such file or directory
The root cause is installing libtidy-dev ends up uninstall the HHVM tidy
extension (hhvm-tidy).
The issue occurred between 16:20 UTC and 18:45 UTC. To the best of my
knowledge it is fully solved.
Sorry for the inconvenience :(
Ref:
https://phabricator.wikimedia.org/T169004
Follow up task:
https://phabricator.wikimedia.org/T169008
--
Antoine "hashar" Musso
[x-posted announcement]
Hello,
This is a reminder that the Wikimedia Language team's office hour is
happening later today (details at the end).
Please note, our agenda has been updated and today we will have a guest
speaker from the Tamil Wikipedia - Ravishankar A
<https://ta.wikipedia.org/wiki/%E0%AE%AA%E0%AE%AF%E0%AE%A9%E0%AE%B0%E0%AF%8D…>,
who will talk about a campaign
<https://ta.wikipedia.org/wiki/%E0%AE%B5%E0%AE%BF%E0%AE%95%E0%AF%8D%E0%AE%95…>
(page
written in Tamil) that is currently underway to create new articles of high
quality using Content Translation. The Tamil community also has a help page
and a video
<https://ta.wikipedia.org/wiki/%E0%AE%89%E0%AE%A4%E0%AE%B5%E0%AE%BF:%E0%AE%8…>
(page
written in Tamil) to help new users learn the tool.
Do let me know if you would like to join in the discussion via our hangout.
You can also ask questions over IRC (check the details below) or over email.
Thanks
Runa
== Details ==
# Event: Wikimedia Language team's office hour session
# When: June 27, 2017 (Tuesday) at 13:00 UTC (check local time
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170627T1300)
# Where: IRC #wikimedia-office (Freenode) and
https://www.youtube.com/watch?v=8Euhu4Q7HF4
# Agenda:
- Ravishankar A from Tamil Wikipedia talks about a state-wide
translation campaign using Content Translation.
- Updates from the Language team and Q & A.
---------- Forwarded message ----------
From: Runa Bhattacharjee <rbhattacharjee(a)wikimedia.org>
Date: Fri, Jun 23, 2017 at 12:58 PM
Subject: WMF Language team office hour and online meeting on June 27, 2017
(Tuesday) at 1300 UTC
To: MediaWiki internationalisation <mediawiki-i18n(a)lists.wikimedia.org>,
Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>, Wikimedia
developers <wikitech-l(a)lists.wikimedia.org>, "Wikimedia & GLAM
collaboration [Public]" <glam(a)lists.wikimedia.org>
[x-posted announcement]
Hello,
The next online office hour session of the Wikimedia Language team is
scheduled for Tuesday, June 27th, 2017 at 13:00 UTC. This will be an open
session to talk about Wikimedia Language projects.
This session is going to be an online discussion over Google
Hangouts/Youtube with a simultaneous IRC conversation. Due to the
limitation of Google Hangouts, only a limited number of participation slots
are available. Hence, do please let us know in advance if you would like to
join in the Hangout. The IRC channel will be open for interactions during
the session.
Our last online round-table session was held in March 2017. You can watch
the recording here: https://www.youtube.com/watch?v=0DWXTRl5ZEk
Please read below for the event details, including local time, youtube
session links and do let us know if you have any questions.
Thank you
Runa
== Details ==
# Event: Wikimedia Language team's office hour session
# When: June 27, 2017 (Tuesday) at 13:00 UTC (check local time
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170627T1300)
# Where: IRC #wikimedia-office (Freenode) and https://www.youtube.com/watch?
v=8Euhu4Q7HF4
# Agenda:
Updates from the Language team and Q & A.
--
Language Engineering Manager
Wikimedia Foundation
--
Language Engineering Manager
Wikimedia Foundation
Hi all!
Here are the minutes from this week's ArchCom meeting. You can also find the
minutes at <https://www.mediawiki.org/wiki/Architecture_committee/2017-06-21>.
See also the ArchCom status page at
<https://www.mediawiki.org/wiki/Architecture_committee/Status> and the RFC board
<https://phabricator.wikimedia.org/tag/mediawiki-rfcs/>.
Here are the minutes, for your convenience:
* Last call: Reading Lists <https://phabricator.wikimedia.org/T164990>. If no
new and pertinent concerns remain unaddressed by July 5, this RFC will be
approved for implementation. Please pay special attention to the proposed DB
schema and REST API.
* RFC discussion on IRC: HTTP redirects for #REDIRECT pages
<https://phabricator.wikimedia.org/T53736>. There are various options, none of
them is perfect - but perhaps we can find one that is better than what we have
now. As always, the discussion will take place in the IRC channel
#wikimedia-office on Wednesday 21:00 UTC (2pm PDT, 23:00 CEST).
* New RFC: Make API usage limits easier to understand
<https://phabricator.wikimedia.org/T167906>
* From SoS: Community Tech would love feedback on
<https://phabricator.wikimedia.org/T152540> regarding HTML5 section IDs
* ArchCom discussed Bryan’s proposal for Special Interest Groups (SIG)
<https://phabricator.wikimedia.org/T164551>. More feedback welcome. Key
questions seem to be: who grants authority to such groups? Is the proposal about
groups that address a subset of ArchCom’s scope, or about concerns that exist on
the same level as ArchCom’s?
* Ongoing discussion about given ArchCom a Charter, and revising scope, name,
and process:
<https://www.mediawiki.org/wiki/Talk:Architecture_committee/Charter>
--
Daniel Kinzler
Principal Platform Engineer
Wikimedia Deutschland
Gesellschaft zur Förderung Freien Wissens e.V.
maybe a wp-l post would help find translators?
Zppix
Volunteer developer for WMF
enwp.org/User:Zppix
On Jun 25, 2017 4:16 AM, "Asaf Bartov" <abartov(a)wikimedia.org> wrote:
I'd like to specially praise *the Turkish volunteer User:Basak* for
creating the first *complete* translation of the subtitles for this 3-hour
tutorial.
https://commons.wikimedia.org/wiki/TimedText:A_Gentle_
Introduction_to_Wikidata_for_Absolute_Beginners_(including_
non-techies!).webm.tr.srt
Thank you, Basak!
(if you find this talk useful, do consider contributing to the translation
effort (from the complete English subtitles), or help recruit someone who
can.)
A.
On Fri, Feb 10, 2017 at 8:32 AM Asaf Bartov <abartov(a)wikimedia.org> wrote:
> Here's the (3-hour) footage of the detailed Wikidata tutorial delivered
> today:
>
> on Commons:
> https://commons.wikimedia.org/wiki/File:A_Gentle_
Introduction_to_Wikidata_for_Absolute_Beginners_(including_
non-techies!).webm
>
> on YouTube: https://www.youtube.com/watch?v=eVrAx3AmUvA
>
> the slides:
> https://commons.wikimedia.org/wiki/File:Wikidata_-_A_Gentle_
Introduction_for_Complete_Beginners_(WMF_February_2017).pdf
>
> It covers what Wikidata is (00:00), how to contribute new data to Wikidata
> (1:09:34), how to create an entirely new item on Wikidata (1:27:07), how
to
> embed data from Wikidata into pages on other wikis (1:52:54), tools like
> the Wikidata Game (1:39:20), Article Placeholder (2:01:01), Reasonator
> (2:54:15) and Mix-and-match (2:57:05), and how to query Wikidata
(including
> SPARQL examples) (starting 2:05:05).
>
> Share and enjoy. :)
>
> A.
>
> On Fri, Feb 3, 2017 at 4:35 PM Rachel Farrand <rfarrand(a)wikimedia.org>
> wrote:
>
>> Please join for the following talk:
>>
>> *Tech Talk**:* A Gentle Introduction to Wikidata for Absolute Beginners
>> [including non-techies!]
>> *Presenter:* Asaf Bartov
>> *Date:* February 09, 2017
>> *Time: *19:00 UTC
>> <
>> https://www.timeanddate.com/worldclock/fixedtime.html?msg=
Tech+Talk%3A+A+Gentle+Introduction+to+Wikidata+for+Absolute+Beginners+%
5Bincluding+non-techies%21%5D+&iso=20170209T19&p1=1440&ah=3
>> >
>> Link to live YouTube stream <https://www.youtube.com/watch?v=eVrAx3AmUvA>
>> *IRC channel for questions/discussion:* #wikimedia-office
>>
>> *Summary: *This talk will introduce you to the Wikimedia Movement's
latest
>> major wiki project: Wikidata. We will cover what Wikidata is, how to
>> contribute, how to embed Wikidata into articles on other wikis, tools
like
>> the Wikidata Game, and how to query Wikidata (including SPARQL examples).
>> _______________________________________________
>> Wikitech-l mailing list
>> Wikitech-l(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Please join for the following talk:
*Tech Talk**:* A Gentle Introduction to Wikidata for Absolute Beginners
[including non-techies!]
*Presenter:* Asaf Bartov
*Date:* February 09, 2017
*Time: *19:00 UTC
<https://www.timeanddate.com/worldclock/fixedtime.html?msg=Tech+Talk%3A+A+Ge…>
Link to live YouTube stream <https://www.youtube.com/watch?v=eVrAx3AmUvA>
*IRC channel for questions/discussion:* #wikimedia-office
*Summary: *This talk will introduce you to the Wikimedia Movement's latest
major wiki project: Wikidata. We will cover what Wikidata is, how to
contribute, how to embed Wikidata into articles on other wikis, tools like
the Wikidata Game, and how to query Wikidata (including SPARQL examples).
A question that came up during Documentation Day was whether or not we
should use the @inheritdoc convention for indicating that methods are
documented in parent classes (rather than leaving them blank).
Some arguments for using it include:
* It can help code-sniffers and linters know that the documentation isn't
missing.
* It lets humans who are looking at the code know that they can find
documentation elsewhere.
* We are already using it. (It appears over 200 times in core JavaScript
and about 40 times in core PHP. It's also used in at least 19 production
extensions.)
Some arguments for not using it:
* It isn't necessary for generating docs at doc.wikimedia.org (Doxygen
automatically inherits method docs if available).
* It would require adding thousands of extra comment blocks to our code to
implement it consistently.
What are people's opinions on using it?
Also, a quick note on usage. A lot of our existing usage looks like "*
{@inheritdoc}". As explained at phpdoc.org, this usage is technically
incorrect:
"Currently some applications have DocBlocks containing just the
{@inheritDoc} inline tag to indicate that their complete contents should be
inherited. This usage breaks with the PHPDoc Standard as summaries cannot
contain inline tags and inheritance is automatic; you do not need to define
a special tag for it. However, it does make clear that an element has been
explicitly documented (and thus not forgotten). As such we are working to
include a new (normal) tag in the PHPDoc Standard @inheritDoc that will
serve that purpose."
Information about the use of @inheritdoc in JavaScript can be found at
http://usejsdoc.org/tags-inheritdoc.html.
Hey,
ORES right now is under pressure and returns overload errors, we are
investigating the cause and we'll send you notice once it's back online.
Sorry for any inconvenience happened
Best
--
Amir Sarabadani Tafreshi
Software Engineer (contractor)
-------------------------------------
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
http://wikimedia.de
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/681/51985.