[OASIS Issue Tracker] Updated: (CAMP-92) Section 2 Concepts and Types

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

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

Adrian Otto updated CAMP-92:
----------------------------

    Proposal: 
1) Make the first paragraph of section 2 into a sub-section.
2) Change "this document specifies" to "this specification defines".
3) Delete the word "typically" from "is typically the interface".

The remainder of the concerns are obviated by the resolution of CAMP-99.

> Section 2 Concepts and Types
> ----------------------------
>
>                 Key: CAMP-92
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-92
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>          Components: Public Review
>            Reporter: Gilbert Pilz
>            Assignee: Gilbert Pilz
>
> Patrick Durusau submitted the following PR comment (https://lists.oasis-open.org/archives/camp-comment/201309/msg00019.html):
> Section 2 begins with this paragraph:
> *****
> This document specifies the self-service management API that a
> Platform as a Service offering presents to the consumer of the
> platform. The API is typically the interface into a platform
> implementation layer that
> controls the deployment of applications and their use of the platform.
> *****
> "This document...?" cut-n-paste error?
> "...is typically the interface..." ?
> Two issues:
> 1) Hanging paragraphs - If this part of 2 is non-normative (typically)
> then how do we declare it? If 2 Concepts and Types is declared to be
> non-normative, does that extend to all of 2?
> I mention that because there is requirements language (SHALL and SHALL
> NOT) that occurs in the paragraph prior to 2.2 Deployment.
> Declaring all of 2 non-normative would exclude those statements from
> the normative portion of the text.
> 2) Section 2 reads like non-normative text but as per the existing
> rule on non-normative text, it is now normative.
> I hesitate because normative text doesn't use terms like "typically."
> I can't conform to "typically."

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