/rdf/ path prefix does not lead anywhere

[jgonggrijp]

Collections, and possibly other RDF entities, currently get IRIs under the /rdf/* path prefix. The Django backend does not recognize those paths (at least not in the case of /rdf/collections/*), so the user is redirected to the index page.

Possible fixes:

Fix	Pro	Con
Rename /rdf/* entities to /api/*	Straightforward	Departs from #156
Move RDF-producing endpoints from /api/* to /rdf/*	Arguably correct	Requires splitting the API router
Change all /api/ routes to /rdf/	Straightforward	Only valid if all API endpoints produce RDF data

[lukavdplas]

I think this concerns collections, records, and projects at this stage.

As I understand, we currently don't have an endpoint (or several) for RDF entities. So even if you adjust the path to avoid a redirect, you would still get a dead end response, because there is no endpoint to which you can actually resolve the URL.

By the way, several of our applications have more than one prefix for backend paths, e.g. /api/* and /auth/*. This works perfectly fine in my experience, but perhaps this is different in the EDPOP setup? Am I missing something that would cause a problem with this?

[jgonggrijp]

I think having multiple backend paths is fine for EDPOP, too.

What do you mean by "we don't have an endpoint for RDF entities"? Isn't /api/collections/* json-ld or something?

[lukavdplas]

It's plain JSON, but it does represent the same resource, so you could direct a collection to that URL. But I meant more that there is no generic endpoint to access RDF data. Nodes that represent, for instance, a field on a record, don't necessarily have a path in the API that is uniquely associated with them.