Re: PUT to create new resource in container?

Hi Rob,

Your reading aligns with mine.

In Lamprey[0], the default behavior is to create a new, uncontained
resource with the specified interaction model at the PUT target. This makes
it easy to create new "root" containers, or free-floating direct/indirect
containers.

I know that Marmotta takes a different tack where, in your example,
/foo/bar would be contained in /foo. I believe it errors if you try to use
PUT to create, e.g., /foo/not-a-container/bar.

Are there other behaviors in existing implementations? What are the
trade-offs?

[0] https://github.com/ruby-rdf/rdf-ldp/

On Sun, Oct 25, 2015 at 1:07 AM, Robert Sanderson <azaroth42@gmail.com>
wrote:

>
> Am I correct in my reading that if there is a container /foo and I use PUT
> rather than POST to create a resource /foo/bar, then it is undefined in the
> specification whether that new resource is ldp:contained by the container?
>
> Justification:
>
> 5.2.4 does not mention using PUT to create new resources, just specifies
> behavior for updating resources.
> 5.2.3 only talks about POST in terms of adding new ldp:contains triples
> 4.2.4.6 specifically allows creation of resources via PUT
>
> Bug, or intentional loophole?
>
> Rob
>
> --
> Rob Sanderson
> Information Standards Advocate
> Digital Library Systems and Services
> Stanford, CA 94305
>