You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@marmotta.apache.org by Rob Atkinson <ro...@metalinkage.com.au> on 2016/05/25 14:05:58 UTC
Follow up on documentation issues
I've managed to find my way round the LDP interface through trial and error
to reach some answers.
It seems that the LDP API is sensitive to the host name:
- in my environment I cannott post to localhost and get a result - I have
to use the external IP address. This makes configuration of a re-usable
backend a bigger pain.
I was able to load reasoning rules and successfully run them.
I am now trying to negotiate PUT vs POST for container creation - it is
optional for PUT to create a new container - Marmotta seems to respond with
a 428 status, so i guess its not supported. The problem is I seem to be
getting a 428 also if i try to use PUT to overwrite an existing container.
Maybe I'm misreading the spec here - but is that the correct behaviour?
Rob Atkinson
Re: Follow up on documentation issues
Posted by Sergio Fernández <wi...@apache.org>.
Yes, we do not have PR workflow for SVN like we have for Git...
Anyway, I applied your patches with some fixes (r1746248) and you have it
now the content live at our staging site:
http://marmotta.staging.apache.org/configuration.html
http://marmotta.staging.apache.org/installation.html
Thanks!
On Tue, May 31, 2016 at 12:45 AM, Rob Atkinson <ro...@metalinkage.com.au>
wrote:
> I guess the list didnt allow attachements,,
>
> not sure if there is a better way of dealing with this with svn- i guess
> it would be a matter of checking in to a review branch?
>
> Rob
>
> On Tue, 31 May 2016 at 01:45 Sergio Fernández <wi...@apache.org> wrote:
>
>> Sorry, I guess the attachment got lost...
>>
>> ASF CMS uses SVN, that's why you can't find it in out git.
>>
>> On Mon, May 30, 2016 at 2:50 PM, Rob Atkinson <ro...@metalinkage.com.au>
>> wrote:
>>
>> > Hi Sergio -
>> >
>> > here are edits to both installation and configuration to make sure
>> things
>> > go in the right order - if I have fully understood the behaviour.
>> >
>> > (I couldnt find a git version of these docs to create a pull request -
>> so
>> > just attached them)
>> >
>> > Rob
>> >
>> > On Mon, 30 May 2016 at 17:56 Sergio Fernández <wi...@apache.org>
>> wrote:
>> >
>> >> Exactly, Marmotta automatically self-configures on the first HTTP
>> request.
>> >>
>> >> Please, if you consider that detail not suffiently explain, you can
>> >> provide
>> >> a patch to
>> >>
>> >>
>> http://svn.apache.org/repos/asf/marmotta/site/trunk/content/markdown/configuration.md
>> >> with a clearer explanation.
>> >>
>> >> On Sat, May 28, 2016 at 12:56 AM, Rob Atkinson <rob@metalinkage.com.au
>> >
>> >> wrote:
>> >>
>> >> > So its the first HTTP request sets a config parameter? This probably
>> >> ought
>> >> > to be made clear - it took a long time to unravel this after I
>> installed
>> >> > marmotta from a remote source and tested it before I tried
>> configuring
>> >> it.
>> >> > I have seen environments where the local machine didnt recognise the
>> >> > external name used - and it would be impossible to access from the
>> local
>> >> > machine n that case I think. I should raise an issue - but is this a
>> >> > documentation issue or a behaviour issue?
>> >> >
>> >> > Thanks for the clarifications.
>> >> >
>> >> > Rob
>> >> >
>> >> >
>> >> > On Fri, 27 May 2016 at 17:57 Sergio Fernández <wi...@apache.org>
>> >> wrote:
>> >> >
>> >> > > On Fri, May 27, 2016 at 9:52 AM, Rob Atkinson <
>> rob@metalinkage.com.au
>> >> >
>> >> > > wrote:
>> >> > > >
>> >> > > > I have read that page many times and I still dont really
>> understand
>> >> > > > exactly what you mean by "Note that the host name and port you
>> are
>> >> > using
>> >> > > > for the first access to your installation is *important* since
>> >> decides
>> >> > on
>> >> > > > how Linked Data resources will be handled later"
>> >> > > >
>> >> > > > what constitutes an "access"?- first time you access in a
>> browser,
>> >> > first
>> >> > > > time you edit configs and restart, first time you post something
>> to
>> >> an
>> >> > > > endpoint?
>> >> > > >
>> >> > >
>> >> > > First time Marmotta is reached (browser, api access or whatever)
>> after
>> >> > > installing.
>> >> > >
>> >> > >
>> >> > >
>> >> > > --
>> >> > > Sergio Fernández
>> >> > > Partner Technology Manager
>> >> > > Redlink GmbH
>> >> > > m: +43 6602747925
>> >> > > e: sergio.fernandez@redlink.co
>> >> > > w: http://redlink.co
>> >> > >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Sergio Fernández
>> >> Partner Technology Manager
>> >> Redlink GmbH
>> >> m: +43 6602747925
>> >> e: sergio.fernandez@redlink.co
>> >> w: http://redlink.co
>> >>
>> >
>>
>>
>> --
>> Sergio Fernández
>> Partner Technology Manager
>> Redlink GmbH
>> m: +43 6602747925
>> e: sergio.fernandez@redlink.co
>> w: http://redlink.co
>>
>
--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernandez@redlink.co
w: http://redlink.co
Re: Follow up on documentation issues
Posted by Sergio Fernández <wi...@apache.org>.
Sorry, I guess the attachment got lost...
ASF CMS uses SVN, that's why you can't find it in out git.
On Mon, May 30, 2016 at 2:50 PM, Rob Atkinson <ro...@metalinkage.com.au>
wrote:
> Hi Sergio -
>
> here are edits to both installation and configuration to make sure things
> go in the right order - if I have fully understood the behaviour.
>
> (I couldnt find a git version of these docs to create a pull request - so
> just attached them)
>
> Rob
>
> On Mon, 30 May 2016 at 17:56 Sergio Fernández <wi...@apache.org> wrote:
>
>> Exactly, Marmotta automatically self-configures on the first HTTP request.
>>
>> Please, if you consider that detail not suffiently explain, you can
>> provide
>> a patch to
>>
>> http://svn.apache.org/repos/asf/marmotta/site/trunk/content/markdown/configuration.md
>> with a clearer explanation.
>>
>> On Sat, May 28, 2016 at 12:56 AM, Rob Atkinson <ro...@metalinkage.com.au>
>> wrote:
>>
>> > So its the first HTTP request sets a config parameter? This probably
>> ought
>> > to be made clear - it took a long time to unravel this after I installed
>> > marmotta from a remote source and tested it before I tried configuring
>> it.
>> > I have seen environments where the local machine didnt recognise the
>> > external name used - and it would be impossible to access from the local
>> > machine n that case I think. I should raise an issue - but is this a
>> > documentation issue or a behaviour issue?
>> >
>> > Thanks for the clarifications.
>> >
>> > Rob
>> >
>> >
>> > On Fri, 27 May 2016 at 17:57 Sergio Fernández <wi...@apache.org>
>> wrote:
>> >
>> > > On Fri, May 27, 2016 at 9:52 AM, Rob Atkinson <rob@metalinkage.com.au
>> >
>> > > wrote:
>> > > >
>> > > > I have read that page many times and I still dont really understand
>> > > > exactly what you mean by "Note that the host name and port you are
>> > using
>> > > > for the first access to your installation is *important* since
>> decides
>> > on
>> > > > how Linked Data resources will be handled later"
>> > > >
>> > > > what constitutes an "access"?- first time you access in a browser,
>> > first
>> > > > time you edit configs and restart, first time you post something to
>> an
>> > > > endpoint?
>> > > >
>> > >
>> > > First time Marmotta is reached (browser, api access or whatever) after
>> > > installing.
>> > >
>> > >
>> > >
>> > > --
>> > > Sergio Fernández
>> > > Partner Technology Manager
>> > > Redlink GmbH
>> > > m: +43 6602747925
>> > > e: sergio.fernandez@redlink.co
>> > > w: http://redlink.co
>> > >
>> >
>>
>>
>>
>> --
>> Sergio Fernández
>> Partner Technology Manager
>> Redlink GmbH
>> m: +43 6602747925
>> e: sergio.fernandez@redlink.co
>> w: http://redlink.co
>>
>
--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernandez@redlink.co
w: http://redlink.co
Re: Follow up on documentation issues
Posted by Rob Atkinson <ro...@metalinkage.com.au>.
Hi Sergio -
here are edits to both installation and configuration to make sure things
go in the right order - if I have fully understood the behaviour.
(I couldnt find a git version of these docs to create a pull request - so
just attached them)
Rob
On Mon, 30 May 2016 at 17:56 Sergio Fernández <wi...@apache.org> wrote:
> Exactly, Marmotta automatically self-configures on the first HTTP request.
>
> Please, if you consider that detail not suffiently explain, you can provide
> a patch to
>
> http://svn.apache.org/repos/asf/marmotta/site/trunk/content/markdown/configuration.md
> with a clearer explanation.
>
> On Sat, May 28, 2016 at 12:56 AM, Rob Atkinson <ro...@metalinkage.com.au>
> wrote:
>
> > So its the first HTTP request sets a config parameter? This probably
> ought
> > to be made clear - it took a long time to unravel this after I installed
> > marmotta from a remote source and tested it before I tried configuring
> it.
> > I have seen environments where the local machine didnt recognise the
> > external name used - and it would be impossible to access from the local
> > machine n that case I think. I should raise an issue - but is this a
> > documentation issue or a behaviour issue?
> >
> > Thanks for the clarifications.
> >
> > Rob
> >
> >
> > On Fri, 27 May 2016 at 17:57 Sergio Fernández <wi...@apache.org> wrote:
> >
> > > On Fri, May 27, 2016 at 9:52 AM, Rob Atkinson <ro...@metalinkage.com.au>
> > > wrote:
> > > >
> > > > I have read that page many times and I still dont really understand
> > > > exactly what you mean by "Note that the host name and port you are
> > using
> > > > for the first access to your installation is *important* since
> decides
> > on
> > > > how Linked Data resources will be handled later"
> > > >
> > > > what constitutes an "access"?- first time you access in a browser,
> > first
> > > > time you edit configs and restart, first time you post something to
> an
> > > > endpoint?
> > > >
> > >
> > > First time Marmotta is reached (browser, api access or whatever) after
> > > installing.
> > >
> > >
> > >
> > > --
> > > Sergio Fernández
> > > Partner Technology Manager
> > > Redlink GmbH
> > > m: +43 6602747925
> > > e: sergio.fernandez@redlink.co
> > > w: http://redlink.co
> > >
> >
>
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernandez@redlink.co
> w: http://redlink.co
>
Re: Follow up on documentation issues
Posted by Sergio Fernández <wi...@apache.org>.
Exactly, Marmotta automatically self-configures on the first HTTP request.
Please, if you consider that detail not suffiently explain, you can provide
a patch to
http://svn.apache.org/repos/asf/marmotta/site/trunk/content/markdown/configuration.md
with a clearer explanation.
On Sat, May 28, 2016 at 12:56 AM, Rob Atkinson <ro...@metalinkage.com.au>
wrote:
> So its the first HTTP request sets a config parameter? This probably ought
> to be made clear - it took a long time to unravel this after I installed
> marmotta from a remote source and tested it before I tried configuring it.
> I have seen environments where the local machine didnt recognise the
> external name used - and it would be impossible to access from the local
> machine n that case I think. I should raise an issue - but is this a
> documentation issue or a behaviour issue?
>
> Thanks for the clarifications.
>
> Rob
>
>
> On Fri, 27 May 2016 at 17:57 Sergio Fernández <wi...@apache.org> wrote:
>
> > On Fri, May 27, 2016 at 9:52 AM, Rob Atkinson <ro...@metalinkage.com.au>
> > wrote:
> > >
> > > I have read that page many times and I still dont really understand
> > > exactly what you mean by "Note that the host name and port you are
> using
> > > for the first access to your installation is *important* since decides
> on
> > > how Linked Data resources will be handled later"
> > >
> > > what constitutes an "access"?- first time you access in a browser,
> first
> > > time you edit configs and restart, first time you post something to an
> > > endpoint?
> > >
> >
> > First time Marmotta is reached (browser, api access or whatever) after
> > installing.
> >
> >
> >
> > --
> > Sergio Fernández
> > Partner Technology Manager
> > Redlink GmbH
> > m: +43 6602747925
> > e: sergio.fernandez@redlink.co
> > w: http://redlink.co
> >
>
--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernandez@redlink.co
w: http://redlink.co
Re: Follow up on documentation issues
Posted by Rob Atkinson <ro...@metalinkage.com.au>.
So its the first HTTP request sets a config parameter? This probably ought
to be made clear - it took a long time to unravel this after I installed
marmotta from a remote source and tested it before I tried configuring it.
I have seen environments where the local machine didnt recognise the
external name used - and it would be impossible to access from the local
machine n that case I think. I should raise an issue - but is this a
documentation issue or a behaviour issue?
Thanks for the clarifications.
Rob
On Fri, 27 May 2016 at 17:57 Sergio Fernández <wi...@apache.org> wrote:
> On Fri, May 27, 2016 at 9:52 AM, Rob Atkinson <ro...@metalinkage.com.au>
> wrote:
> >
> > I have read that page many times and I still dont really understand
> > exactly what you mean by "Note that the host name and port you are using
> > for the first access to your installation is *important* since decides on
> > how Linked Data resources will be handled later"
> >
> > what constitutes an "access"?- first time you access in a browser, first
> > time you edit configs and restart, first time you post something to an
> > endpoint?
> >
>
> First time Marmotta is reached (browser, api access or whatever) after
> installing.
>
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernandez@redlink.co
> w: http://redlink.co
>
Re: Follow up on documentation issues
Posted by Sergio Fernández <wi...@apache.org>.
On Fri, May 27, 2016 at 9:52 AM, Rob Atkinson <ro...@metalinkage.com.au>
wrote:
>
> I have read that page many times and I still dont really understand
> exactly what you mean by "Note that the host name and port you are using
> for the first access to your installation is *important* since decides on
> how Linked Data resources will be handled later"
>
> what constitutes an "access"?- first time you access in a browser, first
> time you edit configs and restart, first time you post something to an
> endpoint?
>
First time Marmotta is reached (browser, api access or whatever) after
installing.
--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernandez@redlink.co
w: http://redlink.co
Re: Follow up on documentation issues
Posted by Rob Atkinson <ro...@metalinkage.com.au>.
Thanks Sergio.
I have read that page many times and I still dont really understand
exactly what you mean by "Note that the host name and port you are using
for the first access to your installation is *important* since decides on
how Linked Data resources will be handled later"
what constitutes an "access"?- first time you access in a browser, first
time you edit configs and restart, first time you post something to an
endpoint?
cheers
Rob
On Fri, 27 May 2016 at 17:12 Sergio Fernández <wi...@apache.org> wrote:
> Rob,
>
> On Wed, May 25, 2016 at 4:05 PM, Rob Atkinson <ro...@metalinkage.com.au>
> wrote:
>
> > I've managed to find my way round the LDP interface through trial and
> error
> > to reach some answers.
> >
> > It seems that the LDP API is sensitive to the host name:
> > - in my environment I cannott post to localhost and get a result - I
> have
> > to use the external IP address. This makes configuration of a re-usable
> > backend a bigger pain.
> >
>
>
>
> Linked Data technologies are sensitive to the names of the resources. The
> host name and port you are using for the first access to your installation
> is important since decides on how Linked Data resources will be handled
> later.
>
> Even if you could reach the software by all the localhost host names
> (localhost, 127.0.0.1 or its public IP), that does not mean all services
> are functional. So you must use the one configured in Marmotta
>
> Marmotta automatically configures the hostname in the first access, but you
> can configure it as you need:
> http://marmotta.apache.org/configuration.html
>
>
> I am now trying to negotiate PUT vs POST for container creation - it is
> > optional for PUT to create a new container - Marmotta seems to respond
> with
> > a 428 status, so i guess its not supported. The problem is I seem to be
> > getting a 428 also if i try to use PUT to overwrite an existing
> container.
> > Maybe I'm misreading the spec here - but is that the correct behaviour?
>
>
> https://www.w3.org/TR/ldp/#h-ldpr-put-precond
>
> Cheers,
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernandez@redlink.co
> w: http://redlink.co
>
Re: Follow up on documentation issues
Posted by Sergio Fernández <wi...@apache.org>.
Rob,
On Wed, May 25, 2016 at 4:05 PM, Rob Atkinson <ro...@metalinkage.com.au>
wrote:
> I've managed to find my way round the LDP interface through trial and error
> to reach some answers.
>
> It seems that the LDP API is sensitive to the host name:
> - in my environment I cannott post to localhost and get a result - I have
> to use the external IP address. This makes configuration of a re-usable
> backend a bigger pain.
>
Linked Data technologies are sensitive to the names of the resources. The
host name and port you are using for the first access to your installation
is important since decides on how Linked Data resources will be handled
later.
Even if you could reach the software by all the localhost host names
(localhost, 127.0.0.1 or its public IP), that does not mean all services
are functional. So you must use the one configured in Marmotta
Marmotta automatically configures the hostname in the first access, but you
can configure it as you need: http://marmotta.apache.org/configuration.html
I am now trying to negotiate PUT vs POST for container creation - it is
> optional for PUT to create a new container - Marmotta seems to respond with
> a 428 status, so i guess its not supported. The problem is I seem to be
> getting a 428 also if i try to use PUT to overwrite an existing container.
> Maybe I'm misreading the spec here - but is that the correct behaviour?
https://www.w3.org/TR/ldp/#h-ldpr-put-precond
Cheers,
--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernandez@redlink.co
w: http://redlink.co