[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [soa-eerp] I053: BQos - Conformance Issues 2
New working Draft WD06 uploaded at http://www.oasis-open.org/committees/document.php?document_id=33226 and it added new conformance paragraph on Line # 447-457. This issue can be closed. Original Message: ----------------- From: eerp_sy@changfeng.org.cn eerp_sy@changfeng.org.cn Date: Sun, 28 Jun 2009 00:20:02 -0400 To: wtcox@coxsoftwarearchitects.com, soa-eerp@lists.oasis-open.org Subject: RE: [soa-eerp] I053: BQos - Conformance Issues 2 Propose to add the following text to close this issue: The minimum set of information exchange for bQoS that would allow conforming applications to exchange information and satisfy the conformance should at least to have /bqos:BQoS/bqos:BQoSPrice/bqos:Price/bqos:Amount element, like this: <?xml version="1.0" encoding="UTF-8"?> <BQoS xmlns="http://docs.oasis-open.org/soa-eerp/bqos/200903"> <BQoSPrice> <Price> <Amount currencyID="USD">0.0</Amount> </Price> </BQoSPrice> </BQoS> Interoperability issue has been addressed on issue # I045. Original Message: ----------------- From: eerp_sy@changfeng.org.cn eerp_sy@changfeng.org.cn Date: Sun, 21 Jun 2009 16:29:30 -0400 To: wtcox@coxsoftwarearchitects.com, soa-eerp@lists.oasis-open.org Subject: [soa-eerp] I053: BQos - Conformance Issues 2 Issue # I053 For BQoS Spec only Related issues: I045, I054 and I055 Original Message: ----------------- From: William Cox wtcox@CoxSoftwareArchitects.com Date: Sat, 20 Jun 2009 23:10:20 -0400 To: soa-eerp@lists.oasis-open.org Subject: [soa-eerp] NEW Issue: Conformance Issues 2 PLEASE DO NOT REPLY TO THIS EMAIL OR START A DISCUSSION THREAD UNTIL THE ISSUE IS ASSIGNED A NUMBER. The issues coordinators will notify the list when that has occurred. Protocol: bqos rating sla Artifact: spec Type: design Title: Conformance Issues 2 Description: This issue applies to BusinessQualityOfService-v1.0-spec-wd04.pdf BusinessRating-v1.0-spec-wd05.pdf BusinessServiceLevelAgreement-v1.0-spec-wd04.pdf Consider whether empty instances would allow conforming applications to exchange information and satisfy the conformance section. Many of the items are zero or one, or otherwise are not required. Analysis of the minimal set of exchanged information should be done to evaluate the quality of the conformance section. Interoperability testing would reveal these issues, when done. Related issues: Unrecognized Attributes and Extensibility Conformance Issues 1 Proposed Resolution: Conduct analysis as described. Plan interoperability testing for the future. bill cox -- *William Cox* Email: wtcox@CoxSoftwareArchitects.com <mailto:wtcox@CoxSoftwareArchitects.com> Web: http://www.CoxSoftwareArchitects.com +1 862 485 3696 mobile +1 908 277 3460 fax -------------------------------------------------------------------- mail2web.com – Enhanced email for the mobile individual based on Microsoft® Exchange - http://link.mail2web.com/Personal/EnhancedEmail
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]