<!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>A Semantic Framework to Compose RESTful Services</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Luís Antonio de Almeida Rodriguez</string-name>
          <email>rodriguezlaar@gmail.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Francisco de Oliveira</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>José Maria Parente de Oliveira</string-name>
          <email>parente@ita.br</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Aeronautics Institute of Technology</institution>
          ,
          <addr-line>São José dos Campos-SP</addr-line>
          ,
          <country country="BR">Brazil</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2026</year>
      </pub-date>
      <fpage>174</fpage>
      <lpage>180</lpage>
      <abstract>
        <p>The widespread adoption of RESTful services has led to a fragmented representational ecosystem, where the lack of a formal semantic description model hinders the reliable and automated composition of services. Reliance on nonstandardized and non-machine-processable documentation introduces integration inconsistencies in distributed functionalities, requiring manual intervention to resolve ambiguities. This paper proposes an ontology-based semantic orchestration model for the composition of RESTful services, addressing two critical gaps: (i) the absence of a semantic model for describing RESTful service features; and (ii) the lack of semantic matching mechanisms for semantic orchestrations. This model proposes an ontological approach for the semantic orchestration of atomic and composite RESTful services' processes, enabling automated discovery and aggregation. This paper also presents an experimental evaluation within the context of the ICAO's SWIM program, demonstrating the efectiveness of composing RESTful shared services. Moreover, the approach reduces manual integration eforts compared to existing methods. The results suggest that the framework provides a replicable paradigm for large-scale service composition, representing an advance toward sustainable interoperability in heterogeneous distributed systems.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;RESTful services</kwd>
        <kwd>Service Composition</kwd>
        <kwd>OWL-S</kwd>
        <kwd>Ontologies</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        The growing adoption of RESTful services as a dominant architecture for web-based system
integration has brought significant advancements in scalability, simplicity, and interoperability over the last
decade. This type of service on the Web [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] is typically lightweight, stateless, and aligned with HTTP
standards, making it suitable for cloud-native applications, public data platforms, and domain-specific
APIs. However, despite their technical advantages, the RESTful paradigm sufers from a profound
limitation when it comes to composing multiple services into a coherent workflow [
        <xref ref-type="bibr" rid="ref2 ref3">2, 3</xref>
        ]. Unlike earlier
service-oriented approaches such as SOAP with WSDL and UDDI, RESTful services often lack formal
mechanisms for description, discovery, and orchestration, which hampers their reuse and automation
across heterogeneous environments.
      </p>
      <p>
        One of the critical challenges in composing RESTful services lies in their documentation. In most
