[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (SOAEERP-31) PR07-T10Non-normative text is not identified
[ http://tools.oasis-open.org/issues/browse/SOAEERP-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19319#action_19319 ] Paul Yang commented on SOAEERP-31: ----------------------------------- Szu's response: >> Change the order of Appendix B and C on bQoS >> see Line 537 on page 22 and Line 992 on page 28 http://www.oasis-open.org/apps/org/workgroup/soa-eerp/download.php/37739/SOA-EERP-Rating-Spec-cd03-diff-wd08.doc - not sure what is changed here, need clarification > 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 > > 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]