OASIS Specification Template



[pic]

Web Services Quality Model v1.0

Draft, 10 December 2007

Artifact Identifier:

wsqm-ws_quality_model-wd-v1.0-r04

Location:



Artifact Type:

WS-QualityModel

Technical Committee:

OASIS Web Services Quality Model TC

Chair(s):

Eunju Kim, National Information Society Agency

Dugki Min, Konkuk University

Editor(s):

Eunju Kim, National Information Society Agency

Yongkon Lee, Korea Polytechnic University

Guil Kang, National Information Society Agency

OASIS Conceptual Model topic area:

Web Services, SOA

Abstract:

As experiences on Service Oriented Architecture (SOA) and web services have been accumulated, the Quality of Service (QoS) has gained more attention. The purpose of this document is to provide a framework for enabling quality in SOA especially focused on Web Services.

Web Services Quality Model is a conceptual model, which need to be shared among stakeholders of SOA and Web Services to reflect quality into a service lifecycle. It defines principle entities such as quality associates, quality activities and quality factors and their relationship. A quality model initially targets on Web Services but it can be easily extended and applied to other standard or technology which can be used for SOA.

Status:

This document was last revised or approved by the WSQM TC on the above date. The level of approval is also listed above. Check the current location noted above for possible later revisions of this document. This document is updated periodically on no particular schedule.

