specific ideas

  • Fix the items mentioned in issues.
  • Add claim-support to the Wikidata-data fetching (and support for claim-data in the field-definitions).
  • Find and integrate a more lightweight MIDI-webcomponent (html-midi-player is more than 0.5MB by itself!)
  • Implement bookmark imported & exporting.
  • Support and document setting up Nginx as a webserver alternative for Apache2.
  • Add optional geolocation-support, so we could route a user from the current location to the location of a topic, using the OSMR routing app.

general ideas

  • Research educational-support enhancements:
    • Collaborative & social learning features (eg. p2p audio-chat and text-chat rooms for each topic)
    • User-created and auto-generated presentations around a topic
    • Auto-generated topic quizzes
    • Auto-generated, spaced-repetition-based facts learning (for a certain topic / set of topics / topic-domain)
    • Note-taking integration (eg.: Bangle, …)
    • Better ways to indicate personal and professional interests (similar to the persona-tags setting)
  • Allow 3rd-party SPARQL-based endpoints to be added as extra “concept stores (besides Wikipedia & Wikidata).
  • Offline(-first?) support with content-caching (especially useful when traveling and/or without reliable internet-connectivity)
  • Research creating some kind of a simple web-application interface standard for input/output/event-handling:
    • URL parameter IO (iso2 language, search-string, ID, …)
    • event handling (other view triggers, key-bindings, fullscreening, …)
  • Look into integrating Solid for user-authentication (WebID, DID) and user-data-storage (LoD pod) workflows. (How would offline work?)
    • Some related thoughts on this topic:
      • Also allow for anonymous usage (if the user wants this). So a form of progressive enhancement for web application authentication.
      • How would offline web application access still work in these environments (this would require some form of client-side caching).
      • Suppose I would like to give a certain group of users some special 'rewards' (eg. access to a certain part of the website / web application), how could that be structured? Preferably there would be some standard web API to check against.
      • Could we mix Solid authentication with OpenID-style authentication (to make it even easier for the user that wants to login)?