[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Created: (CAMP-88) 1.5 PaaS Roles
1.5 PaaS Roles -------------- Key: CAMP-88 URL: http://tools.oasis-open.org/issues/browse/CAMP-88 Project: OASIS Cloud Application Management for Platforms (CAMP) TC Issue Type: Bug Components: Public Review Reporter: Gilbert Pilz Patrick Durusau makes the following PR comment (https://lists.oasis-open.org/archives/camp-comment/201309/msg00015.html): The first two sentences in 1.5 Paas Roles read: ***** There are many roles that can be defined for a PaaS environment. For the purposes of this specification we identify the following roles: ***** Assuming 1.5 to be normative text, wouldn't: ***** There are many roles that can be defined for a PaaS environment. This specification *defines* the following roles: ***** But in checking the rest of the draft, it doesn't define Application End-User. So is the "define" in the first sentence incorrect? That is, should the draft *define* roles for a PaaS environment? Or are PaaS roles relevant to the purpose of the specification? That is anyone could implement the specification without reference to or definition of any PaaS roles? Certainly people in PaaS roles would use the implementation but are they required for the specification? At least in normative text? -- 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]