ࡱ > { ~ x y z g e bjbjVV r< r< $- $- $- $- $- 4 X- X- X- h - / X- 01 X 7 ( 7 7 7 8 x ? A Q S S S S S S $ H w 9 $- #B 8 8 #B #B w $- $- 7 7 w w w #B % $- 7 $- 7 Q w #B Q w w = 7 BQ h 3 = Ɩ 0 " | n D = $- = w #B #B #B w w } #B #B #B #B #B #B #B #B #B #B #B #B #B #B #B #B + :
SOA-EERP Business Quality of Service Version 1.0
Committee Specification 01
25 November 2010
Specification URIs:
This Version:
HYPERLINK "http://docs.oasis-open.org/soa-eerp/bqos/v1.0/SOA-EERP-bQoS-Spec-cs01.html"http://docs.oasis-open.org/soa-eerp/bqos/v1.0/SOA-EERP-bQoS-Spec-cs01.html
HYPERLINK "http://docs.oasis-open.org/soa-eerp/bqos/v1.0/SOA-EERP-bQoS-Spec-cs01.doc"http://docs.oasis-open.org/soa-eerp/bqos/v1.0/SOA-EERP-bQoS-Spec-cs01.doc
HYPERLINK "http://docs.oasis-open.org/soa-eerp/bqos/v1.0/SOA-EERP-bQoS-Spec-cs01.pdf"http://docs.oasis-open.org/soa-eerp/bqos/v1.0/SOA-EERP-bQoS-Spec-cs01.pdf (Authoritative format)
Previous Version:
HYPERLINK "http://docs.oasis-open.org/soa-eerp/bqos/v1.0/SOA-EERP-bQoS-Spec-cd03.html"http://docs.oasis-open.org/soa-eerp/bqos/v1.0/SOA-EERP-bQoS-Spec-cd03.html
HYPERLINK "http://docs.oasis-open.org/soa-eerp/bqos/v1.0/SOA-EERP-bQoS-Spec-cd03.doc"http://docs.oasis-open.org/soa-eerp/bqos/v1.0/SOA-EERP-bQoS-Spec-cd03.doc
HYPERLINK "http://docs.oasis-open.org/soa-eerp/bqos/v1.0/SOA-EERP-bQoS-Spec-cd03.pdf"http://docs.oasis-open.org/soa-eerp/bqos/v1.0/SOA-EERP-bQoS-Spec-cd03.pdf
Latest Version:
HYPERLINK "http://docs.oasis-open.org/soa-eerp/bqos/v1.0/SOA-EERP-bQoS-Specification.html"http://docs.oasis-open.org/soa-eerp/bqos/v1.0/SOA-EERP-bQoS-Specification.html
HYPERLINK "http://docs.oasis-open.org/soa-eerp/bqos/v1.0/SOA-EERP-bQoS-Specification.doc"http://docs.oasis-open.org/soa-eerp/bqos/v1.0/SOA-EERP-bQoS-Specification.doc
HYPERLINK "http://docs.oasis-open.org/soa-eerp/bqos/v1.0/SOA-EERP-bQoS-Specification.pdf"http://docs.oasis-open.org/soa-eerp/bqos/v1.0/SOA-EERP-bQoS-Specification.pdf
Technical Committee:
HYPERLINK "http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=soa-eerp"OASIS Service-Oriented Architecture End-to-End Resource Planning (SOA-EERP) TC
Chair(s):
William Cox
Andy Lee, Changfeng Open Standards Platform Software Alliance
Editor(s):
Szu Chang, Changfeng Open Standards Platform Software Alliance
Related work:
This specification is related to:
SOA-EERP Business Rating of Service specification, Version 1.0,
HYPERLINK "http://docs.oasis-open.org/soa-eerp/rt/v1.0/SOA-EERP-Rating-Specification.pdf"http://docs.oasis-open.org/soa-eerp/rt/v1.0/SOA-EERP-Rating-Specification.pdf
HYPERLINK "http://docs.oasis-open.org/soa-eerp/rt/v1.0/SOA-EERP-bRating-Specification.pdf%0D"SOA-EERP Business Service Level Agreement specification, Version 1.0, HYPERLINK "http://docs.oasis-open.org/soa-eerp/sla/v1.0/SOA-EERP-BSLA-Specification.pdf" http://docs.oasis-open.org/soa-eerp/sla/v1.0/SOA-EERP-BSLA-Specification.pdf
This document is one of three closely related specifications, SOA-EERP Business Quality of Service (bQoS), SOA-EERP Business Rating (bRating) and SOA-EERP Business Service Level Agreement (bSLA) which need to be understood in combination.
Declared XML Namespace(s):
HYPERLINK "http://docs.oasis-open.org/ns/soa-eerp/bqos/200903"http://docs.oasis-open.org/ns/soa-eerp/bqos/200903
Abstract:
This document specifies the XML vocabulary for business quality of service (bQoS), one of three Specifications for end-to-end resource planning (EERP). Business quality of service describes the business-related characteristics or attributes of a service.
Status:
This document was last revised by the SOA-EERP TC on the above date. The level of approval is also listed above. Check the Latest Version or Latest Approved Version location noted above for possible later revisions of this document.
Technical Committee members should send comments on this specification to the Technical Committees email list. Others should send comments to the Technical Committee by using the Send A Comment button on the Technical Committees web page at HYPERLINK "http://www.oasis-open.org/committees/soa-eerp/"http://www.oasis-open.org/committees/soa-eerp/.
For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page ( HYPERLINK "http://www.oasis-open.org/committees/soa-eerp/ipr.php"http://www.oasis-open.org/committees/soa-eerp/ipr.php).
The non-normative errata page for this specification is located at HYPERLINK "http://www.oasis-open.org/committees/soa-eerp/"http://www.oasis-open.org/committees/soa-eerp/.
Notices
Copyright OASIS 2010. All Rights Reserved.
All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.
This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.
OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.
OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.
The names "OASIS", SOA-EERP, EERP-bQoS, and bQos are trademarks of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see HYPERLINK "http://www.oasis-open.org/who/trademark.php"http://www.oasis-open.org/who/trademark.php for above guidance.
Table of Contents TOC \o "1-3" \h \z \u HYPERLINK \l "_Toc278840948" 1 Introduction PAGEREF _Toc278840948 \h 5
HYPERLINK \l "_Toc278840949" 1.1 Terminology PAGEREF _Toc278840949 \h 5
HYPERLINK \l "_Toc278840950" 1.1.1 Notational Conventions PAGEREF _Toc278840950 \h 5
HYPERLINK \l "_Toc278840951" 1.2 Normative References PAGEREF _Toc278840951 \h 6
HYPERLINK \l "_Toc278840952" 1.2.1 Reference PAGEREF _Toc278840952 \h 7
HYPERLINK \l "_Toc278840953" 1.3 Non-Normative References PAGEREF _Toc278840953 \h 7
HYPERLINK \l "_Toc278840954" 2 Quality Measurement Indicators PAGEREF _Toc278840954 \h 8
HYPERLINK \l "_Toc278840955" 2.1 Namespaces PAGEREF _Toc278840955 \h 8
HYPERLINK \l "_Toc278840956" 2.2 Schema Files PAGEREF _Toc278840956 \h 8
HYPERLINK \l "_Toc278840957" 2.3 BQoS Element PAGEREF _Toc278840957 \h 8
HYPERLINK \l "_Toc278840958" 3 BQoSPrice PAGEREF _Toc278840958 \h 10
HYPERLINK \l "_Toc278840959" 4 BQoSPerformance PAGEREF _Toc278840959 \h 12
HYPERLINK \l "_Toc278840960" 5 BQoSQualities PAGEREF _Toc278840960 \h 15
HYPERLINK \l "_Toc278840961" 6 BQoS Examples PAGEREF _Toc278840961 \h 17
HYPERLINK \l "_Toc278840962" 6.1 Service Price with a Batch of Products Examples PAGEREF _Toc278840962 \h 17
HYPERLINK \l "_Toc278840963" 6.2 Storage Service Examples PAGEREF _Toc278840963 \h 17
HYPERLINK \l "_Toc278840964" 7 Conformance PAGEREF _Toc278840964 \h 19
HYPERLINK \l "_Toc278840965" A. Acknowledgements PAGEREF _Toc278840965 \h 21
HYPERLINK \l "_Toc278840966" B. XML Schema PAGEREF _Toc278840966 \h 22
HYPERLINK \l "_Toc278840967" C. Non-Normative Text PAGEREF _Toc278840967 \h 27
HYPERLINK \l "_Toc278840968" D. Revision History PAGEREF _Toc278840968 \h 28
Introduction
This document is the specification for Business Quality of Service (bQoS) for End-to-End Resource Planning (EERP), an XML vocabulary by which a business application may communicate selected characteristics of the service it provides.
According to OASIS Reference Model for Service Oriented Architecture [SOA-RM], the Service Oriented Architecture (SOA) is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. The service within SOA is a mechanism to enable access to one or more capabilities, where the access is provided using a prescribed interface and is exercised consistent with constraints and policies as specified by the service description. This specification further defines the Business Quality of Service for the services that is defined in SOA-RM, within the EERP technology. The applications of this specification are any kind of business services, and they are not limited to only Web Services.
EERP applies the well-known technique for service discovery and optimization in a novel way to improve business results. It models the business process and the range of potential services, and then guides the selection and deployment of services based on the end-to-end business value.
Modeling the business characteristics of a service is a prerequisite for estimating the business value of the process that uses those services. The business characteristics of the service defined in this bQoS specification will enable EERP to determine the varieties of optimization to be supported, and to select optimal end-to-end solution.
In contrast to the QoS in the software/IT world, where the message is network/system oriented measurement indicates that deals with network performance and system availability, the contents of bQoS in this specification is business oriented measurement indicators that deals with business characteristics of a service, such as price, performance, and quality.
Terminology
The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described in REF rfc2119 \h [RFC2119].
Notational Conventions
This specification uses the following syntax to define outlines for detailed elements:
The syntax appears as an XML instance, but values in italics indicate data types instead of literal values.
Characters are appended to elements and attributes to indicate cardinality:
"?" (0 or 1)
"*" (0 or more)
"+" (1 or more)
The character "|" is used to indicate a choice between alternatives.
The characters "(" and ")" are used to indicate that contained items are to be treated as a group with respect to cardinality or choice.
The characters "[" and "]" are used to call out references and property names.
Ellipses (i.e., "...") indicate points of extensibility. Additional children and/or attributes MAY be added at the indicated extension points but MUST NOT contradict the semantics of the parent and/or owner, respectively. By default, if a receiver does not recognize an extension, the receiver SHOULD ignore the extension; exceptions to this processing rule, if any, are clearly indicated below.
XML namespace prefixes (see Table 1) are used to indicate the namespace of the element being defined.
Elements and Attributes defined by this specification are referred to in the text of this document using XPath 1.0 expressions. Extensibility points are referred to using an extended version of this syntax:
An element extensibility point is referred to using {any} in place of the element name. This indicates that any element name can be used, from any namespace other than the namespace of this specification.
An attribute extensibility point is referred to using @{any} in place of the attribute name. This indicates that any attribute name can be used, from any namespace other than the namespace of this specification.
Extensibility points in the exemplar may not be described in the corresponding text.
Normative References
[RFC2119] S. Bradner, Key words for use in RFCs to Indicate Requirement Levels, HYPERLINK "http://www.ietf.org/rfc/rfc2119.txt"http://www.ietf.org/rfc/rfc2119.txt, IETF RFC 2119, March 1997.
[SOAP] W3C Note, "SOAP: Simple Object Access Protocol 1.1", 08 May 2000.
HYPERLINK "http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"http://www.w3.org/TR/2000/NOTE-SOAP-20000508/
[SOAP12] W3C Recommendation, "SOAP 1.2 Part 1: Messaging Framework", 24 June 2003.
HYPERLINK "http://www.w3.org/TR/2003/REC-soap12-part1-20030624/"http://www.w3.org/TR/2003/REC-soap12-part1-20030624/
[URI] T. Berners-Lee, R. Fielding, L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", RFC 3986, MIT/LCS, Day Software, Adobe Systems, January 2005.
HYPERLINK "http://www.ietf.org/rfc/rfc3986.txt"http://www.ietf.org/rfc/rfc3986.txt
[UBL-20] OASIS Standard, Universal Business Language (UBL) v2.0, 12 December 2006
HYPERLINK "http://docs.oasis-open.org/ubl/os-UBL-2.0/UBL-2.0.pdf" http://docs.oasis-open.org/ubl/os-UBL-2.0/UBL-2.0.pdf
[UBL-20-cbc] Universal Business Language (UBL) v2.0, Common Basic Components, October 2006
HYPERLINK "http://docs.oasis-open.org/ubl/os-UBL-2.0/xsd/common/UBL-CommonBasicComponents-2.0.xsd"http://docs.oasis-open.org/ubl/os-UBL-2.0/xsd/common/UBL-CommonBasicComponents-2.0.xsd
[UBL-20-udt] Universal Business Language (UBL) v2.0. Unqualified Data Type, February 2005
HYPERLINK "http://docs.oasis-open.org/ubl/os-UBL-2.0/xsd/common/UnqualifiedDataTypeSchemaModule-2.0.xsd"http://docs.oasis-open.org/ubl/os-UBL-2.0/xsd/common/UnqualifiedDataTypeSchemaModule-2.0.xsd
[XML-Schema1] W3C Recommendation, "XML Schema Part 1: Structures Second Edition", 28 October 2004.
HYPERLINK "http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/"http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/
[XML-Schema2] W3C Recommendation, "XML Schema Part 2: Datatypes Second Edition", 28 October 2004.
HYPERLINK "http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/
[ISO8601] ISO Standard 8601:2004(E), "Data elements and interchange formats Information interchange - Representation of dates and times", Third edition, December 2004
HYPERLINK "http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=40874" http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=40874
[CEFACT] CEFACT Core components specifications, Recommendation 9 January
1996.
HYPERLINK "http://www.unece.org/cefact/recommendations/rec09/rec09_ecetrd203.pdf" \o "blocked::http://www.unece.org/cefact/recommendations/rec09/rec09_ecetrd203.pdf" http://www.unece.org/cefact/recommendations/rec09/rec09_ecetrd203.pdf
[SOA-RM] OASIS Standard, HYPERLINK "http://docs.oasis-open.org/soa-rm/v1.0/soa-rm.pdf"OASIS Reference Model for Service Oriented Architecture 1.0, 12 October 2006
HYPERLINK "http://docs.oasis-open.org/soa-rm/v1.0/soa-rm.pdf" http://docs.oasis-open.org/soa-rm/v1.0/soa-rm.pdf
Reference
In this document reference is made to some basic elements and data types in HYPERLINK \l "ubl20"UBL 2.0, in the following schema:
UBL 2.0 Common Basic Components [ HYPERLINK \l "ubl20cbc"UBL-20-cbc], UBL-CommonBasicComponents-2.0.xsd
UBL 2.0 Unqualified Data Type [ HYPERLINK \l "ubl20udt"UBL-20-udt], UnqualifiedDataTypeSchemaModule-2.0.xsd
This specification is designed to work with the general Web Services framework including WSDL service descriptions, and HYPERLINK \l "soap"SOAP message structure and message processing model. The XML vocabulary defined in bQoS should be applicable to any version of HYPERLINK \l "soap"SOAP.
Non-Normative References
None.
Quality Measurement Indicators
The Business Quality of Service (bQoS) of the XML vocabulary is defined in XML Schema format that defines many quality measurement indicators.
Namespaces
The XML namespace URI that MUST be used by implementations of this specification is:
http://docs.oasis-open.org/ns/soa-eerp/bqos/200903
Table 1 lists XML namespaces that are used in this specification. The choice of any namespace prefix is arbitrary and not semantically significant.
Table SEQ "Table" \*Arabic 1: Prefixes and XML Namespaces used in this specification.
PrefixNamespaceSpecification(s)Shttp://schemas.xmlsoap.org/soap/envelope/[ HYPERLINK \l "soap"SOAP]S12http://www.w3.org/2003/05/soap-envelope[ HYPERLINK \l "soap12"SOAP12]xsdhttp://www.w3.org/2001/XMLSchema[ HYPERLINK \l "xmlschema1"XML-Schema1], [ HYPERLINK \l "xmlschema2"XML-Schema2]cbcurn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2[ HYPERLINK \l "ubl20cbc"UBL-20-cbc]udturn:un:unece:uncefact:data:specification:UnqualifiedDataTypesSchemaModule:2[ HYPERLINK \l "ubl20udt"UBL-20-udt] cctsurn:un:unece:uncefact:documentation:2[ HYPERLINK \l "ubl20"UBL-20]bqoshttp://docs.oasis-open.org/ns/soa-eerp/bqos/200903This specification Schema Files
A normative copy of the XML Schema [ HYPERLINK \l "xmlschema1"XML-Schema1, HYPERLINK \l "xmlschema2"XML-Schema2] description for this specification can be retrieved from the following address:
http://docs.oasis-open.org/soa-eerp/bqos/v1.0/EERP-bQoS-cd04.xsd
BQoS Element
The BQoS is the root element for the Business Quality of Service schema. It can have one or more of the following elements:
BQoSPrice indicates price or cost for the service
BQoSPerformance indicates time to complete the service, or in the alternative, throughput and latency.
BQoSQualities indicates additional properties and attributes.
Any additional elements for quality of service can be either:
Technical aspect such as service availability, accessibility, integrity, reliability, and security; or
Business aspects such as regulatory, geo location, operation hours, and payment methods.
Syntax
bqos:BQoSPriceType
bqos:BQoSPerformanceType ?
bqos:BQoSQualitiesType ?
...
The following describes the attributes and elements listed in the schema outlined above:
/bqos:BQoS
The root element for bQoS
/bqos:BQoS/bqos:BQoSPrice
Price aspect of the service, including the price and other optional elements, see Section 3 for more details.
/bqos:BQoS/bqos:BQoSPrice/@{any}
This is an extensibility mechanism to allow additional attributes, based on schemas, to be added to the BQoSPrice element in the future. Unrecognized attributes MAY cause a fault or be silently ignored.
/bqos:BQoS/bqos:BQoSPerformance
Performance aspect of the service that has time period for the time to complete the whole service, the throughput for duration to complete number of jobs, or optional elements, see Section 4 for more details.
/bqos:BQoS/bqos:BQoSPerformance/@{any}
This is an extensibility mechanism to allow additional attributes, based on schemas, to be added to the BQoSPerformance element in the future. Unrecognized attributes MAY cause a fault or be silently ignored.
/bqos:BQoS/bqos:BQoSQualities
Quality aspect of the service that has additional properties and attributes to describe the quality of the service, see Section 5 for more details.
/bqos:BQoS/bqos:BQoSQualities/@{any}
This is an extensibility mechanism to allow additional attributes, based on schemas, to be added to the BQoSQualities element in the future. Unrecognized attributes MAY cause a fault or be silently ignored.
/bqos:BQoS/@{any}
This is an extensibility mechanism to allow additional attributes, based on schemas, to be added to the BQoS element in the future. Unrecognized attributes MAY cause a fault or be silently ignored.
/bqos:BQoS/bqos:BQoSExtension
BQoSExtension element is an optional element that keeps different (extensible) elements to be specified in the future.
/bqos:BQoS/bqos:BQoSExtension/{any}
This is an extensibility mechanism to allow different (extensible) elements to be specified in the future. Unrecognized elements MAY cause a fault or be silently ignored.
BQoSPrice
BQoSPrice, the Price element for bQoS, describes the price for the service. Price can be expressed in various ways.
There SHOULD be one BQoSPrice element present in the business quality of service.
Syntax
bqos:PriceType
cbc:BaseUnitMeasureType ?
cbc:AmountType
...
The following describes the attributes and elements listed in the schema outlined above:
/bqos:BQoS/bqos:BQoSPrice
Price aspects of the service, including the price and other optional elements
/bqos:BQoS/bqos:BQoSPrice/bqos:Price
Price element that represent the single price for BQoSPrice
/bqos:BQoS/bqos:BQoSPrice/bqos:Price/bqos:Unit
Number of units is a optional element that includes the unit of measurement using cbc:BaseUnitMeasureType
/bqos:BQoS/bqos:BQoSPrice/bqos:Price/bqos:Unit/@unitCode
Unit of measurement in cbc:BaseUnitMeasureType. It is a required attribute using clm66411:unitCodeContentType, xmlns:clm66411="urn:un:unece:uncefact:codelist:specification:66411:2001"
/bqos:BQoS/bqos:BQoSPrice/bqos:Price/bqos:Amount
Amount is a required element in the Price element. It uses cbc:AmountType from UBL that has a required currencyID attribute for currency code.
/bqos:BQoS/bqos:BQoSPrice/bqos:Price/bqos:Amount/@currencyID
Currency ID in cbc:AmountType. It is a required attribute using clm54217:CurrencyCodeContentType, xmlns:clm54217="urn:un:unece:uncefact:codelist:specification:54217:2001"
/bqos:BQoS/bqos:BQoSPrice/{any}
This is an extensibility mechanism to allow different (extensible) price elements to be specified in the future. Unrecognized elements MAY cause a fault or be silently ignored.
Example
The following non-normative example illustrates the use of bQoS price element. It describes 10 units for price of $171.50 US dollar:
(001)
(002)
(003)
(004) 10
(005) 171.50
(006)
(007)
BQoSPerformance
BQoSPerformance element for bQoS is the quality of service measured in the time to complete, or alternatively as throughput and latency.
There MAY be zero or one BQoSPerformance element present in the business quality of service.
Syntax
bqos:TimePeriodType
cbc:DurationMeasureType
cbc:DurationMeasureType ?
udt:DateTimeType ?
|
...
cbc:DurationMeasureType
cbc:DurationMeasureType ?
|
...
The following describes the attributes and elements listed in the schema outlined above:
/bqos:BQoS/bqos:BQoSPerformance
Performance aspect of the service that has time period for the time to complete the whole service job, the throughput for duration to complete number of jobs, or an optional elements.
/bqos:BQoS/bqos:BQoSPerformance/bqos:TimePeriod
TimePeriod is the time period to complete the service, including the duration to complete the service, and optional elements for start time and latency.
/bqos:BQoS/bqos:BQoSPerformance/bqos:TimePeriod/bqos:Duration
Duration element is a required element in the TimePeriod element which is the duration to complete the service. It uses cbc:DurationMeasureType from UBL that has a required unitCode attribute for unit of measurement on the time.
/bqos:BQoS/bqos:BQoSPerformance/bqos:TimePeriod/bqos:Duration/@unitCode
Unit of measurement in cbc:BaseUnitMeasureType. It is a required attribute for the duration time, such as Second, Minute, Hour, Day, Week, etc, using clm66411:unitCodeContentType, xmlns:clm66411="urn:un:unece:uncefact:codelist:specification:66411:2001".
/bqos:BQoS/bqos:BQoSPerformance/bqos:TimePeriod/bqos:StartTime
StartTime is an optional element for the date and time to start the service. It uses udt:DateTimeType which is in UTC time format [ISO8601].
/bqos:BQoS/bqos:BQoSPerformance/bqos:TimePeriod/bqos:Latency
Latency is an optional element that describes the time delay before a service is expected to begin. It uses cbc:DurationMeasureType from UBL that has a required unitCode attribute for unit of measurement on the time.
/bqos:BQoS/bqos:BQoSPerformance/bqos:TimePeriod/bqos:Latency/@unitCode
Unit of measurement in cbc:BaseUnitMeasureType. It is a required attribute for the duration time, such as Second, Minute, Hour, Day, Week, etc, using clm66411:unitCodeContentType, xmlns:clm66411="urn:un:unece:uncefact:codelist:specification:66411:2001".
/bqos:BQoS/bqos:BQoSPerformance/bqos:Throughput
Throughput of the performance which is measured by is the amount of work that a service can provide in a given time period. It includes the quantity of the item and the duration to complete the work.
/bqos:BQoS/bqos:BQoSPerformance/bqos:Throughput/bqos:Duration
Duration element is a required element in the Throughput element. This is the duration to complete the service. It uses cbc:DurationMeasureType from UBL that has a required unitCode attribute for unit of measurement on the time.
/bqos:BQoS/bqos:BQoSPerformance/bqos:Throughput/bqos:Duration/@unitCode
Unit of measurement in cbc:BaseUnitMeasureType. It is a required attribute for the duration time, such as Second, Minute, Hour, Day, Week, etc, using clm66411:unitCodeContentType, xmlns:clm66411="urn:un:unece:uncefact:codelist:specification:66411:2001"
/bqos:BQoS/bqos:BQoSPerformance/bqos:Throughput/bqos:Quantity
Quantity is a required element in the Throughput element. It is the numbers for the throughput, with an attribute of unit of measurement, such as EA, pounds, cubic-feet, etc.
/bqos:BQoS/bqos:BQoSPerformance/bqos:Throughput/bqos:Latency
Latency is an optional element for the time delay for starting the service. It uses cbc:DurationMeasureType from UBL that has a required unitCode attribute for unit of measurement on the time.
/bqos:BQoS/bqos:BQoSPerformance/bqos:Throughput/bqos:Latency/@unitCode
Unit of measurement in cbc:BaseUnitMeasureType. It is a required attribute for the duration time, such as Second, Minute, Hour, Day, Week, etc, using clm66411:unitCodeContentType, xmlns:clm66411="urn:un:unece:uncefact:codelist:specification:66411:2001".
/bqos:BQoS/bqos:BQoSPerformance/{any}
This is an extensibility mechanism to allow different (extensible) performance or time elements to be specified in the future. Unrecognized elements MAY cause a fault or be silently ignored.
Examples
The following non-normative example illustrates the use of bQoS Performance element using the Throughput element instead of TimePeriod element. It describes the throughput of 10 units per day:
(001)
(002)
(003)
(004) 1
(005) 10.0
(006)
(007)
The following non-normative example illustrates the use of bQoS Performance element using the TimePeriod element. It describes the 8 hours of the duration, and can be started on October 17, 2009, 9:30:47.02 Zulu time:
(001)
(002)
(003)
(004) 8
(005) 2009-10-17T09:30:47.0Z
(006)
(007)
BQoSQualities
The BQoSQualities, the Quality elements for bQoS, describes additional properties and attributes for the service. While any quality name/value can be asserted by a Service Provider to represent the quality of the service, this specification is not addressing issues of namespace management for qualities beyond the three pre-defined EERP namespaces.
There SHOULD be zero or one BQoSQualities element present in the business quality of service.
Syntax
bqos:PropertyType
bqos:PropertyNameType
bqos:PropertyValue ?
+
...
The following describes the attributes and elements listed in the schema outlined above:
/bqos:BQoS/bqos:BQoSQualities
Quality aspect of the service is measured in terms of additional properties and attributes. It has a list of property for BQoSQualities and other optional elements.
/bqos:BQoS/bqos:BQoSQualities/bqos:Property
Property element is for additional property or attribute for quality measurement of the service in bQoS that has name and value pair to describe the quality of the service.
/bqos:BQoS/bqos:BQoSQualities/bqos:PropertyName
Property name is a required element for the name in the name and value pair in the Property element. It uses bqos:PropertyNameType which is a cbc:NamType from UBL that has a optional languageID attribute for language code.
/bqos:BQoS/bqos:BQoSQualities/bqos:Property/bqos:PropertyName/@languageID
Language ID is an optional attribute in the PropertyName element, using xsd:language type. The value can be those defined in urn:un:unece:uncefact:codelist:specification:5639:1988.
/bqos:BQoS/bqos:BQoSQualities/bqos:Property/bqos:PropertyName/@{any}
This is an extensibility mechanism to allow additional attributes, based on schemas, to be added to the PropertyName element in the future. This can be the namespace and the format for the Property. Unrecognized attributes MAY cause a fault or be silently ignored.
/bqos:BQoS/bqos:BQoSQualities/bqos:Property/bqos:PropertyValue
The property value is an optional element for the value in the name and value pair in the Property element. It uses bqos:PropertyValueType which is a cbc:NamType from UBL that has a optional languageID attribute for language code.
/bqos:BQoS/bqos:BQoSQualities/bqos:Property/bqos:PropertyValue/@languageID
Language ID is an optional attribute in the PriceValue element, using xsd:language type. The value can be those defined in urn:un:unece:uncefact:codelist:specification:5639:1988.
/bqos:BQoS/bqos:BQoSQualities/bqos:Property/@{any}
This is an extensibility mechanism to allow additional attributes, based on schemas, to be added to the Property element in the future. Unrecognized attributes MAY cause a fault or be silently ignored.
/bqos:BQoS/bqos:BQoSQualities/{any}
This is an extensibility mechanism to allow different (extensible) properties or attribute elements to be specified in the future. Unrecognized elements MAY cause a fault or be silently ignored. For example, one or more /bqos:BQoS/bqos:BQoSQualities/Performance:QualityAssertion elements can be placed in here for the Service Provider to assert the specific Qualities of its services.
Example
The following non-normative example illustrates the use of bQoS price element. It describes the Class is Golden and it has Network Connection as additional property for this service:
(001)
(002)
(003)
(004) Class
(005) Golden
(006)
(003)
(004) Network Connection
(006)
(007)
BQoS Examples
The examples in this section are non-normative.
Service Price with a Batch of Products Examples
This bQoS example will show the following quality indicators:
The service price is CNY 120000 per service, including 1000 gas-meters for one batch.
The throughput is usually 1 week or 7 days for the service. In another words, it will cost 1 week or 7 days to provide and delivery 1000 gas-meters as one batch of product.
The service has additional attributes to provide the IC card gas-meters integrated with iron IC-card box for the quality indicators.
Example
The following example illustrates the whole bQoS document for quality indicators:
1000
120000
7
1000
0