[OASIS Issue Tracker] Issue Comment Edited: (CAMP-152) Normative Tags Challenges, and other issues arising from aligning TAs to WD30+

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

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

Jacques Durand  edited comment on CAMP-152 at 1/8/14 6:56 PM:
--------------------------------------------------------------

(extension to this issue spun off to #158)

      was (Author: jdurand2):
    Four new questions/challenges:

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

  
> Normative Tags Challenges, and other issues arising from aligning TAs to WD30+
> ------------------------------------------------------------------------------
>
>                 Key: CAMP-152
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-152
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Improvement
>          Components: Spec
>            Reporter: Jacques Durand 
>
> Normtag Issues on WD30:
> issue#1: RMR-07: described in Section 3.3, "Plan Schema", 
> Issue: no such 3.3 section
> issue#2:. Section 4.1:
> "Section 4.1.1, "Plan Overview")."
> Issue: no such 4.1.1 section, but 4.2
> issue#3:.Section 4.3.5:
> Norm tag missing? Formerly PDP-25 missing? (MUST be either "href" or "data")
> issue#4:. A PDP MAY contain a certificate, named camp.cert, at the root of the archive. [PDP-08] This file contains a signed SHA256 digest for the manifest file and the corresponding X.509 certificate
> Missing norm tag?

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