ISO/IECJTC1/SC32/WG 2 Nxxxx
Date:2012-12-30
ISO/IEC CD 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 CD 19763-7:2012(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.
ContentsPage
Foreword......
Introduction......
1Scope......
2Normative references......
3Terms, definitions and abbreviated terms......
3.1Terms and definitions......
3.1.1service
3.1.2service operation
3.1.3qos type
3.1.4qos assertion
3.1.5input message
3.1.6output message
3.1.7precondition
3.1.8postcondition
3.1.9exitcondition
3.1.10user tag
3.1.11expression
3.1.12atomic expression
3.1.13composite expression
3.1.14entity Service
3.1.15task Service
3.1.16utility Service
3.1.17service involvement
3.1.18message type......
3.2Abbreviated terms
4Conformance......
4.1General......
4.2Degree of conformance......
4.2.1General......
4.2.2Strictly conforming implementation......
4.2.3Conforming implementation......
4.3Implementation Conformance Statement (ICS)......
5Structure of MFI Service registration......
5.1 Overview of MFI Service registration
5.2 Associations between MFI Service registration and MFI Core and mapping
5.3 Detail Provided in each metaclass definition......
5.4 MFI Service registration
5.4.1 Service
5.4.2 Service_Description_Language
5.4.3 Service_Model
5.4.4 QoS_Type
5.4.5 QoS_Assertion
5.4.6 Expression
5.4.7 Atomic_Expression
5.4.8 Composite_Expression
5.4.9 Service_Operation
5.4.10 Precondition
5.4.11 Postcondition
5.4.12 Exit_Condition
5.4.13 Input_Message
5.4.14 Output_Message
5.4.15 User_Tag
5.4.16 TypeOfService
5.4.17Service_Involvement
5.4.18 Message_Type
Annex A (informative) List of existing Service description languages
Annex B (informative) Example......
B.1 Example of WSMO Service Registration
B.2 Example of WADL Service Registration
B.3 Example of OWL-S Service Registration
B.4 Example of WSDL Service Registration
Bibliography......
Figures
Figure1— Scope of MFI Service registration
Figure 2 - Metamodel of MFI Service registration
Figure 3 - The associations between MFI Service Registration and MFI Core and mapping
Tables
Table A 1 - List of Existing ServiceDescriptionLanguages
Table B.1 1 - Model of “Book Ticket Web Service of WSMO” (fragment)
Table B.2 1 - Model of “Amazon search items Web Service of WADL” (fragment)
Table B.3 1 - Model of “A B2C book buying Service example of OWL-S” (fragment)
Table B.4 1 - WSDL 2.0 Model for the GreatH Web Service (fragment)
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
Part3: Metamodel for ontology registration
Part 5: Metamodel for process model registration
Part 6: Registration procesure
Part 7: Metamodel for Service registration
Part 8: Metamodel for role and goal registration
Part 9: On Demand Model Selection based on RGPS [Technical Report]
Part 10: Core model and basic mapping
Part11: Structured model registering [Technical Report]
Part 12: Metamodel for information model registration
Part 13: Metamodel for forms registration
Introduction
With the rapid development of 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. A web service is a kind of Web based application which encapsulates one or more computing modules and is designed to support interoperable machine-to-machine interaction over a network.
In Web Service registration and management, ebXML RegRep is a standard defining the Service interface, protocols and information model for an integrated registry and repository, which provides basic support for publishing and discovering Web Services within and across enterprises. Nevertheless,keyword matching is the basic service discovery method in ebXML RegRep, 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 non-functional information aboutservices in an explicit way.
©ISO/IEC 2012 – All rights reserved / 1ISO/IEC CD 19763-7:2012(E)
Information technology – Metamodel framework for interoperability (MFI) – Part 7: Metamodel for Service registration
1Scope
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 improveinteroperabilitythroughthe reuse ofservices.
This part of ISO/IEC 19763 can be applicable only for Web Services whose capability is described by some web service description language. Figure 1 shows the scope of this part of ISO/IEC 19763.
NOTE: Not every model needs to exist in a repository before registration
Figure1— Scope of MFI Service registration
2Normative 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-3:2010, Information technology – Metamodel Framework for Interoperability (MFI) – Part 3: Metamodel for ontology registration
ISO/IEC 19763-10, Information technology – Metamodel framework for interoperability (MFI) – Part 2:Core model and basic mapping
3Terms, definitions and abbreviated terms
3.1Terms and definitions
The definitions provided in ISO/IEC 19763-10, ISO/IEC 19763-3:2010, ISO/IEC 19763-5, ISO/IEC 19763-8,shall apply to this part of ISO/IEC 19763.
3.1.1service
kind of Web based application, which encapsulates one or more computing modules and can be accessed througha specified interface
3.1.2service operation
execution action of aservice
3.1.3qos type
specifiednon-functionalproperty for aservice, such as availability, response time, etc.
3.1.4qos assertion
specification of one or more qos types fortheservice
3.1.5inputmessage
information contained inthe message that the service consumes for its execution
3.1.6outputmessage
informationcontained in the message that the service operation generates after its execution
3.1.7precondition
state that shall exist before a process or serviceoperation is invokedsuccessfully
NOTE: the associated metaclass defined in this part is also used by 19763-5: metaclass for process model registration
3.1.8postcondition
state that shall exist after a process or service operation is successfullyinvoked
NOTE: the associated metaclass defined in this part is also used by 19763-5: metaclass for process model registration
3.1.9exitcondition
state that shall exist when a process or service operation exits abnormally
NOTE: the associated metaclass defined in this part is also used by 19763-5: metaclass for process model registration
3.1.10user tag
tag annotated by an individual or organization in order to describe the service according to the understanding of thecreator of the tag
3.1.11expression
sentence which is described by a kind oflogical notation to express a fact
3.1.12atomic expression
logical expression that has the unit granularity
3.1.13composite expression
logical expressionthat comprises multiple atomic expressions by using connectives such as conjunction, disjunction and negation
3.1.14entity Service
Webservice that bases its functional boundary on one or more related organization entities, such as customer, employee, invoice and claim
3.1.15task Service
Webservicewith a functional boundary directly associated with a process model
3.1.16utility Service
Web service that is dedicated to provide reusable, cross-cutting utility functionality, such as event logging, notification, and except handling
3.1.17service involvement
specification about how a particular role is involved in this service
3.1.18message type
type of the message that is consumed or generated for execution of service operation
3.2Abbreviated terms
ebXML RegRep
ebXML Registry and Repository (See OASIS ebXML RegRep Version 4.0: 2012)
IRI
Internationalized Resource Identifier (See W3C RFC 3987: 2005)
MFI Core
ISO/IEC 19763-10, Information technology –Metamodel Framework for Interoperability – Part-2 : Core model and basic mapping
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 PMR
ISO/IEC 19763-5, Information technology –Metamodel Framework for Interoperability (MFI)– Part-5: Metamodel for process models registration
MFI Role and Goal registration
ISO/IEC 19763-8, Information technology –Metamodel Framework for Interoperability (MFI)– Part-8: Metamodel for role and goal registration
OWL-S
Web Ontology Language for Services (Seebibliography item [7])
QoS
Quality of Service (See bibliography item [9])
SWRL
A Semantic Web Rule Language (See bibliography item [10])
WADL
Web Application Description Language (See bibliography item [6])
WSDL
Web Service Description Language (See bibliography item [3])
WSML
A Web Service Modelling Language (See bibliography item [5])
WSMO
Web Service Modelling Ontology (See bibliography item [11])
4Conformance
4.1General
An implementation claiming conformance with this part of ISO/IEC 19763 shall support the metamodel specified in 5, depending on a degree of conformance as described below.
4.2Degree of conformance
4.2.1General
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.
4.2.2Strictly conforming implementation
A strictly conforming implementation
a) shall support the metamodel specified in 5;
b) shall not support any extensions to the metamodel specified in 5.
4.2.3Conforming implementation
A conforming implementation
a) shall support the metamodel specified in 5;
b) may support extensions to the metamodel specified in 5 that are consistent with the metamodel specified in 5.
4.3Implementation 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 (4.2);
b) what extensions are supported if it is a conforming implementation.
5Structure of MFI Service registration
5.1 Overview of MFIService registration
This part of MFI specifies the metamodel that can be used to register functional and non-functional information about services. This metamodel supports the registration of informationin service descriptions expressed in the service description languages listed in Annex A.
Figure 2 shows the metamodel for the registration of services. This metamodel allows the registration of the common functional and non-functional features of services described using a number of service description languages.Each service model, expressed using a specific service description language, may describe one or more services.Each service is comprised of one or more service operations. Each service is described by zero or one QoS assertion. This QoS assertion is used to represent the quantitative or qualitative non-functional features of the service, such as response time, cost, reliability, etc. Each QoS assertion is defined using one and only one expression, which may be a composite expression or an atomic expression.Each QoS assertion is of one or more QoS types.
Figure2 -Metamodel of MFI Service registration
A service is an independent and modular component and it can be accessed only by interfaces. For this reason the functional capability of a service is expressed using service operations, where each service operation denotes an execution action of the service. Each service is comprised of one or more service operations.
Each service operation is described with zero or one pre-condition and with zero or one post condition. A pre-condition specifies the state that shall be satisfied before a service operation is invoked and a post-condition specifies the state that shall be satisfied after a service operation is invoked successfully. Each pre-condition and each post-condition is defined using one and only one expression, which may be a composite expression or an atomic expression.Each service operation is also described with zero, one or more input messages and with zero, one or more output messages. Each input message specifies information that the operation needs for its execution. Each output message specifies information that the operation generates after its successful execution. Each input message is constrained by zero, one or more pre-conditions and each output message is constrained by zero, one or more post conditions.Service can be annotated by user tags which are created by all the people using the service.In order to add semantic information for a service, an annotation, a reference to domain ontology, can be provided for each service, service operation, input message and output message.
Figure 2 also shows the associations between MFI Service registration and MFI Role and Goal registration, MFI PMR and MFI Ontology registration. Eachserviceachieveszero, one or more goals.Each goal is achieved by zero, one or moreservices. Each service operation achieves zero, one or more goals.Each goal is achieved by zero, one or more service operations.Each service operation can fully realize zero, one or more processes. Each process is fully realized by zero, one or more services. Each service operation aggregates zero, one or more service involvements. Each service involvement can be involved in one service operation. Each role can be involved in zero, one or more service involvement. Each service involvement can involve only one role.
5.2 Associations between MFIService registration and MFI Core and mapping
The relationship between the metaclasses in MFI Service registration and the metaclasses in MFI Core is shown in Figure 3. Service_Description_Language in MFI Serviceregistration is the subclass of Model_Language in MFI Core and mapping. Service_Model in MFI Serviceregistration is the subclass of Model in MFI Core and mapping. All the remaining metaclasses are the subclasses of Model_Element in MFI Core and mapping. On the other hand, the association between Service_Model and Service_Description_Language is a specialization of the association between Model and Modeling_Language in MFI Core and mapping. The association between Service_Model and Service is a specialization of the association between Model and Model_Element in MFI Core and mapping.
Figure 3 - The associations between MFI Service Registration and MFI Core and mapping
5.3 Detail Provided in each metaclass definition
For each metaclass the following detail is shown:
1)A definition that describes the role or significance of instances of the metaclass.
2)The name of its immediate supertype.
3)Any alternative names (synonyms or aliases) for the metaclass.
4)A list of attributes.
5)A list of references.
For each attribute the following detail is shown:
1)The name of the attribute; where the attribute is the one that is provided by the type defined in the MDR metamodel by which the instances of metaclasses are extended the name is italicised.
2)The datatype for values of the attribute.
3)The multiplicity of the attribute.
4)A description that describes the role or significance of values of the attribute.
For each reference the following detail is shown:
1)The name of the reference; this is the role name that describes the role played by the referenced metaclass with respect to the association identified by this reference.
2)The name of the referenced metaclass.
3)The multiplicity of the reference.
4)A description that describes the role or significance of the instance, or instances, of the referenced metaclass with respect to an instance of this metaclass.