[OASIS Issue Tracker] Commented: (SOAEERP-31) PR07-T10Non-normative text is not identified

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

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

Szu Chang  commented on SOAEERP-31:
-----------------------------------

Same as issue SOA-EERP-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-T10 Non-normative text is not identified
> ---------------------------------------------
>
>                 Key: SOAEERP-31
>                 URL: http://tools.oasis-open.org/issues/browse/SOAEERP-31
>             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 
>
> 11. Again in Rating, line 624 (and similar locations in the other specs): OASIS specifies that the normative schema is that in the identified separate file. This should be noted in all of the schema in the specifications. In (e.g.) bQoS, Appendix B "Non-Normative Text" says "none" but is followed by non-normative Appendix C which is not identified as non-normative. 

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