[OASIS Issue Tracker] Commented: (CAMP-80) Section 6.11 "Registering an Application" is unclear about what Content-Type header must be for various scenarios

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

    [ http://tools.oasis-open.org/issues/browse/CAMP-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34421#action_34421 ] 

Alex Heneveld commented on CAMP-80:
-----------------------------------

i agree with your rule 3 -- if it's a PDP binary archive then do the normal thing.  that won't surprise anyone.

it is rule 1,2, and 4 where i'm suggesting it must be a valid DP, but we introduce a simple way in the DP schema to reference another DP or PDP.  so use cases 1 and 2 (passing by reference) are handled by supplying a tiny, but valid, DP which is parsed as per normal DP's and the references loaded.

advantages here are that:

* JSON and YAML can be treated the same way, it must be a DP (don't surprise the user)
* any DP or PDP can refer to others, allowing composition and re-use of deployment plans neatly


> Section 6.11 "Registering an Application" is unclear about what Content-Type header must be for various scenarios
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMP-80
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-80
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>            Reporter: Gilbert Pilz
>            Priority: Critical
>
> While implementing the code for Section 6.11 I noticed that there are a couple of scenarios in which the spec is unclear about the expected Content-Type of the POST request. The more minor of these is the case in which the Consumer POSTs a JSON object that contains the URI of the PDP or DP. Since the request is JSON, an implementer can infer that the Content-Type should be "application/json", but the spec should really be clear about this just to avoid any misunderstandings.
> The second, and more serious, case is when the Consumer directly POSTs the contents of a DP in the request body.
> This is important because, as defined in the spec, Content-Type is the only information an implementation has to figure out which of the four different methods a Consumer is attempting to use when they POST to the Platform resource.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira