[OASIS Issue Tracker] Updated: (CAMP-45) Normative Statement Overhaul

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

     [ http://tools.oasis-open.org/issues/browse/CAMP-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Chapman  updated CAMP-45:
--------------------------------

    Assignee: Anish Karmarkar
    Priority: Critical  (was: Major)

This is assigned to all editors.

> Normative Statement Overhaul
> ----------------------------
>
>                 Key: CAMP-45
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-45
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Improvement
>          Components: Spec
>            Reporter: Adrian Otto
>            Assignee: Anish Karmarkar
>            Priority: Critical
>
> The spec must be edited so that all normative statements conform to a consistent style. Decide on either RFC-2119, or ISO Keywords. Each testable normative statement should be labeled with a source identifier in the form S-N where N is a non-zeropad increasing integer. Each test assertion should reference these labels. Each test assertion has a label in the form TA-N.

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