<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Extending OWL for QoS-based Web Service Description and Discovery</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Main Theme of Thesis</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>University of Crete</institution>
          ,
          <addr-line>Heraklion</addr-line>
          ,
          <country country="GR">Greece</country>
        </aff>
      </contrib-group>
      <fpage>73</fpage>
      <lpage>78</lpage>
      <abstract>
        <p>Web Services (WSs) are modular, self-describing, loosely-coupled, platform and programming language-agnostic software applications that can be advertised, located and used across the Internet. They are viewed as one of the promising technologies that could help business entities to automate their operations on the web on a large scale by automatic discovery and consumption of services. Based on the above reasons, the WS paradigm is being adopted by many companies and individuals and many WSs are being deployed and running. However, as all of these WSs are advertised in a UDDI-based repository, an unavoidable fact as UDDI is a de-facto standard, the problem of discovering them based on a requester's functional needs becomes crucial. UDDI uses a syntaxbased approach for WS description leading to purely syntactic discovery e®orts returning imprecise and inaccurate results. OWL-S [OWL-S Coalition 2003] and similar joint Semantic Web and WS e®orts solve the problem of syntactic WS description by using ontologies for describing WSs. Ontologies provide meaning to concepts and relationships between them, leading to semantic WS Discovery algorithms, which provide more precise and accurate results. But even if all the advertised WSs satisfying a requester's functional needs are returned, many results may be produced. So a non-functional concept is needed that will di®erentiate between the functionally equivalent WS advertisements. This concept is quality of service (QoS). QoS is closely related with the performance of a WS as well as with other features of a WS that bear on its ability to satisfy stated or implied needs. Therefore it has a substantial impact on users' expectations from a service. Thus WS descriptions must be enhanced with QoS descriptions. Additionally, WS discovery algorithms should perform QoS-based matchmaking and selection in order to produce fewer ranked results. Unfortunately, all the current research e®orts fail in correctly describing QoS for WSs. Semantics seems to be missing from the QoS description of a WS leading to purely syntactic QoS-based WS matchmaking and selection algorithms. But even if semantics is introduced, QoS description is not rich enough and not quite extensible. So the main issue of this PhD thesis is the rich, extensible, and semantic description of QoS for WSs. Additionally, new QoS-based WS matchmaking and selection algorithms must be devised or the current best should be extended in order to take advantage of this enhanced semantic QoS description.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Motivation for Research</title>
      <p>After reviewing several de¯nitions for QoS for WSs, we consider QoS for a WS
as "a set of non-functional characteristics/attributes that may impact the quality
of the service o®ered by the WS ". If a WS is advertised to have certain values (or
range of values) in these QoS attributes, then it is said that this WS conforms
to a certain QoS level. In this section we explain the reasons for incorporating
QoS in WS description.</p>
      <p>
        According to [
        <xref ref-type="bibr" rid="ref2">Cardoso et. al. 2004</xref>
        ], several researchers have identi¯ed Web
Processes (WPs) as the computing model that enables a standard method of
building Web-services applications and processes to connect and exchange
information over the Web. For organizations, the ability to characterize WPs based
on QoS has four distinct advantages. First, it allows organizations to
translate their vision into their business processes more e±ciently, since WPs can be
designed according to QoS metrics. For e-commerce processes it is important
to know the QoS an application will exhibit before making the service available
to customers. Second, it allows for the selection and execution of WPs based
on their QoS, to better ful¯l customer expectations and requirements. Third,
it makes possible the monitoring of WPs based on QoS to assure compliance
both with initial QoS requirements and targeted objectives. QoS monitoring
allows adaptation strategies to be triggered when undesired metrics are identi¯ed
or when threshold values are reached. Fourth, it allows for the evaluation of
alternative strategies when adaptation becomes necessary. It is essential that
the services rendered follow customer speci¯cations to meet their expectations
and ensure satisfaction. Customer expectations and satisfaction can be translated
into the quality of service rendered. Organizations have realized that quality of
service management is an important factor in their operations.
      </p>
      <p>As WPs are composed or single WSs, all the above advantages of QoS
