Hello Sergio,

In my few experiments so far, the requested URI is described in the
response. For example, if I request
http://www.example.com/my_dataset/resource123, the response contains the
triples in which http://www.example.com/my_dataset/resource123 is the
subject.

I have tried the Linked Data validator at  http://vafu.redlink.io/. The
only tests that fail are those in which the request does not specify a
content type.

In detail, a request (with a specified content type) for
http://www.example.com/my_dataset/resource123 seems to be handled as
follows (http://www.example.com is the Marmotta main site in this example):

get http://www.example.com/my_dataset/resource123
> 302 Found:
http://www.example.com/marmotta/resource?uri=http://www.example.com/my_dataset/resource123
get
http://www.example.com/marmotta/resource?uri=http://www.example.com/my_dataset/resource123
>303 See other:
http://www.example.com/marmotta/resource?uri=http%3A%2F%2Fwww.example.com%2Fmy_dataset%2Fresource123
get
http://www.example.com/marmotta/resource?uri=http%3A%2F%2Fwww.example.com%2Fmy_dataset%2Fresource123
>200 OK

So a first pass sticks the "http://www.example.com/marmotta/resource?uri=";
in front of the URI and a second pass encodes the URI.

I wonder if I can get rid of the first 302... But is there anything that
goes against Linked Data principles this way?

Regards,
Frans





2016-05-02 8:47 GMT+02:00 Sergio Fernández <wik...@apache.org>:

> Frans, although I understand your practical need of getting those request
> gettingin, you should be aware it is invalid according the Linked Data
> principles. If you try a Linked Data validator, such as
> http://vafu.redlink.io/ , you would notices that the original resource
> does not come described in the response.
>
> Marmotta provides other means of tweaking that, see
> http://marmotta.apache.org/configuration.html
>
> On Fri, Apr 29, 2016 at 4:02 PM, Frans Knibbe <frans.kni...@geodan.nl>
> wrote:
>
>> Hello,
>>
>> The following addition to my Apache HTTPD configuration seems to work
>> well:
>>
>> RewriteEngine on
>> <Location "/mydataset">
>>   RewriteRule ^
>> http://www.example.org/marmotta/resource?uri=http://%{HTTP_HOST}%{REQUEST_URI}
>> </Location>
>>
>> Regards,
>> Frans
>>
>>
>>
>> 2016-04-29 13:02 GMT+02:00 Frans Knibbe <frans.kni...@geodan.nl>:
>>
>>> Thank you Sergio, that certainly helps.
>>>
>>> I have just tested this approach, and after I found out my {BASE} value (
>>> http://www.example.com/marmotta) I could successfully GET the resources
>>> in the format specified in the Accept header.
>>>
>>> So I think that if I want the resource URIs to be dereferencable
>>> directly I have to configure some HTTP query rewriting. I will give that a
>>> try.
>>>
>>> Greetings,
>>> Frans
>>>
>>>
>>>
>>> 2016-04-26 17:40 GMT+02:00 Sergio Fernández <wik...@apache.org>:
>>>
>>>> Hi Frans,
>>>>
>>>> On Tue, Apr 26, 2016 at 4:14 PM, Frans Knibbe <frans.kni...@geodan.nl>
>>>> wrote:
>>>>>
>>>>> What doesn't work (yet) is dereferencing the URIs in my dataset. For
>>>>> example, http://www.example.com/mydataset or
>>>>> http://www.example.com/mydataset/myResource give HTTP 404 errors
>>>>> (produced by Tomcat).
>>>>>
>>>>> Is there a way to enable or configure URI dereferencing in Marmotta?
>>>>>
>>>>
>>>> Whenever either a context or a resource is not named (located) under
>>>> the default namespace, http://www.example.com/context/... and
>>>> http://www.example.com/resource/... respectively, Marmotta provides an
>>>> alternative way to dereference them:
>>>>
>>>> * /context?graph=<URI>
>>>> * /resource?uri=<URI>
>>>>
>>>> In your case:
>>>>
>>>> *
>>>> http://www.example.com/context?graph=http%3A%2F%2Fwww.example.com%2Fmydataset
>>>>
>>>> *
>>>> http://www.example.com/resource?uri=http%3A%2F%2Fwww.example.com%2Fmydataset%2FmyResource
>>>>
>>>> If you are interested about further background, that's the relevant
>>>> documentation:
>>>>
>>>> * Graph Identification at SPARQL 1.1 Graph Store
>>>> HTTP Protocol:
>>>> https://www.w3.org/TR/sparql11-http-rdf-update/#graph-identification
>>>>
>>>> * https://bitbucket.org/srfgkmt/lmf/wiki/Principles-Linked-Media
>>>>
>>>> Hope that helps.
>>>>
>>>> Cheers,
>>>>
>>>> --
>>>> Sergio Fernández
>>>> Partner Technology Manager
>>>> Redlink GmbH
>>>> m: +43 6602747925
>>>> e: sergio.fernan...@redlink.co
>>>> w: http://redlink.co
>>>>
>>>
>>>
>>
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernan...@redlink.co
> w: http://redlink.co
>

Reply via email to