Forwarding an announcement to other lists that may be interested in this
development.
Pine
( https://meta.wikimedia.org/wiki/User:Pine )
---------- Forwarded message ---------
From: Michal Lester <mlester(a)wikimedia.org.il>
Date: Thu, Feb 14, 2019 at 9:40 AM
Subject: [Wikimedia-l] Developing instructional material for Wikidata Query
Service
To: <Wikitech-l(a)lists.wikimedia.org>, <wikimedia-l(a)lists.wikimedia.org>
Dear all,
One recurring phenomenon we encounter when we present Wikidata to various
audiences, is the enthusiasm with they react to the Wikidata Query Service,
and the possibilities it offers for extracting specific information from
the vast network of linked and structured data contained in Wikidata. This
enthusiasm is not surprising, as the query feature of Wikidata is quite
unique within the landscape of information services available today.
The Wikidata Query Service is powered by SPARQL – a semantic query language
for databases. Unfortunately, for users who are new to Wikimedia platforms,
there is currently little instructional material on how to learn SPARQL for
use in Wikidata. At Wikimedia Israel we believe that a user-friendly
tutorial to Queries/SPARQL will attract new users to engage with Wikidata
and help build a community around the project.
In recent years, Wikimedia Israel has developed online instructional
materials, such as the Wikipedia courseware and the guide for creating
encyclopedic content. We plan to use our experience in this field, and in
collaboration with Wikimedia Deutschland, we intend to develop a website
with a step-by-step tutorial to learn how to use the Wikidata Query
Service. The instructional material will be available in three languages
(Hebrew, Arabic and English) but it will be possible to add the same
instructions in other languages. We are quite confident that having a
tutorial that explains and teaches the Query Service will help expand
Wikidata to new audiences worldwide.
*Best regards,*
*Michal Lester,*
*Executive DirectorWikimedia Israel*
_______________________________________________
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>
18th International Semantic Web Conference (ISWC 2019)
“Knowledge Graphs, Linked Data, Linked Schemas and AI on the Web”
Auckland, New Zealand, 26-30 October, 2019
https://iswc2019.semanticweb.org/
The International Semantic Web Conference (ISWC) is the premier venue for
presenting fundamental research, innovative technology, and applications
concerning semantics, data, and the Web. It is the most important
international venue to discuss and present latest advances and applications
of the semantic Web, knowledge graphs, linked data, ontologies and
artificial intelligence (AI) on the Web.
ISWC attracts a large number of high quality submissions every year and
participants from both industry and academia. ISWC brings together
researchers from different areas, such as artificial intelligence,
databases, natural language processing, information systems, human computer
interaction, information retrieval, web science, etc., who investigate,
develop and use novel methods and technologies for accessing, interpreting
and using information on the Web in a more effective way.
Follow us:
Twitter: @iswc_conf , #iswc_conf ( https://twitter.com/iswc_conf )
LinkedIn: https://www.linkedin.com/groups/13612370
Facebook: https://www.facebook.com/ISWConf/
Become part of ISWC 2019 by submitting to the following tracks & activities
or just attend them!
(All deadlines are midnight Hawaii time.)
In this announcement:
* Highlights
1. Call for Research papers
2. Call for In-use papers
3. Call for Resource papers
4. Call for Doctoral Consortium
* Highlights
*******************************************
* Research, In-use and Resource tracks: submission of the same work to
multiple tracks is not allowed and may result in a rejection of the work
across all tracks without a review. Before submitting, authors are asked to
consult the calls of the other tracks featured at ISWC 2019 and to choose
the track that best suits their contribution. Please consult the following
page as well when deciding to which track to submit:
https://iswc2019.semanticweb.org/paper-features-per-track/
* Research track: papers submitted to the research track will be subject
to **double blind** peer review.
* Research track: a reproducibility certification with a dedicated review
board will be proposed to the accepted research track papers that include a
significant experimental evaluation.
* Doctoral Consortium: papers submitted to the doctoral consortium will be
subject to **double blind** peer review.
1. Call for Research papers
*******************************************
In this track of ISWC 2019, we are looking for novel and significant
research contributions addressing theoretical, analytical and empirical
aspects of the Semantic Web. While we welcome work that relates to the W3C
Semantic Web recommendations (e.g., RDF, OWL, SPARQL, etc.), we also
encourage contributions to research at the intersection of Semantic Web and
other scientific disciplines. Submissions to the research track should
describe original, significant, and replicable research on the Semantic
Web. All papers must include method evaluations that are rigorous,
repeatable and reproducible. This will be one of the key paper reviewing
criteria. We also strongly encourage papers that provide material such as
data sets, source code, queries used to evaluate their approach, and/or
live deployments. To comply with the double blind review policy we
encourage the usage of non-personal storage spaces or the additional
material facility available at submission time.
Topics of interest include, but are not limited to:
* Database, information retrieval, information extraction, natural
language processing and artificial intelligence techniques for the Semantic
Web
* Knowledge representation and reasoning on the Web
* Knowledge graphs and deep semantics
* Machine learning and data mining methods for the Semantic Web
* Data mining and knowledge discovery in Linked data and ontologies
* Robust and scalable management of semantics and data on the Web and in
Linked Data
* Processing and storage of semantic data on the blockchain
* Methods to investigate and catalogue semantic primitives used in
ontology definitions
* Enabling access to ontologies and knowledge bases by rendering the
knowledge in different modalities, e.g. as natural language text,
explanatory video, interactive elements, etc.
* Languages, tools, and methodologies for representing and managing
semantics and data on the Web
* Programming the Semantic Web
* Architectures and algorithms for extreme volume, heterogeneity,
dynamicity, and decentralization of Semantic Web data
* Cleaning, quality assurance, and provenance of Semantic Web data,
services, and processes
* Ontology-based data access and integration/exchange on the Web
* Ontology engineering and ontology patterns for the Web
* Ontology modularity, mapping, merging, and alignment for the Web
* Search, query, integration, and analysis on the Semantic Web
* Supporting multi-linguality in the Semantic Web
* Question answering over Linked Data and ontologies
* Information visualization and exploratory analysis methods for Semantic
Web data
* Semantic social network mining, analysis, representation, and management
* Crowdsourcing semantics; methods, dynamics, and challenges
* Geospatial semantics and data on the Web
* Data streams and the Internet of Things
* Semantic technologies for mobile platforms
* Trust, privacy, and security on the Semantic Web
* Semantic Web and Linked Data for cloud environments
* Access control and privacy in semantic data
Further info:
https://iswc2019.semanticweb.org/call-for-research-track-papers/
== Important Dates ==
Abstracts: April 3, 2019
Full papers: April 10, 2019
== Program Chairs ==
Contact: iswc2019-program(a)inria.fr
Chiara Ghidini, Fondazione Bruno Kessler (FBK), Italy
Olaf Hartig, Linköping University, Sweden
2. Call for In-use papers
*******************************************
The adoption of Semantic Web technologies has accelerated in recent years,
where they are now deployed in a variety of real-world settings at a
variety of scales. The In-Use Track at ISWC 2019 continues the tradition of
demonstrating and learning from the increasing adoption of Semantic Web
technologies by providing a forum for the community to explore the benefits
and challenges of applying such technologies in concrete, practical use
cases, beyond the research communities from which they originate, in
contexts ranging from industry to government and science.
The In-Use Track thus seeks submissions describing applied and validated
solutions such as software tools, systems or architectures that benefit
from the use of Semantic Web technologies (including, but not limited to,
technologies based on the Semantic Web standards). Importantly, submitted
papers should provide convincing evidence of the use of the proposed
application or tool by the target user group, preferably outside the group
that conducted the development and, more broadly, outside the Semantic Web
research community. A main focus of the submissions should be on the
benefits of Semantic Web technologies for the intended use case, as well as
(if relevant) the added challenges they introduce.
We welcome submissions that demonstrate the use of Semantic Web
technologies such as those mentioned in the Call for Papers of the Research
Track, and additionally cover one or more of the following topics:
* Applications in domain-specific areas (e.g., libraries, cultural
heritage, healthcare, life sciences, engineering, smart manufacturing,
smart cities, open government)
* Description and analysis of concrete and novel problems or use cases in
a specific domain in which Semantic Web technologies were applied (this
should be part of submissions presenting a concrete application)
* Descriptions of how Semantic Web resources (ontologies, datasets,
software, standards, etc) are being used in practice
* Assessment of the Semantic Web technologies from diverse points of view,
such as:
- Usability and acceptance by stakeholder groups
- Uptake outside the Semantic Web research community
- Scalability of Semantic Web solutions and their large scale
deployment
- Technical strengths and weaknesses especially in comparison with
alternative technologies (e.g., database management systems, model-driven
engineering)
- Costs and benefits of implementing, deploying, using, and
managing Semantic Web technologies
- Risks and opportunities of using Semantic Web technologies in
organizations with respect to their businesses and customers
* Lessons learned and best practices from deploying and using an
application or service based on Semantic Web technologies
* Comparison of Semantic Web technologies with alternative approaches that
use conventional or competing technologies
Further info: https://iswc2019.semanticweb.org/call-for-in-use-track-papers/
== Important Dates ==
Abstracts: April 3, 2019
Full papers: April 10, 2019
== Program Chairs ==
Contact: iswc2019-in-use(a)inria.fr
Isabel Cruz, University of Illinois at Chicago, USA
Aidan Hogan, Universidad de Chile, Chile
3. Call for Resource papers
*******************************************
Resources are of paramount importance as they foster scientific
advancement. For example, the DBpedia resource had a major influence on the
Semantic Web community by enabling the Linked (Open) Data movement.
Validating a research hypothesis or providing answers to a research
question often goes together with developing new resources that support
these achievements. Sharing resources is key to allow other researchers to
compare new results, reproduce experimental settings and explore new lines
of research, in accordance with the FAIR principles for scientific data
management. Yet, resources themselves rarely get the same recognition as
the scientific advances they facilitate.
The ISWC 2019 Resources Track aims to promote the sharing of resources
including, but not restricted to: datasets, ontologies/vocabularies,
ontology design patterns, evaluation benchmarks or methods, software
tools/services, APIs and software frameworks, workflows, crowdsourcing task
designs, protocols, methodologies and metrics, that contribute to the
generation of novel scientific work. In particular, we encourage the
sharing of such resources following best practices within the Semantic Web
community. This track calls for contributions that provide a concise and
clear description of a resource and its usage.
A typical Resource track paper has its focus set on reporting on one of the
following categories of resources:
* Datasets produced
- to support specific evaluation tasks;
- to support novel research methods;
- by novel algorithms;
* Ontologies, vocabularies and ontology design patterns, with a focus on
describing the modelling process and decisions underlying their creation;
* Benchmarking activities focusing on datasets and algorithms for
comprehensible and systematic evaluation of existing and future systems;
* Reusable research prototypes / services supporting a given research
hypothesis;
* Community-shared software frameworks that can be extended or adapted to
support scientific study and experimentation;
* Scientific and experimental workflows used and reused in practical
studies;
* Novel evaluation methodologies and metrics, and their demonstration in
an experimental study.
Further info:
https://iswc2019.semanticweb.org/call-for-resources-track-papers/
== Important Dates ==
Abstracts: April 3, 2019
Full papers: April 10, 2019
== Program Chairs ==
Contact: iswc2019-resource(a)inria.fr
Maria Maleshkova, SDA, University of Bonn, Bonn, Germany
Vojtěch Svátek, University of Economics, Prague, Czech Republic
4. Call for Doctoral Consortium Papers
**********************************************
The ISWC 2019 Doctoral Consortium will take place as part of the 18th
International Semantic Web Conference in Auckland, New Zealand. This forum
will provide PhD students an opportunity to share and develop their
research ideas in a critical but supportive environment, to get feedback
from mentors who are senior members of the Semantic Web research community,
to explore issues related to academic and research careers, and to build
relationships with other Semantic Web PhD students from around the world.
The Consortium aims to broaden the perspectives and to improve the research
and communication skills of these students.
The Doctoral Consortium is intended for students who have a specific
research proposal and some preliminary results, but who have sufficient
time prior to completing their dissertation to benefit from the consortium
experience. Generally, students in their second or third year of PhD will
benefit the most from the Doctoral Consortium. In the Consortium, the
students will present their proposals and get specific feedback and advice
on how to improve their research plan.
All proposals submitted to the Doctoral Consortium will undergo a thorough
reviewing process with a view to providing detailed and constructive
feedback. The international program committee will select - submissions for
presentation at the Doctoral Consortium.
Students with accepted submissions at the Doctoral Consortium will be
eligible to apply for travel fellowships to offset some of the travel
costs but they will be asked to attend the whole day of the Doctoral
Consortium.
We ask the PhD students to submit a 12 page description of their PhD
research proposal. All proposal have to be submitted electronically via the
EasyChair conference submission System. The proposal text must have at
least 8 sections (some can be very short), addressing each of the following
questions:
1. Problem statement: What is the problem that you are addressing?
2. Relevancy: Why is the problem important? Who will benefit if you
succeed? Who should care?
3. Related work: How have others attempted to address this problem? Why is
the problem difficult?
4. Research question(s): What are the research questions that you plan to
address?
5. Hypotheses: What hypotheses are related to your research questions? See
Is This Really Science? The Semantic Webber’s Guide to Evaluating Research
Contributions.
6. Preliminary results: Do you have any preliminary results that
demonstrate that your approach is promising?
7. Approach: How are you planning to address your research questions and
test your hypotheses? What is the main idea behind your approach? The key
innovation?
8. Evaluation plan: How will you measure your success – faster/ more
accurate/ less failures/ etc.? How do you plan to test your hypothesis?
What will you measure? What will you compare to?
9. Reflections: Why do you think you will succeed where others failed?
Provide an argument, based either on common knowledge or on evidence that
you have accumulated, that your approach is likely to succeed.
Further info:
https://iswc2019.semanticweb.org/call-for-doctoral-consortium-papers/
== Important Dates ==
Full papers due April 17, 2019
Notifications May 15, 2019
Camera-ready papers due June 14, 2019
== Program Chairs ==
Contact: iswc2019-doctoral-consortium(a)inria.fr
Miao Qiao, Computer Science Department, the University of Auckland,
Auckland, New Zealand
Mauro Dragoni, Fondazione Bruno Kessler, Trento, Italy
See you all in Auckland!
The ISWC 2019 Organising Team (
https://iswc2019.semanticweb.org/organizing-committee/ )
I'm wondering how to relate key people to companies, when the exact
names of their roles have to be maintained.
Some examples are below. To pick out one motivating example, the
Japanese term "代表取締役社長" is called "Representative Director and
President" by T&D Holdings, but "President and Chief Executive Officer"
by NTT Docomo.
(Ebara use the very slightly different "代表執行役社長" for what is
basically the same role, calling them "President [and] Representative
Executive Officer".)
NOTE: this is not something that we can normalize. So, just using a P169
(CEO) property for both of them would not work. And it isn't a "also
known as".
In other words, calling the boss of NTT the "Representative Director and
President" would be incorrect, as would calling the boss of T&D the
"President and Chief Executive Officer".
I'm wondering if I should still relate them with P169, but then also use
two P1448 (official name) relations (attached to that P169 relation, as
qualifiers?), one each for Japanese and English?
The idea of adding lots of new property children, descended from P169,
for each possible combination of the Japanese and English name for the
title, feels very wrong. Even if there are only 5 to 10 possible
combinations.
Any other approaches?
(If anyone has an example in a language other than Japanese, I'd love to
hear them.)
Thanks,
Darren
代表取締役会長 Representative Director and Chairman T&D Tetsuhiro
Kida 喜田 哲弘
代表取締役社長 Representative Director and President T&D Hirohisa
Uehara 上原 弘久
取締役（社外役員・非常勤） Director (outside officer, part-time) T&D
Haruka Matsuyama 松山 遙
代表取締役社長 President and Chief Executive Officer NTT Kazuhiro
Yoshizawa 吉澤 和弘
取締役 Member of the Board of Directors NTT Teruyasu Murakami
村上 輝康 (outside director:社外取締役)(independent director:独立役員)
取締役会長 Chairman of the Board Ebara Natsunosuke Yago 矢
後 夏之助
代表執行役社長 President Representative Executive Officer Ebara
Toichi Maeda 前田 東一
Director 取締役 Ebara Toichi Maeda 前田 東一
Independent Director 取締役（社外） Ebara Sakon Uda 宇田 左近
https://www.td-holdings.co.jp/en/company/management/https://www.td-holdings.co.jp/company/management/index.htmlhttps://www.nttdocomo.co.jp/english/corporate/about/outline/index.htmlhttps://www.nttdocomo.co.jp/corporate/about/outline/index.htmlhttps://www.ebara.co.jp/en/about/corporate/about/executive/index.htmlhttps://www.ebara.co.jp/about/corporate/about/executive/index.html
Hi!
I've been working for a while now on splitting the code that does
searching - and more specifically, searching using
ElasticSearch/CirrusSearch - out from Wikibase extension code and into a
separate extension (see https://phabricator.wikimedia.org/T190022). If
you don't know what I'm talking about here (or not interested in this
topic), you can safely skip the rest of this message.
The extension WikibaseCirrusSearch is meant to have all the code related
to ElasticSearch and CirrusSearch extension integration to Wikibase, so
main Wikibase repo does not have any Elastic-specific code. This means
that if you have your own Wikibase install, you'll need (after migration
is done) to install WikibaseCirrusSearch to get search functionality
like we have on Wikidata now. There will also be change in
configurations - I'll make a migration document and announce it
separately. We're now working on deploying and testing it on
Beta/testwiki, after which we'll start migrating production to running
the code in this extension for search, after which the search code in
the Wikibase repo itself will be removed. You can track the progress in
the Phabricator task mentioned above.
Since code migration is in pretty advanced stage now, I'd like to ask if
you make any changes to any code under repo/includes/Search or
repo/config in Wikibase repo, or any tests or configs related to those,
please inform me (by adding me to patch reviewers/CC or by email or by
any other reasonable means) so that these changes won't be lost in the
migration. I'll be looking into the latest patches for anything related
periodically, but I might miss things.
WikibaseLexeme code that relates to search will be also migrated to a
separate extension (WikibaseLexemeCirrusSearch), that work will be
starting soon. So the request above applies to the search parts of the
WikibaseLexeme code also.
If you have any questions/comments, please feel free to ask me, on the
lists or on the IRC.
Thanks,
--
Stas Malyshev
smalyshev(a)wikimedia.org
Is it possible to get an impression on how often a set of Wikidata items is
being used?
I am interested in two ways of usage.
1. User statistics on a specific wikidata item. i.e. how often is a page
visited and from where and how often does a wikidata item shows up in a
query result?
2. How connected a Wikidata item is. Once an item is created how does it
connect to other area's? Is everything connected, or are we actually
looking at a collection of isolated data clusters? Is there a way to
visualize this?
Any ideas on how to answer this?
Cheers,
Andra
Hi everyone,
From some months ago I am having a doubt about one query I made. In this
query [1] I get 1085 items and I would like to get the same but as a bar
chart. Thus I have this second query [2]. However, I don't know why in
the second query I get only 573 items... The number of items differ a
lot, but practically both are the same.
What could be happening?
Thanks in advance for your time!
Regards,
Iván
[1]: http://tinyurl.com/ydhnwcr5
[2]: http://tinyurl.com/ycx2eyoc
--
Iván Hernández Cazorla
Historiador e interesado en las humanidades digitales
Miembro de Wikimedia España
https://ivanhercaz.com | https://keybase.io/ivanhercaz