[OASIS Issue Tracker] Commented: (CAMP-105) 4.2 Deployment Plan Overview - RPM file?

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/CAMP-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35866#action_35866 ] 

Anish Karmarkar commented on CAMP-105:
--------------------------------------

Proposal: parenthetically add an inlined URL reference to rpm.org where RPM is mentioned for the first time in the document.

> 4.2 Deployment Plan Overview - RPM file?
> ----------------------------------------
>
>                 Key: CAMP-105
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-105
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>          Components: Public Review
>            Reporter: Gilbert Pilz
>
> 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.

-- 
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