[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 ]

Gilbert Pilz updated CAMP-80:
-----------------------------

    Proposal: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/51336/camp-spec-v1.1-wd29-issue80.doc  (was: 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))

Add concrete proposal that closes the holes in the specification with normative statements. The conformance target of these normative statements is the Provider in the sense that "the Provider must do at least the following ...". This leaves the door open for Providers to implement extension mechanisms and the Consumer to take advantage of these extensions without violating any normative statements.

So for both deploying an application and registering a Plan:

Using a PDP by reference - Content-Type is "application/json", request body is bespoke JSON object defined in 6.11.1/6.12.1

Using a Plan by reference - Content-Type is "application/json", request body is bespoke JSON object defined in 6.11.1/6.12.1

Using a PDP by value - Content-Type is either "application/x-zip", "application/x-tar", "application/x-tgz"; request body is correspondingly a ZIP, TAR, or TGZ PDP archive

Using a Plan by value - Content-Type is "application/x-yaml"; request body is a YAML file (as defined by Section 4).

Deploying an application or registering a Plan using a Plan file encoded as JSON (an extension in itself as we define Plan files to be "well-formed YAML") is left as an extension.

> 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