management of WPs also apply to WSs. So WSs can be designed and implemented
according to QoS metrics (properties). They can also be discovered and selected
based on their QoS capabilities. In addition, they can be monitored in order to
reassure the promised QoS levels to the customers. Moreover, monitoring of QoS
for WSs can trigger adaptation strategies when undesired metrics are identi¯ed,
threshold values are reached, network or software or hardware errors happen.
Now, we will closely examine the advantages of QoS description (management)
in other non-basic activities/functions of the Service Oriented Architecture.</p>
      <p>After the process of WS Selection, the requester chooses the best WS from
an ordered WS advertisement list. However, even if WS clients ¯nd the
appropriate WS, they are not con¯dent that the WS's described QoS levels will actually
be delivered during WS execution. For this reason, the WS client and provider
enter a multi-step negotiation phase, where they try to agree on a trusted
third-party entity monitoring QoS levels delivered, on the penalties that will be
imposed when one of the two main parties does not keep up with its promises,
and on the validity period of the promises. The result of this negotiation phase
is a contract or a Service Level Agreement (SLA) document that will give
con¯dence and trust to the entities providing and consuming the service and will
lead and guide the process of WS Execution. If agreement is not met, the
negotiation is stopped and the WS client contacts the next WS from the returned
list of the WS Selection phase.</p>
      <p>
        When composing a WS, component services are associated to the
individual tasks of the composite WS and are invoked during each execution of
the WS. However, the number of services providing a given functionality may
be large and constantly changing and some of these services will not always be
available due to network problems, software evolution and repair, and hardware
problems. One solution to this problem is given at design time by QoS-based
WS discovery. Another solution is the runtime selection of component
services, during the execution of a composite WS, based on quality criteria (i.e.
constraints and preferences) and following a local [
        <xref ref-type="bibr" rid="ref1">Benatallah et. al. 2002</xref>
        ] or a
global [
        <xref ref-type="bibr" rid="ref12">Zeng et. al. 2003</xref>
        ] selection strategy. In the latter case, service selection
is formulated as an optimization problem and linear programming is used to
compute optimal execution plans for composite services.
3
      </p>
    </sec>
    <sec id="sec-2">
      <title>Review of Related Work</title>
      <p>In this section, the current research approaches for QoS-based WS Description
and Discovery are described and their de¯ciencies are analyzed.</p>
      <p>The Web Service Description Language (WSDL) and UDDI WS
standards are syntactical approaches that do not express the QoS aspect/part of
WS Description. While OWL-S is a standard semantic approach for WS
Description, it does not describe QoS o®ers or demands as it only contains an
attribute used for rating a WS.</p>
      <p>
        [
        <xref ref-type="bibr" rid="ref10">Tosic et. al. 2002</xref>
        ] argue that for the speci¯cation of constraints for QoS
metrics/attributes, ¯ve ontologies must be developed from which the most
important (the top one) is the metrics ontology. They describe the structure and
involved elements in four out of the ¯ve ontologies but they did not develop any
ontology. In addition, the requirements speci¯ed are incomplete as each from the
four aspects of QoS description needs further analysis.
      </p>
      <p>
        In [Shuping
        <xref ref-type="bibr" rid="ref8">Ran 2003</xref>
        ], an extension to UDDI is proposed that represents
description of QoS information about a particular WS. However, there is no
actual description of the contents of this extension apart from its structure.
Moreover, it relies on the UDDI (model), so it can be used only for syntactic
matchmaking of o®ers and demands.
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref5">Maximilien and Singh 2002</xref>
        ], an architecture and a conceptual model
of WS reputation (QoS) (which encloses a QoS attributes model) are presented.
However, the reputation of a WS is calculated and not it's QoS. In addition, not
only concepts like QoS constraints and QoS o®ers and demands are not modeled
but also the QoS metrics model is not rich enough.
      </p>
      <p>
        Work described in [
        <xref ref-type="bibr" rid="ref11">Tosic et. al. 2003</xref>
        ], which presents the Web Service
O®erings Language (WSOL), proposes that a WS must o®er di®erent classes
of service in order to satisfy a greater amount and type of customers and in
order to deal successfully with situations where there is a variation in QoS due
to network problems or mobility reasons. This work comes with the following
shortcomings: (a) no separation and integration of constraint dimensions; (b) no
speci¯cation of a QoS demand; (c) the metrics ontologies are not yet developed.
      </p>
      <p>
        The research e®ort described in [
        <xref ref-type="bibr" rid="ref9">Tian et. al. 2003</xref>
        ] analyzes what must be