cases, RESTful APIs are described informally through human-readable resources such as HTML pages,
Swagger/OpenAPI files, or vendor-specific guides [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Although these formats may help developers
during manual implementation, they do not allow machine-based reasoning or semantic search [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. As
a result, service integration becomes an error-prone, non-scalable, and context-dependent process that
depends heavily on developer interpretation and custom integration logic. This becomes particularly
problematic when attempting to aggregate services provided by independent organizations, each
adhering to diferent naming conventions, data structures, and interface assumptions.
      </p>
      <p>
        The absence of a unified standard to semantically describe the behavior and capabilities of RESTful
services exacerbates the situation [
        <xref ref-type="bibr" rid="ref3 ref5">3, 5</xref>
        ]. Without a shared vocabulary or formal representation of
the functionalities of the service, there is no reliable way to automate the discovery, matching, or
composition of services based on their meaning or role in a process. This severely limits the potential for
dynamic service orchestration in domains that demand agility, such as meteorology, logistics, healthcare,
and air trafic management. For these sectors, the ability to semantically describe and connect service
processes is fundamental to achieving interoperability, scalability, and intelligent automation.
      </p>
      <p>
        This paper addresses these issues by proposing a semantic framework for describing and orchestrating
RDF Knowledge Graphs representing RESTful services using ontologies, specifically by extending an
OWL-S-based model presented in [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], which extends OWL-S to RESTful architectures. The identified
core problem is the absence of an agreed-upon semantic representation for service processes that
enables semantic orchestration and reasoning, which will enable automatic composition based on QoS
criteria by any API. The proposed solution introduces an ontologically grounded approach for describing
RESTful service capabilities, including the associations between atomic and composite processes, with
an agreed-upon semantic language that integrates and allows automated extraction of information
from the ontologies. A case study based on a meteorological service platform used in aviation (e.g.,
REDEMET-API) presents the efectiveness and applicability of this model within the broader context of
global civil aviation and SWIM (System Wide Information Management).
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. Semantic Standardization in SWIM and the Role of OWL-S</title>
      <p>The System Wide Information Management (SWIM) program, coordinated by the International Civil
Aviation Organization (ICAO), is a global initiative that standardizes information exchange and fosters
interoperability across civil aviation systems [? ]. SWIM incorporates data exchange models, governance
methodologies, and infrastructure patterns to ensure eficient, secure, and machine-readable distribution
of air trafic information. Its primary objective is to enhance the availability, accessibility, and consistency
of air navigation data across national and organizational boundaries. By complementing traditional
human-to-human communication with structured and automated information flows, SWIM establishes
an environment where stakeholders benefit from high-quality semantic data exchange, which is critical
for safety, scalability, and international collaboration [? ].</p>
      <p>The alignment of SWIM with W3C Semantic Web standards is achieved through the OWL-S ontology,
which provides the formal structure to represent service capabilities, behaviors, and grounding protocols
in a machine-interpretable manner. ICAO and EUROCONTROL documentation emphasize OWL-S as
a foundational tool for semantic interoperability, ensuring precise, reusable, and automated service
descriptions [? ]. However, since OWL-S was originally grounded in SOAP-based infrastructures,
extending its principles to RESTful architectures is necessary. This research contributes by adapting
OWL-S to REST semantics—incorporating HTTP verbs, URIs, content negotiation, and resource
representation types—thus bridging the gap between traditional SOAP/WSDL-based services and modern
Web services. This ontology-driven extension enables automated discovery, quality-aware
composition, and accurate invocation of RESTful services, fulfilling SWIM’s requirements for semantic-native
interoperability in heterogeneous and distributed aviation environments.</p>
    </sec>
    <sec id="sec-3">
      <title>3. A Semantic Orchestration Model</title>
      <p>The goals of this section are the following.</p>
      <p>
        1. To extend the work presented in [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] and create a semantic model to support the orchestration
of service process relationships to automate the composition of services by APIs. Building
upon the OWL-S extension developed in this paper, where RESTful services’ processes have an
ontologically defined taxonomy using ’Atomic’ and ’Composite’ classifications, this work involved
classifying those implemented SOA-unit service processes and building an RDF Knowledge Graph
by associating them, creating a RDF Knowledge Graph.
2. Refactor the software proposed in [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] and develop a new functionality to perform automated
dynamic service composition, driven by the common web user’s own choices. Specifically, this
functionality leverages the semantically enriched processes already orchestrated in the model
and links them with the REDEMET-API RESTful services, generalizing the composition coded
with Python to accommodate service descriptions with diferent abstraction levels.
      </p>
      <p>
        The orchestration logic, grounded in OWL-S’ ontological compatibility, enables any API to integrate
diverse services into cohesive workflows without requiring manual intervention. This enhancement
addresses the broader vision of democratizing service composition, allowing non-expert users to trigger
complex sets of services by specifying ’Quality of Service Level’ ranks for each one. In doing so, this
paper’s proposal reinforces the practical value of semantic description environments in real-world web
architectures and extends the OWL-S adaptation presented in [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] toward multi-provider interoperability
for intelligent compositions.
      </p>
      <p>
        The central point of this section is the Process ontology, exactly as it is presented in [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. This ontology,
within the extension of OWL-S proposed in this paper, serves as a foundational component to describe
the behavioral dynamics of services on the Web. Its internal structure is systematically organized
according to several defining criteria that establish the functional and operational semantics of service
processes. These criteria facilitate the semantic search, and the specific Atomic-Composite association
facilitates service composition. Central to this ontology are the Inputs, Outputs, Preconditions, and
Efects (IOPE), which provide a formal specification of a service’s capability, allowing for precise
semantic matching during service discovery. Precise search and discovery of services are essential
prerequisites for service composition; finding the best services enables the creation of an optimal
composition.
      </p>
      <p>
        Martin [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] comments that Atomic processes represent indivisible actions with direct invocations,
while Composite processes, on the other hand, define complex associations through atomic or other
composite processes. The Process ontology’s ontological representation enforces a strict taxonomic
distinction whereby every individual of the Process class must also be instantiated as a member of
AtomicProcess. Figure 1 shows that some of them are instances of the CompositeProcess class,
in full compliance with the foundational specifications of OWL-S. This mandatory classification is
formally realized through two canonical inverse properties, as depicted in the modeling presented in [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
Figure 1 illustrates that:
• expandsTo - An ’Aggregation’: AtomicProcess → CompositeProcess
      </p>
      <p>This dual-property framework ensures both structural integrity and semantic consistency in process
decomposition, thereby enabling rigorous reasoning over service composition orchestrations such as
this one. Using these properties, it is possible to select all instances of services already implemented
and insert their ’process entities’ into the existing OWL classes: Atomic and Composite, in the Process
ontology. After that, associations among composite and atomic entities are necessary using object
properties already defined in this ontology (e.g., collapsesTo and expandsTo). Why classify them all as
atomic and some as composite? By doing this, it is possible to establish two types of composition:
• A composite service composed only of atomic services, and
• A composite service composed of atomic and other composite services.</p>
      <p>
        The formalization of service processes classification and maximization was given considering the
OWL-S Compliant Knowledge Graph. According to [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], all instances of service processes within the
developed knowledge base have been systematically classified as members of the AtomicProcess
class, and some were classified in the CompositeProcess class. This strict taxonomic enforcement
ensures adherence to the foundational semantics of OWL-S and a new characteristic: the ability to
create composite services composed of other composite services.
      </p>
      <p>
        To establish machine-interpretable semantic relationships between processes, each instance of a
process from the semantic registry built in [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] has been explicitly associated with the canonical object
properties collapsesTo and expandsTo, thereby formalizing hierarchical dependencies within service
compositions:
• AtomicProcess individuals represent an indivisible service set of operations, with no further
decomposition permitted under the axiomatic constraints of the ontology (e.g., even for ’composite
services’ classified as such).
• CompositeProcess individuals are structured aggregations of subprocesses, recursively defined
via the collapsesTo property, which links a composite service to its constituent atomic or nested
composite processes.
      </p>
      <p>The resultant RDF knowledge graph encodes these relationships as semantically described triples,
conforming to OWL-S specifications while enabling advanced querying capabilities. Through SPARQL
queries, the graph can be interrogated to:
• Retrieve atomic services meeting specific functional criteria (e.g., inputs/outputs, preconditions);
• Decompose composite services into their procedural workflows, exposing nested execution logic;
• Validate process compositions by reasoning over property constraints.</p>
      <p>The structured representation presented in Figure 1 collaborates with more criteria for the discovery
of semantic services and the analysis of automated composition, as the formal semantics of the graph
permit inference about the compatibility of processes and behavioral equivalence. It is possible to
mention some consequences of applying our model proposed in Figure 1 to the resulting RDF Knowledge
Graph:
• Establishment of a hierarchical process topology
• Creation of an explicit definition of the service composition paths through relationships among
nodes, represented by Triples
• A layer of descriptions made by semantic machine-readable composition patterns
By formalizing process hierarchies, constraints, and operational logic, the Process Ontology ensures
that services can be dynamically discovered, composed, and invoked in a semantically consistent
manner.</p>
    </sec>
    <sec id="sec-4">
      <title>4. Case Study</title>
      <sec id="sec-4-1">
        <title>4.1. Motivation</title>
        <p>
          RESTful aeronautical service development communities encounter systemic interoperability barriers
due to representational fragmentation: a divergence in service description models [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ]. This causes a
huge development efort to build APIs able to use RESTful shared services on the Web.
This study addresses the urgent need to realize SWIM’s vision of seamless and standardized air trafic
management (ATM) data exchange between the ICAO member states, aiming to improve the ability to
use shared RESTful services [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ] to create more complex services. SWIM’s proposed semantic enrichment
of service descriptions transforms interoperability from a legacy concept into a natively standardized
communication paradigm, enabling a globally harmonized aviation data interoperability. Building on
existing frameworks, this paper aims to bridge these gaps, ensuring deterministic composition made by
software through semantically enriched service descriptions.
        </p>
      </sec>
      <sec id="sec-4-2">
        <title>4.2. Orchestrating and Composing Complex RESTful Services</title>
        <p>
          The article by Rodriguez and Parente de Oliveira [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ] presents a rigorous semantic model designed to
enable the composition of RESTful services through ontologically grounded orchestration. Drawing on
the foundational architecture of OWL-S, the model presents a dual-level abstraction also presented in
the original OWL-S: atomic and composite processes. Each SOA-unit service registered in this semantic
registry has its process entity semantically annotated and encapsulated within a class called Atomic
process, which is connected, in the RDF Knowledge Graph, with entities that describe its capabilities,
such as inputs, outputs, preconditions, and efects (IOPE).
        </p>
        <p>
          Composite processes are structured as orchestrations of atomic processes made to define the logical
and temporal relations between service calls [
          <xref ref-type="bibr" rid="ref5 ref8">8, 5</xref>
          ]. This semantic representation enables reasoning
engines to identify, match, and bind services dynamically, thereby automating the composition of
services into coherent workflows. To instantiate the model presented in [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ], the authors applied it in a
case study involving the semantic representation and orchestration of 23 SOA unit services from the
original model. The propagation of the orchestration of SOA-unit services will reach 17 RESTful services
provided by REDEMET-API [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ], and three other RESTful services as part of a provider specifically
created in the registry for this paper, the SWIM Provider. The SOA-unit services’ process entities
were first formalized as an atomic process, where the semantic annotations create an atomic foundation
for serving several composite processes.
        </p>
        <p>
          The semantic orchestration presented in this paper was implemented in the Process ontology, such
as in [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ] using Protégé 5.5. The procedure begins with the import of the OWL-S ontology into a new
project. The entity of the process of each generic service was created in the ServiceModel class as
an instance of the AtomicProcess class. The HTTP semantics, including the type of the method and
the endpoint URI, were encoded through custom data properties or extended using existing ontologies
such as Aerodrome, Country, and RESTfulExtension.
        </p>
        <p>
          Subsequently, composite processes were created using the CompositeProcess class, and their
execution flow was defined via semantic relationships between the processes using Object Properties
already existing in the previous model [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ]. This ultimately results in a machine-interpretable semantic
representation that captures the logic of SOA-unit composite services and propagates to the constraints
and sequencing of the REDEMET-API RESTful services network. This case study implementation
efort produced a machine-interpretable semantic infrastructure that not only encapsulates the logic
of composite SOA-unit services but also propagates the predefined features about process sequencing
across the REDEMET-API meteorological RESTful services network.
        </p>
        <p>The case study practical outcomes are multifold: for the developers community, it ofers a reusable
and extensible description model for service composition’s orchestration; for global civil aviation, the
model aligns with SWIM’s vision of semantic interoperability and dynamic information sharing; for end
users and companies, it enables intelligent service discovery and automated interaction, thus reducing
integration costs, enhancing scalability, and paving the way for a new generation of semantically aware
RESTful ecosystems.</p>
        <p>The orchestration model proposed and implemented in this study provides concrete generic-domain
benefits by enabling a semantic composition framework that propagates from generic SOA-units
to specific RESTful services. By providing a formal semantic description, developers can automate
essential events of the composition pipeline, replacing ad hoc scripting and manual configuration
with logically inferred orchestration. By ofering semantic transparency and structural formalization,
the orchestration mechanism allows heterogeneous provider services to be composed into reliable
workflows without human intervention, enhancing situational awareness, operational eficiency, and
safety. Beyond aviation, the approach serves as a generic technological contribution to the field of
service composition by demonstrating that OWL-S-based semantic models can be successfully adapted
to RESTful paradigms.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Conclusions</title>
      <sec id="sec-5-1">
        <title>5.1. Contributions</title>
        <p>
          A key contribution is the definition of a novel orchestration format, grounded in OWL-S and enriched
with precise object properties (e.g., expandsTo, collapsesTo), which allows developers to express
composition relationships among services with reduced syntactic ambiguity. It reduces the cognitive and
technical efort required to construct complex service integrations, exactly as evaluated in [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ], replacing
heuristic-based composition methods with logic-based reasoning. Moreover, by implementing and
validating the model over a real-world API—REDEMET, the paper contributes a reusable,
standardsaligned methodology for modeling and composing RESTful services in domains requiring high semantic
precision, such as civil aviation under the SWIM framework.
        </p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>Declaration on Generative AI</title>
      <p>During the preparation of this work, the author(s) used Deep Seek as a tutor for English Grammar
Correction.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>R. T.</given-names>
            <surname>Fielding</surname>
          </string-name>
          ,
          <article-title>Architectural Styles and the Design of Network-based Software Architectures</article-title>
          ,
          <source>Ph.d. dissertation</source>
          , University of California, Irvine, Irvine, CA, USA,
          <year>2000</year>
          . URL: https://www.ics.uci.edu/ ~fielding/pubs/dissertation/fielding_dissertation.pdf.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Gamha</surname>
          </string-name>
          ,
          <article-title>A framework for rest services discovery and composition</article-title>
          ,
          <source>Service Oriented Computing and Applications</source>
          <volume>17</volume>
          (
          <year>2023</year>
          )
          <fpage>259</fpage>
          -
          <lpage>275</lpage>
          . doi:
          <volume>10</volume>
          .1007/s11761-023-00376-6.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>M.</given-names>
            <surname>Bennara</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Mrissa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Amghar</surname>
          </string-name>
          ,
          <article-title>An approach for composing restful linked services on the web</article-title>
          ,
          <source>in: Proceedings of the 23rd International Conference on World Wide Web</source>
          , Seoul, South Korea,
          <year>2014</year>
          . doi:
          <volume>10</volume>
          .1145/2567948.2579222,
          <fpage>hal</fpage>
          -
          <lpage>01212722v2</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>REDEMET-API</surname>
          </string-name>
          , Brazilian Aeronautical Provider, https://ajuda.decea.mil.br/base-de
          <article-title>-conhecimento/ api-redemet-</article-title>
          <string-name>
            <surname>o-</surname>
          </string-name>
          que-e/,
          <year>2025</year>
          . Accessed: Apr.
          <volume>16</volume>
          ,
          <year>2025</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>L. A. A.</given-names>
            <surname>Rodriguez</surname>
          </string-name>
          ,
          <string-name>
            <surname>J. M. P. de Oliveira</surname>
          </string-name>
          ,
          <article-title>A semantic model to describe restful services</article-title>
          ,
          <source>IEEE Access 13</source>
          (
          <year>2025</year>
          )
          <fpage>72402</fpage>
          -
          <lpage>72426</lpage>
          . doi:
          <volume>10</volume>
          .1109/ACCESS.
          <year>2025</year>
          .
          <volume>3562503</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>D.</given-names>
            <surname>Martin</surname>
          </string-name>
          ,
          <article-title>Bringing semantics to web services: The owl-s approach</article-title>
          ,
          <source>IEEE Intelligent Systems</source>
          <volume>22</volume>
          (
          <year>2007</year>
          )
          <fpage>72</fpage>
          -
          <lpage>81</lpage>
          . doi:
          <volume>10</volume>
          .1109/MIS.
          <year>2007</year>
          .
          <volume>100</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>EUROCONTROL</surname>
          </string-name>
          ,
          <article-title>Swim technical infrastructure and governance: Semantic interoperability guidelines</article-title>
          ,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>OWL-S Coalition</surname>
          </string-name>
          ,
          <article-title>Owl-s: Semantic markup for web services</article-title>
          ,
          <source>version 1</source>
          .2, https://www.daml.org/ services/owl-s/1.2/,
          <year>2006</year>
          .
          <article-title>Released by the OWL-S Coalition, including members from SRI International</article-title>
          , Carnegie Mellon University, BBN Technologies, and University of Maryland.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>