[OASIS Issue Tracker] Issue Comment Edited: (CAMP-99) 3.2 Creating an Assembly Template from a PDP (Is Secton 3 normative?)

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

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

Martin Chapman  edited comment on CAMP-99 at 10/18/13 9:46 AM:
---------------------------------------------------------------

At oct f2f:

 MOTION: m=Adrian s=Gil to resolve CAMP-99 with a direction to the editors to make changes outlined by Martin's proposal added to CAMP-99 as a comment.
MartinC1: Proposal: 


Adrian Otto (Rackspace) [scribe]: No discussion.
      No objections.
      Motion passed.

      was (Author: martin.chapman):
    At oct f2f:

 MOTION: m=Adrian s=Gil to resolve CAMP-99 with a direction to the editors to make changes outlined by Martin's proposal added to CAMP-99 as a comment.
MartinC1: Proposal: 


Adrian Otto (Rackspace) [scribe]: No discussion.
  
> 3.2 Creating an Assembly Template from a PDP (Is Secton 3 normative?)
> ---------------------------------------------------------------------
>
>                 Key: CAMP-99
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-99
>             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/msg00036.html):
> At the end of the first paragraph under 3.2 Creating an Assembly
> Template from a PDP, I read:
> *****
> The model might then appear as follows:
> *****
> In normative text?
> I understand the need for informal explanation of possible uses but
> those are usually consigned to notes (for brief explanations) and/or
> non-normative appendices for longer explanations.
> It enables implementers to distinguish between the requirements (the
> MUST, SHOULD, MAY, etc.) and the prose that gives them meaning, from
> the non-binding and informal explanations about the creation of
> implementations that follow those requirements.
> Not a good idea to mix the two.

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