Hello, Marmotta can show users the triples in a resource like http://example.org/resource123. For this I have configured my http server to rewrite http://example.org/resource123 to http://example.org/marmotta/resource?uri=http://example.org/resource123. I see this URI in turn is 303-redirected to http://example.org/marmotta/meta/text/html?uri= http://example.org/resource123, when the URI is requested by a web browser.
That gives a HTML page where data are formatted as a table with column headings 'property', 'has value', 'context' and 'info'. The URIs in the data are rendered as clickable hyperlinks. Clicking on some of the data URIs goes well, I get new page in the same format with the data describing the URI I clicked, even when the data come from other servers. Obviously in those cases the data have been cached by Marmotta, a nice feature. But other URIs for some reason can not be served from the cache and consequently get a 404 Not Found error when clicked. The problem in such cases is that the URI is accessible, but not as http://example.org/marmotta/resource?uri=<the URI>. And the page generated by the http://example.org/marmotta/meta/text/html page seems to redirect each URI to http://example.org/marmotta/resource?uri=<some URI>. It seems to me that that should only happen if there is data from that URI in Marmotta's LD Cache. But if I look at the generated page, I see all <a href> hyperlinks have an attribute class="ldcache", causing http://example.org/marmotta/resource?uri= to be prefixed to the URI. Shouldn't that class="ldcache" only be assigned to resources that are actually in the LD Cache? What happens now is that resources that are accessible on the web seem not be be accessible because they are not cached in Marmotta. Or perhaps it should be that when a resource can not be found in the LD Cache, the URI should be used to request in on the web? Blacklisting certain prefixes in the LD Cache configuration does not seem to help: even URI's with a blacklisted prefix still get the class="ldcache" attribute. Disabling the LD Cache altogether does not solve the problem, the class="ldcache" attribute is still assigned to all URIs. Can anyone help or explain what I could do to solve the problem? Thanks in advance, Frans
