<!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>Towards a Semantic City Service Ecosystem</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>CEFRIEL</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Politecnico di Milano</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>via Fucini</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Milano</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Italy</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>firstname.lastsurnameg@cefriel.com</string-name>
        </contrib>
      </contrib-group>
      <abstract>
        <p>We introduce the concept of City Service Ecosystem (CSE) as digital environment for the governance of urban services. We trace the research challenges and opportunities of adding semantics to improve the management of such ecosystems, especially in relation to description and retrieval of urban-related Web services. We explain the peculiarities and distinct characteristics of CSEs resulting from their relation to the city space and we introduce our current work to enhance with semantics an existing CSE in the city of Milano, in relation to the forthcoming World Exposition (EXPO 2015).</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>Cities are complex environments in which multiple heterogeneous
stakeholders produce, consume and exchange digital information. Public utilities monitor
their goods consumption (water, electricity, waste, etc.) and gather information
from complementary sources to improve their business and service performance;
public bodies provide information and services to their citizens with the aim to
satisfy people needs and with the mandate to govern and coordinate the actions
on the territory; citizens request and provide information about what happens
in their cities during their everyday activities as part of their lives.</p>
      <p>
        It is thus clear that in every city a diverse and intertwined ecosystem of
services exists and that multiple and independent information systems are put
in place to manage the digital representation of those services. We name City
Service Ecosystem (CSE) the digital environment in which those services live,
according to the principles and guidelines of the so-called API economy [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Such
a CSE should allow for the coordinated and independent governance of the
services provided and consumed by the di erent stakeholders, respecting the legal
and business rules that apply, following the concept of coopetition (cooperation
and competition [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]).
      </p>
      <p>The peculiarity of a CSE with regards to other digital environments (e.g. any
other B2B system) lies in the strong connection with a spatio-temporal context :
those services are related and insist on a physical area and are widely dependent
on the timing and possible co-occurrences of events happening in the city.</p>
      <p>Taking the example of city mobility, multiple actors o er information
services: local transportation utilities (timetables of buses and subways, availability
of taxis), long-range transport companies (train and ights arrivals and
departures), environmental-friendly or sustainable mobility means (availability of bike
sharing or car sharing) and of course private transportation (GPS traces of
vehicles, tra c sensors in the streets). The mobility providers are in a business
competition, but, if they cooperate by exchanging their information (passenger
ows, availability of services, congestion and delays), the whole city ecosystem
bene ts and the quality of life of citizens improves.</p>
      <p>Our investigation questions are therefore: how should such a CSE be shaped
and organized? How can semantics support the life-cycle of city services? This
short paper is aimed at exploring (a part of) such a research space and at
providing preliminary answers to those questions.
3</p>
    </sec>
    <sec id="sec-2">
      <title>City Services</title>
      <p>Managing city services within a CSE means managing their descriptions in the
rst place. In this section, we address the issue of using semantics to make
explicit and machine-readable their speci cations. Beyond the general
considerations applicable to the semantic description of any Web service, we focus on
the speci city of urban services.
3.1</p>
      <sec id="sec-2-1">
        <title>Describing City Services</title>
        <p>There is a large literature about ontological models and semantic enrichment of
SOAP-based Web services [3{6]. However, those proposals have shown limited
adoption outside the research community; one of the reasons is probably the high
cost of producing such descriptions, making it an entry barrier that discouraged
a real uptake.</p>
        <p>
          Another reason is the rising popularity of Web APIs and REST services [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]
which represent a more \developer-friendly" paradigm for Web services. Also
in this space several proposals have been formulated for enhancing their
descriptions with semantics [
          <xref ref-type="bibr" rid="ref8 ref9">8, 9</xref>
          ]. It is undoubted that APIs and especially REST
interfaces are \closer" to the structure of the data they exchange. For this
reason, their description is more strictly bound to the description of their data
semantics.
        </p>
        <p>
          Since cities are complex environments, their services span a large set of di
erent domains, covering the heterogeneous aspects of citizens' lives. Nonetheless,
they all share the city context from both a spatial and temporal point of view
[
          <xref ref-type="bibr" rid="ref10 ref11">10, 11</xref>
          ]. As such, city services' data exchanges very likely share at least a part
of their \semantics" in relation to the physical space and to the timing1. This
fact must be taken into account when semantically annotating city services:
describing a service, indeed, is not only a matter of explaining its behaviour in
terms of functionalities, but it is also related to the speci cation of the service
context, to allow on the one hand the discovery of the service (see next section),
but foremost its comprehension and use.
        </p>
        <p>Adopting common models to describe geographic and temporal features, as
well as building and re-using identi ers for relevant points of interest (POI) in
a city becomes therefore of utmost importance to add the relevant semantics to
urban services. The question arises whether spatio-temporal semantics should
be used to annotate the description of a service interface rather than to \shape"
the data exchanged through the services, so to enable the interoperability of
services' requests and responses. We think that both those conditions apply:
in the former case, semantics supports the selection of the relevant service on
the basis of the requester's needs (e.g., choosing the best transportation service
for a speci c geographical area); in the latter case, semantics allows an easier
mash-up of di erent services in the same context (e.g., combining two di erent
transportation services on the basis of the proximity between the stops/stations
of the di erent providers so to enable a multi-modal journey planning).
3.2</p>
      </sec>
      <sec id="sec-2-2">
        <title>Retrieving City Services</title>
        <p>
          Web service descriptions are intended in the rst place to be employed to discover
{ either at design time or at run-time { the best service to ful l a speci c need.
Research focused also on semantically-enhanced Web service discovery
(including our own results [
          <xref ref-type="bibr" rid="ref12 ref13">12, 13</xref>
          ]), especially foreseeing a global process of automatic
discovery, selection, replacement and composition of Web services. However, as
outlined above, those fully-automated methods rarely exited the labs.
        </p>
        <p>
          We believe that a semi-automatic or only partially automated scenario is
more likely to happen: a developer needs a service to complete a business
process and would like to nd it, exactly as he would do by searching the Web for
information. As a consequence, in this paper we talk about Web service retrieval
rather than discovery. A number of Web service catalogues and directories have
1 A very interesting discussion about the interplay between spatial and temporal
description is taking place within the W3C Locations and Addresses Community
Group, cf. http://www.w3.org/community/locadd/.
emerged2, both as pure editorial e orts or collaborative wiki-like initiatives;
developers can look for services via traditional keyword-based search or category
facets/ lters. Along those lines, some proposals emerged within the Semantic
Web community to build scalable \search engines" for Web services [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ], by
focusing on simple yet e ective ontological models to enable service retrieval (like
the minimal ontologies proposed by [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ] and [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ]).
        </p>
        <p>In the context of cities, the same considerations are valid and it is clear
that a city service description should include spatial information to allow for a
geo-based retrieval (e.g. which public transportation services cover an area of x
kilometre radius from this position?). Within a CSE, in which multiple actors
cooperate and compete, other service details are very important, like usage terms
and conditions: a semantic description of such non-functional properties of urban
services should be mandatory for a semantic CSE.</p>
        <p>It is worth noting that such non-functional description are not only limited
to generic business rules (e.g., whether a service is available to everybody vs.
limited to registered users, or provided for free vs. requiring a fee), but also
to city-speci c peculiarities and conditions related to the actual usage of such
services (e.g. is a ticket from a transportation service valid to travel with another
provider? will a shuttle bus connection service wait for the arrival of a speci c
train service in case of delay?): with the increasing blending of the physical and
cyber systems, digital representations of such features becomes essential for an
e ective governance of a CSE.
4</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>The experience of E 15 Digital Ecosystem</title>
      <p>Milan will host the World Exposition in 2015 whose main theme is \Feeding the
Planet, Energy for Life"3. This event is a major opportunity to introduce
disruptive innovations in all aspects of the urban life: infrastructures, transportation,
cultural and social life, accommodation, services and facilities.</p>
      <p>
        E 15 [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ] is a CSE enabling and fostering interoperability between di erent
organizations and companies, from both the private and public sector, that can
join the digital ecosystem for free4. It is a business environment where the
participants openly publish their Web services and APIs, described both in terms
of functionalities and in terms of rules and usage policies (licenses, service level
agreements and possible remuneration models are speci ed and made available).
Interoperability is based on open standards: Web Service interoperability
speci cations (e.g., WS-I Basic Pro le 1.1 [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]) and security standards (e.g., WS-I
Basic Security Pro le 1.1 [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ]). Usage requests and access to services are
regulated by common guidelines and processes.
      </p>
      <p>While in its current realization, E 15 does not make use of semantic
technologies, all the issues related to an e ective description of the o ered services
emerged during its design and development. In order to lower the entry barrier
2 Like the very popular ProgrammableWeb, http://www.programmableweb.com/.
3 Cf. http://en.expo2015.org/.
4 Cf. http://www.e015.expo2015.org/.
for participants, E 15 requires providers to compile a form to describe their
services (besides producing the technical details, for example WSDL les): the
completed forms can be the basis for a semantic description of E 15 services.
We are currently exploring and comparing the di erent existing ontologies to
describe Web services, in order to come up with a simple but powerful model,
able to cover both SOAP-based services and APIs and REST services; we are
adopting a bottom-up approach, by starting from the concrete E 15 services so
to take into consideration all the concrete requirements coming from a real CSE.
While E 15 currently encompasses services mainly in the domains of
transportation, accommodation and tourism, we believe it is an interesting test-bed
to experiment with semantic technologies.</p>
      <p>E 15 also fosters interoperability at data level by promoting sharing and
reuse of glossaries between di erent services; for example, the services providing
real-time information about ight arrivals and departures of the three airports
around Milano, even if operated by di erent stakeholders, adopted the same
service interface and data structures5. Semantic technologies can for sure play
an important role in de ning common and shared vocabularies and ontologies
and in paving the ground for an improved interoperability of city services.
5</p>
    </sec>
    <sec id="sec-4">
      <title>Conclusions and Outlook</title>
      <p>In this paper, we introduced the concept of a City Service Ecosystem and we
explained the rational and the possible bene ts of adopting \a little semantics"6
to improve city service descriptions and enable an easier service retrieval and an
improved interoperability at city level. We are currently applying the
considerations expressed in this paper to enhance the E 15 service ecosystem of Milano;
our plan is to design and develop a semantic registry for city services (something
like LOV7 for services) and to enable a semantically-enhanced retrieval of those
services.</p>
    </sec>
    <sec id="sec-5">
      <title>Acknowledgments</title>
      <p>This work was supported by SPAC3 (project id 40696059) co-funded by Regione
Lombardia (POR-FESR 2007-2013), and by 3cixty (id 14523) and Connecting
Digital Cities (id 14465) projects co-funded by EIT.
5 The di erent providers were invited to agree on a common conceptualization and
they thus adopted the same model, perceiving the value of sharing such \semantics".
6 Cf. http://www.cs.rpi.edu/~hendler/LittleSemanticsWeb.html.
7 CF. http://lov.okfn.org/.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Gat</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Succi</surname>
          </string-name>
          , G.:
          <article-title>A Survey of the API Economy</article-title>
          .
          <source>Agile Product and Project Management Executive Update</source>
          <volume>14</volume>
          (
          <issue>6</issue>
          ) (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Brandenburger</surname>
            ,
            <given-names>A.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nalebu</surname>
            ,
            <given-names>B.J.:</given-names>
          </string-name>
          <article-title>Co-opetition</article-title>
          .
          <source>Random House Digital</source>
          , Inc. (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Lausen</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Polleres</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Roman</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <string-name>
            <surname>Web Service Modeling Ontology (WSMO). W3C Member Submission</surname>
          </string-name>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Martin</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Burstein</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hobbs</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lassila</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McDermott</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McIlraith</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Narayanan</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Paolucci</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Parsia</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Payne</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sirin</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Srinivasan</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sycara</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>OWL-S: Semantic Markup for Web Services</article-title>
          .
          <article-title>W3C member submission (</article-title>
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Akkiraju</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Farrell</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Miller</surname>
            ,
            <given-names>J.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nagarajan</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sheth</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Verma</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Web Service Semantics { WSDL-S. Technical report</article-title>
          , IBM and University of Georgia (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Sivashanmugam</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Verma</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sheth</surname>
            ,
            <given-names>A.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Miller</surname>
            ,
            <given-names>J.A.</given-names>
          </string-name>
          :
          <article-title>Adding Semantics to Web Services Standards</article-title>
          .
          <source>In: 1st International Conference on Web Services</source>
          . (
          <year>2003</year>
          )
          <volume>395</volume>
          {
          <fpage>401</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Wilde</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pautasso</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          : REST: From Research to Practice. Springer (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Verborgh</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Harth</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maleshkova</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , Stadtmuller,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Steiner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            ,
            <surname>Taheriyan</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.</surname>
          </string-name>
          , Van de Walle, R.:
          <article-title>Survey of Semantic Description of REST APIs</article-title>
          .
          <source>In: REST: Advanced Research Topics and Practical Applications</source>
          . Springer (
          <year>2014</year>
          )
          <volume>69</volume>
          {
          <fpage>89</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Lanthaler</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Leveraging Linked Data to Build Hypermedia-Driven Web APIs</article-title>
          .
          <source>In: REST: Advanced Research Topics and Practical Applications</source>
          . Springer (
          <year>2014</year>
          )
          <volume>107</volume>
          {
          <fpage>123</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Janowicz</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Scheider</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pehle</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hart</surname>
          </string-name>
          , G.:
          <article-title>Geospatial semantics and linked spatiotemporal data { Past, present, and future</article-title>
          .
          <source>Semantic Web</source>
          <volume>3</volume>
          (
          <issue>4</issue>
          ) (
          <year>2012</year>
          )
          <volume>321</volume>
          {
          <fpage>332</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Grossner</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Janowicz</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ke ler</surname>
          </string-name>
          , C.:
          <string-name>
            <surname>Place</surname>
          </string-name>
          , Period, and
          <article-title>Setting for Linked Data Gazetteers</article-title>
          . In JR. Mostern,
          <string-name>
            <given-names>H.</given-names>
            <surname>Southall</surname>
          </string-name>
          , M.B., ed.: Placing Names: Enriching and
          <string-name>
            <given-names>Integrating</given-names>
            <surname>Gazetteers</surname>
          </string-name>
          . Indiana University Press, Bloomington, IN (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <given-names>Della</given-names>
            <surname>Valle</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            ,
            <surname>Cerizza</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Celino</surname>
          </string-name>
          ,
          <string-name>
            <surname>I.</surname>
          </string-name>
          :
          <article-title>The mediator centric approach to Automatic Web Service Discovery of Glue</article-title>
          . MEDIATE2005
          <volume>168</volume>
          (
          <year>2005</year>
          )
          <volume>35</volume>
          {
          <fpage>50</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Carenini</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cerizza</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Comerio</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>Della</given-names>
            <surname>Valle</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            ,
            <surname>De Paoli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            ,
            <surname>Maurino</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Palmonari</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Turati</surname>
          </string-name>
          ,
          <string-name>
            <surname>A.</surname>
          </string-name>
          :
          <article-title>Glue2: A Web Service Discovery Engine with NonFunctional Properties</article-title>
          .
          <source>In: IEEE Sixth European Conference on Web Services (ECOWS)</source>
          ,
          <source>IEEE</source>
          (
          <year>2008</year>
          )
          <volume>21</volume>
          {
          <fpage>30</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Steinmetz</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lausen</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brunner</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Web service search on large scale</article-title>
          .
          <source>In: Service-Oriented Computing</source>
          . Springer (
          <year>2009</year>
          )
          <volume>437</volume>
          {
          <fpage>444</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <given-names>Della</given-names>
            <surname>Valle</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            ,
            <surname>Cerizza</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Celino</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I.</given-names>
            ,
            <surname>Turati</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Lausen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            ,
            <surname>Steinmetz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            ,
            <surname>Erdmann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Funk</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            :
            <surname>Realizing</surname>
          </string-name>
          Service-Finder:
          <article-title>Web service discovery at web scale</article-title>
          .
          <source>In: European Semantic Technology Conference (ESTC)</source>
          , Vienna. (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Kopecky</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vitvar</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pedrinaci</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maleshkova</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>RESTful services with lightweight machine-readable descriptions and semantic annotations</article-title>
          . In: REST: From Research to Practice. Springer (
          <year>2011</year>
          )
          <volume>473</volume>
          {
          <fpage>506</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Celino</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bonardi</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fuggetta</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          : E 15:
          <article-title>a Digital Ecosystem promoting Open Innovation and Coopetition (</article-title>
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Ballinger</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ehnebuske</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ferris</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gudgin</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Liu</surname>
            ,
            <given-names>C.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nottingham</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yendluri</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <source>Basic Pro le Version 1</source>
          .1.
          <string-name>
            <given-names>Web</given-names>
            <surname>Services-Interoperability Organization (WS-I)</surname>
          </string-name>
          (
          <year>2006</year>
          ) Available at http://www.ws-i.org/Profiles/BasicProfile-1.1. html.
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>McIntosh</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gudgin</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Morrison</surname>
            ,
            <given-names>K.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Barbir</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <source>Basic Security Pro le Version 1</source>
          .1.
          <string-name>
            <given-names>Web</given-names>
            <surname>Services-Interoperability Organization (WS-I)</surname>
          </string-name>
          (
          <year>2010</year>
          ) Available at http://www.
          <source>ws-i.org/profiles/basicsecurityprofile-1</source>
          .1.html.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>