enclosed into the QoS information for a WS request or advertisement with the
help of a QoS ontology. However, not only there is not a complete and accurate
description of QoS constraints but also metrics ontologies are not developed but
just referenced.
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref13">Zhou et. al. 2004</xref>
        ], DAML-S WS description language is extended to
include a QoS speci¯cation ontology. In addition, a novel QoS matchmaking
algorithm is proposed, which is based on the concept of QoS pro¯le
compatibility. The de¯ciencies of this research e®ort are the following: (a) The metrics
model is not rich enough; (b) QoS metrics have the set IN+ as their range;
(c) DL reasoners are slow and do not support the most complex mathematical
expressions.
      </p>
      <p>
        The research e®ort described in [
        <xref ref-type="bibr" rid="ref4">Mart¶³n-D¶³az et. al. 2003</xref>
        ] uses a
symmetric QoS model expressing mathematical constraints for QoS metrics.
However, semantics is missing leading to syntactic matchmaking and selection
algorithms. Before matchmaking, a QoS speci¯cation is transformed to a
Constraint Satisfaction Problem (CSP) [
        <xref ref-type="bibr" rid="ref3">Hentenryck and Saraswat 1996</xref>
        ] which
is checked for consistency (if it has any solution). Matchmaking is performed
according to the concept of conformance (if every solution of o®er is a solution
of demand). Concerning WS Selection, the (QoS) score of a WS advertisement
is expressed as a Constraint Satisfaction Optimization Problem (CSOP)
[
        <xref ref-type="bibr" rid="ref3">Hentenryck and Saraswat 1996</xref>
        ] where from all solutions to the CSP of an o®er
we try to ¯nd the one that minimizes the weighted sum of the weight of each
metric multiplied with its utility assessment value. Unfortunately, CS(O)Ps can
have non-polynomial solutions when there are non-linear expression at QoS
constraints.
4
      </p>
    </sec>
    <sec id="sec-3">
      <title>Future Work of the Thesis</title>
      <p>Based on the previously analyzed research work, we propose the following steps
that must be taken to address the issues of the thesis; the ful¯lment of which will
lead to correct, e±cient and accurate QoS-based WS Description and Discovery
processes. Some of them have already been performed while the other will be
dealt with in the future. These steps are:</p>
      <p>Requirements for QoS-based WS Description: This step has already
