<!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>Flexible Service Offering with Semantic Policies</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Marco Comerio</string-name>
          <email>comerio@disco.unimib.it</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Flavio De Paoli</string-name>
          <email>depaoli@disco.unimib.it</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Matteo Palmonari</string-name>
          <email>palmonari@disco.unimib.it</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ioan Toma</string-name>
          <email>ioan.toma@sti2.at</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>STI Innsbruck - ICT - Technikerstrasse 21a</institution>
          ,
          <addr-line>6020 Innsbruck</addr-line>
          ,
          <country country="AT">Austria</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>University of Milano - Bicocca</institution>
          ,
          <addr-line>viale Sarca 336, 20126 Milano</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>One of the challenges in Service Oriented Computing consists in supporting service discovery and composition according to the so-called non functional properties (NFP). In this paper we propose a linguistic framework to describe NFPs of services independently of the grounding technology by means of semantic Web technologies. In particular, the approach is based on an extension of the Web Service Modeling Language (WSML). The linguistic framework supports flexible NFP representations by allowing (i) to reuse existent models and ontologies, (ii) to represent both the definition of single NFPs and clusters of NFPs grouped into policies. A policy collects a set of related and possibly interdependent properties to form a single entity that can be referenced and discovered. As a result, definitions of NFPs can be independent of specific services, and vice versa, so to support flexible associations.</p>
      </abstract>
      <kwd-group>
        <kwd>Non-functional properties</kwd>
        <kwd>Policy</kwd>
        <kwd>Semantic Web Services</kwd>
        <kwd>Web Service Modeling Ontology</kwd>
        <kwd>service level agreements</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Service-based interactions to support activities of organizations and end-users
require the retrieval, composition and execution of services. One of the major
challenges is to support service discovery according to the so-called non
functional properties (NFP). NFPs are related to technical issues (e.g., quality of
service (QoS) such as performance, availability, security), and also to business,
social, legal and economic issues, just to mention a few. It is likely that users
will be interested in selecting the desired services among a large set of available
services, each one providing the same or similar functionalities.</p>
      <p>To achieve the goal, a user can issue a request that can be split into functional
and non-functional constraints. From the point of view of service discovery and
selection, which is our main perspective, the role of functional constraints is to
filter eligible services, while the role of non-functional constraints is to compute
degrees of satisfaction for that set of services (i.e., NFP constraints could be fully,
partially or not satisfied). Therefore, NFPs could be quite relevant to match a
service request and a service description. In fact, even if a service matches the
requested functionalities, it could be unacceptable in terms of NFPs (e.g., if
availability is not sufficient, performance is too poor, cost is too expensive).</p>
      <p>
        A model to support a scenario in which a client wants to select the “best”
available service needs to address both provider and client perspectives: providers
need to define and publish descriptions of NFPs associated with candidate
services; clients need to specify the criteria for service selection. The Web Service
Modeling Ontology (WSMO) [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ] is a conceptual model for Semantic Web
services that, differently e.g. from OWL-S [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ], explicitly takes into account clients
and providers. In particular, WSMO defines four top-level elements: (1)
ontologies, as formal explicit specifications of share conceptualizations providing the
terminology used to describe services, (2) goals, as descriptions of the objectives
a client may have when consulting a service, (3) web services, as descriptions of
functionalities and (4) mediators, as means to address the heterogeneity
problem that occurs between descriptions at different levels (i.e. data, protocol and
process level).
      </p>
      <p>
        In this paper we present a linguistic framework for the semantic
representation of (Web) services’ NFPs in WSMO. The framework extends the Web Service
Modeling Language (WSML) [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], the language used by WSMO. The aim of
semantic descriptions of NFP is to achieve a new level of automation for service
related tasks like discovery, selection, composition, negotiation, and monitoring,
by supporting automated reasoning about NFPs. Moreover, the framework aims
to achieve flexibility by providing users with constructs to accommodate NFP
descriptions at different level of details. It supports simple descriptions that deal
with individual properties by means of logical expressions; as well as
composite descriptions that are defined by the policy construct, which collects a set
of related and possibly interdependent properties in a single entity that can be
referenced and discovered.
      </p>
      <p>A definitions of non-functional properties can be independent of any specific
