This folder contains guidelines and materials for the Conference Live app Challenge at ESWC 2016.
In the past two years the Extended Semantic Web Conference (ESWC) has provided a semantic Web application to browse conference data. The application, called Conference Live, is a Web and mobile application based on conference data from the Semantic Web Dog Food server, which provides facilities to browse papers and authors at a specific conference. The data-backend is provided by the metadata chairs, while the front-end application has been developed by different teams for ESWC2014 and ESWC2015. In this challenge we call for a front-end application for ESWC2016. The task consist in implementing a system that allows the navigation of ESWC-16 semantic metadata. The system should satisfy specific requirements indicated in the call. The metadata chairs provide:
- data which is enriched with social features (e.g. integrated Twitter accounts of paper authors), scheduling features (calendar information are attached for paper presentations and social events)
- a backend service to vote for publications, if the conference includes sessions where participants can vote, as it is popular e.g. for poster and demo sessions.
Submissions (via EasyChair) will consist of:
- A summary description (abstract) of up to 200 words;
- A paper presenting the details of the implemented method, which discusses its novelty (if applicable), and highlights its strengths and weaknesses;
- Web Access: the Web application must be fully implemented and the code must be accessible either via the Web (e.g github) or downloadable. In particular, the application should be:
- Open Source
- compatible with Cordova framework
- Challenge papers and systems submission deadline: Monday March 21st, 2016
- Challenge paper reviews due: Tuesday April 5th, 2016
- Notifications sent to participants: Friday April 8th, 2016
- Final ESWC 2016 data published (for final test of the winning system): Friday April 8th, 2016
- Camera ready papers due: Sunday April 24th, 2016
- ESWC 2016 conference: May 29th - June 2nd,ß 2016
The notification will already declare the winning system, which will be distributed by Conference Live as the official ESWC-16 App. If a winning system cannot be proclaimed (e.g. all submissions fail to meet the minimum requisites) the metadata chair will provide a Conference Live baseline system.
Accepted challenge papers will be published by Springer in the CCIS series. The best challenge papers will be also published in the Satellite Event proceedings (a separate Springer LNCS Volume) of ESWC2016.
The task consist in implementing a system that allows the navigation of ESWC-16 semantic metadata. The system should satisfy the following requirements:
- Availability: be Open Source.
- Implementation: compatible with Cordova framework.
- Voting: enable voting for poster and demo through the REST service provided by the organizers (details on the service are provided to participants).
- Browsing: the system must provide a mechanism to browse papers and authors at the conference. The system will exploit the Linked Data of the conference provided as input for providing effective App-based visualisations of conference related knowledge, including basic information (author names, affiliations, paper titles...), roles covered by each person at the conference and additional data including: author picture, author additional contacts (e.g. social media account), thumbnail for each paper. Additional data might or might not be available for all persons/papers. The system must handle the null cases.
- Scheduling: the system must provide to the users the conference calendar with the scheduling of events (either social or academic) and paper presentations.
- Social: provide social functionalities and access to social channels (e.g., Twitter, ResearchGate, etc.) for enabling/improving scholarly net- working and interaction.
- Proceedings: enable accessing to the conference proceedings
- Enrichment: enable data enrichment from external and potentially heterogeneous sources. For example, the App could gather authors’ publications and other information related to their scholarly activity (e.g., social accounts or personal webpages) from Open Linked Data or Open Source API.
Requirements 1-5 are essential, a system which doesn’t implement any of these will be disqualified. Requirements 6-8 are preferable and will constitute added value. For implementation examples participants can refer to the systems used at ESWC2014 and ESWC2015. For an explanation on meeting the requirements they can refer to Gentile et al. 2015.
In order to facilitate the system development, we provide data from the past two editions of ESWC. These data is enriched with social features (e.g. integrated Twitter accounts of paper authors) and scheduling features (calendar information are attached for paper presentations and social events). Two rdf dumps are available:
We provide a backend service to vote for publications. The voting service is implemented as a REST service. To save a user vote, it is sufficient to send a GET query with three parameters: in the form: curl -G -X GET -d id=PAPER NUMBER -d track=PAPER TRACK -d code=USER SECRET CODE The is generated internally by the service, concatenating and
- IF the vote is cast correctly the response is an HTTP status code 200, with an extra json file as output, which simply contains the following content "status":"ok"
- IF has been used already for voting the best paper of a track, there is a CONFLICT ERROR CODE is: HTTP status code 409
- IF either the or the do not exist ERROR CODE is: HTTP status code 404
- IF there is a syntactic error (parsing of the query string) caused by either the or by the , there is a PRECONDITION FAILED ERROR CODE is: HTTP status code 412
For testing purposes we provide:
- a voting service for each provided dataset:
- a pool of valid secret codes as a txt file. The actual secret codes will be an alpha-numeric string, in the range [a-zA-Z0-9]
- a tool to verify currently saved votes for each provided dataset:
We will define two evaluations:
- implementation of requirements: the challenge organizers will score each of the requirements with a vote from 0 to 3, where 0 means not implemented, 1 partially implemented, 2 fully implemented, 3 outstanding implementation. The final vote will be a linear combination of the votes for each requirements.
- usability: a goal oriented evaluation will be carried out. Participants will we asked to complete tasks such as finding the time of a presentation, finding the author of a publication, voting for best poster/demo and then complete a questionnaire in order to record the System Usability Scale (SUS). The SUS is a metric used for evaluating the usability of a system and it is technology-independent, and reliable even with a very small sample size. For a system to be evaluated we ask the participants to strictly meet requirement R2 and potentially provide the application already packaged as an Apache Cordova Web App.
- Anna Lisa Gentile, University of Mannheim, Germany
- Andrea Giovanni Nuzzolese, STLab-CNR, Italy
- Valentina Presutti, STLab-CNR, Italy
- Maribel Acosta Deibe, KIT, Karlsruhe, Germany
- Luca Costabello, Fujitsu Linked Data Research Team, Galway, Ireland
- Mauro Dragoni, Fondazione Bruno Kessler, Trento, Italy
- Aldo Gangemi, Université Paris 13, France
- Suvodeep Mazumdar, University of Sheffield, UK
- Lionel Médini, Université Claude Bernard Lyon 1, France
- Christoph Pinkel, fluidOps, Germany
- Diego Reforgiato, STLab-CNR, Italy
- Giuseppe Rizzo, ISMB, Torino, Italy
- Raphaël Troncy, EURECOM, Sophia Antipolis, France