[OASIS Issue Tracker] Updated: (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:all-tabpanel ]

Martin Chapman  updated CAMP-80:
--------------------------------

    Proposal: 
from scrum session 1:

In 6.11

Change PR-32 to
    "Providers SHALL support the use of the media type "application/x-yaml" for deploying an application using a Plan file by value. [PR-32]"

add after [PR-32]:
     "Providers SHALL support the use of the media type "application/json" for deploying an application using a reference to a PDP or a Plan file [NEW-XX]"


In 6.12

     (make all statements about content type analagous to 6.11)

  was:
from scrum session 1:

In 6.11

Change PR-32 to
    "When deploying an application or registering a Plan using a Plan file by value, the Consumer SHALL set the value of the Content-Type header in the HTTP POST request to "application/x-yaml" [PR-32]"

add after [pr-32]:
     When deploying an application or registering a Plan using a reference to a PDP or a Plan file, the Consumer SHALL set the value of the Content-Type header in the HTTP POST request to "application/json" [NEW-XX]

The normative statements in 6.11 about content type needs to be replicated to 6.12



> 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
>          Components: Spec
>            Reporter: Gilbert Pilz
>            Assignee: Anish Karmarkar
>            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