Skip to content

Commit 1206258

Browse files
kuefmzkuefmz
authored
Merge pull request #5 from iswc-conf/dev
Add calls
2 parents 077952f + 4caa495 commit 1206258

15 files changed

+1275
-124
lines changed

‎src/App.js

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ import Research from "./components/calls/Research";
1010
import Resource from "./components/calls/Resource";
1111
import InUse from "./components/calls/InUse";
1212
import Posters from "./components/calls/Posters";
13-
import SemanticWeb from "./components/calls/SemanticWeb";
13+
import Challenges from "./components/calls/Challenges";
1414
import IndustryTrack from "./components/calls/IndustryTrack";
1515
import DoctoralConsortium from "./components/calls/DoctoralConsortium";
1616
import HTMLSubmissionGuide from "./components/guidelines/HTMLSubmissionGuide";
@@ -44,7 +44,7 @@ export default function HeroComponent() {
4444
<Route path="/calls/resource" element={<Resource />} />
4545
<Route path="/calls/in-use" element={<InUse />} />
4646
<Route path="/calls/posters" element={<Posters />} />
47-
<Route path="/calls/semantic" element={<SemanticWeb />} />
47+
<Route path="/calls/challenges" element={<Challenges />} />
4848
<Route path="/calls/industry" element={<IndustryTrack />} />
4949
<Route path="/calls/doctoral" element={<DoctoralConsortium />} />
5050
<Route path="/calls/workshopstutorials" element={<WorkshopsTutorials />} />

‎src/components/calls/Challenges.jsx

Lines changed: 133 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,133 @@
1+
import React from "react";
2+
export const Challenges = () => {
3+
return (
4+
<>
5+
<div className="mt-[74px] px-4 pt-2 bg-white flex items-center justify-center">
6+
</div>
7+
<br />
8+
<div className="flex justify-start items-start flex-col pt-10 pb-0 lg:pt-16 lg:pb-4 mb-4 lg:my-6 lg:h-auto lg:px-32 px-8 overflow-visible">
9+
<p style={{ color: '#e94607' }} className="text-3xl font-bold mb-4 lg:mx-10 sm:mx-2 tracking-wide text-center">Call for Challenges Proposals</p>
10+
<div className="text-md lg:text-lg font-[300] lg:mx-10 sm:mx-2">
11+
<p>
12+
A great way to advance the state of the art in a given domain is to create competition. We invite you to propose an ISWC 2025 Challenge, in which you define an open competition on a problem of your choice within the Semantic Web domain.
13+
</p>
14+
15+
<h2 style={{ color: '#e94607' }} className="text-xl font-semibold mt-6">Important Dates</h2>
16+
<ul>
17+
<li>Challenge proposal submission due: <strong>February 18th, 2025</strong></li>
18+
<li>Notification of challenge acceptance: <strong>March 2nd, 2025</strong></li>
19+
</ul>
20+
<p>All deadlines are 23:59 AoE (Anywhere on Earth).</p>
21+
22+
<h2 style={{ color: '#e94607' }} className="text-xl font-semibold mt-6">Topics</h2>
23+
<p>For ISWC 2025, Challenge proposals are invited for any challenge involving Semantic Web tasks, including but not limited to:</p>
24+
<ul className="list-disc ml-16 text-md lg:text-lg font-[300]">
25+
<li>Ontology and knowledge graph alignment</li>
26+
<li>Ontology and knowledge graph quality assurance (QA)</li>
27+
<li>Knowledge graph construction and refinement</li>
28+
<li>Graph embeddings and graph neural networks</li>
29+
<li>Query and reasoning scalability</li>
30+
<li>Open information extraction</li>
31+
<li>Neurosymbolic reasoning</li>
32+
<li>Semantic Web and data mining</li>
33+
<li>Semantic Web, machine learning, and neuro-symbolic AI</li>
34+
<li>Link prediction</li>
35+
<li>Question answering</li>
36+
<li>Stream processing and reasoning</li>
37+
<li>Semantic table understanding</li>
38+
<li>Agents (especially using neuro-symbolic methods) and agentic workflows</li>
39+
<li>Retrieval Augmented Generation (RAG)</li>
40+
</ul>
41+
<p>Recent Challenge examples can be found at:</p>
42+
<ul>
43+
<li><a href="https://iswc2023.semanticweb.org/semantic-web-challenges/" target="_blank" rel="noopener noreferrer">ISWC 2023 Semantic Web Challenges</a></li>
44+
<li><a href="https://iswc2022.semanticweb.org/index.php/challenges/" target="_blank" rel="noopener noreferrer">ISWC 2022 Challenges</a></li>
45+
<li><a href="https://iswc2021.semanticweb.org/challenges" target="_blank" rel="noopener noreferrer">ISWC 2021 Challenges</a></li>
46+
</ul>
47+
48+
49+
<h2 style={{ color: '#e94607' }} className="text-xl font-semibold mt-6">Proposal Stage</h2>
50+
<p>
51+
ISWC 2025 will run multiple challenges with the aim of evaluating and comparing software solutions for the Semantic Web and Knowledge Graphs in a systematic way. To propose a challenge, you are required to:
52+
</p>
53+
<ul className="list-disc list-inside text-md lg:text-lg font-[300]">
54+
<li>Specify a task to be addressed.</li>
55+
<li>Provide an evaluation dataset.</li>
56+
<li>Define evaluation measures to compare the performance of participating systems.</li>
57+
</ul>
58+
59+
<h2 style={{ color: '#e94607' }} className="text-xl font-semibold mt-6">Showcase Stage</h2>
60+
<p>
61+
At ISWC 2025, each challenge will receive one slot during the main conference, where organizers present the challenge, participating systems with accepted solutions, and announce the winner. At least one organizer must register and be present at the conference. Participants have the option to present their systems during the poster and demo session. Winners will receive a certificate.
62+
</p>
63+
64+
<h2 style={{ color: '#e94607' }} className="text-xl font-semibold mt-6">Proposal Submission Guidelines</h2>
65+
<p>
66+
Proposals for challenges should be concise (2–4 pages) and include:
67+
</p>
68+
<ul className="list-disc list-inside text-md lg:text-lg font-[300]">
69+
<li>Names and affiliations of the organizers.</li>
70+
<li>Description of the challenge, including its relevance to the Semantic Web community.</li>
71+
<li>Process for selecting, acquiring, and preparing data for training and evaluation, with conditions of availability. Describing data in relation to the FAIR principles is recommended.</li>
72+
<li>Procedure for evaluating the performance of systems, including metrics and availability of evaluation software.</li>
73+
<li>A timeline based on the provided template for all challenges.</li>
74+
<li>Expected number of participants with supporting evidence (e.g., expression of interests, forum discussions, attendance in previous editions).</li>
75+
<li>Plan for dissemination of the challenge (targeted mailing lists, social media, etc.).</li>
76+
<li>Any other relevant information, including previous evaluations for the proposed challenge.</li>
77+
</ul>
78+
79+
80+
<h2 style={{ color: '#e94607' }} className="text-xl font-semibold mt-6">Selection Criteria</h2>
81+
<ul className="list-disc list-inside text-md lg:text-lg font-[300]">
82+
<li>Relevance to the Semantic Web community.</li>
83+
<li>Potential number of interested participants.</li>
84+
<li>Rigor and transparency of task description and evaluation procedure.</li>
85+
</ul>
86+
<p>
87+
Please submit through EasyChair and select the track “Challenge-Proposal”.
88+
<a href="https://easychair.org/conferences/?conf=iswc2025" style={{ color: '#e94607' }} target="_blank">Submit Proposal</a>
89+
</p>
90+
91+
<h2 style={{ color: '#e94607' }} className="text-xl font-semibold mt-6">Requirements upon Acceptance</h2>
92+
<p>
93+
Accepted challenges will need to adhere to the following requirements:
94+
</p>
95+
<ul className="list-disc list-inside text-md lg:text-lg font-[300]">
96+
<li>Challenge Web Page: Organizers must prepare a challenge web page with detailed participation instructions, format, and timelines.</li>
97+
<li>Timeline for Deadlines: Organizers are encouraged to adhere to the indicative timeline for challenges provided by ISWC.</li>
98+
<li>Participation Requirements: At least one challenge organizer must register for the conference by the early bird registration deadline and attend the challenge in person.</li>
99+
</ul>
100+
101+
<h2 style={{ color: '#e94607' }} className="text-xl font-semibold mt-6">Timeline Template for Challenge Organizers</h2>
102+
<p>
103+
The tentative timeline template for organizing a Challenge is as follows (all deadlines are 23:59 AoE):
104+
</p>
105+
<ul className="list-disc list-inside text-md lg:text-lg font-[300]">
106+
<li>Website & first call for participation - Mar 16th</li>
107+
<li>Release datasets - Mar 30th</li>
108+
<li>Release of Test Set (optional) - May 16th</li>
109+
<li>Submission of Systems - June 28th</li>
110+
<li>System Results - July 19th</li>
111+
<li>Notification of Acceptance - July 19th</li>
112+
</ul>
113+
<p>
114+
Note: The deadlines and mostly the dataset release deadline and system submission deadline can be flexibly adjusted according to the challenge, especially if the challenge includes several evaluation rounds (e.g., http://www.cs.ox.ac.uk/isg/challenges/sem-tab/2020/index.html).
115+
</p>
116+
117+
<h2 style={{ color: '#e94607' }} className="text-xl font-semibold mt-6">Semantic Web Challenge Chairs</h2>
118+
<p>
119+
Contact: <a href="mailto:[email protected]">[email protected]</a>
120+
</p>
121+
<p>
122+
<b>Mayank Kejriwal</b> - University of Southern California, United States
123+
</p>
124+
<p>
125+
<b>Pablo Mendes</b> - Upwork, United States
126+
</p>
127+
</div>
128+
</div>
129+
</>
130+
);
131+
}
132+
133+
export default Challenges;

‎src/components/calls/DoctoralConsortium.jsx

Lines changed: 70 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,13 +2,77 @@ import React from "react";
22
export const DoctoralConsortium = () => {
33
return (
44
<>
5-
<div className="flex justify-center item-center flex-col pb-0 lg:pb-4 mb-4 lg:my-6 lg:h-[14rem] lg:px-16 px-6">
6-
<p style={{ color: '#e94607' }} className="text-3xl font-bold mb-4 lg:mx-10 sm:mx-2 tracking-wide text-center">Doctoral Consortium</p>
5+
<div className="mt-[74px] px-4 pt-2 bg-white flex items-center justify-center">
6+
</div>
7+
<br />
8+
<div className="flex justify-start items-start flex-col pt-10 pb-0 lg:pt-16 lg:pb-4 mb-4 lg:my-6 lg:h-auto lg:px-32 px-8 overflow-visible">
9+
<p style={{ color: '#e94607' }} className="text-3xl font-bold mb-4 lg:mx-10 sm:mx-2 tracking-wide text-center">Call for Doctoral Consortium Submissions</p>
10+
<div className="text-md lg:text-lg font-[300] lg:mx-10 sm:mx-2">
11+
<p>
12+
The ISWC 2025 Doctoral Consortium (DC) will take place as part of the <a href="https://iswc2025.semanticweb.org/" target="_blank" style={{ color: '#e94607' }}>24th International Semantic Web Conference</a>. This forum provides PhD students an opportunity to:
13+
<ul className="list-disc ml-16 text-md lg:text-lg font-[300]">
14+
<li>present and discuss their research ideas in a supportive, formative and yet critical environment;</li>
15+
<li>receive feedback from mentors, typically senior members of the Semantic Web research community, and peers;</li>
16+
<li>and network and build collaborations with other members of the community.</li>
17+
</ul>
18+
</p>
19+
<p>
20+
The event is intended for students who have articulated a reasonably detailed research proposal, preferably supported by some preliminary results, but are not yet on the final stretch of their thesis, such that the feedback gathered at the DC will have a maximal impact. The aim is to support the students in refining their proposal and to suggest possible ways to improve their research plan and to achieve results with prospective greater impact.
21+
</p>
22+
<p>
23+
The submissions to the Doctoral Consortium should be structured like a research proposal (see “<a href="https://iswc2023.semanticweb.org/call-for-doctoral-consortium-papers/#submission-details" target="_blank" style={{ color: '#e94607' }}>Submission Details</a>” below). Please note that anything that looks like a research paper will be rejected without review.
24+
</p>
25+
<p>
26+
All proposals submitted to the Doctoral Consortium will undergo a rigorous review process. The reviewers will provide detailed and constructive feedback and select which submissions will be presented at the Doctoral Consortium. If accepted, students will have to register and attend the full day event.
27+
28+
</p>
29+
<p>
30+
We anticipate having student travel grants to cover some of the travel expenses to the conference.
31+
</p>
32+
<h3 style={{ color: '#e94607' }} className="text-lg font-medium mt-4">Important Dates:</h3>
33+
<p>All deadlines are 23:59 AoE (anywhere on Earth)</p>
34+
<ul>
35+
<li>Submissions Due: <b>June 3, 2025</b></li>
36+
<li>Notifications: <b>July 8, 2025</b></li>
37+
<li>Camera-ready Submissions Due: <b>July 31, 2025</b></li>
38+
<li>Doctoral Consortium: <b>November 3, 2025</b></li>
39+
</ul>
40+
41+
<h3 style={{ color: '#e94607' }} className="text-lg font-medium mt-4">Topics of Interest:</h3>
42+
<p>
43+
We are the doctoral consortium of the ISWC. As such, submissions should broadly fit the topics of interest of the ISWC research track.
44+
</p>
45+
<h3 style={{ color: '#e94607' }} className="text-lg font-medium mt-4">Submission Details:</h3>
46+
<p>
47+
Students should submit a 7-page description of their PhD research proposal. All proposals have to be submitted electronically via the EasyChair conference submission system.
48+
</p>
49+
<p>
50+
The submission should address the following questions:
51+
</p>
52+
<ol className="list-disc ml-16 text-md lg:text-lg font-[300]">
53+
<li><b>Problem statement:</b> what is the problem that you are trying to solve?</li>
54+
<li><b>Importance:</b> Why is this problem important and for whom? Who will benefit and who should care? What is the impact of solving this problem (for the research community, or society in general)?
55+
</li>
56+
<li><b>Related work:</b> Has a solution to this problem been attempted before and how? If you are addressing an existing problem, what are the limitations of current solutions? What are you adding that is novel? Why? If not, have research efforts tried or solved similar, analogous problems? What can you learn from these efforts? </li>
57+
<li><b>Research question(s) and hypotheses:</b> What research questions do you plan to explore? What hypotheses do you make in formulating your solution?</li>
58+
<li><b>Preliminary results:</b> Do you have any preliminary results that inform your research questions or hypotheses?</li>
59+
<li><b>Evaluation:</b> How will you know you’ve answered your question(s)? What are the methods you apply to test your hypotheses? Have you identified criteria to measure the degree of success of your solution?</li>
60+
<li><b>Reflection and future work:</b> Are there any limitations in your approach? What are your planned next steps to complete your investigation?
61+
</li>
62+
</ol>
63+
64+
<p>Please aim to answer the above questions with as much detail as possible, especially questions 2 and 4. You should provide as much detail as possible to allow a knowledgeable reviewer from the Semantic Web community, but possibly not an expert in your topic, to assess the validity of your research contribution. All submissions should include references. References will not count towards the page limit. All submissions exceeding 7 pages will be rejected without review.</p>
65+
<p><b>The student should be the sole author of the submission.</b> The supervisor(s) should be acknowledged at the end of the submission, together with a funding agency or any other party who supports or contributes to the research.</p>
66+
67+
<p>Submissions must use the new CEUR-ART style. For details on the CEUR-ART style, see <a href="https://ceur-ws.org/HOWTOSUBMIT.html" target="_blank" style={{ color: '#e94607' }}>Publishing at CEUR-WS.org</a>. For HTML submission guidance, please see the <a href="https://iswc2023.semanticweb.org/html-submission-guide/" target="_blank" style={{ color: '#e94607' }}>HTML submission guide</a>. They must be submitted online via <a href="https://easychair.org/my/conference?conf=iswc2023" target="_blank" style={{ color: '#e94607' }}>EasyChair</a>, in PDF or HTML format.</p>
68+
69+
<p>DC Proceeding will be published with <a href="http://ceur-ws.org/" target="_blank" style={{ color: '#e94607' }}>CEUR-WS.org</a>.</p>
770

8-
<p className="text-md lg:text-lg font-[300] lg:mx-10 sm:mx-2">
9-
Coming soon...
10-
</p>
11-
71+
<h3 style={{ color: '#e94607' }} className="text-lg font-medium mt-4">Doctoral Consortium Track Chairs:</h3>
72+
<p><b>Abraham Bernstein</b> - University of Zurich, Switzerland</p>
73+
<p><b>Natasha Noy</b> - Google Research, US</p>
74+
<p>Contact: <a href="mailto:[email protected]">[email protected]</a></p>
75+
</div>
1276
</div>
1377
</>
1478
);

0 commit comments

Comments
 (0)