-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major
-
None
-
Affects Version/s: None
-
Component/s: Public Review
-
None
-
Environment:
Remove Application End-User from section 1.5.
Change "identifies" to "defines".
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?