[OASIS Issue Tracker] Created: (SOAEERP-31) PR07-T10 Non-normativetext is not identified

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

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
            Reporter: Paul Yang 
            Assignee: William Cox


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