Apologies for cross-posting
Call for Research & Innovation Papers
Call for Research & Innovation Papers
SEMANTiCS 2015
Transfer // Engineering // Community
11th International Conference on Semantic Systems
Vienna, Austria September 15-17, 2015
http://www.semantics.cc
<http://www.google.com/url?q=http%3A%2F%2Fwww.i-semantics.at%2F&sa=D&sntz=1&…>
Important Dates (Research & Innovation)
* Abstract Submission Deadline: May 22, 2015
* Paper Submission Deadline: May 29, 2015
* Notification of Acceptance:June 26, 2015
* Camera-Ready Paper: July 15 , 2015
SEMANTiCS proceedings will be published by ACM ICP.
Submissions via Easychair:
https://easychair.org/conferences/?conf=semantics2015research
<https://www.google.com/url?q=https%3A%2F%2Feasychair.org%2Fconferences%2F%3…>
The calls for “Industry & Use Case Presentations” and “Posters and
Demos”at SEMANTiCS 2015 can be found here:http://www.semantics.cc/
<http://www.google.com/url?q=http%3A%2F%2Fwww.semantics.cc%2Fopen-calls%2Fpa…>
The annual SEMANTiCS conference is the meeting place for professionals
who make semantic computing work, who understand its benefits and
encounter its limitations. Every year, SEMANTiCS attracts information
managers, IT-architects, software engineers and researchers from
organisations ranging from NPOs, through public administrations to the
largest companies in the world. Attendees learn from industry experts
and top researchers about emerging trends and topics in the fields of
semantic software, enterprise data, linked data & open data strategies,
methodologies in knowledge modelling and text & data analytics. The
SEMANTiCS community is highly diverse; attendees have responsibilities
in interlinking areas like knowledge management, technical
documentation, e-commerce, big data analytics, enterprise search,
document management, business intelligence and enterprise vocabulary
management.
The success of last year’s conference in Leipzig with more than 230
attendees from 22 countries proves that SEMANTiCS 2015 will continue a
long tradition of bringing together colleagues from around the world.
There will be presentations on industry implementations, use case
prototypes, best practices, panels, papers and posters to discuss
semantic systems in birds-of-a-feather sessions as well as informal
settings. SEMANTICS addresses problems common among information
managers, software engineers, IT-architects and various specialist
departments working to develop, implement and/or evaluate semantic
software systems.
The SEMANTiCS program is a rich mix of technical talks, panel
discussions of important topics and presentations by people who make
things work - just like you. In addition, attendees can network with
experts in a variety of fields. These relationships provide great value
to organisations as they encounter subtle technical issues in any stage
of implementation. The expertise gained by SEMANTiCS attendees has a
long-term impact on their careers and organisations. These factors make
SEMANTiCS for our community the major industry related event across Europe.
The following ‘horizontals’ (research) and ‘verticals’ (industries)
topics are of interest:
* Business Models, Governance & Data Strategies
* Knowledge Discovery & Intelligent Search
* Data Integration & Enterprise Linked Data
* Big Data & Text Analytics
* Data Portals & Knowledge Visualization
* Semantic Information Management
* Document Management & Content Management
* Terminology, Thesaurus & Ontology Management
* Industry & Engineering
* Life Sciences & Health Care
* Public Administration
* Galleries, Libraries, Archives & Museums (GLAM)
* Media, Publishing & Advertising
* Financial & Insurance Industry
* Telecommunications
* Energy, Transport & Environment
Research / Innovation Papers
The Research & Innovation track at SEMANTiCS welcomes the submission of
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 should follow the ACM
ICPS guidelines for formatting
(http://www.acm.org/sigs/publications/proceedings-templates
<http://www.google.com/url?q=http%3A%2F%2Fwww.acm.org%2Fsigs%2Fpublications%…>)
and must not exceed 8 pages in lenght for full papers and 4 pages for
short papers, including references and optional appendices.
All accepted full papers and short papers will be published in the
digital library of the ACM ICP Series under the ISBN-No.:
978-1-4503-1972-0. Research & Innovation papers should be submitted
through EasyChair at:
https://easychair.org/conferences/?conf=semantics2015research
<https://www.google.com/url?q=https%3A%2F%2Feasychair.org%2Fconferences%2F%3…>.
Papers must be submitted in PDF (Adobe's Portable Document Format)
format. Other formats will not be accepted. For the camera-ready
version, the source files (Latex, Word Perfect, Word) will also be needed.
Important Dates (Research & Innovation)
* Abstract Submission Deadline: May 22, 2015
* Paper Submission Deadline: May 29, 2015
* Notification of Acceptance:June 26, 2015
* Camera-Ready Paper: July 15 , 2015
Research and Innovation Chairs:
Sebastian Hellmann, AKSW, Universität Leipzig
Josiane Xavier Parreira, Siemens AG Österreich
Programme Committee:
to be announced
SEMANTiCS 2015 Organisation Committee:
* Axel Polleres, Conference Chair
* Tassilo Pellegrini, Conference Chair
* Christian Dirschl, Industry Chair
* Sebastian Hellmann, Research & Innovation Chair
* Josiane Xavier Parreira, Research & Innovation Chair
* Agata Filipowska, Poster and Demo Chair
* Ruben Verborgh, Poster and Demo Chair
* Anna Fensel, Workshop Chair
Please join the Analytics Engineering team for...
Office Hours: EventLogging & Dashboarding
Hosts: Dan and Nuria
Date: January 14
Time: 20:00 UTC - Convert to Local Time
<http://www.timeanddate.com/worldclock/fixedtime.html?msg=EventLogging+and+D…>
Hangout: https://plus.google.com/hangouts/_/wikimedia.org/a-batcave
IRC: #wikimedia-analytics
Description:
Teams need metrics on how their product or feature is performing, then they
need to visualize those metrics. This is accomplished with instrumenting
code with EventLogging, mashing data with some queries and setting up a
Limn Dashboard. The Analytics Engineering team is open for office hours to
answer questions about the process, help solve any issues and listen to
feedback on the process. Feel free to drop in the Goolge Hangout linked
above or ask questions on the IRC channel during our Office Hours.
All,
TL;DR:
* References made using Cite will be configurable with a different system
* New approach being prototyped in Parsoid's native implementation of the
Cite extension
The Cite extension[0], which provides in-page footnotes is a crucial part
of how many of us use wikis, especially for Wikipedias. However, it was
written a very long time ago, even by MediaWiki standards, and in its
creation, we made some design choices which made sense at the time, but
don't work very well for us anymore. As CSS has gotten more features, and
those features have become more reliably implemented in modern browsers, we
have more choices now.
One of the great things about the Cite extension is its flexibility, such
as each wiki being able to choose how the footnotes display to readers.
Unfortunately, the means by which this flexibility is provided is currently
done through a series of 14 different MediaWiki namespace wikitext messages
which are interpreted to create the HTML to display to the user.
This has a number of disadvantages. Most wikis use the default values (and
even very experienced users are probably unaware of how it works or even
that it can be changed). Because they are implemented in wikitext,
per-user changes such as with a gadget or a user script aren't possible to
do neatly (and instead need JavaScript to re-write the content, which is
slower and more complex), and changes take up to 30 days to be visible to
anonymous users whilst they wait for the cache to change. Due to how
MediaWiki's messages system works, changes to the display styles need to be
copied into each of the ~300 display languages for users, else those users
with different languages will see different reference styles on the same
page. Any system that wishes to display MediaWiki references has to
implement most of MediaWiki just to format these references correctly.
To fix this, the Parsoid and editing teams are proposing to replace the
current way to configure the Cite extension with some CSS rules, which will
solve these issues. Experimenting will be much easier to do on a per-user
or gadget-basis in advance of making larger changes. Styles will be shared
by all users of the wiki, regardless of their preferred language, and
complicated user scripts or gadgets that slow down the system will not be
needed to change the style. Changes will be instant for all users, even
those logged out, and non-MediaWIki users can use styles to correctly and
consistently display references. A currently-under-review patch[1] for
Parsoid demonstrates use of CSS to do variations found on enwiki, eswiki,
and fawiki. We think that this approach will allow us to match each of the
current styles used on Wikimedia wikis. If there is any variation
(currently in use) that we should experiment with, please let us know.
We plan to continue to prototype this approach in Parsoid and work through
any rendering issues. Given that most Wikimedia wikis don't customize the
extension, for most Wikimedia wikis, we expect this will work with the
basic configuration (and for a few Wikipedias which need different
configuration, we will add styling). Once we port this solution over to the
master branch of the Cite extension, this will be a breaking configuration
change in the MediaWiki 1.25 release. If you have a gadget or user script
which changes how references appear or relies on something local to your
wikis, you may need to tweak it.
Given that older browsers (IE6 and IE7 most notably) may not implement the
CSS features that we need for this, we don't plan to rely solely on a
CSS-based approach. Our current approach is to use a default bare HTML
style on browsers that don't support content generation (like ::after and
counters).
We invite your comments, feedback, and help with this.
Thanks,
Marc, Parsoid and Editing teams.
[0] – https://www.mediawiki.org/wiki/Extension:Cite
[1] – https://gerrit.wikimedia.org/r/#/c/170936/
Hi, this is how far the organization of the MediaWiki Developer Summit will
go pre-scheduling plenary sessions and other sessions in the main room:
https://www.mediawiki.org/wiki/MediaWiki_Developer_Summit_2015#Schedule
There might be still adjustments driven by the owners of these sessions,
but we have gone through enough planning discussions.
Regardless of whether you are attending the Summit or not, you can help
making the most of each of these sessions -- and any Summit session. They
all have a related task in Phabricator where the stuff that matters should
be discussed and documented in their descriptions. Here are some ideas to
raise the bar:
* Is the goal of the session declared, and is it the best goal we can aim
for?
* Is the scope of the session clear in itself and in relation to other
sessions?
* Is the description useful to understand the topic and be ready for a
productive session?
* Are there links to wiki pages, etherpad, slides, related sessions...?
* Is the task associated to the appropriate projects in addition to #MWDS15?
* Are there blocker/blocking tasks this session should be associated with?
* After the event, is there an evaluation of the achievements of the
session, and related notes?
Also, why waiting to the Summit when you can start to discuss / collaborate
in the task itself? And why stopping after the event if there are open
topics and actions left?
In other words, don't let anybody miss an opportunity like the MediaWiki
Developer Summit in the topics that matter to you. Except supplanting the
speakers, you have good tools to influence a session and drive it to the
most successful outcome. Use them!
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Hello,
A reminder that the Language Engineering office hour will be happening
later today at 1600UTC on #wikimedia-office. The original announcement can
be found in the section below. We will be posting the logs at:
https://meta.wikimedia.org/wiki/IRC_office_hours#Office_hour_logs
Thanks
Runa
---------- Forwarded message ----------
From: Runa Bhattacharjee <rbhattacharjee(a)wikimedia.org>
Date: Mon, Jan 12, 2015 at 10:48 AM
Subject: [x-post] Language Engineering IRC Office Hour on 14 January 2015
(Wednesday) at 1600 UTC
To: MediaWiki internationalisation <mediawiki-i18n(a)lists.wikimedia.org>,
Wikimedia developers <wikitech-l(a)lists.wikimedia.org>, Wikimedia Mailing
List <wikimedia-l(a)lists.wikimedia.org>, "Wikimedia & GLAM collaboration
[Public]" <glam(a)lists.wikimedia.org>
[x-posted announcement]
Hello,
Language Engineering team of the Wikimedia Foundation is hosting the next
IRC office hour on January 14, 2015 (Wednesday) at 1600 UTC on
#wikimedia-office . We will be taking questions and discussing about our
ongoing projects. You may have also read our recent announcement about
making Content Translation available very soon as a beta feature[1] on a
few Wikipedias. We will be happy to address questions you may have about
this.
Please see below to check local time and event details
Thanks
Runa
[1]
http://blog.wikimedia.org/2015/01/10/content-translation-beta-coming-soon
<http://blog.wikimedia.org/2015/01/10/content-translation-beta-coming-soon/>
Monthly IRC Office Hour:
==================
# Date: January 14, 2015 (Wednesday)
# Time: 1600 UTC (Check local time:
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150114T1600 )
# IRC channel: #wikimedia-office
# Agenda:
1. Content Translation beta feature
2. Q & A (Questions can be sent to me ahead of the event)
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
I am pleased to announce that Corey Floyd joins WMF this week as a
Software Engineer for the Mobile App Team.
Corey is based in Philadelphia where he will be working remotely. He
previously worked as a mobile consultant, during which he developed
iOS apps for organizations like the Human Rights Campaign, Vimeo, and
Johnson & Johnson. Before joining Wikimedia, Corey spent the last year
helping to stand up the new mobile team at Urban Outfitters.
Corey is passionate about creating great user experiences and building
software that people love to use.
Prior to being an engineer, Corey was a meteorologist in the Air Force
and spent most days forecasting rain in Western Europe.
When not working, he reads way too much Apple news, plays a little
guitar, watches Scrubs on Netflix, and is learning to box. Both he and
his wife love to travel.
Corey is excited to join the Mobile Team as they take the Wikipedia
apps to the next level.
Please Welcome Corey
--tomasz
I am pleased to announce that Brian Gerstle joins WMF this week as a
Software Engineer for the Mobile App Team.
Brian comes to us from Spotify, where he worked as an iOS
developer—with a brief stint as a Quality Engineer. He's really
excited to join the team and contribute to the WMF mission by
polishing and innovating on the Wikipedia iOS experience for both
readers and contributors. He's also looking forward to working on an
open-source project and hopes to get more involved in the FOSS
community.
Brian lives in Miami, Florida with his wife and 2 dogs. Among his
many interests are: music (especially jazz), audio (was a recording
studio technician in a former life), science, health, and
sci-fi/fantasy (just started reading Name of the Wind).
Please Welcome Brian
--tomasz