Missing base and `vartrans` prefix declaration in RDF output of https://en-word.net/

[jmkeil]

Hi. The RDF output of https://en-word.net/ is missing a declaration of

1. the prefix vartrans, and
2. the base.

For example, in https://en-word.net/ttl/lemma/case the following declarations are missing:

@prefix vartrans: <http://www.w3.org/ns/lemon/vartrans#> .
@base <https://en-word.net/lemma/case> .

Due to problem 1, the RDF files can not be parsed.

Due to problem 2, the identifiers of all contained resources differ based on the location it is loaded from: For example, if loaded from its original location https://en-word.net/ttl/lemma/case, the relative identifier <#case-n> expands to <https://en-word.net/ttl/lemma/case#case-n> (note the contained ttl/), if downloaded beforehand, it might expand to <file:/C:/Users/jmkeil/Downloads/case#case-n>. Both differs from the (intended) identifier in the dump: <https://en-word.net/lemma/case#case-n> (without ttl/).

[jmkeil]

Thank you for addressing the issue. Unfortunately, the fix only resolves the missing @prefix vartrans: problem, but keeps unresolved the missing @base problem.

[jmccrae]

Good point. I think the solution is not to add an @base declaration but to fix the URLs for lemmas. The problem being that lemmas then have to be derefenceable as well. It makes it all a bit of a challenge and as I have nearly completed a redevelopment of this interface, I will not fix it here

[jmkeil]

Isn't https://en-word.net/lemma/... (e.g. https://en-word.net/lemma/case#case-n) already differentiable? And for direct access to RDF, content negotiation with a simple URL rewrite from https://en-word.net/lemma/ to https://en-word.net/ttl/lemma/ if text/turtle or application/turtle has highest precedence in the Accept header should be sufficient.