[OASIS Issue Tracker] Commented: (SOAEERP-28) PR07-T7 Include anon-normative section in each specification

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

    [ http://tools.oasis-open.org/issues/browse/SOAEERP-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19444#action_19444 ] 

Szu Chang  commented on SOAEERP-28:
-----------------------------------

Added "non-normative" to the examples, and Appendix  B. 

 >> BQoS spec: Line 379, 522-523

379 The examples in this section are non-normative. 

522 Note: The separate machine readable schema document, listed on Section 2.2, is normative. The text
523 included here is non-normative. 

http://www.oasis-open.org/committees/download.php/38435/SOA-EERP-bQoS-Specwd09-diff-cd03.pdf

>> Rating spec: Line 460,  645-646

460 The examples in this section are non-normative.

645 Note: The separate machine readable schema document, listed on Section 2.2, is normative. The text
646 included here is non-normative.

http://www.oasis-open.org/committees/download.php/38429/SOA-EERP-bRating-Spec-wd09-diff-cd03.pdf

>> BSLA spec: Line 672, 860-861

672 The examples in this section are non-normative.

860 Note: The separate machine readable schema document, listed on Section 2.2, is normative. The text
861 included here is non-normative.

http://www.oasis-open.org/committees/download.php/38432/SOA-EERP-bSLA-spec-wd09-diff-cd03.pdf
 

> PR07-T7 Include a non-normative section in each specification
> -------------------------------------------------------------
>
>                 Key: SOAEERP-28
>                 URL: http://tools.oasis-open.org/issues/browse/SOAEERP-28
>             Project: OASIS Service-Oriented Architecture End-to-End Resource Planning (SOA-EERP) TC
>          Issue Type: Sub-task
>          Components: PR Comments
>            Reporter: Paul Yang 
>            Assignee: Szu Chang 
>
> 8. A non-normative section should be included in each specification showing additional samples, and demonstrating that empty or nearly empty artifacts do not conform. 

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