Apologies for cross-posting
Invitation
====
SEMANTiCS 2019 - The Power of Artificial Intelligence and Knowledge
Graphs, September 9 - 12, 2019
15th International Conference on Semantic Systems
Karlsruhe, Germany
====
Important Dates (specific track dates are given below)
Abstract Submission Deadline: April 23, 2019 (11:59 pm, Hawaii time)
Paper Submission Deadline: April 30, 2019 (11:59 pm, Hawaii time)
Notification of Acceptance: June 17, 2019 (11:59 pm, Hawaii time)
Camera-Ready Paper: July 29, 2019 (11:59 pm, Hawaii time)
Find the detailed calls here: https://2019.semantics.cc/calls
Submission via Easychair on
https://easychair.org/conferences/?conf=semantics2019
Proceedings of SEMANTiCS19 will be published by Springer LNCS & CEUR.
====
SEMANTiCS 2019 particularly welcomes submissions on the following key
topics:
+ Web Semantics & Linked (Open) Data
+ Enterprise Knowledge Graphs, Graph Data Management and Deep Semantics
+ Machine Learning & Deep Learning Techniques
+ Semantic Information Management & Knowledge Integration
+ Terminology, Thesaurus & Ontology Management
+ Data Mining and Knowledge Discovery
+ Reasoning, Rules and Policies
+ Natural Language Processing
+ Data Quality Management and Assurance
+ Explainable Artificial Intelligence
+ Semantics in Data Science
+ Semantics of Blockchain & Distributed Ledger Technologies
+ Trust, Data Privacy, and Security with Semantic Technologies
+ Economics of Data, Data Services and Data Ecosystems
----
+ Special Sub-Topic: Digital Humanities and Cultural Heritage
+ Special Sub-Topic: LegalTech
We especially encourage contributions that illustrate the applicability
of the topics mentioned above for industrial purposes and/or illustrate
the business relevance of their contribution for specific industries.
We invite contributions to the following tracks:
====
Research and Innovation Track
The Research and Innovation track at SEMANTiCS welcomes papers on novel
scientific research and/or innovations relevant to the topics of the
conference. Submissions must be original and must not have been
submitted for publication elsewhere. Papers must follow the guidelines
given in the author instructions, including references and optional
appendices. Each submission will be reviewed by several PC members who
will judge it based on its innovativeness, appropriateness, and impact
of results in terms of effectiveness at solving real problems.
Important Dates:
Abstract Submission Deadline: April 23, 2019 (11:59 pm, Hawaii time)
Paper Submission Deadline: April 30, 2019 (11:59 pm, Hawaii time)
Notification of Acceptance: June 10, 2019 (11:59 pm, Hawaii time)
Camera-Ready Paper: July 29, 2019 (11:59 pm, Hawaii time)
Author instructions: Reviews will be carried out in a single-blind mode.
Long papers should have a maximum length of 15 pages and short papers of
6 pages. Submissions should follow the guidelines of the Springer LNCS
format.
====
Posters and Demos Track
The Posters and Demonstrations Track invites innovative work in
progress, late-breaking research and innovation results, and smaller
contributions in all fields related to the Semantic Web and Linked Data
in a broader sense. 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 or pieces of code that may attract developers and
potential research or business partners.
Important Dates (Posters & Demos)
Paper Submission Deadline: June 10, 2019 (11:59 pm, Hawaii time)
Notification of Acceptance: July 8, 2019 (11:59 pm, Hawaii time)
Camera-Ready Paper: July 22, 2019 (11:59 pm, Hawaii time)
Author instructions: Proceedings will be published via CEUR Workshop
proceedings and should follow the guidelines of the Springer LNCS format.
====
Industry and Use Case Track
Focusing strongly on industry needs and ground breaking technology
trends SEMANTICS invites presentations on enterprise solutions that deal
with semantic processing of data and/or information. A special focus of
Semantics 2019 will be on the convergence of machine learning techniques
and knowledge graphs. Additional topics of interest are Enterprise
Knowledge Graphs, Semantic AI & Machine Learning, Enterprise Data
Integration, Linked Data & Data Publishing, Semantic Search,
Recommendation Services, Thesaurus and/or Ontology Management, Text
Mining, Data Mining and any related fields. All submissions should have
a strong focus on real-world applications beyond the prototypical stage
and demonstrate the power of semantic systems!
Important Dates:
Proposal Deadline: May 27, 2019 (11:59 pm, Hawaii time)
Notification of Acceptance: June 10, 2019 (11:59 pm, Hawaii time)
A detailed Call for Industry and Use Case Presentations will be
available soon.
====
Workshops and Tutorials
Workshops and Tutorials at SEMANTiCS 2018 allow your organisation or
project to advance and promote your topics and gain increased
visibility. The workshops and tutorials will provide a forum for
presenting widely recognised contributions and findings to a diverse and
knowledgeable community. Furthermore, the event can be used as a
dissemination activity in the scope of large research projects or as a
closed format for research and commercial project consortia meetings.
Important Dates for Workshops:
Workshop Proposals: March 4, 2019 (23:59 Hawaii Time)
Notification of Acceptance: March 18, 2019 (23:59 Hawaii Time)
Important Dates for Tutorials (and other meetings, e.g. seminars,
show-cases, etc., without call for papers):
Submission deadline: May 6, 2019 (23:59 Hawaii Time)
Notifications: May 13, 2019 (23:59 Hawaii Time)
====
Vocabulary Innovation Award #VIA
Bootstrap your vocabulary project: At the Vocabulary Innovation Award
you can present your ideas, early stage or camera-ready vocabularies in
order to showcase your work, find the right people and get the
discussion going. For this event, we provide both, an academic and
industry track. We use a broad definition of what a vocabulary is. For
instance, ontologies, classification schemes, thesauri, taxonomies,
subject heading and metadata schemes, whichever their format, be it RDF
or not, are all welcome. More details will follow.
Proposal Deadline: May 20, 2019 (11:59 pm, Hawaii time)
Notification of Acceptance: June 03, 2019 (11:59 pm, Hawaii time)
====
Semantics 2019 Organizing Committee
Research and Innovation Chairs:
+ Philippe Philippe Cudré-Mauroux, University of Fribourg
+ Maribel Acosta, Karlsruhe Institute of Technology (KIT)
Industry and Use Case Presentation Chairs:
+ Andreas Blumauer, Semantic Web Company
+ Christian Dirschl, Wolters Kluwer
Workshops and Tutorials Chairs:
+ Anna Lisa Gentile, IBM Research
+ Irene Celino, Cefriel
Posters and Demos Chairs:
+ Mehwish Alam, Consiglio Nazionale delle Ricerche (CNR)
+ Ricardo Usbeck, University of Paderborn
Vocabulary Innovation Award:
+ Alexandra Garatzogianni, L3S Research Center of the Leibniz University
of Hannover
+ Andreas Ledl, BARTOC.org & Basel University Library
Proceedings Chairs:
+ Maria Maleshkova, University of Bonn
+ Tassilo Pellegrini, UAS St. Pölten
Conference Chairs:
+ Harald Sack, FIZ Karlsruhe
+ York Sure Vetter, Karlsruhe Institute of Technology
+ Tassilo Pellegrini, UAS St. Pölten
The program committee will be announced on the conference website
https://2019.semantics.cc/
Hello everyone,
I'm excited to announce that we've released OOUI v0.30.0 today.
Key highlights of this release:
- OOUI widgets are now fully accessible in regards to following the
Web Content Accessibility Guidelines specification requirements.
That's my personal pre-holiday highlight, as the varying support has
been one of the first things identified when started contributing and
has gone a long way ever since, with milestones like
-- WCAG 2.0 level AA conforming color contrast from v0.18+ on for
low-vision users,
-- consistent keyboard accessibility from v0.7+ on,
-- touch-target size optimized elements for non-pointer device users
from v0.20+ on
-- usage of ARIA roles and attributes from v0.6.4+ on for screen reader users.
Many of those improvements are helping not only affected user
groups, but they are also often providing simpler usage for all users.
To give an example, the contrast requirements help easier interact
with a site on a device in the sunlight.
Some of the work has been started long before my first
contribution. Thanks to Bartosz Dziewoński, Prateek Saxena, and
volunteer Derk-Jan Hartman for all their accomplishments
along the way to this release.
While we are providing the handles for a low-hurdle interface, it's
still up to the implementors to make the right choices, use the right
configuration and user-test them. Our demos are a good starting point
for configuration examples[0].
Apart from above, there are also possible breaking changes in this release:
The following changes might cause breaking of your interface, please carefully
consider if they affect your code.
- Drop 'advanced' icon, deprecated in v0.28.1, in this release removed
completely
- Make non-continuous StackLayouts non-scrollable
You can find details on additional new features, code-level and accessibility
changes, styling and interaction design amendments, and all
improvements since v0.29.0 in the full changelog[1].
If you have any further queries or need help dealing with breaking
changes, please let me know.
As always, library documentation is available on mediawiki.org[2],
there is comprehensive generated code-level documentation and
interactive demos and tutorials hosted on doc.wikimedia.org[3].
OOUI version: 0.30.0
MediaWiki version: 1.33.0-wmf.12
Date of deployment to production: Regular train after end-of-year
break, starting Thursday 10 January
[0] - https://doc.wikimedia.org/oojs-ui/master/demos/#widgets-mediawiki-vector-ltr
[1] - https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md
[2] - https://www.mediawiki.org/wiki/OOUI
[3] - https://doc.wikimedia.org/oojs-ui/master/
Best,
Volker
--
Senior UX Engineer
Wikimedia Foundation
volker.e(a)wikimedia.org | @Volker_E
After seven weeks, Google Code-in 2018 ended last week.
199 students (last year: 300) (out of 420 who claimed Wikimedia tasks)
worked hard to complete 765 tasks (last year: 760). Thank you!
Thanks to our 39 mentors (last year: 51) for being available, also on
weekends & holidays.
Thanks to everybody on IRC, Gerrit, Phabricator, mailing lists, Github,
Telegram for your friendliness, patience, support and help.
Thanks to Wikimedia org admins for helping to run this pretty smoothly.
And, last but not least, thanks to Google for organizing this
opportunity for young humans to learn about and contribute to free
software and free knowledge.
You might have already seen the impressive half-time achievements in
https://lists.wikimedia.org/pipermail/wikitech-l/2018-November/091146.html
In addition, some more latest students' achievements:
* Several students prepared/deployed WM site configuration changes
* Dozens of fixes & new features for WMCZ's application "Tracker"
* Several fixes for the JSDoc WMF theme
* Removed unchecked calls to Title::getTalkPage in MW extensions
* Replaced usage of jshint/jscs with eslint in numerous MW extensions
* Some guided tours created for MW's StructuredDiscussions extension
* Improved code examples for the Wikidata Query UI
* Category overlay in MW's MobileFrontend extension now refreshes
after a category was added to a page
* Some fixes for syntax errors in translated messages in MW/extensions
* Images (corresponding to an emoji) added to Commons Twitter Bot code
We also encouraged students to write about their experience and link it
from https://www.mediawiki.org/wiki/Google_Code-in/2018#Blog_posts
We welcome your feedback what Wikimedia could improve at
https://www.mediawiki.org/wiki/Google_Code-in/Lessons_learned#2018
The Grand Prize winners & finalists will be announced on January 7th.
Again congratulations everybody, and thanks for your hard work!
See you around on IRC, mailing lists, Gerrit, Phabricator, Github, ...!
Cheers,
andre
--
Andre Klapper | Bugwrangler / Developer Advocate
https://blogs.gnome.org/aklapper/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
There are a few changes to the Python `tox` jobs that CI is running:
1. Most importantly, Python 3.5 is now the default version when
invoked with `tox`. This can be overridden by using basepython[1].
2. Multiple Python 3 versions are available: 3.4, 3.5, 3.6, and 3.7
(T191764).
3. It's now based on Debian Stretch, instead of Jessie, so some system
libraries are newer.
It's possible that #1 will break some repos, but with the Python 2 EOL
coming very soon, it was time to just do it.
You can take advantage of #2 by having multiple environments in
tox.ini, see keyholder[2] for an example.
I'm still working on rolling these out, so it might take another day
or two for it to take effect. If you run into any issues/problems,
please file a bug in the Continuous-Integration-Config Phabricator
project.
[1]
https://tox.readthedocs.io/en/latest/example/general.html#basepython-def
aults-overriding
[2]
https://gerrit.wikimedia.org/r/plugins/gitiles/operations/software/keyho
lder/+/master/tox.ini#3
- -- Legoktm
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE+h6fmkHn9DUCyl1jUvyOe+23/KIFAlwY188ACgkQUvyOe+23
/KIsDg/9Eklx7TR5XM3YYtrWyJAZrht6fHNJp7ox/5MjTQOMgOyh6WBqliGwVZ9u
gqGT+N9THn5ukCjOUBGm/DmH1Xa/zMwVwQ22r2aLyhcrtXFWR3fj24YMda4AiLer
/hqdfuZH5SNXxrA2jUASpYusJRABmTLLw/bVifEUmnmoYCmZQrWT/J123EEMGmE5
nasGusozeI4hPvpDWQqHH5sWzoZ4VTcU4KcET1rMAVdKdJZgBbULM/DM+h/H6RVj
oaDS3gsV4uOR67hlccnO+dD5IUlkKavfsdhEW+nDpBmDf9BDL7iwpHogFD8JoOLg
bzOj91TEQVhqrNHnuhxtklBlKJqpgGxnWsgs15YEb1hnv5S2RWemFVEPWuE2hhRQ
sqCqsrdlnRngeg2finLIiguAmp9Y+wtVqF/Li+NEOTIvLl/vAYwobfYNQNg+0V9V
vzxwgyleEB1plGp+V3jsKz7VG0SPJu2va1dzMRAvyvYxU4OCw/TfW4Ywk5M7tEvy
Yhsit5MXsL00AZ6piJGFCKQV+m/MIkuntTE+yaHTxQHIBAapfMKJZFuJe1ENW50B
biL9/uPv580jLW9Ng3Esf5hf9W74FXy1M4vGPfyF3IgzC7NvBAG63Vi1dGYVKT6L
l+G8Lq1zQn6cShdpZGF27NvSNI6ebTtwqGrQ6UeyvhDldCOYuJk=
=ZsQw
-----END PGP SIGNATURE-----
// sorry for cross-posting
Hello everyone,
the Technical Advice IRC Meeting [1] is taking a 4-week break. The next
meeting will take place in 2019, on January 16.
Also, please take note that there’ll be only one time slot for the
Technical Advice IRC Meeting in 2019: 4 pm UTC.
See you in 2019!
Johanna (for the Technical Advice IRC Meeting crew)
[1] https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Code Health Newsletter - Issue 2 Volume 1
The Code Health[0a] newsletter is a publication provided by the Code
Health Group[0b]. The Code Health Group serves as the hub for all
Code Health topics and activities within the movement. If you are
aware or engaged in Code Health activities, we'd love to hear about
it.
The Code Health Newsletter is a new and hopefully valuable activity.
If you have feedback about this issue or any past issues[0c], please
don’t hesitate to share. You can also submit content that you’d like
to share through Phabricator (use the Code-Health-Newsletter project).
# Code Health First Responders
After last issue there was some concern voiced about calling this
"First Responders" as the term is already used within the community.
As a result, we've tweaked the name a bit to call it "Code Health
First Responders".
Please remember to share your experiences tackling your Code Health
challenges. Become or nominate a First Responder by submitting a task
in Phabricator in the Code-Health-First-Responder project.
More information available here[1].
# Code Stewardship
## Quarterly Reviews
This quarter's Code Stewardship review cycle is open and ending on
January 16th. At the moment we've got three items being reviewed:
CodeReview extension, UserMerge extension, and Graphoid service.
Join the discussion in Phabricator[2a] or on Wiki[2b].
## Latest Code Stewardship Coverage
Core Components: 63%
Extensions: 74%
Services: 65%
Note: these numbers are based on the Developers/Maintainers[2c] page.
## What it means to be a Code Steward
Over the course of the last several months, the Foundation has been
working to close the gap on the number of un/under-funded Components,
Extensions, and Services deployed to the production environment. Many
have already stepped up to become Code Stewards, but outside of some
aspirational goals about bug resolution rates, and code review
responsiveness, there hasn't been much guidance. Over the course of
the next few weeks, we will be attempting to bring more clarity to
that.
# Code Health by the Numbers
The following are some stats regarding Code Health. As we are early
in defining/implementing our Code Health metrics, data is limited.
See the Code Health Metrics project[3a] for more information.
In future issues of the newsletter, we'll expand this section to
include other metrics as well as trending information.
## Code Coverage
0-50% 51-90% 90-100%
_______________________________
Extensions 67 16 4
Code Components 5 11 18
Services Not Available Yet
Note: As of 11/30/18[3b].
### Did you know?
Coverme[3c], a tool written by legoktm, is a great tool to help
prioritize areas for additional test coverage. It helps by
identifying the code that is most often executed in production and its
current coverage level. Please note that currently these tools support
PHP code bases. We are currently investigating what it would take to
expand into other languages.
Historical coverage charts can been seen here[3d]. These charts can
be used to gauge the overall trend of test coverage for the 12 months.
This is an important tool to use for measuring incremental progress
over time.
# Code Health Learning Circles
If you have a topic that you'd like to share, but want a little help
with organizing, please submit a Phabricator ticket to the
Code-Health-Learning-Circles project.
Are there some topics that you’d like to see some Learning Circles
about? Submit a Phabricator ticket to the
Code-Health-Learning-Circles project and we’ll do what we can to make
it happen.
More information about Code Health Learning Circles available here[4].
# Help Wanted
## Memory Profiling/Leak Troubleshooting
Do you have experience/expertise in memory profiling? We’re trying to
chase down some memory leaks using Chromium’s profiling tools, but
we’re running into challenges. Join the conversation in phabricator[5]
and/or in the wikimedia-codehealth irc channel.
# Code Health Group Activities
Although the Code Health Group looks to act as a hub for all code
health topics, the group also sponsors various broader reaching
initiatives.
## Recent Activities
### Code Health Metrics
The Code Health Metrics Working Group has been busy over the last
couple of months. The groups primary focus has been to evaluate some
of the code metrics frameworks. These tools provide us with code
analysis, reporting, and a framework to plug in the results of other
analysis tools.
The two that are available for evaluation are:
SonarQube [6a]
PHPMetrics [6b]
## Upcoming Activities:
### Code Reviews
Code reviews are a critical part of our development process. They are
key to ensuring code changes are of the highest quality possible.
That being said, getting timely code reviews can prove to be
challenging at times.
The foundation is forming a Code Review Working Group to help better
define the challenges and propose some solutions. If you’re
interested in participating in this discussion, please join us on the
wikimedia-codehealth irc channel, check out the Code-Review-Workgroup
Phabricator work board [6c], and/or reach out to jrbranaa or aklapper
directly if you’re interested in being part of the working group.
### Expanding Code Coverage to Services
As noted in Code Coverage section of this newsletter, Services are not
currently included in our Code Coverage metrics. We are working to
change that. If you’re interested in helping with that, please see
Task T211710[6d].
# Footnotes
[0a][Code Health - MediaWiki](https://www.mediawiki.org/wiki/Code_Health)
[0b][Code Health Group - MediaWiki
(https://www.mediawiki.org/wiki/Code_Health_Group)
[0c]https://www.mediawiki.org/wiki/Code_Health#Newsletters
[1][Code Health/First-Responders -
MediaWiki](https://www.mediawiki.org/wiki/Code_Health/First-Responders)
[2a][Code-Stewardship-Reviews ·
Workboard](https://phabricator.wikimedia.org/project/board/3144/)
[2b][Code stewardship reviews/Feedback solicitation -
MediaWiki](https://www.mediawiki.org/wiki/Code_stewardship_reviews/Feedback…
[2c][Developers/Maintainers -
MediaWiki](https://www.mediawiki.org/wiki/Developers/Maintainers)
[3a][Code Health Group/projects/Code Health Metrics -
MediaWiki](https://www.mediawiki.org/wiki/Code_Health_Group/projects/Code_H…
[3b][Test coverage - Documentation](https://doc.wikimedia.org/cover/)
[3c]https://tools.wmflabs.org/coverme/
[3d][Index of /coverage/charts/](https://tools.wmflabs.org/coverage/charts/)
[4][Code Health Group/Learning Circles -
MediaWiki](https://www.mediawiki.org/wiki/Code_Health_Group/Learning_Circle…
[5]https://phabricator.wikimedia.org/T212135
[6a][SonarCloud](https://sonarcloud.io/organizations/wmftest/projects)
[6b][PhpMetrics
report](https://doc.wikimedia.org/mediawiki-core/master/phpmetrics/index.ht…
[6c][Code-Review-Workgroup](https://phabricator.wikimedia.org/project/view/3…
[6d][⚓ T211710 Expose code coverage stats for
Services](https://phabricator.wikimedia.org/T211710)
Hello,
tag_summary table was introduced in 2009 as a roll up table for change_tag.
One of the reasons it was being used was that MySQL databases that were
using earlier versions of 4.1 (Released at 15 February 2005) could not use
GROUP_CONCAT feature.
Around five years ago, developers started to replace usages of tag_summary
with change_tag primarily because GROUP_CONCAT became available then and it
most cases it was faster. For example [1] but it wasn't done fully which
led us to having discrepancies. For example, Special:RecentChanges uses
change_tag table but its API counterpart uses tag_summary table.
Maintaining two extremely large tables is a technical debt that have been
biting us since its deployment. Also, with normalization of change_tag
table in place [2], it's more performant than tag_summary.
So we are replacing usages of this table with change_tag and in the next
couple of weeks, and then we will drop the whole table. If you're using it
in cloud replicas, please change it to change_tag. If you have any concerns
or notes, feel free to chime in at https://phabricator.wikimedia.org/T209525
(Also, review of the patches would be extremely appreciated)
Thank you and sorry for any inconvenience.
[1]: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/95584
[2]: https://phabricator.wikimedia.org/T185355
Best
--
Amir Sarabadani
Software Engineer
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.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/029/42207.