[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (SOAEERP-35) PR07-T14 Common wordsare not defined in three specifications
[ http://tools.oasis-open.org/issues/browse/SOAEERP-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19434#action_19434 ]
Szu Chang commented on SOAEERP-35:
-----------------------------------
New revision on WD09:
Whitepaper line 161 - 180 of http://www.oasis-open.org/committees/download.php/38426/EERP-Model-UseCase-WhitePaper-wd09-diff-cd03-withLineNumber.pdf
161 Business Quality of Service (bQoS) models the business characteristics of a service for
162 estimating the business value of one or a set of services in a business process. In
163 contrast to the QoS in the software/IT world, where the message is network/system
164 oriented measurement that deals with network performance and system availability, the
165 contents of bQoS in this specification is business oriented measurement that deals with
166 business characteristics of a service, such as price, performance, and quality.
167 Business Rating (bRating) defines credibility, reliability and reputation of the service
168 need to be understood for estimating the overall business quality of the process that uses
169 those services. It has two major kinds of rating: Rating and Credentials. Rating are
170 provided by the rating provider to show the ranking and reputation of a given service
171 provider, in comparison of other providers. In contrast, Credentials are provided by the
172 service provider itself to show the credibility of providing a given service.
173 Business Service Level Agreement (bSLA) is the agreement between the service
174 requestor and the service provider, and primary address the bQoS content, Rating and
175 Credentials. These contents are all business related. In contrast to the SLA (Service Level
176 Agreement) in the software/IT world, where SLA is the contract between the service
177 provider and the network/system provider, and the SLA is network/system oriented
178 agreement that deals with network performance and system availability. The bSLA in the
179 EERP is business oriented agreement that deals with price, time to deliver, and the
180 quality/rating of the service.
bQoS spec http://www.oasis-open.org/committees/download.php/38435/SOA-EERP-bQoS-Specwd09-diff-cd03.pdf
Line 21 -24
21 In contrast to the QoS in the software/IT world, where the message is network/system oriented
22 measurement indicates that deals with network performance and system availability, the contents of
23 bQoS in this specification is business oriented measurement indicators that deals with business
24 characteristics of a service, such as price, performance, and quality.
bRating spec http://www.oasis-open.org/committees/download.php/38429/SOA-EERP-bRating-Spec-wd09-diff-cd03.pdf
Line 161-164:
161 The ListOfRating element contains the list of Rating issued by a Rating Provider. The Rating Provider is a
162 party unaffiliated with either the requester or the target of the rating request, such as a third party rating
163 organization, given a reference to a particular business service and provider, issues either a number or a
164 classification description for rating.
bSLA spec http://www.oasis-open.org/committees/download.php/38432/SOA-EERP-bSLA-spec-wd09-diff-cd03.pdf
Line 24-29:
24 The bSLA is different than the SLA (Service Level Agreement) in the software/IT world. The bSLA in this
25 specification is the contact between the service requester and the service provider. The bSLA in this
26 specification is the contact between the service requester and the service provider, and the SLA is the
27 contract between the service provider and the network/system provider. The SLA is network/system
28 oriented agreement that deals with network performance and system availability. The bSLA is a business
29 oriented agreement that deals with price, time to deliver, and the quality/rating of the service.
> PR07-T14 Common words are not defined in three specifications
> -------------------------------------------------------------
>
> Key: SOAEERP-35
> URL: http://tools.oasis-open.org/issues/browse/SOAEERP-35
> 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
>
> 15. All three specifications use common words (e.g. Service, SLA, Quality of Service, Rating, Credentials) but do not define them or reference the relevant definitions. All the specifications should carefully compare and conrast, and where a specific technical meaning or meaning may be understood, indicate whether that meaning is intended. Otherwise the documents are hard to comprehend. The missing comparison and contast beteween "SLA" and "BSLA" is one case in point (see item 14). The connections all need to be explicit, not implicit or suggested (but never confirmed). The documents read as if there were a detailed architectural and interaction model that is understood by the authors but never explained to the readers. This is a barrier to implementation, understanding, and conformance.
--
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]