[OASIS Issue Tracker] Commented: (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=35232#action_35232 ] 

Martin Chapman  commented on CAMP-99:
-------------------------------------

Proposal:

In section 1.6, terminology, add the following text after the 2nd para:

The normative statements that use these keywords have been highlighted as per this sentence, and each such statement has been given a unique tag in the following manner: [EX-00][{note to editor highlight the sentence} For convenience these statements have been tabulated and cross-indexed by their tags and appear in Appendix C, Normative Statements. All examples and notes in this document are informative. Unless marked otherwise text in this specification is normative.

In addition add the following text as the first line of section 2 and section 3.

"This section is informative."

Editors discretion to mark other sections/appendices as informative.


> 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