OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

camp-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [camp-comment] 4.2 Deployment Plan Overview - RPM file?


Patrick,

This comment has been captured as Jira issue CAMP-105 and will be processed by the TC. We will inform you when this issue has been resolved.

~ gp


On 9/5/2013 12:03 PM, Patrick Durusau wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greetings!

Under 4.2 Deployment Plan Overview, I find:

*****
Example 1: Minimal DP describing an application consisting of a single
RPM file.
*****

Not recognizing "RPM file" I searched the rest of the specification.

I may be mistaken but the only uses of RPM that I can find are in 4.2,
4.2.1 and 4.2.2.

It is variously:

*****
Example 1: single RPM file

Following paragraph, first sentence: a single RPM package

4.2.1 Types, first paragraph, next to last sentence: a group of PaaS
providers could agree to use the artifact type “org.rpm:RPM” to
identify RPM packages.

Example 2: how to install the RPM

Following paragraph, second sentence: describe the relationship of the
RPM artifact to some (unspecified) service.

Paragraph following Example 3, first sentence: parameters of the
service on which the RPM is to be installed.

Paragraph following Example 3, last sentence: ndicates that the target
service for the RPM is a Linux instance.
*****

I understand that the RPM isn't changing based on whether it is called
a file, artifact, etc. but introducing an acronym without expansion
and then choosing different ways to refer to it, can only lead to
misunderstanding.

If RPM is just an arbitrary label, then say so. And then don't refer
to it by various other terms.

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/

iQIcBAEBAgAGBQJSKNVtAAoJEAudyeI2QFGoC08QAMX+ba20Rc7qK1R1265iEe11
YS7UAH/t7WAA9H5cGFw0Rh51zuxeDx2FFOl3TGPSQPVXWiI/tIbAVIfpKRRqPFX+
mxMdJIle3OPRGkjS4sqTAvgXExgzFtcjN8aHKoBK1NlpQyIpCqJudG3j0+fYGmlO
4g31smlxbsEIOwuY0DpGVTPLxvblnrwtU1Nv9nWsq+VSJSarfIbOEj+6Its3ZBAF
Gi6uA2E8Uj92e+rQ9DLVsmreGkYHDseTxgIGuPsmayEveixlLTBvU3JlImkulQoB
UjwA3WAk5C1H5v0lvDUuiF4lcokPSNTbKxfefVlkK9y9YuNHFwxnZxOjh36ScN8R
qcJUT81a029MjRQ25EuWfpw15PMm+B/fxP0bDSXpIgPpC2siEkrJGUMXs9m+AJ44
pLJrgq21pXYCPFex/V8a9KPMi3zPZbDVBarnGv6I3DQNaduorpatlSAPwGrziKSv
7AXqlKmtAbvXQD2eRNgx7W0SNt9NW9Jkn/cTjudQE5aJQzSiz8rcqZPqa6jEC3Zg
MZsFsXqUhpHhv9WCgt9JOBVW5n9ccHfJTajl3GsLnSUU7iHbNGvbQ2AhTXI5Uyjh
TvhmGDg7yGF47pIQK3apCXpkC59sXpJ+36pYLq10MXDtCpYpAst8sIiXclBlQrTX
ammA/btQ1Rr+PeIxXGAn
=XXcc
-----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/




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]