been taken. We have come up with the following requirements:
{ Extensible and formal semantic QoS model
{ Standards compliance
{ Syntactical separation of QoS-based and functional parts of service
speci¯cation
{ Both requester and provider QoS speci¯cation
{ Re¯nement of QoS speci¯cations (extensibility, reusability)
{ Fine-grained QoS speci¯cation (QoS specs for the whole WS and its parts)
{ Extensible and formal QoS attribute/metric model which must at least
specify: (a) The value set of the attribute; (b) The domain of knowledge of the
attribute; (c) The relationship of the attribute with other attributes; (d)
The association of the attribute with a unit, a measured property and a
measurement function; (e) A functional description of how a QoS attribute
of a complex WS can be derived from the corresponding QoS attribute of
the individual WSs that constitute the complex one.
{ Classes of service (an advertisement should present many o®ers)</p>
      <p>QoS-based WS Description : Based on the above requirements, a
QoSbased WS ontology has been developed with the name OWL-Q. This ontology
extends OWL-S (standard) WS Description ontology and is carefully separated
into many facets, each capturing one aspect of QoS WS (metric) description
except from the basic one that associates OWL-S elements with OWL-Q
elements. This ontology satis¯es the above requirements and enables the semantic
matchmaking of QoS advertisements and o®ers.</p>
      <p>Semantic QoS metric matchmaking: Based on the OWL-Q ontology, we
have developed an algorithm that semantically matches QoS metrics of demands
and o®ers. This algorithm can be used as a building block for the QoS-based WS
matchmaking and selection algorithms. For matchmaking simple metrics, this
algorithm compares the type and measurement directive of the metrics, while
for composite metrics it also compares the metrics' measurement functions.</p>
      <p>
        Develop a new or extend an old QoS-based WS
matchmaking algorithm: We have extended the matchmaking algorithm proposed in
[
        <xref ref-type="bibr" rid="ref4">Mart¶³n-D¶³az et. al. 2003</xref>
        ] in order to incorporate the semantic QoS metric
matchmaking algorithm. To be more speci¯c, when transforming QoS o®ers and
demand to CSPs, we are careful to assign same metrics to same CSP variables
and to perform unit transformation of the same metrics.
      </p>
      <p>
        Develop a new or extend an old QoS-based WS selection algorithm:
We have extended the selection algorithm proposed in [
        <xref ref-type="bibr" rid="ref4">Mart¶³n-D¶³az et. al. 2003</xref>
        ]
in order to incorporate the semantic QoS metric matchmaking algorithm. To be
more speci¯c, when transforming QoS o®ers to CSOPs, we are careful to assign
same metrics to same CSP variables and to perform unit transformation of the
same metrics. We have also changed the scoring function: now this function is
the partial sum of the minimum and maximum assessment sums. That is we
solve two CSOPs for the same o®er and then we perform a partial sum of their
results.
      </p>
      <p>
        Implement these matchmaking and selection algorithms: This is a
step under development. The implementation uses an OWL inference engine for
the semantic QoS metric matching and the ECLiPSe [
        <xref ref-type="bibr" rid="ref6">Novello and Schimpf 1999</xref>
        ]
engine for solving CS(O)Ps.
      </p>
      <p>Formal evaluation of the above algorithms: The above three algorithms
should be formally evaluated in order to prove that they are e±cient, quick,
accurate and precise.</p>
      <p>Extend the ontology and the algorithms: After performing all the above
steps, OWL-Q ontology should be extended to include other non-functional
descriptions of WSs (mainly contextual ones) and its design must be ¯nalized. In
addition, the QoS-based matchmaking algorithm must be extended in order to
distinguish between soft and hard non-functional constraints.</p>
      <p>Tools: GUIs and other utilities should be constructed that will help the user
in describing and discovering WSs.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <string-name>
            <surname>BENATALLAH</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>DUMAS</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>SHENG</surname>
          </string-name>
          ,
          <string-name>
            <surname>Q. Z.</surname>
          </string-name>
          , AND NGU,
          <string-name>
            <surname>A.</surname>
          </string-name>
          <year>2002</year>
          .
          <article-title>Declarative Composition and Peer-to-Peer Provisioning of Dynamic Web Services</article-title>
          .
          <source>In Proc. of ICDE'02</source>
          , IEEE Computer Society, pages
          <fpage>297</fpage>
          {
          <fpage>308</fpage>
          , San Jose.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <string-name>
            <surname>CARDOSO</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>SHETH</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>MILLER</surname>
          </string-name>
          ,
          <string-name>
            <surname>J.</surname>
          </string-name>
          ,
          <string-name>
            <surname>ARNOLD</surname>
          </string-name>
          ,
          <string-name>
            <surname>J.</surname>
          </string-name>
          , AND KOCHUT,
          <string-name>
            <surname>K.</surname>
          </string-name>
          <year>2004</year>
          .
          <article-title>Quality of Service for Work°ows and Web Service Processes</article-title>
          .
          <source>Journal of Web</source>
          Semantic (to appear in
          <year>2004</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <string-name>
            <surname>HENTENRYCK</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          , AND SARASWAT,
          <string-name>
            <surname>V.</surname>
          </string-name>
          <year>1996</year>
          .
          <article-title>Strategic directions in constraint programming</article-title>
          .
          <source>ACM Computing Surveys</source>
          ,
          <volume>28</volume>
          (
          <issue>4</issue>
          ),
          <year>December 1996</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <string-name>
            <surname>MART¶IN-D¶IAZ</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>RUIZ-CORT E¶S</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>BENAVIDES</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>DURAN</surname>
          </string-name>
          ,
          <string-name>
            <surname>A.</surname>
          </string-name>
          , AND TORO,
          <string-name>
            <surname>M.</surname>
          </string-name>
          <year>2003</year>
          .
          <article-title>Automating the procurement of Web Services</article-title>
          .
          <source>In Proc. of the International Conference on Service Oriented Computing (ICSOC'03)</source>
          , Springer LNCS 2910, pages
          <fpage>91</fpage>
          {
          <fpage>103</fpage>
          , Berlin, Germany.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <string-name>
            <surname>MAXIMILIEN</surname>
            ,
            <given-names>E.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>AND SINGH</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.</surname>
          </string-name>
          <year>2002</year>
          .
          <article-title>Conceptual model of web service reputation</article-title>
          .
          <source>SIGMOD Record</source>
          , ACM Special Interest Group on Management of Data (
          <year>2002</year>
          )
          <volume>36</volume>
          {
          <fpage>41</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          <string-name>
            <surname>NOVELLO</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          , AND SCHIMPF,
          <string-name>
            <surname>J.</surname>
          </string-name>
          <year>1999</year>
          .
          <article-title>ECLiPSe Embedding and Interfacing Manual</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          <string-name>
            <surname>OWL-S COALITION</surname>
          </string-name>
          (
          <year>2003</year>
          )
          <article-title>: OWL-S 1.0 Release</article-title>
          . http://www.daml.org/services/owl-s/1.0/.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          <string-name>
            <surname>RAN</surname>
          </string-name>
          , SHUPING.
          <year>2003</year>
          .
          <article-title>A Model for Web Services Discovery with QoS</article-title>
          .
          <source>ACM SIGecom Exchanges</source>
          ,
          <volume>4</volume>
          (
          <issue>1</issue>
          ):1{
          <fpage>10</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          <string-name>
            <surname>TIAN</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>GRAMM</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>NABULSI</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.</surname>
          </string-name>
          ,
          <string-name>
            <surname>RITTER</surname>
          </string-name>
          , H.,
          <string-name>
            <surname>SCHILLER</surname>
          </string-name>
          ,
          <string-name>
            <surname>J.</surname>
          </string-name>
          , AND T. VOIGT,
          <string-name>
            <surname>T.</surname>
          </string-name>
          <year>2003</year>
          . QoS Integration in Web Services.
          <source>Gesellschaft fur Informatik DWS</source>
          <year>2003</year>
          ,
          <article-title>Doktorandenworkshop Technologien und Anwendungen von XML (Ph</article-title>
          .D. students workshop Technologies and Applications of XML), Berlin, Germany, Oct.
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          <string-name>
            <surname>TOSIC</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>ESFANDIARI</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>PAGUREK</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>PATEL</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <year>2002</year>
          .
          <article-title>On Requirements for Ontologies in Management of Web Services</article-title>
          .
          <source>In Proceedings of the Workshop on Web Services</source>
          , e-Business,
          <article-title>and the Semantic Web -</article-title>
          WES (at CAiSE'02), Bussler,
          <string-name>
            <surname>C.</surname>
          </string-name>
          et al. (eds.), Toronto, Canada, May
          <year>2002</year>
          . Springer-Verlag, Lecture Notes in Computer Science (LNCS),
          <source>No. 2512</source>
          , pp.
          <volume>237</volume>
          {
          <fpage>247</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          <string-name>
            <surname>TOSIC</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>PAGUREK</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          , AND PATEL,
          <string-name>
            <surname>K.</surname>
          </string-name>
          <year>2003</year>
          .
          <article-title>WSOL | A Language for the Formal Speci¯cation of Classes of Service for Web Services</article-title>
          .
          <source>In the Int. Conf. on Web Services (ICWS03)</source>
          .
          <source>Las Vegas</source>
          , USA, June
          <volume>23</volume>
          {
          <fpage>26</fpage>
          ,
          <year>2003</year>
          , CSREA Press, pp.
          <volume>375</volume>
          {
          <fpage>381</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          <string-name>
            <surname>ZENG</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>BENATALLAH</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>DUMAS</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>KALAGNANAM</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            ,
            <surname>SHENG</surname>
          </string-name>
          ,
          <string-name>
            <surname>Q.</surname>
          </string-name>
          <year>2003</year>
          .
          <article-title>Quality driven web services composition</article-title>
          .
          <source>In: WWW</source>
          <year>2003</year>
          :
          <volume>411</volume>
          {
          <fpage>421</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          <string-name>
            <surname>ZHOU</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>CHIA</surname>
            ,
            <given-names>L-T.</given-names>
          </string-name>
          ,
          <article-title>AND</article-title>
          <string-name>
            <surname>LEE</surname>
            ,
            <given-names>B-S.</given-names>
          </string-name>
          <year>2004</year>
          .
          <article-title>DAML-QoS Ontology for Web Services</article-title>
          .
          <source>In: ICWS</source>
          <year>2004</year>
          :
          <volume>472</volume>
          {
          <fpage>479</fpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>