We would like to give you a heads up on a quite exciting project that will
be starting soon. Wikimedia Deutschland just received a grant from the
organization Arcadia <https://www.arcadiafund.org.uk/>. The goal of this
grant is to make our software more usable by cultures underrepresented in
technology, people of the Global South and speakers of minority languages.
This project will be defined over the coming months and will run for 3
years, ideally in close collaboration with other Wikimedia organizations.
Our first milestone will be to support the creation of a new development
team that will function together with Wikimedia Deutschland to improve
parts of our codebase and to develop new functionality. With this
experiment, we would like to share and transfer the knowledge of the
Wikidata development team to other organizations around the globe.
If you have any questions, feel free to reach out to us directly by email.
Community Engagement Coordinator
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
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.
[Please pardon me if you have already read this on the Wikidata chat]
TL;DR: what do you think of the 3 validation criteria below?
I'm excited to let you know that the soweego 2 project has just started !
To cut a long story short, soweego links Wikidata to large third-party
The next step will be all about synchronization of Wikidata to a given
target catalog through a set of validation criteria. Let me paste below
some key parts of the project proposal.
1) existence: whether a target identifier found in a given Wikidata item
is still available in the target catalog;
2) links: to what extent all URLs available in a Wikidata item overlap
with those in the corresponding target catalog entry;
3) metadata: to what extent relevant statements available in a Wikidata
item overlap with those in the corresponding target catalog entry.
These criteria would respectively trigger a set of actions. As a toy
1) Elvis Presley (Q303) has a MusicBrainz identifier 01809552, which
does not exist in MusicBrainz anymore.
Action = mark the identifier statement with a deprecated rank;
2) Elvis Presley (Q303) has 7 URLs, MusicBrainz 01809552 has 8 URLs, and
Action = add 5 URLs from MusicBrainz to Elvis Presley (Q303) and
submit 4 URLs from Wikidata to the MusicBrainz community;
3) Wikidata states that Elvis Presley (Q303) was born on January 8, 1935
in Tupelo, while MusicBrainz states that 01809552 was born in 1934 in
Action = add 2 referenced statements with MusicBrainz values to
Elvis Presley (Q303) and notify 2 Wikidata values to the MusicBrainz
In case of either full or no overlap in criteria 2 and 3, the Wikidata
identifier statement should be marked with a preferred or a deprecated
Please note that the soweego bot already has an approved task for
criterion 2 , together with a set of test edits . In addition, we
performed (then reverted) a set of test edits for criterion 1 .
I'm glad to hear any thoughts about the validation criteria, keeping in
mind that the more generic the better.
Stay tuned for more rock'n'roll!
As announced with the release of WikidataCon’s theme
for 2021, *Reimagining Wikidata from the margins* is starting! I invite you
all to check out the project’s page here
Although Wikidata intends to structure the sum of all human knowledge,
we’re still missing Global South and other marginalized communities from
the North - both in data and in contributors. Before WikidataCon 2021 later
in October, the *Reimagining Wikidata from the margins* project is taking
place as a series of discussions with underrepresented communities to
collectively imagine how to decenter Wikidata to be more inclusive and fair
in representing their knowledge. This process was designed to address our
communitie’s hopes and expectations for a sustainable future for Wikidata.
To bring more clarity on what kind of discussion we’re aiming for with
Wikidata from the margins*, you can find here some starting questions
Both underrepresented communities and good allies are welcome to
participate in the process!
How will it work?
We’re starting now a first round of conversations with local groups to
better understand the challenges, expectations and perspectives they have
in the Wikidata ecosystem. Then, the second round will gather people from
different locations discussing topics in common (i.e. engagement with the
broad community, language diversity, GLAM processes etc.). After that,
we’ll write a document to be released at WikidataCon with the insights from
the previous rounds. The idea is to collaboratively build an analytical yet
inspiring document that can serve our community beyond WikidataCon itself.
You can find our timeline here
If you want to collaborate, do not hesitate to reach out to us! You can
send a message to erica(a)wmnobrasil.org and then we’ll arrange a meeting or
find any other suitable way for collaboration. Mohammed Sadat and I will
also actively reach out to some communities and individuals that may be
interested in participating in the process. Simultaneous translation may be
available so people feel more comfortable speaking their native language
during our meetings.
You can also *organize local meetings* with people from your community to
discuss the topics concerning *Reimagining Wikidata from the margins* and
then let us know your insights and perspectives.
We’ll also release *a survey* for those of you who want to collaborate with
the process, but can’t get involved in conversations.
You can also *help us translate* the *Reimagining Wikidata from the margins*
page to your native language so more people can get engaged!
Hope to hear from you soon :)
*Érica Azzellini | User:EAzzellini (WMB)*
*Communications Manager | **Wiki Movimento Brasil*
We hope this email finds you well and you are staying safe.
The Afrocine Project core team would once again like to thank everyone who
contributed towards ensuring the success of the Months of African Cinema
Contest in 2020. Due to your valued efforts, the third iteration was a
success! Over 3,000 articles were created across various Wikimedia projects
and in 19 different languages.
Months of African Cinema, 2021 is three months away! To ensure a more
seamless organization this year and better support, we are calling on
interested local organizers from across the movement to join us in
facilitating this contest in their various communities.
This year, in addition to local community organizers, we are particularly
also inviting Wikimedians to help coordinate the contest in their local
languages, as this will play a huge role in the number of languages that
would be eligible for international prizes. If you would love to join us in
organizing this exciting contest in your local community or your local
language wiki, kindly show your interest by listing your community or
project on the organizer’s meta page.  Please try to sign up by 23rd
Thank you once again! We are looking forward to your participation.
Community Liaison, Afrocine Project
Workshop on Ontology Design and Patterns (12th edition) - WOP2021 will take place at the 20th International Semantic Web Conference, ISWC2021, virtually, in October 2021 <https://iswc2021.semanticweb.org<https://iswc2021.semanticweb.org/>>
Workshop Website: <http://ontologydesignpatterns.org/wiki/WOP:2021>
**EXTENDED** Submission deadline (papers and patterns): July 19, 2021
Call for Papers
We invite submissions to the 12th Workshop on Ontology Design and Patterns
(WOP2021) to be held in conjunction with the International Semantic Web Conference (ISWC) that will take place online from Oct. 24 to 28, 2021. WOP2021 is a full-day workshop consisting of three parts: paper presentations, a poster session, and an interactive breakout discussion session.
The workshop aims to discuss issues of quality in ontology design. In particular, it focuses on the role and use of ontology design patterns (ODPs) for data and knowledge engineering in the Semantic Web, as related to the ontologydesignpatterns.org<http://ontologydesignpatterns.org/> initiative. The increased attention to ODPs in recent years through their interaction with emerging trends of Semantic Web such as knowledge graphs can be attributed to their benefit for knowledge engineers and Semantic Web developers. Such benefits come in the form of direct link to requirements, reuse, guidance, and better communication. The workshop's aim is to: 1) provide an arena for discussing patterns, pattern-based ontologies, systems, datasets, and 2) broaden the pattern community by developing its own "discourse" for discussing and describing relevant problems and their solutions.
We particularly welcome contributions on topics concerning development of high-quality ontologies in general (with or without the help of ODPs) as well as studies and applications of ODPs for knowledge graph construction and maintenance. In addition, as usual we also welcome pattern descriptions of all sorts, including patterns geared towards applications in specific domains such as geosciences, biomedical science, digital humanities, or e-commerce. The main topics of interest are:
1) Use of ontology design patterns for any kind of knowledge engineering, including
- Pattern-based ontology design, conceptual modeling or knowledge engineering broadly
- Use in knowledge graphs or linked data settings (including
pattern-driven linking or data publishing)
- Pattern-based information extraction, ontology learning, and relation to NLP
- Use in streaming, ingesting or evolving knowledge
- Use of patterns for ontology evaluation, quality assurance,
ontology selection, integration or alignment
- Pattern-based development of semantic applications
- Reasoning with patterns (including automated reasoning,
verification, or contextual reasoning)
2) Methods and tools for developing high-quality ontologies (with or without the help of patterns), including
- Ontology engineering by domain experts
- Quality attributes or metrics in ontologies and ontology engineering
- Quality assurance approaches for ontology engineering
- Critical analysis of the design of existing ontologies, and
proposals on how to improve the design, possibly by using ODPs
3) Development or analysis of ontology design patterns, including
- Pattern extraction
- Analyses of ontology design patterns or their uses
- Antipatterns and their relations to ODPs
4) Development and use of patterns in specific domains, including
- Date lakes, business intelligence, or Big Data integration
- Geosciences, life sciences, engineering, digital humanities, cultural preservation
- IoT, smart homes & cities, smart agriculture
- Semantic technology including social networks, semantic wikis or blogs
We invite the submission of original research results related to the focus areas of the workshop, in one of three categories given below. All submissions are requested through EasyChair.
1) Research papers (maximum 15 pages LNCS style) presenting mature work and established results.
2) Short papers (maximum 5 pages LNCS style) presenting proposed research directions, novel ideas, or more general positions or discussions.
3) Ontology Design Patterns (5-12 pages LNCS style) should solve a particular modelling problem, of relevance either to the broader ontology engineering community, or to some specific knowledge domain, in a novel and reusable manner. Pattern serialization must be made available, ideally at a permanent IRI. When preparing the camera-ready version, patterns must additionally be submitted through the ontologydesignpatterns.org<http://ontologydesignpatterns.org/> community portal, as described at http://ontologydesignpatterns.org/wiki/WOP:2021/Submission.
Submissions should be made via <https://easychair.org/my/conference?conf=wop2021>.
Detailed instructions can be found at the submission page <http://ontologydesignpatterns.org/wiki/WOP:2021/Submission>.
Important Dates: Anywhere on Earth!
Papers submissions: July 19, 2021
Papers notifications: August 8, 2021
Camera-ready version submissions: September 1, 2021
Workshop will be held on October 24, 2021
Accepted research papers and pattern descriptions will be published online as CEUR-Workshop Proceedings.
- Karl Hammar, Jönköping University, SWE (general chair)
- Cogan Shimizu, Kansas State University, USA (papers co-chair)
- Hande Kucuk McGinty, Ohio University, USA (papers co-chair)
- Luigi Asprino, University of Bologna, IT (patterns co-chair)
- Valentina Anita Carriero, University of Bologna, IT (patterns co-chair)
We often act like and think that things are, well ... forever (even our own
lives!). But Time waits for no one. So...
I had posted this over in the LD4 Slack channel but thought that this would
be good for folks here to at least always be aware of and think about in
our growing Linked Data world.
All Linked Data efforts need stable identifiers (on both ends of a
"link"). I.E. linking is only good if the other side will be retrievable
and available (online or offline through web/archives/files) throughout the
expected lifetime of an effort and beyond. Think closely about "knowledge
retention" (libraries/books hold knowledge for hundreds of years!) and what
the Linked Data lifecycle itself that ideally will do that for your
projects. Then look towards not the tools, but instead the communities
that are well established and have the likelihood to continue to provide
stable identifiers that are retrievable well into the future + another 100+
years. This might include government efforts, or communities that have
foundations behind them that are well grounded through philanthropic means
with perpetuity ... to avoid link rot or non-retrievability through
complete void of the knowledge or stable identifiers in the future.
I'm hopeful that communities will think about data retention policies and
generally "Linked Data Availability" much more deeply and seriously. This
could be likened to something like GitHub's Arctic Vault, Internet Archive,
or decentralized storage solutions like Filecoin, to be able to backup and
retain the knowledge for thousands of years, if need be.