[OASIS Issue Tracker] (OSLCCORE-6) How does POST to an LDPC that supports multiple creationTypes indicate which resource to create?

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/OSLCCORE-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59509#comment-59509 ] 

Martin Pain  commented on OSLCCORE-6:
-------------------------------------

Issue 1:
I see creationType only being returned on a GET, and them having no defined meaning on a POST. The type should be available in the body.

(Aside: although we ought to clarify exactly where in the body - do we define what URI should be given to the resource being created? I presume the empty URI, but I've heard objections to that in the past. I don't really know what our implementation does in OSLC 2 - we just do whatever the Lyo libraries do. If it's the blank URI, then the type to be created is in the body in a triple: <> rdf:type <type-URI>.)

For non-RDF resources, they cold specify it with a Link header with rel="type". (Presuming it would be a URI not a media type - media types can be in Accept-Post and Content-Type headers).

That is, for both RDF and non-RDF cases, I would expect it to be in the POST exactly where it would be in a GET on the created resource after it has been created.

> How does POST to an LDPC that supports multiple creationTypes indicate which resource to create?
> ------------------------------------------------------------------------------------------------
>
>                 Key: OSLCCORE-6
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-6
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Task
>            Reporter: James Amsden
>            Assignee: James Amsden
>
> An OPTIONS request on an LDPC could return multiple Link: headers with rel="http://open-services.net/ns/core#creationType"; indicating the container can support multiple resource types. The Accept-Post header indicates the entity request body format, but does not specify the resource type expressed by that content. RDF resources could specify their type directly in an assertion, but this is not available for LDP-NR (Non-RDF) sources. 
> Section A.1.2 creationType seems to indicate that this could be used on a Link-relation rel value for POST, but this should be explicitly specified and have an example.
> A related issue is that an HTTP OPTIONS request on an LDPC can also return multiple Link: headers with rel="http://www.w3.org/ns/ldp#constrainedBy";. A POST or PUT to create or update a resource can use return this header when the request fails because of violation of the constraint. But there is currently no way to associate multiple creationType and constrainedBy link relations for an LDPC. The constraindBy link may need to include a context IRI (anchor parameter) to identify the resource type that is being constrained.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)