Re: [camp-comment] 1.5 PaaS Roles

[GILBERT PILZ <gilbert.pilz@oracle.com>]

Patrick,

This comment has been captured as Jira issue CAMP-88 and will be processed by the TC.

~ gp

On 9/5/2013 7:40 AM, Patrick Durusau wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greetings!

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?

Hope everyone is having a great day!

Patrick

- -- 
Patrick Durusau
patrick@durusau.net
Technical Advisory Board, OASIS (TAB)
Former Chair, V1 - US TAG to JTC 1/SC 34
Convener, JTC 1/SC 34/WG 3 (Topic Maps)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)

Another Word For It (blog): http://tm.durusau.net
Homepage: http://www.durusau.net
Twitter: patrickDurusau
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJSKJfwAAoJEAudyeI2QFGoy18P/A0pWdr9VSJMW/Z9zVPHKPOf
FgWbUp7HKqPebGkEr7zYhtI0/yJRuC7lJsM2RQYn7ydwmqQ1GCOjT3kgJh6fVqUI
sGp+KSaDf5fMVzOfzS+BMS12KwR/5CgtfwbIJCWj7YeG8ukPdFEtkS+jKwSFN2ZZ
PY0vBiVH8wereCnuHLR1Tgv7N5NIJsNstD9HRk/5VhD6dD75MB+rfXAPLGZWNUg3
6L+REEUNNYIntm2RgzKKxR82li4cnW+tRXSsNAEQPi+D4y/zSm3otycyhnrhd8r2
LW1+/+Sx1UnbYMf/uSrWlw75ofMfJDz6gQ1d3RnQwSPalvDyZog6iaj+Ocv7SEFy
hFATdwgZlVYF2OSSxv88IPKhaFSbtzVVUq/OTBW7mWnna8BXoXo8SxFPMO+aN7DV
oRn3ZPzBj9K1pwZY1xrDEiBMRC/MVdkCDYKdH8qc5SZNHzTUKDQ9F7i6JW95aXWm
YlWLBkyI6nkhWJhaLu+YRkx97zDZrjsv8hHZKaux9JwVL1sJGVSqQg7lVTb+x1fo
/k/HRABOUAnx+UjI9qBn6FztwohRMdEvalGGQA6OBJ0SFfz7RA+roj949OUiG+xt
2d/lnk1jlupH6kV6Bz/6xQYtI1Y6EsGZm9Th3osh1GI+zlHNmMQVEGU3fHZd6lE2
Por3EAxlAN+Q220W5wU4
=sqAs
-----END PGP SIGNATURE-----

--
This publicly archived list offers a means to provide input to the
OASIS Cloud Application Management for Platforms (CAMP) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: camp-comment-subscribe@lists.oasis-open.org
Unsubscribe: camp-comment-unsubscribe@lists.oasis-open.org
List help: camp-comment-help@lists.oasis-open.org
List archive: http://lists.oasis-open.org/archives/camp-comment/
Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
Committee: http://www.oasis-open.org/committees/camp
Join OASIS: http://www.oasis-open.org/join/