[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Issue Comment Edited: (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=20124#action_20124 ] Szu Chang edited comment on SOAEERP-31 at 8/2/10 3:05 AM: ----------------------------------------------------------- The proposed changes are in WD09 of bRating spec as they are referenced in the proposal at http://www.oasis-open.org/committees/download.php/38429/SOA-EERP-bRating-Spec-wd09-diff-cd03.pdf was (Author: szuchang): The proposed changes are in WD09 of bSLA spec as they are referenced in the proposal at 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: PR01 Comments > Affects Versions: cd03 > Reporter: Paul Yang > Assignee: Szu Chang > Fix For: cd04 > > > 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]