Here are the features we're planning for LinkedDataHub, in a decreasing priority order. Feedback is welcome.

• OpenID Connect-based login (with GitHub/Twitter/Google etc.)

  • API-level support withrefresh tokens

• Decentralized use cases

  • Saving a local copy of a remote document
  • Editing documents in a remote LDH app

• Inline RDF editing

• Multi-language UI

• Full-text search

  Instead of the SPARQLregex() based implementation, search and autocomplete widgets should be able to use triplestore's full-text search API, if suchis provided

• Support forSHACL constraints in addition toSPIN

  This will require adding a new validating request filter

• Better SEO

  JSON-LD withschema.org metadata embedded in HTML (requires some kind of mapping if data is not using schema.org)

• Ontology import that generates constructors for classes

  Currently exists in experimental form

• New UI for constructors: template with fields (as in Podio, PowerApps etc) instead of SPARQL query string

  It could possibly be reused for CSV mapping queries

• Date/time picker widget

• New HTML+RDFa editor that allows:

  • Semantic annotations (e.g. selecting text, choosing property from typeahead and entering a value to create a triple)
  • Embedding objects, similar to notebooks
    • Resources
    • Files
    • Charts
    • SPARQL queries/results
    • HTML content

• Improved map layout

  • Support for WKT literals (including polygons)

• Improved graph layout

  • Selecting/moving nodes
  • Editing RDF in graph mode

• Graceful degradation

  Make sure the UI is still functional with JavaScript disabled

• Document versioning (possibly support for theMemento protocol)

  • See a list of revisions
  • See changes between revisions

• Comments on documents? Social media style

• New design theme (for example usingMaterial design)

• Mobile client app

• Refactor the stylesheets usingXSLT 3.0 packages