[OASIS Issue Tracker] Updated: (CAMP-158) Normative Tag Challenges: on wd33

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

     [ http://tools.oasis-open.org/issues/browse/CAMP-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gilbert Pilz updated CAMP-158:
------------------------------

    Proposal: CONCRETE PROPOSAL: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/52025/camp-spec-v1.1-wd36-158.doc

Linked to concrete proposal that:

1.) Adds JSON pseudo-schema to the description of the "plan resource".

2.) Many editorial tweaks to reinforce the distinction between Plan files and "plan resources"

> Normative Tag Challenges: on wd33
> ---------------------------------
>
>                 Key: CAMP-158
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-158
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>          Components: Spec
>            Reporter: Jacques Durand 
>
> Four new questions/challenges on wd33, that need be resolved for completing TA specification:
> 1. Questionable normative tag (not testable): PR-61
> "To register a Plan by value, a Consumer SHALL send an HTTP POST request to the URL of the Plans resource as described in this section. [PR-61]."
> In other places, we removed such statements that are pseudo-requirements for Consumers, and have the normative behavior be turned into a requirement for the Provider: of the kind: "When receiving a POST request to the URL of the Plans , the Provider SHALL..."
> 2. Questionable normative tag (not testable):
> "To register a Plan by reference, a Consumer SHALL send an HTTP POST request to the URL of the Plans resource as described in this section. [PR-56]"
> 3.
> "The schema of the plan resource returned from a CAMP Provider SHALL conform to the schema for Plans described in Section 3.3, "Plan Schema", with the following additional requirements: [RMR-07]"
> "Plan Schema", is in fact Section 4.3.
> But RMR-07 seems redundant with PLAN-09.
> 4. Unclear how to test separately acceptance of the "application/json" media type.
> - "To support the deployment of applications via a reference to either a PDP or a Plan file, Providers SHALL accept the "application/json" media type. [PR-68]"
> - "To support the registration of Plans via a reference to either a PDP or a Plan file, Providers SHALL accept the "application/json" media type. [PR-69]"
> How different from:
> -"Providers SHALL provide representations of all available resources in JSON. [PR-01]" 

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