ISO/IECJTC1/SC32/WG 2 N1512
Date:2011-03-25
ISO/IEC WD2 19763-7
ISO/IECJTC1/SC32/WG2
Secretariat:ANSI
Information technology – Metamodel framework for interoperability
(MFI) Part 7: Metamodel for service registration
Warning
This document is not an ISO International Standard. It is distributed for review and comment. It is subject to change without notice and may not be referred to as an International Standard.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation.
ISO/IEC WD2 17963-7:2011(E)
Copyright notice
This ISO document is a working draft or committee draft and is copyright-protected by ISO. While the reproduction of working drafts or committee drafts in any form for use by participants in the ISO standards development process is permitted without prior permission from ISO, neither this document nor any extract from it may be reproduced, stored or transmitted in any form for any other purpose without prior written permission from ISO.
Requests for permission to reproduce this document for the purpose of selling it should be addressed as shown below or to ISO's member body in the country of the requester:
[Indicate the full address, telephone number, fax number, telex number, and electronic mail address, as appropriate, of the Copyright Manger of the ISO member body responsible for the secretariat of the TC or SC within the framework of which the working document has been prepared.]
Reproduction for sales purposes may be subject to royalty payments or a licensing agreement.
Violators may be prosecuted.
Contents Page
Foreword v
Introduction vi
1 Scope 1
2 Conformance 1
2.1 General 1
2.2 Degree of conformance 2
2.2.1 General 2
2.2.2 Strictly conforming implementation 2
2.2.3 Conforming implementation 2
2.3 Implementation Conformance Statement (ICS) 2
3 Normative references 3
4 Terms, definitions and abbreviated terms 3
4.1 Terms and definitions 3
4.2 Broad terms 3
4.3 Abbreviated terms 3
5 Structure of MFI Service registration 4
5.1 Overview of MFI Service registration 4
5.2 Relationship between MFI service registration and other parts in MFI 5
5.3 MFI Service registration 6
5.3.1 Service 6
5.3.2 Quality_Property 6
5.3.3 QoSAssertion 6
5.3.4 LogicalExpr 6
5.3.5 Predicate 7
5.3.6 Argument 7
5.3.7 Operation 8
5.3.8 Precondition 8
5.3.9 Postcondition 8
5.3.10 Input 9
5.3.11 Output 9
Annex A (informative) List of existing service description languages 10
Annex B (informative) Example 11
B.1 Example of WSMO Service Registration 11
B.2 Example of WADL Service Registration 13
Figures
Figure1— Scope of MFI service registration 1
Figure 2 - Metamodel of MFI service registration 5
Figure 3 – Relationship between MFI service registration and other parts in MFI 5
Tables
Table A.1 – List of Existing Service Description Languages 10
Table B.1.1 - Code of “Book Ticket Web Service” (fragment) 11
Table B.1.2 – Service Registration Information………………………………………………………………………12
Table B.1.3 – Operation00 Registration Information…………………………………………………………………12
Table B.1.4 Input & Output Registration Information………………………………………………………………...12
Table B.1.5 – Precondition02 Registration Information……………………………………………………………...13
Table B.2.1 – Code of “Amazon search items Web Service”……………………………………………………….13
Table B.2.2 - “Amazon search items Web Service” according to MFI Service Registration…………………….15
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IECJTC1.
International Standards are drafted in accordance with the rules given in the ISO/IECDirectives, Part2.
The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75% of the national bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
ISO/IEC197637 was prepared by Joint Technical Committee ISO/IECJTC1, Information Technology, Subcommittee SC32, Data management and Interchange.
ISO/IEC19763 consists of the following parts, under the general title Information technology— Metamodel framework for interoperability (MFI):
Part1: Reference model
Part2: Core model
Part3: Metamodel for ontology registration
Part4: Metamodel for model mapping
Part 5: Metamodel for process model registration
Part6: Registration Process
Part 7: Metamodel for service registration
Part 8: Metamodel for role and goal registration
Part 9: Registry of Registries
TR: Using RGPS for on demand model selection
Introduction
Due to the spread of e-Business and e-Commerce over the Internet, the effective interchange of business transactions or other related information across countries and cultures is an important concern for people in both the IT industry and other non-IT industries.
With the rapid development of SOA (Service Oriented Architecture) and SOC (Service Oriented Computing), more and more computing resources are presented in the form of Web services. Meanwhile, business integration based on Web services is becoming a popular application development method. Web service is a kind of Web based application, which encapsulates certain computing module and is designed to support interoperable machine-to-machine interaction over a network.
In Web service registration and management, UDDI is a widely applied specification, which provides basic support for publishing and discovering Web services within and across enterprises. Keyword matching is the basic service discovery method in UDDI, thus the discovery results will be inevitably inaccurate, and the discovery process will be time-consuming. When business information interchange and integration becomes increasingly frequent, major work in service discovery should be processed by machine, therefore, it is necessary to semantically describe service information including functional and non-functional information, and provide corresponding registration and management mechanism.
This part of ISO/IEC 19763 intends to provide a generic framework for registering functional and nonfunctional information of services in an explicit way.
©ISO/IEC 2011 – All rights reserved / vISO/IEC WD2 17963-7:2011(E)
Information technology – Metamodel framework for interoperability (MFI) – Part 7: Metamodel for service registration
1 Scope
The primary purpose of the multipart standard ISO/IEC 19763 is to specify a metamodel framework for interoperability. This part of ISO/IEC 19763 specifies a metamodel for registering services that can enable users to discover appropriate services.
The metamodel that this part specifies is intended to promote interoperation between various services.
It does not specify industry categorization of services and contact information of service providers, which are specified in UDDI.
Figure 1 shows the scope of this part of ISO/IEC 19763.
Figure1— Scope of MFI service registration
2 Conformance
2.1 General
An implementation claiming conformance with this part of ISO/IEC 19763 shall support the metamodel specified in 5.3, depending on a degree of conformance as described below.
2.2 Degree of conformance
2.2.1 General
The distinction between “strictly conforming” and “conforming” implementations is necessary to address the simultaneous needs for interoperability and extensions. This part of ISO/IEC 19763 describes specifications that promote interoperability. Extensions are motivated by needs of users, vendors, institutions and industries, but are not specified by this part of ISO/IEC 19763.
A strictly conforming implementation may be limited in usefulness but is maximally interoperable with respect to this part of ISO/IEC 19763. A conforming implementation may be more useful, but may be less interoperable with respect to this part of ISO/IEC 19763.
2.2.2 Strictly conforming implementation
A strictly conforming implementation
a) shall support the metamodel specified in 5.1;
b) shall not support any extensions to the metamodel specified in 5.1.
2.2.3 Conforming implementation
A conforming implementation
a) shall support the metamodel specified in 5.1;
b) may support extensions to the metamodel specified in 5.1 that are consistent with the metamodel specified in 5.1.
2.3 Implementation Conformance Statement (ICS)
An implementation claiming conformance with this part of ISO/IEC 19763 shall include an Implementation Conformance Statement stating
a) whether it is a strictly conforming implementation or a conforming implementation (2.2);
b) what extensions are supported if it is a conforming implementation.
3 Normative references
The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 19763-1, Information technology – Metamodel framework for interoperability (MFI) – Part 1: Reference model
ISO/IEC 19763-2, Information technology – Metamodel framework for interoperability (MFI) – Part 2: Core model
ISO/IEC 19763-3, Information technology – Metamodel framework for interoperability (MFI) – Part 3: Metamodel for ontology registration
ISO/IEC 19763-5, Information technology – Metamodel framework for interoperability (MFI) – Part 5: Metamodel for process model registration
ISO/IEC 19763-8, Information technology – Metamodel framework for interoperability (MFI) – Part 8: Metamodel for Role & Goal registration
4 Terms, definitions and abbreviated terms
4.1 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC 19763-1, ISO/IEC 19763-3 ISO/IEC 19763-5 and the following apply.
4.2 Broad terms
4.2.1
Service
a kind of Web based application, which encapsulates certain computing module and can be accessed by certain interface.
4.3 Abbreviated terms
MFI Core
ISO/IEC 19763-2, Information technology –Metamodel Framework for Interoperability – Part-2 : Core model
MFI Service registration
ISO/IEC 19763-7, Information technology – Metamodel framework for interoperability (MFI) – Part 7: Metamodel for service registration
MFI Ontology registration
ISO/IEC 19763-3, Information technology – Metamodel framework for interoperability (MFI) – Part 3: Metamodel for ontology registration
MFI Process registration
ISO/IEC 19763-5, Information technology –Metamodel Framework for Interoperability (MFI) – Part-5: Metamodel for process models registration
UDDI
Universal Description, Discovery, and Integration
WSDL
Web Service Description Language
OWL-S
Web Ontology Language for Services
WSMO
Web Service Modelling Ontology
WADL
Web Application Description Language
5 Structure of MFI Service registration
5.1 Overview of MFI Service registration
This part of MFI describes administrative information of services, including functional and nonfunctional description.
As Figure 2 shows, MFI service registration metamodel is provided to capture the common functional and nonfunctional information of various kinds of services. Service aggregates multiple Quality_Property and multiple Operation. The nonfunctional description is depicted by Quality_Property, which can be used to represent the quantitative or qualitative value of service in certain aspect such as response time, cost, reliability, and so on. An observable property of a service that can be retrieved at execution time is described by QoSAssertion, which may have one or multiple LogicalExpr. A LogicalExpr has one predicate, and one or two argument.
As for the functional description, since a service is an independent and modular component and it can be accessed only by interfaces, a service’s functionality is embodied in multiple Operation. Operation is used to denote the execution action. An operation has Precondition and Postcondition, which are essential to invoking and executing the service. Precondition is used to specify the state that should be satisfied before a service is invoked, while Postcondition is used to specify the state that should be satisfied after a service is invoked successfully. Same as QoSAssertion, Precondition and Postcondition are also expressed with LogicalExpr. Apart from Precondition and Postcondition, Operation has Input and Output. Input is constrained by Precondition, and Output is constrained by Postcondition.
In order to add semantic information for service, Input, Output, Precondition, Postcondition, Operation, Predicate and Argument have a property of annotation, which are annotated by the concepts of domain ontology.
Figure 2 - Metamodel of MFI service registration
5.2 Relationship between MFI service registration and other parts in MFI
Figure 3 shows the relationship between MFI service registration and other parts in MFI. That is, Service can perform one Process specified in MFI process registration. Service can achieve one Goal and be invoked by one or multiple Role specified in MFI Role & Goal registration.
Some metaclasses will inherit Ontology_Atomic_Construct in MFI ontology registration such as Operation. See Figure 2, other metaclasses include Input, Output, Predicate and Argument.
Figure 3 – Relationship between MFI service registration and other parts in MFI
5.3 MFI Service registration
5.3.1 Service
Service is a metaclass representing an independent and modular component on the Internet.Attribute / DataType / Multiplicity / Description
name / String / 1..1 / Name of the corresponding service
URI / String / 1..1 / URI where the corresponding service exists
Reference / Class / Multiplicity / Description
Aggregation / Quality_Property / 1..* / Certain quality feature of Non-functional description of the corresponding service
Aggregation / Operation / 1..* / Operations that denote the execution actions of the service
Constraints
The value of attribute “URI” has to be unique in this metaclass.
5.3.2 Quality_Property
Quality_Property is a metaclass that is used to represent a certain Non-functional feature for service, such as availability, response time, etc.Attribute / DataType / Multiplicity / Description
type / String / 1..* / Type of the Non-functional feature
Reference / Class / Multiplicity / Description
used in / QoSAssertion / 1..* / An atom description of a certain Non-functional property for service
5.3.3 QoSAssertion
QoSAssertion is a metaclass that is used to represent an atom description of a certain Non-functional property for service.
Attribute / DataType / Multiplicity / Descriptionname / String / 1..1 / Name of corresponding QoSAssertion
Reference / Class / Multiplicity / Description
uses / Quality_Property / 1..* / A certain Non-functional feature for service, such as availability, response time, etc.
hasLogicalExpr / LogicalExpr / 1..* / An assertion have one or multiple logical expressions
5.3.4 LogicalExpr
LogicalExpr is a metaclass that represents logical expression within QoSAssertion, Precondition or Postcondition.