Technical Committee members should send comments on this specification to the Technical Committee’s email list. Others should send comments to the Technical Committee by using the “Send A Comment” button on the Technical Committee’s web page at mittees/wsqm.

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 (mittees/wsqm/ipr.php.

The non-normative errata page for this specification is located at mittees/wsqm.

Notices

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's procedures with respect to rights in OASIS specifications can be found at 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 implementors or users of this specification, can be obtained from the OASIS Executive Director.

OASIS invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to implement this specification. Please address the information to the OASIS Executive Director.

Copyright © OASIS® 1993–2007. All Rights Reserved. OASIS trademark, IPR and other policies apply.

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 paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document 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 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

The names "OASIS", 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 for above guidance.

Table of Contents

1 Introduction 5

1.1 What is Web Service Quality Model? 5

1.2 Goals and Requirements 5

1.3 Relationships to Other Standards 6

1.4 Terminology 6

1.5 Normative References 6

2 Quality Associates 7

2.1 Acquirer 9

2.2 Service Developer 9

2.3 Service Provider 9

2.4 Service Consumer 9

2.5 Quality Information Provider 9

2.6 Quality Assuror 9

2.7 Quality Authenticator 10

2.8 Quality Manager 10

3 Quality Activities 11

3.1 Acquisition and Development Activity 13

3.1.1 Acquisition 13

3.1.2 Development 13

3.1.3 Revaluation and Acceptance 13

3.2 Operation and Quality Management Activity 13

3.2.1 Operation 14

3.2.2 Operation entrustment 14

3.2.3 Quality Management 14

3.2.4 Quality Management Entrustment 14

3.3 Quality Information Offer Activity 15

3.3.1 Registration 15

3.3.2 Quality Information Collection 15

3.3.3 Authentication Information Collection 15

3.3.4 Quality Information Offer 15

3.3.5 Quality Information Search 15

3.4 Quality Authentication Activity 15

3.4.1 Authentication Request 15

3.4.2 Quality Information Collect 16

3.4.3 Quality Authentication 16

3.4.4 Authentication Information Search 16

3.5 Quality Assurance Activity 16

3.5.1 Monitoring 16

3.5.2 Quality Assurance 17

3.5.3 Quality Assurance Data Request 17

3.6 Quality Contract Activity 17

3.6.1 Development Contract 17

3.6.2 Operation Contract 17

3.6.3 Quality Management Contract 17

3.6.4 Use Contract 17

3.6.5 Authentication Contract 17

3.6.6 Assurance Contract 18

4 Quality Factors 19

A. Acknowledgements 21

B. Non-Normative Text 22

C. Revision History 23

Introduction

Different from exiting software, Web Services as a service are used remotely if needed so it is fundamentally considered to be loosely coupled with application. The service oriented characteristic requires a new software paradigm which converts the way of installation software to distributed service. Furthermore, in order to unify automated service which is not tied with variety applications, Web Services uses defined XML based standard protocol when extension is needed. According to this, it is a strong necessity to set a new definition of quality which fulfils service oriented Web Services characteristics based on standard protocol and hence requirements followed by interested party.

This document defines Web Service quality characteristic in a quantitative or qualitative method, excluding the traditional functionality of service. To maximize the best use of Web Services quality, it is essential to have a guideline and detailed implementation notation. Therefore, we present five co-relations but independent specifications i.e. WS-Quality Model, WS-Quality Factors, WS-Quality Description Language, WS-Quality Test Guideline, and WS-Quality Use Case.

The specifications consist of the following five family specifications;

• WS-Quality Model (WS-QM) defines a conceptual model for Web Services quality and defines the concept, role and reciprocal action between quality associates, quality activities and quality factors in the lifecycle of Web Services.

• WS-Quality Factors (WS-QF) defines a set of attributes which is used to represent and evaluate the quality of a web service.

• WS-Quality Description Language (WS-QDL) provides a basic description method in forms of XML schema standard in order to standardize the expression of Web Service quality which is exchanged between Web Service quality associates

• WS-Quality Test Guideline (WS-QTG) provides a guideline for process, methods and architecture in order to measure and evaluate the quality level of Web Services

• WS-Quality Use Case (WS-QUC) provides a number of use cases as best practices that Web Services quality associates could be faced with in the process of developing and using Web Services

1 Goals

The purpose of this document is to provide a conceptual model for Web Services quality and to define the role and reciprocal action between quality associates, quality activities and quality factors. A standardized quality model makes quality associates to perform quality activities more clearly and makes management of Web Services quality more easily by offering consistence on variety of quality activities.

2 What is Web Service Quality Model?

Web Services quality model is conceptually a super set model which defines the reciprocal action between quality associates, quality activities and quality factors to enable quality of Service (QoS) in the lifecycle of Web Services

Quality associates refer to the person or the organization that directly undertakes or indirectly relates to quality activities in each step of Web Services lifecycle. Quality activities refers to a series of activities that through the development, deployment and use of Web services, the quality associates create and use the quality information as well as maintain and manage the quality level in the Web Services lifecycle. Quality factors refer to a group of items that uses for representing and valuing the quality of Web services.

In this quality model, Quality associates perform quality activities using quality factor. For example, quality associates like a web service provider and consumer perform quality activities as contracting a service level agreement (SLA) using quality factors like performance and stability. illustrates the relationship between quality associates, quality activities and quality factors.

[pic]

Web Services Quality Model

The following chapters define the concept of quality associates, quality activities and quality factors and describe the detailed explanation of their role.

3 Relationships to Other Standards

The international standard ISO-25000 approved by the International Standards Organization defines the software quality named as ‘software quality’. This ISO-25000 standard has a view point that software as a product and software quality defines as a totality of characteristic. The quality model of ISO-25000 presents a wide scope and variety of characteristics of product which product has in general. In addition, view point of software quality characteristics can be divided into internal, external or operational use. Web Services can be considered as software so it is possible to apply ISO-25000 software quality model to define Web Services quality. However, Web Services’ characteristics are different from the model presented in ISO-25000 so it is not suitable to directly apply this model to Web Services.

Due to its nature, this quality model may have implied relationship with any group that:

• Considers its work “quality oriented”;

• Makes (publicly) an adoption statement to use the quality model for Web Services as a base or inspiration for their work; and

• Standards or technologies that claim to be quality oriented.

4 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 [RFC2119].

5 Normative References

[RFC2119] S. Bradner, Key words for use in RFCs to Indicate Requirement Levels, , IETF RFC 2119, March 1997.

Quality Associates

A web service quality associate refers to the person or the organization that directly undertakes or indirectly relates to quality activities in each step of Web Services lifecycle. Quality associates can be divided into development associates, service persons and quality supporters with regards to development, use and support qualities related to Web Services.

Development associates’ main role is to request and to develop Web Services, and they are consists of both, acquirer and developer.

Service persons’ main role is to provide and to use Web Services, and they are consists of both, provider and consumer.

Quality supporters’ main role is to manage quality, to provide information, to authenticate and to assure Web Services. They are consists of quality information provider, quality assuror, quality authenticator, and quality manager.

illustrates the level of structure of Web Services quality associates

[pic]

Structure of Web Services Quality Associates

demonstrates the relationship between these quality associates

[pic]

Relationships of Web Services Quality Associates

1 Acquirer

Acquirer’s main role is to be the central figure in requesting service development to the developer. In addition once the Web Services system has been developed, they will become the owners of that system. Having a contract with the developer, Acquirer SHALL request various quality requirements from the developer. Acquirer and developer SHALL perform a test which examines the functionality of the developed Web Services and to make sure the quality level meets requirements. This test is called ‘revaluation procedure‘.

2 Service Developer

Developer’s main role is to facilitate web services functionality via having a contract with the acquirer. At this point, a developer MUST design and develop Web Services which fulfill the acquirer’s quality level expectations.

3 Service Provider

Provider’s main role is to provide Web Services by operating the service and managing both quality and the system. Acquirer and provider may be the same person or organization however, if they exist independently, acquirer MAY entrust the Web services’ operation and management to the provider. The provider MAY have a contract with the consumer concerning the quality level which has to be protected while Web Services is being operated. Provider MAY entrust quality management of Web services to a third party quality manager.

4 Service Consumer

Consumer’s main role is to use Web Services which are provided from the provider and will directly impact the quality of Web Services. Consumer can choose suitable Web Services after searching the system that will refer the quality information provided by the quality information provider. Furthermore, consumer can confirm quality insurance information of Web Services via the quality authenticator, and be able to request the certification for the quality written in the contract to the quality assuror.

5 Quality Information Provider

Quality information provider’s main role is to store registered quality information of Web services after collecting them and to provide the quality information of Web Services when there is a request from quality associates. The quality information provider keeps pace with the functionality of Web Services registry repository so that they are able to carry out Web Services search and provide quality information simultaneously. If Web Services registry repository (UDDI) and quality information provider exists independently, quality information provider can offer quality information to UDDI.

6 Quality Assuror

Quality assuror’s main role is to observe and make sure to keep the responsibility of the provider for quality level of Web services is written in the contract between the provider and the consumer. Quality assuror carries out an assurance of negotiation or compensation when a difference occurs between the provider and the consumer after monitoring the provided Web Services.

7 Quality Authenticator

Quality authenticator’s main role is to certify the quality after valuating each quality element of the quality information in standard basis. Quality certification refers to the certifying procedure of the status of the provided Web Services and is up to a certain quality level that keeps it continuously stable. This quality certification can be used a way to certify whether certain quality levels are adequate or achieve Web Services quality level grades defined by the authenticator.

8 Quality Manager

Quality manager’s main role is to control the Web Services operation environment and manage error situation in order to keep the quality level which the provider requires. Quality manager must inform the status of Web Services operation and notify particular error situation to the provider.

Quality Activities

Quality activities refers to a series of activities that the quality associates create or use the quality information and maintain or manage the quality level through out the whole of Web Services’ lifecycle with regards to development, deployment and use of Web Services. Quality activities can be divided into the development, operation, quality management, quality information offer, quality authentication, quality certification and quality contract.

shows the relationship between these Web Services quality associates and the quality activities.

[pic]

relationship of Web Services Quality Activities

1 Acquisition and Development Activity

Acquisition and development activity refers to an activity of framing and acquiring a request for proposal requirements which describes detail concepts and requirements in regard to developing Web Services, thus, to design and complete the implementation of the service based on the proposal requirements. Acquisition and development activity is the stage that initially the Web Services’ quality and level is defined and also quality information is created in the Web Services lifecycle. Acquirer and developer define functionalities and quality level of Web Services via having a development contract. Sub-quality activities are consisted of acquisition, development, development contract and revaluation procedure. Acquirer MAY directly undertakes the operation of Web Services as a provider or entrusts operation to third party provider when system implementation is completed,

1 Acquisition

This is an activity of acquirer defines functionalities of Web Services with regard to quality requirements and requests from developer to develop Web services development based on the definition. At this point, acquirer performs a series of activities starting with defining the concepts then moves onto defining the system or service requirements, preparing a request for proposal requirement, valuating and making a contract with proposal requirements, requesting maintenance, etc.

2 Development

This is an activity of developer that performs for requirement analysis, design, coding, testing, implementation and acceptance which are related to development of Web Services. There are many factors which would influence on service quality in every stage of Web Services development. Consequently, in order to complete development which is tailored for particular quality level, the developer must keep a check on quality continuously from the phase of Web Services development. If there is a necessity for implementing the system in connection with Web Services development, activities which are related to the system can be included. Developer undertakes or supports activity of development process according to the contract with acquirer

3 Examination and Acceptance

Revaluation procedure refers to a verification activity that acquirer performs to decide whether defined requirements and quality level are coincided when developed Web Services acquires. At this point, acquirer goes with a series of activities consist of product check, service functionality test, service quality level test, etc. Acceptance refers to an activity of receiving final product that acquirer agrees on the matter of development of Web Services that coincidence of requirements which written in acquisition contract has met. Acquirer exams acceptance or failure of Web Services’ operation in real environment by having an operation test

2 Operation and Quality Management Activity

This is an activity of developer that manages Web Services and operation system’s quality in order to provide service continuously without error. This refers to system operation and management activity to ensure seamless service and quality level.

Operation process refers to operate the system which includes the software and performs the operation support for consumer. Operation process derives operation requirements by system operator collects consumer’s requirements. Based on this, sets up operation plan and includes installation of developed system and deployment. Also according to system deployment, it includes support of system operation test, system operation and system consumer. Operation and quality management activity refers to an activity that provider operates system, which includes service, continuously without error and manages system and quality in order to keep quality level is up to defined quality level. At this point, provider directly manages Web Services or entrusts management to third party quality manager. Sub-quality activities consist of operation, operation entrustment, quality management and quality management entrustment.

1 Operation

Operation refers to a series of activities that provider operates system according to the defined operation procedure in order to provide Web Services that consumer can use them continuously. At this point, provider maintains system continuously in order to reflect consumer’s requirements or solve the problem during the operation.

2 Operation entrustment

Operation entrustment means an activity that acquirer entrusts operation to third party provider in order to operate Web Services which is built by developer. In the case of entrusting operation, acquirer determines entrustment based on valuation of provider’s system operation capability.

3 Quality Management

Quality management refers to management activity about Web Services and system that provider performs in order to fulfill quality requirements written in the use contract with consumer. Provider performs an adequate action about management of service quality, if there is occurrence of quality deterioration via service quality measurement and valuation based on service quality policy and detailed statements. Provider can entrust Web Services’ quality management to third party quality manager.

1 Monitoring

It means an activity of checking the status of Web Services’ quality by setting up the fixed period of time.

2 Report

It means an activity of informing quality status which has been inspected during the fixed period of time.

3 Notification

It means an activity of notifying to consumer in the real time basis, if there is a problem of Web Services has occurred.

4 Quality Management Entrustment

Quality management entrustment means an activity that provider entrusts quality management to third quality manager not only manages quality side’s data but manages functionality of Web Services which is provided by provider. In the case of entrusting management, it can be determined by valuating quality manager’s ability which estimates the capability of management developed Web Services. If required quality level is not fulfilled by analyzing the result of monitoring of Web Services’ quality, quality manager performs a series of activities such as report or notification to provider and consumer, etc.

3 Quality Information Offer Activity

Quality information offer activity refers to an activity that quality information provider intermediates consumer and provider based on Web Services quality information. Quality information provider collects quality information about service and provides them to consumer via service registry. Sub quality activity consists of registration, quality information collect, assurance information collection, quality information offer, quality information search.

1 Registration

Registration refers to an activity that provider requests quality information provider to collect provider’s Web Services quality information.

2 Quality Information Collection

Quality information collection refers to an activity that quality information provider collects quality information from provider in order to provide Web Services’ quality information. Quality information collection can be achieved by searching the stored information or monitoring in real time basis.

3 Authentication Information Collection

Authentication information collection refers to an activity that quality information provider collects authentication information from quality authenticator, if provider’s Web Services gets the quality authentication from quality authenticator.

4 Quality Information Offer

Quality information offer refers to an activity that quality information provider uses collected quality information to provide consumer about Web Services quality information which requires service functionality or quality level.

5 Quality Information Search

It means an activity of searching Web Service quality information which is coincided functionality or quality level required or needed by consumer.

4 Quality Authentication Activity

Quality authentication refers to a provider’s activity that Web Services quality level is inspected by quality authenticator. Quality authenticator goes through authentication contract, quality information collection, and quality authentication, if provider request authentication for quality authentication and then determines Web Services’ quality level and grants authentication to provider’s Web Services. Authentication information created by this process can be provided to consumer as objective information for Web Services’ quality information. Sub quality activities consist of authentication request, authentication contract, quality information collection and quality authentication.

1 Authentication Request

Authentication request refers to an activity that provider requests quality authentication to quality authenticator in order to inspect Web Service quality level. For authentication request, provider demands it as online method via using a particular quality authentication system or as offline method to quality authenticator.

2 Quality Information Collection

Quality information collect refers to an activity that quality authenticator collects quality information about provider’s Web Services for quality authentication. Quality information collect can be included various on-off line operation such as Web services test, statistical analysis, research of consumer’s reaction, etc.

3 Quality Authentication

Quality authentication refers to an activity that quality authenticator values collected quality information in standard basis and determines quality level. Authentication data or authentication certificate can be issued on authenticated Web Service

1 Evaluation

Valuation means an activity of testing and measurement that provider’s Web Services is fulfilled the particular quality level according to quality authenticator’s standard.

2 Authentication Certificate Issue

Authentication certificate issue means an activity of approving that provider’s Web Services is fulfilled the particular quality level according to quality authenticator’s standard.

4 Authentication Information Search

Authentication information search refers to activity that consumer searches quality authentication information about particular Web Services. Consumer trusts provider’s Web Services via quality authentication information and uses as a basis for selecting Web services which satisfies its expectation. Quality information provider can use authentication information search for collecting provider’s authentication information.

5 Quality Assurance Activity

Quality assurance activity refers to an activity that quality assuror assures Web Services quality level based on quality assurance contract. Quality assuror can conclude assurance contract with provider or consumer or to be based on use contract between consumer and provider. Quality assuror performs monitoring provider’s Web Services in real time bases in order to assure Web Service quality is up to particular level which is written in the contract. Sub quality activities consist of assurance contract, monitoring, quality assurance, quality assurance data request.

1 Monitoring

Monitoring means an activity of observing that Web Services’ quality level is continuously up to particular level which is written in the assurance contract and also accomplishes immediate management if irregular matter is arisen.

2 Quality Assurance

Quality assurance refers to an activity of analyzing the reason, negotiating solution for problem and compensating in case a provider cannot provide the consumer the service quality level which is written in the assurance contract.

3 Quality Assurance Data Request

Quality assurance date request refers to an activity that consumer requests to quality assuror about the information related to provider’s Web Service assurance or the use information of Web Services.

6 Quality Contract Activity

Quality contract refers to an activity that defines and states quality lists and level according to Web Service lifecycle between the quality associates. Quality contract is defined as development contract, operation contract, management contract, use contract, authentication contract and assurance contract according to the purpose between quality associates and quality activates. When each quality contract is concluded, SLA (Service Level Agreement), which describes service level agreement, compensation and penalty, can be applied

1 Development Contract

Development contract can be concluded between acquirer and developer in order to develop Web Services. They must include agreement which describes list of requirements, functionality, quality level, maintenance, tutorial and revaluation list, etc. In Web Service development contract, it must includes precise specification of quality which developer has to achieve for developing Web Services and valuation notations that acquirer performs once Web Service development is completed.

2 Operation Contract

Operation contract can be concluded between Web Services acquirer and provider when acquirer does not operate Web Services and entrusts service operation and providing after Web Service development has been completed. Operation contract means Web Services provider fundamentally manage quality factors, quality level and system operation, in order to maintain Web Services quality which is announced for Web Services consumer.

3 Quality Management Contract

Quality management contract can be concluded between provider and quality manager when provider entrusts management of Web Services’ quality to third party manager. Quality management contract must specify quality factors and quality level which are managed in regular basis. In order to follow this, they also include agreement which describes data measurement method, management activity, and report and notification schedule.

4 Use Contract

Use contract can be concluded between consumer and provider in order to use providing Web Service. In Web Service use contract, they must include agreement which describes detailed management in case of breach that provider must provide consumer about functionality details, quality factors, quality level.

5 Authentication Contract

Authentication contract can be concluded between quality authenticator and provider that authoritative organization authenticates provider’s service is up to particular level of service. In the case of valuing quality level, quality authenticator can request various dates related to quality from provider or monitoring provider’s system so that quality information can be collected. In order to authenticate quality, cost of authentication can be changed by scale of the system, range of valuation, valuation period, input so that quality authenticator and provider must specify agreement of these parts in the authentication contract.

6 Assurance Contract

Quality assuror concludes assurance contract with provider and consumer in order to provide quality level which is Web Services quality factors provided from provider that services to consumer continuously. Assurance contract must includes an agreement list about the compensation if quality level of service which is written in the contract is not provided

Quality Factors

The Web Services Quality Factors are primarily selected for planning, implementing and evaluating of Web Services amongst software quality provided by ISO-9126. They are grouped into architecture, operation and business perspective and each quality factors are specified.

Web Services quality factors refer to groups of items that use for representing and valuing the quality of Web services.

Web Services quality factors can be divided into the system information quality group, service measurement quality group and business value quality group in the point of use by consumer. (Please refer to )

[pic]

Structure of Web Services quality factor

Business value quality group refers to a group of referenced quality factors that they can be referred as for deciding the business value of service when consumer chooses a particular Web Services. Business value quality is consisted of service cost, service suitability, service aftereffect and service brand value.

Service measurement quality group refers to a group of measurable quality factors which can be measured while consumer uses the Web Services. They are consisted of response time, maximum throughput, accessibility and successability. The measurement value of the quality factor in this service measurement group can be dynamically varied while service is being used. Service level measurement quality is consisted of performance and stability.

System information quality group refers to a group of qualities which are about the systematic functionality of Web Services that they can be recognized and evaluated before consumer uses the service. They are consisted of suitability for standards, business process quality, manageability quality and security quality. All the factors in this quality group will be determined as soon as the service development is completed. Firstly, suitability for standards is consisted of conformability and interoperability. Secondly, business process quality is consisted of message reliability, transaction processing ability and business process collaboration ability. Thirdly, manageability quality is consisted of management information offerability, observability and controllability. Fourthly, security quality is consisted of confidentiality, integrity, authentication, access control, non-repudiation, availability, traceability, privacy and distributed authorization.

A. Acknowledgements

The following individuals have participated in the creation of this specification and are gratefully acknowledged:

Participants:

B. Non-Normative Text

C. Revision History

|Revision |Date |Editor |Changes Made |

| | | | |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download