Martynas Jusevičius

URI of created resource

4

In the example [Creating documents (files)](blob/master/api-rest.md#creating-documents-files), what is the URI of the created resource? `Location` response header is missing.

See [OAuth2CodeGrantFlow](https://eclipse-ee4j.github.io/jersey.github.io/apidocs/2.29/jersey/org/glassfish/jersey/client/oauth2/OAuth2CodeGrantFlow.html)

Edit mode uses hidden inputs such as `forClass` to carry metadata. They could be replaced with [`@data-` attributes](https://developer.mozilla.org/en-US/docs/Learn/HTML/Howto/Use_data_attributes) which already are used in content loading.

When HTML is requested by the client-side stylesheet, it should be enough to render `` instead of the full ``, as only that fragment is used.

SPARQL `ASK` query results not written properly

1

[Boolean results](https://www.w3.org/TR/rdf-sparql-XMLres/#boolean-results) should simply contain true Currently they are returning an empty result set:

Relax bash and openssl requirements in the setup script

2

96a8769e7b7e30c8b6dcb845f349fff95a8740dc introduced checks for minimum versions of Bash (4) and OpenSSL (1.1.1) in the `setup.sh` script. This will probably backfire by the checks themselves failing... MacOS seems to have `libressl`...

We could implement some interactivity in the graph layout: * interactive positioning, i.e. nodes could gradually move into their final positions * highlighting nodes and their links on mouseover event...

Maybe the reasoner could replaced by [GraphRDFS](https://jena.apache.org/documentation/javadoc/arq/org/apache/jena/rdfs/GraphRDFS.html).

Add a configuration option for the `Access-Control-Allow-Origin` response header: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin

Verify JWT token

4

Implement [OpenID Connect](https://openid.net/connect/) as an alternative authentication method to WebID, starting with [support for Google](https://developers.google.com/identity/protocols/oauth2/openid-connect).