Patrick Durusau submitted the following PR comment (https://lists.oasis-open.org/archives/camp-comment/201309/msg00050.html):

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.