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

 


Help: OASIS Mailing Lists Help | MarkMail Help

camp message

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


Subject: [OASIS Issue Tracker] Created: (CAMP-91) 1.6 Terminology - normative text


1.6 Terminology - normative text
--------------------------------

                 Key: CAMP-91
                 URL: http://tools.oasis-open.org/issues/browse/CAMP-91
             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/msg00018.html):

In 1.6 Terminology, the following text is embedded in the second
paragraph of that section:

*****
All text except examples, unless otherwise labeled, is normative. All
examples are non-normative.
*****

Rather than embedding this text in the terminology section, I would
suggest a separate section on normative text.

For example:

Normative Text

All the text of this specification is normative with the following
exceptions:

1) Sections or sub-sections that are labeled: (Non-Normative).

2) All examples are non-normative without labeling.

?

I have questions about other items or sections being non-normative or
not but I will raise those as appropriate.

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

        


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