[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=34368#action_34368 ] 

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

Good spot.

I don't like semantics that "JSON means PDP reference but YAML means DP".  It is a WTF-in-waiting, since if I wrote my DP as JSON (valid as YAML also) then I'd expect it to work whether I post as media type JSON or YAML.

Can we modify the DP language so that it supports referencing other PDP's ?  That would be a very clean solution in my view as we are no longer relying on content-type to determine intention.

> 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
>         Environment: PR1
>            Reporter: Gilbert Pilz
>
> 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