[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=59520#comment-59520 ] 

James Amsden commented on OSLCCORE-6:
-------------------------------------

Issue 1: Agreed. There is no need to identify the type to be created using a creationType relationship. When POSTing to an LDPC, the LDPC will determine if an RDF resource in the entity request body can be a member of the container or not based on the body content. For non-RDF resources, the Content-Type header should be sufficient.

Issue 2: The Resource Shapes 2.0 specification indicates ResourceShape has an oslc:describes property that describes the Resource(s) the shape constrains. So there is no need to redundantly specify this in the Link header. 

I added a small amount of clarification in the Discovery specification. Closing this issue as resolved. 

> 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)