<?xml version="1.0" encoding="UTF-8"?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
  <responseDate>2026-07-21T20:32:03Z</responseDate>
  <request identifier="829" metadataPrefix="oai_dc" verb="GetRecord">https://drops.dagstuhl.de/oai</request>
  <GetRecord>
    <record>
      <header>
        <identifier>oai:drops-oai.dagstuhl.de:829</identifier>
        <datestamp>2024-03-06T11:06:58Z</datestamp>
        <setSpec>ddc:004</setSpec>
        <setSpec>open_access</setSpec>
      </header>
      <metadata>
        <oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
          <dc:title>DecSerFlow: Towards a Truly Declarative Service Flow Language</dc:title>
          <dc:creator>van der Aalst, Wil</dc:creator>
          <dc:creator>Pesic, Maja</dc:creator>
          <dc:subject>DecSerFlow</dc:subject>
          <dc:subject>LTL</dc:subject>
          <dc:subject>service flows</dc:subject>
          <dc:subject>web services</dc:subject>
          <dc:subject>SOA</dc:subject>
          <dc:description>The need for process support in the context of web services&#13;
has triggered the development of many languages, systems, and standards. &#13;
Industry has been developing software solutions and proposing&#13;
standards such as BPEL, while researchers have been advocating the&#13;
use of formal methods such as Petri nets and pi-calculus. The languages&#13;
developed for service flows, i.e., process specification languages for web&#13;
services, have adopted many concepts from classical workflow management &#13;
systems. As a result, these languages are rather procedural and&#13;
this does not fit well with the autonomous nature of services. Therefore,&#13;
we propose DecSerFlow as a Declarative Service Flow Language. DecSerFlow &#13;
can be used to specify, enact, and monitor service flows. The&#13;
language is extendible (i.e., constructs can be added without changing&#13;
the engine or semantical basis) and can be used to enforce or to check the&#13;
conformance of service flows. Although the language has an appealing&#13;
graphical representation, it is grounded in temporal logic.</dc:description>
          <dc:publisher>Schloss Dagstuhl – Leibniz-Zentrum für Informatik</dc:publisher>
          <dc:contributor>Wil van der Aalst and Maja Pesic</dc:contributor>
          <dc:date>2006</dc:date>
          <dc:relation>Is Part Of Dagstuhl Seminar Proceedings, Volume 6291, The Role of Business Processes in Service Oriented Architectures (2006)</dc:relation>
          <dc:type>InProceedings</dc:type>
          <dc:type>Text</dc:type>
          <dc:type>doc-type:ResearchArticle</dc:type>
          <dc:type>publishedVersion</dc:type>
          <dc:format>application/pdf</dc:format>
          <dc:identifier>doi:10.4230/DagSemProc.06291.10</dc:identifier>
          <dc:identifier>urn:nbn:de:0030-drops-8298</dc:identifier>
          <dc:identifier>https://drops.dagstuhl.de/entities/document/10.4230/DagSemProc.06291.10</dc:identifier>
          <dc:language>eng</dc:language>
          <dc:rights>https://creativecommons.org/licenses/by/4.0/legalcode</dc:rights>
        </oai_dc:dc>
      </metadata>
    </record>
  </GetRecord>
</OAI-PMH>
