-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Spec
-
Labels:None
-
Proposal:
-
Resolution:
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]"