service, and vice versa. The advantage is to be able to publish the same service
associated with different NFP policies to address the needs of different clients;
and to publish a policy that can be associated with different services to facilitate
the discovery process and composition. The separation between services and
descriptions opens the opportunity to build predefined, possibly standard, policies
that can be reused to facilitate the task of publishing, retrieving and composing
services.</p>
      <p>
        The linguistic constructs discussed in this paper have been implemented into
semantic Web search engines to support NFP aware WS discovery and selection.
In particular, the ranking engine discussed in [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ] supports the computation
of individual properties; the GLUE2 discovery engine [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] deals with composite
properties as described by the Policy-Centered Meta-model (PCM) [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. PCM
provides for an ontology-based model to describe single properties to be
composed into policies as discussed in this paper.
      </p>
      <p>The paper is organized as follows. Section 2 describes semantic and
nonsemantic approaches for NFP descriptions. Section 3 shows our approach for
modeling NFPs and policies. Examples of flexible NFP publishing are reported
in Section 4. Finally, Section 5 draws some conclusions.</p>
    </sec>
    <sec id="sec-2">
      <title>Related Work</title>
      <p>
        Developing models and languages for non-functional properties has been a
challenging problem in many research areas. In software engineering especially NFPs
models and languages were developed to support the description of NFP
aspects and requirements of software systems. In [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] for example, a language for
NFPs called ProcessNF L is proposed to express correlations and conflicts
between NFPs and also compositional aspects and strengths. In [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] the ODRL-S
language is proposed to describe economical and legal aspects of a service as
license clauses. In [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] the CQML modeling language is proposed for specification
of Quality of Service (QoS) (i.e., the particular kind of NFPs related to
technological characteristics of a Web services) allowing QoS characteristics to be
refined and aggregated. The QML [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] language and model is a domain
independent approach to describe QoS providing a refinement mechanism that allows
QoS aspects to be defined as refinements of existing ones. [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] provides a formal
machine processable description of software and services by means of constraints
instead of ontologies. In addition, QRL provides a mechanism to express
alternative NFPs for the same service by means of the so-called negotiation clauses.
In the Web services area some efforts to describe NFPs resulted in the WS-*
specifications. Considerable related work has been done also in the context of
Service Level Agreements.
      </p>
      <p>
        One important limitation of the former approaches is the lack of machine
processable descriptions. Formal machine processable descriptions of software
and services would enable a higher degree of automation required to solve
complex problems. With the emergence of semantic technologies as solutions for the
previous limitation, several approaches for semantic NFP descriptions have been
proposed. A model that facilitates providers in expressing policies and consumers
in expressing preferences on QoS is proposed in [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. A model to establish a set
of rules that are used to represent QoS characteristics of Web services along with
the relationships among them is introduced in [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ].
      </p>
      <p>
        Current standards for semantic descriptions of services (e.g., WSMO [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]
and OWL-S [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]) cover only marginally the specification of NFPs. OWL-S [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]
basically adopts attribute-value descriptions. The OWL-S profile only includes
an expandable list of NFPs (e.g., average completion time, classification,
quality of service) expressed as service parameters. Some papers propose to fill the
gap by complementing OWL-S with models for NFP description. Kritikos and
Plexousakis [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] propose to enrich OWL-S with an extensible model for
describing QoS. Giallonardo and Zimeo [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] define a model that allow service providers
advertising offered QoS, and service consumers specifying QoS requirements
associated to an OWL-S profile. Comerio et al. in [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] introduce the concept of
NFP Policy, with a meta-model providing structure to NFP descriptions to
support service selection. The early versions of WSMO [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ] adopted as well an
attribute-values approach to describe NFPs. As attributes non-functional
property identifier are provided. Values can be any identifier and thus it can be an
IRI, a data value, an anonymous identifier or a list of the former. The
recommended common set of non-functional properties was mainly based on Dublin
Core Metadata Initiative [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ]. Other approaches such as
      </p>
      <p>
        In this paper, we present a comprehensive approach to NFP description
compliant with different NFP models instead of a new NFP model. The ideas behind
the logical expression-based approach to NFP description, together with a
NFPaware discovery algorithm for WS described with WSMO were introduced in
[
        <xref ref-type="bibr" rid="ref17">17</xref>
        ]. The concept of NFP Policy was first introduced within the Policy-Centered
Meta model (PCM) [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]; the refinement and formalization of PCM is described
in [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ], while a NFP-aware discovery engine based on such model is presented in
[
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. Here, elaborating on these preliminary works, we present a unified approach
within the WSMO framework, discussing in particular the main advantages
expected from the approach in a future Internet business scenario.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Representing Non Functional Properties and Policies</title>
      <p>
        The definition and management of NFPs is a complex task due to the nature
of the involved properties. NFPs concern a variety of service aspects, ranging
from technical issues to pricing policies to legal aspects [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. Similar properties
may have different names (e.g., in different languages or domains) or the same
name may refer to different properties (e.g., in different domains a property may
have different implications). Numeric values can be expressed in different units
(e.g., price in Euro or in USD), or properties can be purely qualitative (e.g., the
usability is “good”, trust is “high”, software is “open source”).
      </p>
      <p>
        Moreover, sometimes the value of a NFP is not fixed but needs to be
calculated at runtime when the context or the request provide additional information
(e.g., the bandwidth a service is provided with). Nonetheless, as discussed in
[
        <xref ref-type="bibr" rid="ref14">14</xref>
        ], it could be helpful for the discovery process to publish some information
about the possible values these NFPs might assume (e.g. a range), or about the
methods the values are calculated with. Moreover, clusters of NFP offers and
requests need to be considered because of technological or business
interdependencies among NFPs (e.g. a higher price for the service that guarantee a certain
bandwidth).
      </p>
      <p>In more general terms, a web service can provide the same functionality with
different non-functional property levels. Several real world services provide
evidence of this consideration. For example, the Italian railway company Trenitalia
web site3 offers different fares (e.g, Flexi, Standard, Amica, Blu card rail plus4)
for booking ticket services. Each fare is characterized by a set of non-functional
properties such as discount, advantages and constraints; some property, such as
allowed trains, specifies the applicability conditions. Therefore, it is possible to
buy a transit pass for a destination under different conditions (e.g., weekly or
monthly one-way or return pass for IC/EC trains). Service descriptions should
reflect these clustering of related NFPs. Moreover, these descriptions should be</p>
      <sec id="sec-3-1">
        <title>3 http://www.ferroviedellostato.it/ferrovie/util/inglese.jsp</title>
        <p>4 The description of the several fares offered by Trenitalia can be found at
http://www.trenitalia.com/en/oraribiglietti/infotariffe.html
independent of the functional description of a service since they are subject
to change more frequently. For example, the price may change due to market
conditions or special discount campaign may be introduced anytime.</p>
        <p>In this paper we propose an approach to handle the heterogeneity of NFP
descriptions, support the clustering of NFP offered and requested, and finally
decoupling FP and NFP specifications. The last feature allows for a more flexible
provision of services, where descriptions of NFPs can be changed modularly over
a set of persistent FPs.</p>
        <p>Single NFPs and NFP policies can be attached to WSs and goals. The
NFPaware discovery process is based on the evaluation of a matching degree between
a goal and a number of WS which takes into account NFPs and policies attached
to these elements. Since NFP and policy descriptions are attached to goals in
the same way they are attached to WS, in the rest of the paper we will show
only the WS-side of NFP and policy descriptions.
3.1</p>
        <p>Representation of individual NFPs
The proposed solution is based on semantic technologies and starts from two
considerations: providing a unique and shared model of all the possible NFPs
is unfeasible; nonetheless, there is the need of a systematic approach to NFP
description to support selection activity beside the traditional technological
perspective.</p>
        <p>
          A first step towards the definition of a self-contained semantically enabled
modeling framework for NFPs and policies is the creation of ontological models
for specifying non-functional properties. Providers and clients should be made
able to refer to different NFPs by adopting existent ontologies or even defining
a set of new ones. As part of our initial work (i.e. [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ]) we have developed a
set of ontologies to provide a formal model for the most common non-functional
properties like availability, security, etc.; other models, e.g. those mentioned in
Section 2, can be used as well if represented in WSML.
        </p>
        <p>Once domain ontologies have been defined, they can be used to describe
NFPs within WSMO service descriptions through identifiers followed by logical
expressions. A simplified model of a WSMO service following this approach is
illustrated in Listing 1.15:
¨</p>
        <p>Listing 1.1. Service description structure
webService
capability idCapability
precondition definedBy axiomP recond
postcondition definedBy axiomP ostcond
assumption definedBy axiomAssumption
effect definedBy axiomEffect
nonFunctionalProperty</p>
        <p>idNF P hasValue valuelistnfp definedBy axiomNF P
5 Please notice that in WSMO the default cardinality for each statement is
zero-tomany, which holds for the listings presented along the paper.
¥
¦
¨
Class nonFunctionalProperty
hasAnnotations type annotations
hasDefinition type logicalExpression</p>
        <p>According to this approach one or more NFP can be attached to service
descriptions in a similar way as capabilities are attached. The WSMO model has
been extended with the class nonFunctionalProperty, characterized as illustrated
in Listing 1.2.</p>
        <sec id="sec-3-1-1">
          <title>Listing 1.2. Non-functional property class</title>
          <p>In the NFP specification, ontological references are first introduced as set of
values. Such values can be instances of domain ontologies (e.g., a price defined
by amount and currency) or variables defined by an axiom. The exploitation
of axioms allows for a great freedom in NFP definition, allowing for description
such as ”if the client is older than 60 or younger than 10 years old the invocation
price is lower than 10 euro”; an example is given in Section 4.
3.2</p>
          <p>Representation of NFP clusters with NFP Policies
Besides modeling single NFPs, we have extended the WSMO model with the
concept of Policy. A NFP policy (policy for short) is a cluster of non functional
properties offered or requested (e.g., a specification of price, of a security level
that is guaranteed and so on). More than one policy can be associated with a
service and each policy has an applicability condition specifying when it can be
accessed (e.g., the premium policy can be accessed only by clients older then
60).</p>
          <p>In WSMO, a policy collects a set of NFPs that are elements of the class
nonFunctionalProperty. Policy conditions are described by axioms; a WS can
have one of more conditions; when more conditions are specified their conjunction
is taken to hold, as it is defined for similar WSMO elements. Formally, the
WSMO conceptual model can be extended by the class Policy characterized as
follows (Listing 1.3).</p>
        </sec>
        <sec id="sec-3-1-2">
          <title>Listing 1.3. WSMO conceptual model extensions</title>
          <p>¨
Class policy
hasAnnotations type annotations
importsOntology type ontology
usesMediator type ooMediator
hasCondition type Axiom
hasNfp type nonFunctionalProperty</p>
          <p>
            Imported ontologies allows for reuse of existing ontologies in the policy
descriptions; mediators can be exploited to support matching between offered and
requested policies, as described in [
            <xref ref-type="bibr" rid="ref3">3</xref>
            ]. Policies are attached to service
descriptions as done for single NFPs. A simplified model of a WSMO service resulting
from this approach is illustrated in Listing 1.4:
          </p>
          <p>The advantage is to give developers the freedom to model non functional
properties as single NFPs or clustered NFPs defined by policies. However, it
should also be stated that the the use of both policies and single NFPs together
should be avoided.</p>
          <p>The policies that are included in service descriptions can be extracted to
form independent entities identified by URIs, supporting policy reuse. In fact,
the specification of the fields idP olicy and valuelistnf p may refer to instances
of existing ontologies. This is a key factor to address flexibility, since the same
policy can be associate with more services. A positive side effect is to reduce
the effort in writing semantic policy descriptions, which could be a non trivial
task for complex specifications (e.g., legal clauses). In particular, this opens to
future solutions in which policy descriptions are collected in repositories to
address NFP management, reuse and evolution, separately from WS and functional
specification management. Repositories will be able to support the creation of
standard and shared policies to address specific needs (e.g., to conform business
rules of an organization or to fulfill legal prescriptions).</p>
          <p>In principle, single-NFP and policy-based approaches are equally expressive;
however, the policy-based approach provides a more direct, explicit, and compact
way to cluster NFPs; when such clusters are taken into account the policy-based
approach is easier to read and manipulate due to the explicit linguistic structure;
when more freedom in modelling is needed the single NFP approach can be
adopted.
4</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Examples of flexible NFP publishing</title>
      <p>In this section, we present some examples to illustrate the proposal6. Listing 1.5
shows how NFPs can be individually attached to service descriptions by
exploiting WSML axioms. The axiom states that a given price (lower than 10 euro) is
for clients older than 60 or younger than 10 years.
6 Please notice that the WSML syntax used in this section is not yet supported by
WSMO/WSML tools (e.g. WSMT). Future extensions of WSMO and WSML towards
better support of non-functional properties and policies, as well as the associated
tool support will be most probably based on the proposal described in this paper.
¥
¦
nonFunctionalProperty
§
capability wsCapability
interface wsInterface</p>
      <p>Listing 1.5. Example of NFPs descriptions based on the proposed extensions
¨
webService ”http://example.org/ws”
importsOntology { ”http://www.wsmo.org/ontologies/nfp/priceNFPOntology”,
”http://www.example.org/ontologies/humansOntology”,
”http://www.example.org/ontologies/clientsOntology”}
price hasValue ?price
definedBy ?client[age hasValue ?age] memberOf hu#human and ?age[amount hasValue ?years,
units hasValue hu#YearsDuration] memberOf hu#age and (greaterEqual(?years, 60) or
lessEqual(?years,10)) implies ?price[hasAmount hasValue ?amount, hasCurrency
hasValue cur#Euro] memberOf po#AbsoultePrice and lessEqual(?amount, 10).</p>
      <p>
        In the next example (Listing 1.6), a service offers two different policies, one
for users applying for repetitive travels, and one for ’Gold’ subscribers users.
The conditions associated with the policies state the client status to access the
policy and consequently the corresponding property values. In order to show the
modularity of the approach, the example exploits the PCM external ontology [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]
to describe the involved NFPs. Moreover, the Gold policy refers to the external
ontology PolicyRepository where this policy is described (Listing 1.7).
Listing 1.6. Example of Web Service description including policy descriptions
¨
webService WSOmniTransport
¥
importsOntology{ ”http://www.siti.disco.unimib.it/ontologies/LOOntology#LOOntology”,
”http://www.siti.disco.unimib.it/ontologies/PCMOntology#PCMOntology”,
”http://www.siti.disco.unimib.it/ontologies/NFPOntology#NFPOntology”,
”http://www.siti.disco.unimib.it/ontologies/PolicyRepository#PolicyRepository”}
policy policyForRepetitiveTravel
policyCondition repetitiveTravelCondition
definedBy pcm#appliable(policyForRepetitiveTravel) :− #[lo#numberOfTravelsSubscribed
hasValue ?n and ?n &gt; 1] memberOf lo#LogisticOperatorClient.
nonFunctionalProperty
paymentMethod hasValue offeredPaymentMethodOT
definedBy offeredPaymentMethodOT[constraintOperator hasValue exact
      </p>
      <p>pcm#parameters hasValue nfpo#carriageForward] memberOf nfpo#ListPaymentMethod.
nonFunctionalProperty
price hasValue offeredBasePriceOTrepetitive
definedBy offeredBasePriceOTrepetitive[pcm#constraintOperator hadValue pcm#equal,
pcm#parameter hasValue 20, pcm#unit hasValue nfpo#euro]
memberOf nfpo#SingleValueBasePrice.
nonFunctionalProperty
deliveryDuration hasValue offeredHoursToDeliveryOTrepetitive
definedBy offeredHoursToDeliveryOTrepetitive[pcm#constraintOperator hasValue pcm#interval,
pcm#minParameter hasValue 24, pcm#maxParameter hasValue 48,
pcm#unit hasValue nfpo#hour] memberOf nfpo#RangeHoursToDelivery
policy pr#policyGold
capability wsCapability
interface wsInterface
¥
¦</p>
      <p>Three NFPs are represented in the example, namely, Payment Method (the
method accepted for paying the service), Base Price (the starting price upon
which total price is calculated taking into account size, weight and distance),
and Hours To Delivery (the time spent by the providers before shipping the
goods). The value of each NFP is an instance in the ontology; the properties
of this instance are specified by the axiom immediately following the WSML
construct “defined by”. In the example the two policies offer the same payment
methods, but associated with different base price and duration of the delivery.
Observe that the delivery duration cannot be defined with a fixed value; therefore
a range is published according to PCM range constraint operators.</p>
      <p>Listing 1.7. Example of independent policy definition
ontology PolicyRepository
importsOntology{ ”http://www.siti.disco.unimib.it/ontologies/LOOntology#LOOntology”,
”http://www.siti.disco.unimib.it/ontologies/PCMOntology#PCMOntology”,
”http://www.siti.disco.unimib.it/ontologies/NFPOntology#NFPOntology”}
¨
§
5
¥
¦
policy policyGold
policyCondition goldCondition
definedBy pcm#appliable(policyGold) :− #[lo#userTypology hasValue lo#subscribed]</p>
      <p>memberOf lo#LogisticOperatorClient.
nonFunctionalProperty</p>
      <p>paymentMethod hasValue offeredPaymentMethodOT
nonFunctionalProperty
price hasValue offeredBasePriceOTgold
definedBy offeredBasePriceOTgold[pcm#constraintOperator hadValue pcm#equal,
pcm#parameter hasValue 15, pcm#unit hasValue nfpo#euro]
memberOf nfpo#SingleValueBasePrice.
nonFunctionalProperty
deliveryDuration hasValue offeredHoursToDeliveryOTgold
definedBy offeredHoursToDeliveryOTgold[pcm#constraintOperator hasValue pcm#interval,
pcm#minParameter hasValue 12, pcm#maxParameter hasValue 32,
pcm#unit hasValue nfpo#hour] memberOf nfpo#RangeHoursToDelivery</p>
    </sec>
    <sec id="sec-5">
      <title>Conclusions and Future Work</title>
      <p>This paper has introduced a modeling approach for non-functional properties
and policies. Both service provider and consumer perspectives are supported
allowing the specification of what, how and in which way non-functional
properties and policies are provided and requested. Distinctive features are (i) the
semantic description of non-functional properties and policies that heavily use
ontologies to define terminology and concepts; (ii) the declarative approach to
model non-functional properties and policies using axioms, and (iii) the
definition of policies as independent entities that clusters non-functional properties
and related applicability condition.</p>
      <p>
        Currently the proposal is under evaluation to become part of the official
definition of WSMO/WSML. Future plans deal with the development of a lighter
version of the descriptions. This is motivated by emerging lighter modeling
frameworks for Semantic Web service, such as WSMO-Lite[
        <xref ref-type="bibr" rid="ref19">19</xref>
        ] and SA-WSLD7.
The aim is to deliver lighter ontologies describing a reduced but sufficient (most
common used) set of non-functional properties and policies. A key aspect of the
current and future activity is the development of tools to evaluate the practical
applicability of the proposal. In the framework of the sponsoring projects we are
developing a discovery engine and case studies. Moreover, these topics will be
part of next Semantic Challenge proposals [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
    </sec>
    <sec id="sec-6">
      <title>Acknowledgements</title>
      <p>The work presented in this paper has been partially supported by the European
IST project n. 27347 SEEMP - Single European Employment Market-Place, IST
project n. 27867 SOA4ALL - Service Oriented Architectures For All, and the
Italian FIRB project RBNE05XYPW NeP4B - Networked Peers for Business.</p>
      <sec id="sec-6-1">
        <title>7 http://www.w3.org/2002/ws/sawsdl/</title>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>J.</given-names>
            <surname>Aagedal</surname>
          </string-name>
          and
          <string-name>
            <given-names>J. Earl F.</given-names>
            <surname>Ecklund</surname>
          </string-name>
          . Modelling QoS:
          <article-title>Towards a UML Profile</article-title>
          .
          <source>In UML '02: Proceedings of the 5th International Conference on The Unified Modeling Language</source>
          , pages
          <fpage>275</fpage>
          -
          <lpage>289</lpage>
          , London, UK,
          <year>2002</year>
          . Springer-Verlag.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>A.</given-names>
            <surname>Carenini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Cerizza</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Comerio</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E. D.</given-names>
            <surname>Valle</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F. D.</given-names>
            <surname>Paoli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Maurino</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Palmonari</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Sassi</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Turati</surname>
          </string-name>
          .
          <article-title>Semantic web service discovery and selection: a test bed scenario</article-title>
          .
          <source>In In proc of. Sixth International Workshop on Evaluation of Ontology-based tools and the Semantic Web Service Challenge (EON &amp; SWSChallenge</source>
          <year>2008</year>
          ),
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>A.</given-names>
            <surname>Carenini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Cerizza</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Comerio</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E. D.</given-names>
            <surname>Valle</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F. D.</given-names>
            <surname>Paoli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Maurino</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Palmonari</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <surname>A. Turati.</surname>
          </string-name>
          <article-title>Glue2: a web service discovery engine with non-functional properties</article-title>
          .
          <source>In ECOWS. IEEE Computer Society</source>
          ,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>M.</given-names>
            <surname>Comerio</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>DePaoli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Maurino</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Palmonari</surname>
          </string-name>
          .
          <article-title>Nfp-aware semantic web services selection</article-title>
          .
          <source>In Proc. of the Enterprise Computing Conference (EDOC)</source>
          .,
          <string-name>
            <surname>Annapolis</surname>
          </string-name>
          , Maryland, USA,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>A. R.</given-names>
            <surname>Cortes</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O. M.</given-names>
            <surname>Diaz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. D.</given-names>
            <surname>Toro</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Toro</surname>
          </string-name>
          <article-title>. mproving the Automatic Procurement of Web Services Using Constraint Programming</article-title>
          .
          <source>Int. J. Cooperative Inf. Syst.</source>
          ,
          <volume>14</volume>
          (
          <issue>4</issue>
          ):
          <fpage>439</fpage>
          -
          <lpage>468</lpage>
          ,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>J. de Bruijn</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          <string-name>
            <surname>Lausen</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Krummenacher</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Polleres</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          <string-name>
            <surname>Predoiu</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Kifer</surname>
            , and
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Fensel</surname>
          </string-name>
          .
          <article-title>The Web Service Modeling Language WSML</article-title>
          .
          <source>Technical report, DERI. WSML Final Draft D16</source>
          .
          <year>1v0</year>
          .21. http://www.wsmo.
          <source>org/TR/d16/d16.1/v0.21/.</source>
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>S.</given-names>
            <surname>Frølund</surname>
          </string-name>
          and
          <string-name>
            <given-names>J.</given-names>
            <surname>Koistinen</surname>
          </string-name>
          .
          <article-title>Qml: A Language for Quality of Service Speicifcation</article-title>
          .
          <source>Techincal report, Hewlett Packard</source>
          ,
          <volume>02</volume>
          1998. Available from http://www.hpl.hp.com/techreports/98/HPL-98-10.html.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <given-names>G.</given-names>
            <surname>Gangadharan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Comerio</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.-L.</given-names>
            <surname>Truong</surname>
          </string-name>
          , V.
          <string-name>
            <surname>D'Andrea</surname>
            ,
            <given-names>F. D.</given-names>
          </string-name>
          <string-name>
            <surname>Paoli</surname>
            , and
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Dustdar</surname>
          </string-name>
          .
          <article-title>License-aware Service Selection</article-title>
          .
          <source>In IEEE 2008 Conference on Enterprise Computing</source>
          , E-Commerce and
          <string-name>
            <surname>E-Services (</surname>
          </string-name>
          <source>EEE '08)</source>
          , Crystal City, Washington,
          <string-name>
            <surname>D.C.</surname>
          </string-name>
          , USA,
          <year>July 2008</year>
          . IEEE Computer Society.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <given-names>E.</given-names>
            <surname>Giallonardo</surname>
          </string-name>
          and
          <string-name>
            <given-names>E.</given-names>
            <surname>Zimeo</surname>
          </string-name>
          .
          <article-title>More semantics in qos matching</article-title>
          .
          <source>In Proc. of International Conference on Service-Oriented Computing and Application (SOCA07)</source>
          , pages
          <fpage>163</fpage>
          -
          <lpage>171</lpage>
          , Newport Beach, CA, USA,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <given-names>K.</given-names>
            <surname>Kritikos</surname>
          </string-name>
          and
          <string-name>
            <given-names>D.</given-names>
            <surname>Plexousakis</surname>
          </string-name>
          .
          <article-title>Semantic qos metric matching</article-title>
          .
          <source>In ECOWS '06: Proceedings of the European Conference on Web Services</source>
          , pages
          <fpage>265</fpage>
          -
          <lpage>274</lpage>
          , Washington, DC, USA,
          <year>2006</year>
          . IEEE Computer Society.
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11. E. Maximilien and
          <string-name>
            <given-names>M.P.</given-names>
            <surname>Singh</surname>
          </string-name>
          .
          <article-title>A framework and ontology for dynamic web services selection</article-title>
          .
          <source>IEEE Internet Computing</source>
          ,
          <volume>08</volume>
          (
          <issue>5</issue>
          ):
          <fpage>84</fpage>
          -
          <lpage>93</lpage>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>J. O'Sullivan</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Edmond</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A. H. ter</given-names>
            <surname>Hofstede</surname>
          </string-name>
          .
          <article-title>Formal description of nonfunctional service properties</article-title>
          .
          <source>Technical report</source>
          , Queensland University of Technology, Brisbane,
          <year>2005</year>
          . Available from http://www.service-description.com/.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>OWL-S. Semantic</surname>
          </string-name>
          <article-title>Markup for Web Services</article-title>
          . Available at: http://www.daml.org/services/owl-s/1.0/owl-s.html,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <given-names>F. D.</given-names>
            <surname>Paoli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Palmonari</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Comerio</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Maurino</surname>
          </string-name>
          .
          <article-title>A meta-model for nonfunctional property descriptions of web services</article-title>
          .
          <source>In ICWS</source>
          , pages
          <fpage>1048</fpage>
          -
          <lpage>1055</lpage>
          . IEEE Computer Society,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <given-names>D.</given-names>
            <surname>Roman</surname>
          </string-name>
          , H. Lausen, , and U. Keller.
          <article-title>Web Service Modeling Ontology (WSMO). www</article-title>
          .wsmo.org,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <given-names>N. S.</given-names>
            <surname>Rosa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P. R.</given-names>
            <surname>Cunha</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Freire</surname>
          </string-name>
          , and
          <string-name>
            <given-names>G. R.</given-names>
            <surname>Justo</surname>
          </string-name>
          .
          <article-title>Process NFL: A language for describing non-functional properties</article-title>
          .
          <source>In Proceedings of the 35th Annual Hawaii International Conference (HICSS)</source>
          ,
          <source>March</source>
          <volume>29</volume>
          ,
          <year>2005</year>
          , Hawaii, USA, pages
          <fpage>3676</fpage>
          -
          <lpage>3685</lpage>
          ,
          <year>2002</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17. I.
          <string-name>
            <surname>Toma</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Roman</surname>
            , and
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Fensel</surname>
          </string-name>
          .
          <article-title>On describing and ranking services based on non-functional properties</article-title>
          .
          <source>In NWESP '07: Proceedings of the Third International Conference on Next Generation Web Services Practices</source>
          , pages
          <fpage>61</fpage>
          -
          <lpage>66</lpage>
          , Washington, DC, USA,
          <year>2007</year>
          . IEEE Computer Society.
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <given-names>D.</given-names>
            <surname>Tsesmetzis</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Roussaki</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Papaioannou</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Anagnostou</surname>
          </string-name>
          .
          <article-title>Qos awareness support in web-service semantics</article-title>
          .
          <source>In In AICT/ICIW '06: Proceedings of the Advanced International Conference on Telecommunications and International Conference on Internet and Web Applications and Services</source>
          , pages
          <fpage>128</fpage>
          -
          <lpage>135</lpage>
          , Guadeloupe, French Caribbean,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <given-names>T.</given-names>
            <surname>Vitvar</surname>
          </string-name>
          , J. Kopecky´,
          <string-name>
            <given-names>M.</given-names>
            <surname>Zaremba</surname>
          </string-name>
          , and
          <string-name>
            <given-names>D.</given-names>
            <surname>Fensel</surname>
          </string-name>
          .
          <article-title>Wsmo-lite: Lightweight semantic descriptions for services on the web</article-title>
          .
          <source>In ECOWS '07: Proceedings of the Fifth European Conference on Web Services</source>
          , pages
          <fpage>77</fpage>
          -
          <lpage>86</lpage>
          , Washington, DC, USA,
          <year>2007</year>
          . IEEE Computer Society.
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>K. J. L. C. Weibel</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          and
          <string-name>
            <given-names>M.</given-names>
            <surname>Wolf</surname>
          </string-name>
          .
          <article-title>Rfc 2413 - dublin core metadata for resource discovery</article-title>
          .
          <source>Technical report</source>
          ,
          <year>1998</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>