Web Application Development

project proposals

A project proposal could be chosen by maximum 3 teams. A team includes 2—3 persons.

Each team should fill in the WADe Project Assessment form – deadline: Monday, 17 October. The list of submitted project applications is also available.

  1. CryK (Cryptocurrency Knowledge Manager)

    Starting with Description Of A CryptoCurrency, develop a modular Web system capable to express and manage the knowledge about existing cryptocurrencies and their (meta-)data. Each functionality will be implemented by a (micro-)service and all queries will be performed via a SPARQL endpoint. Exposed information will be available in multiple formats (at least, HTML+RDFa and JSON-LD). Also, multiple visualizations of interest will be provided. For additional resources, explore CryptoMinded.

  2. DiS (Distributed System Ontology)

    Create – possibly, by reusing (parts of) existing ontologies – an ontological model regarding certain aspects – data communication, data processing, data storage, etc. – regarding a distributed system (including platform, framework,...) used in various contexts such as big data, e-health, multimedia streaming, Internet/Web of Things. Starting with this conceptual specification, a test-bed application will be developed in order to manage the collected knowledge about a given solution and context. For instance, significant concepts, relations, restrictions, individuals should be considered as examples for a real software solution – like Apache Hadoop, Git Large File Storage, Wikibase – might be taken into account. Consult also Awesome distributed systems, Real Life Architectures, and The New Stack.

  3. GaDa (Game on Web of Data)

    Propose a (micro-)service-oriented Web game – i.e. an RPG (Role-Playing Game) or strategy game – by using the data about the characters provided by Marvel Comics API, Star Trek API, Star Wars API, and/or PokéAPI (use minimum two of them). Various player interactions, game rules, characteristics and assets will be modeled and accessed by using RDF, SPARQL, RDF Schema, SKOS, and OWL. Additional resources: Electronic Game Design [RO] , Web Game Development, OWL-based Modeling of RPG Games. All interactions between players and the game itself could be textual. Inspiration: Open Source Game Clones. Bonus: the NPC (Non-Playable Character) behavior or some aspects of the game strategy will make use of a reasoner.

  4. ImP (Image Smart Processor)

    Considering the Kaggle Image Datasets – or, alternatively, the EPIC-KITCHENS-100 Dataset –, develop an extensible microservice-based system able to perform processing tasks such as browsing, smart faceted searching & filtering, etc. Adopting both deep learning (or machine learning) techniques and semantic Web technologies, the platform will be able to generate various visualizations (e.g., semantic zoom), correlations, classifications, and recommendations exposed via a SPARQL endpoint. Also, a comparison study will be provided to explain the obtained results. Additional info: An Introduction to Data Visualization.

  5. MiR (Migration Reporting Tool)

    Considering observations provided by users (e.g., messages posted on a social network) or various sensors, develop an "intelligent" Web system capable to generate in real-time an interactive map regarding the migrations performed by various entities (birds, humans, robots, extraterrestrial beings) in a specific context (season, working, politic factors, calamity). A migration-related event could be directly reported – in conjunction to the GPS info + optional (meta)data – into the implemented platform or by using #mig-here hashtag on an existing social Web application (Instagram, Twitter, Vimeo). Several useful statistics and visualizations about the migratory habits of specific species – including information on geographical areas, climate, seasons, user comments/images/videos, etc. – should be offered by a SPARQL endpoint – possibly enhanced by additional knowledge provided by DBpedia and/or Wikidata. Visit also Migration Data Portal. Bonus: adopting a stream processing approach.

  6. NeP (Web News Provenance)

    Create a Web application/platform able to model and manage – including operations like query, visualize, recommend,... – the knowledge about the provenance of each online newspaper article, which content could be textual or multimedia (pictures, illustrations, presentations, podcasts – audio files available for streaming, videos,...), possibly available in different languages and structured by using meta-data/classification models like DCMI, ITPC Standards and Social Semantic Web Thesaurus. Additional (meta)data could be provided by DBpedia and/or Wikidata. A SPARQL endpoint – exposing RDFa and JSON-LD including Creative Work concept from schema.org – is also necessary to provide access to interesting knowledge (e.g., list fresh editorials concerning a specific topic, provide the articles under 4000 words written in English or Spanish about the international IT contests, offer the title + description of the investigations and/or documentaries posted on Web by the Romanian journalists). For inspiration, study Europeana Stories and The London Gazette. Explore also News Services APIs.

  7. NoW (Notarial Knowledge Web Tool)

    Using the official data regarding public notary entities [RO] and authorized translators + interpreters [RO], develop a smart modular Web system capable to provide support for locating offices and services – such as notarized documents: acknowledgments, oaths/affirmations, copy certification, signature witnessing, others legal procedures – according to user preferences, geographical places, fees, restrictions, and other aspects (e.g., support for foreign citizens) – consider also legal paper provenance. Via SPARQL endpoints, the application will offer useful maps – see also Place schema.org concept – and additional knowledge (contact info, timetable, reviews, related points of interest) about each notary office.

  8. ODa (Open Dataset Visualizer)

    Considering a collection of public datasets, build a modular Web tool – such as SPA (Single Page Application) or a Web browser extension – able to provide useful visualizations for better understanding of data/information/knowledge. The core functionalities – based on a knowledge model expressed in SKOS and/or OWL including various vocabularies – will be accessed via a SPARQL endpoint. Different extensions (at least 3) will be provided in order to demonstrate specific operations – e.g., "intelligent" filtering, layered visualizations, trend computations, comparations, etc. Bonus: exposing 3D visualizations by using WebGL and/or WebXR.

  9. PhAs (Phobia-related Web Assistant)

    Develop a multi-device application suggesting various remedies (medications, physical/psychological exercises, serious games, useful Web resources,...) for overcoming a specific (set of) phobia(s) affecting a user or a group of users: family, coworkers, "friends" from a social network, etc. To accomplish this goal, a general knowledge base like DBpedia and/or Wikidata, plus conceptualizations such as schema.org's health/medical types will be used. Also, the application will notify users regarding a potential reaction to a specific phobia – for instance, take into consideration the context – e.g., claustrophobia is triggered when a user is located into an elevator or a season (e.g., an allergy to polen trigerred only in Spring). Additional information could be provided by WikiDoc and the user's entourage. See also a list of health-related APIs. Bonus: using a rule-based approach (for instance, if the user has an allergy to polen and the current season is Spring and the trees located in his/her area are blossoming, then send an alert and provide information of interest).

  10. SoRe (Social Recommender)

    Develop a Web modular system able to recommend certain items of interest (people, events, places, other things) according to a given knowledge graph expressed in RDF and automatically built for a specific user – for example, based on her/his social media profile(s) – by considering multiple similar features/properties. For instance, suggesting the members of an IT team based on desired skills (excellent knowledge of certain areas like Web technologies + open hardware), geographic location (i.e. from Romania and Chile only), technical preferences (e.g., using free software), background info (demographics, education, occupation history, driving license, other competencies), hobbies (i.e. horror movies + classical music), aversions (e.g., communication by phone, sport, politics) and so on. The system should be "smart" enough to improve recommendations based on various methods such as user feedback, reasoning, and/or machine learning. The recommended items will be available via a SPARQL endpoint.

  11. UICS (UI Component Smart Generator)

    By considering an UI component API provided by a library/framework – for instance, a React UI component solution like MUI and/or Ionic UI Components –, create an OWL-based ontology able to specify the interactive I/O controls/components. This knowledge model will be used to cleverly suggest and generate – via a SPARQL end-point – the proper controls for various Web interfaces by using a set of controlled language constructs such as "Build a section with I images|videos and P paragraphs placed below|above|left|right" or "Build main section having a user profile with minimum 2 paragraph, 1 image and a submit button labeled "Edit" vertically|horizontally arranged". Several keywords/parameters could be inserted to express the interface designer's intention – e.g., a section could have a specific role (content, navigation, download, footer, photo gallery, calendar, slider, and so on); using a direction indicator such as "ltr" (left to right); instead of "image", some refined terms could be used to specify the semantics: "photo", "diagram", "logo", "chart" with some modifiers like "big", "small", "medium", "responsive" (examples: "Build an aside|main section with 2 small photos 1 search input 2 nav links 1 download button", "Build a table with 5 images 5 paragraphs 5 buttons by rows|columns" – if 'columns' is chosen, the tool automatically can generate 5 columns, each column having 1 image, 1 paragraph, and 1 button). Test and exemplify your proposal for at least 2 use-cases.

  12. USe (Unsplash Semantic API)

    Following the Linked Data principles, create a multi-device Web application using a knowledge graph/base and a SPARQL endpoint (API) to perform various tasks – e.g., visualize, augment, filter, compare,... – on the knowledge about the nature-themed photos provided by the Unsplash Lite Dataset. Use various conceptual models such as schema.org and Getty Thesaurus of Geographic Names, in addition to the knowledge about photography, natural beauties, geography, etc. available on Wikidata and DBpedia. Additional resources: Unsplash Developers.

  13. ViRe (Vinyl Recommender Tool)

    Build a (micro-)service Web system able to "intelligently" recommend – by exposing a SPARQL endpoint – vinyl music records according to various criteria: user preferences (specified via controlled natural language constructs such as "I always like/love/prefer classical music, especially opera music by Rossini or Verdi and performed by Angela Gheorghiu or Juan Diego Flórez; I sometimes like progressive rock and post-rock; I like only metal albums released before 2000; I always dislike/hate rap and hip-hop; I dislike songs produced by Flood in the last 25 years"), past song purchases on various music stores, playlists – available online via music streaming services: Last.fm and alternative solutions – and/or locally – for instance, by uploading a JSPF/XSPF document. The playlists could be created by the user or shared by her/his virtual "friends" (consider at least one social network). The system will use several music-related knowledge models (e.g., Music Ontology or MusicRecording concept from schema.org) and available public resources: Discogs, MusicBrainz, Musicmoz Music Styles.

  14. WADO (WADe Ontology)

    By using the GitHub's GraphQL API to have access to public software repositories, create a conceptual model expressed in OWL – possibly, by reusing (parts of) existing ontologies – able to express the most significant aspects regarding the Web application development: programming paradigms and languages, architectures, methodologies, plus different types of software tools specific to a certain development ecosystem (i.e. JavaScript, PHP, Python,...): runtime platforms, operating systems, drivers, utilities, virtual machines, compilers, interpreters, application servers, frameworks, SDKs, libraries, components, IDEs, and so on. Important concepts, relations, restrictions, individuals should be considered as examples for a real software product (e.g., a cloud-based development platform) like REPLit – for others, explore Real Life Architectures. A testbed application will be provided in order to manage the accumulated knowledge. Consult a list of awesome lists.