[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CAMP-158) Normative Tag Challenges: on wd33
[ http://tools.oasis-open.org/issues/browse/CAMP-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36338#action_36338 ] Jacques Durand commented on CAMP-158: -------------------------------------- "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 also RMR-07 seems underspecified: - . this section (5.15) talks of a Resource, serializable in JSON. Section 4.3 talks of a YAML artifact. It is unclear how to map the YAML schema is supposed to mal to a corresponding JSON representation. Proposal outline: - some general rules need be stated, e.g. a YAML node maps to an Resource attribute. - do some nodes like "artifacts" and "services" map to Resource, and how? - mapping of some node types such as ArtifactSpecification[] , ServiceSpecification[] need be described, if any. - why not add a JSON pseudo-schema in 5.15, like for any other resource. > 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]