Hi Michel and Fabian,

2014-10-08 15:33 GMT+02:00 Bohms, H.M. (Michel) <michel.bo...@tno.nl>:

>   Great that it works that way!
>
> Thx Fabian for reasking this issue, would be good to have extra
> examples/documentation on this indeed.
>

There is some documentation on the pre-Apache project page at
https://code.google.com/p/lmf/ . We intended to move it already for a long
time but never found the chance. Time to fix it ;-)




>
>
>
> You ask me "Would a feature that allows automatically rewriting certain
> URI prefixes be useful to you? " the answer is that I don't have such a
> need so far. But from my experience with pubby, I guess it could bring
> some flexibility on the RDF data (not forcing published resources to be
> defined with http://<server>/<marmotta>/resource/ prefix). But are there
> real life needs about that ? I mean, in a linked data environment URL needs
> to be fixed and long lasting, so where does URL rewriting really come into
> play in such a context ?
>
>
>

There is a certain scenario where users first create data in some external
tool and then only then decide they want to publish it as Linked Data under
a certain URL. We've had that problem from time to time and always did a
manual fix. But it could of course be done automatically as well. If you
don't have such a need, I am happy with it ;-)

BTW, the /resource prefix is there mostly for technical reasons (i.e. being
able to distinguish between what is a resource and what is some other page
in Marmotta). You can avoid the /resource prefix if you put an Apache HTTPD
as proxy and define appropriate rewrite rules to /resource?uri=...




>   And the last question is about LDP: does it mean that LDP is all about
> handling "containers", but don't say anything about Linked Data
> publishing (i.e. dereferencing a resource). Thats the conclusion from
> Michel, and so far it is also mine. But that seems surprising at first
> glance. In other words, LDP would define how to access and handle a bunch
> of resources (refering to the container), but not how to access a single
> resource, is that right ?
>


Indeed, the LDP specification does not say much about dereferencing. It is
in many parts still a bit underspecified (and in others IMHO a bit
overspecified, e.g. enforcing certain vocabularies as system properties).
Sergio and Jakob are more experts here, they can help you on this.

Note that the feature-complete LDP module in Marmotta is separate to the
/resource functionality and is new in the current Marmotta development
snapshot. We are planning a release for the next days, so if you want to
try out these features, maybe it is worthwhile waiting a bit ;-)




Greetings,

Sebastian

Reply via email to