Providing Transactional Properties for Migrating Workflows View Full Text


Ontology type: schema:ScholarlyArticle     


Article Info

DATE

2004-10

AUTHORS

Andrzej Cichocki, Marek Rusinkiewicz

ABSTRACT

Current workflow management systems have several limitations that need to be addressed by the research community. This paper deals with two of them: the lack of flexibility necessary in a changing business environment, and the lack of transactional guarantees for workflow applications. To handle the dynamic character of current business environments and processes, we have proposed the Migrating Workflow Model. A migrating workflow transfers its code (specification) and its execution state to a site, negotiates a service to be executed on its behalf, receives the results, and moves on. The next place visited by the workflow, and the next service requested, is determined by both the objectives of the process and the results of the current requests. The transactional properties are addressed by merging of the Migrating Workflow Model with a Transactional Workflow Model, in which the workflow designer has the ability of specifying, independently, the task coordination requirements, the failure atomicity requirements, and the execution atomicity requirements. The result, described in this paper, is a migrating workflow model endowed with transactional properties that guarantee the correct execution of workflow applications in the presence of failures and in the presence of concurrent access to shared data. More... »

PAGES

473-480

Identifiers

URI

http://scigraph.springernature.com/pub.10.1023/b:mone.0000034701.73879.cf

DOI

http://dx.doi.org/10.1023/b:mone.0000034701.73879.cf

DIMENSIONS

https://app.dimensions.ai/details/publication/pub.1051270669


Indexing Status Check whether this publication has been indexed by Scopus and Web Of Science using the SN Indexing Status Tool
Incoming Citations Browse incoming citations for this publication using opencitations.net

JSON-LD is the canonical representation for SciGraph data.

TIP: You can open this SciGraph record using an external JSON-LD service: JSON-LD Playground Google SDTT

[
  {
    "@context": "https://springernature.github.io/scigraph/jsonld/sgcontext.json", 
    "about": [
      {
        "id": "http://purl.org/au-research/vocabulary/anzsrc-for/2008/0806", 
        "inDefinedTermSet": "http://purl.org/au-research/vocabulary/anzsrc-for/2008/", 
        "name": "Information Systems", 
        "type": "DefinedTerm"
      }, 
      {
        "id": "http://purl.org/au-research/vocabulary/anzsrc-for/2008/08", 
        "inDefinedTermSet": "http://purl.org/au-research/vocabulary/anzsrc-for/2008/", 
        "name": "Information and Computing Sciences", 
        "type": "DefinedTerm"
      }
    ], 
    "author": [
      {
        "affiliation": {
          "alternateName": "Ericsson (United States)", 
          "id": "https://www.grid.ac/institutes/grid.432790.b", 
          "name": [
            "Information and Computer Sciences Research Laboratory, Telcordia Technologies, USA"
          ], 
          "type": "Organization"
        }, 
        "familyName": "Cichocki", 
        "givenName": "Andrzej", 
        "id": "sg:person.0620441046.64", 
        "sameAs": [
          "https://app.dimensions.ai/discover/publication?and_facet_researcher=ur.0620441046.64"
        ], 
        "type": "Person"
      }, 
      {
        "affiliation": {
          "alternateName": "Ericsson (United States)", 
          "id": "https://www.grid.ac/institutes/grid.432790.b", 
          "name": [
            "Information and Computer Sciences Research Laboratory, Telcordia Technologies, USA"
          ], 
          "type": "Organization"
        }, 
        "familyName": "Rusinkiewicz", 
        "givenName": "Marek", 
        "id": "sg:person.015306104725.95", 
        "sameAs": [
          "https://app.dimensions.ai/discover/publication?and_facet_researcher=ur.015306104725.95"
        ], 
        "type": "Person"
      }
    ], 
    "citation": [
      {
        "id": "https://doi.org/10.1016/s0306-4379(99)00026-5", 
        "sameAs": [
          "https://app.dimensions.ai/details/publication/pub.1006585768"
        ], 
        "type": "CreativeWork"
      }, 
      {
        "id": "sg:pub.10.1007/978-3-642-58908-9_15", 
        "sameAs": [
          "https://app.dimensions.ai/details/publication/pub.1019381722", 
          "https://doi.org/10.1007/978-3-642-58908-9_15"
        ], 
        "type": "CreativeWork"
      }, 
      {
        "id": "sg:pub.10.1007/bf00119339", 
        "sameAs": [
          "https://app.dimensions.ai/details/publication/pub.1024666070", 
          "https://doi.org/10.1007/bf00119339"
        ], 
        "type": "CreativeWork"
      }, 
      {
        "id": "https://doi.org/10.1142/s0218215792000155", 
        "sameAs": [
          "https://app.dimensions.ai/details/publication/pub.1062965327"
        ], 
        "type": "CreativeWork"
      }, 
      {
        "id": "https://doi.org/10.7146/dpb.v19i338.6569", 
        "sameAs": [
          "https://app.dimensions.ai/details/publication/pub.1073611135"
        ], 
        "type": "CreativeWork"
      }
    ], 
    "datePublished": "2004-10", 
    "datePublishedReg": "2004-10-01", 
    "description": "Current workflow management systems have several limitations that need to be addressed by the research community. This paper deals with two of them: the lack of flexibility necessary in a changing business environment, and the lack of transactional guarantees for workflow applications. To handle the dynamic character of current business environments and processes, we have proposed the Migrating Workflow Model. A migrating workflow transfers its code (specification) and its execution state to a site, negotiates a service to be executed on its behalf, receives the results, and moves on. The next place visited by the workflow, and the next service requested, is determined by both the objectives of the process and the results of the current requests. The transactional properties are addressed by merging of the Migrating Workflow Model with a Transactional Workflow Model, in which the workflow designer has the ability of specifying, independently, the task coordination requirements, the failure atomicity requirements, and the execution atomicity requirements. The result, described in this paper, is a migrating workflow model endowed with transactional properties that guarantee the correct execution of workflow applications in the presence of failures and in the presence of concurrent access to shared data.", 
    "genre": "research_article", 
    "id": "sg:pub.10.1023/b:mone.0000034701.73879.cf", 
    "inLanguage": [
      "en"
    ], 
    "isAccessibleForFree": false, 
    "isPartOf": [
      {
        "id": "sg:journal.1136741", 
        "issn": [
          "1383-469X", 
          "1572-8153"
        ], 
        "name": "Mobile Networks and Applications", 
        "type": "Periodical"
      }, 
      {
        "issueNumber": "5", 
        "type": "PublicationIssue"
      }, 
      {
        "type": "PublicationVolume", 
        "volumeNumber": "9"
      }
    ], 
    "name": "Providing Transactional Properties for Migrating Workflows", 
    "pagination": "473-480", 
    "productId": [
      {
        "name": "readcube_id", 
        "type": "PropertyValue", 
        "value": [
          "f43b6aaccc74b714f1075ff919573647c2c0a1749e6bc68b88695c3dbe13d1a5"
        ]
      }, 
      {
        "name": "doi", 
        "type": "PropertyValue", 
        "value": [
          "10.1023/b:mone.0000034701.73879.cf"
        ]
      }, 
      {
        "name": "dimensions_id", 
        "type": "PropertyValue", 
        "value": [
          "pub.1051270669"
        ]
      }
    ], 
    "sameAs": [
      "https://doi.org/10.1023/b:mone.0000034701.73879.cf", 
      "https://app.dimensions.ai/details/publication/pub.1051270669"
    ], 
    "sdDataset": "articles", 
    "sdDatePublished": "2019-04-10T22:30", 
    "sdLicense": "https://scigraph.springernature.com/explorer/license/", 
    "sdPublisher": {
      "name": "Springer Nature - SN SciGraph project", 
      "type": "Organization"
    }, 
    "sdSource": "s3://com-uberresearch-data-dimensions-target-20181106-alternative/cleanup/v134/2549eaecd7973599484d7c17b260dba0a4ecb94b/merge/v9/a6c9fde33151104705d4d7ff012ea9563521a3ce/jats-lookup/v90/0000000001_0000000264/records_8690_00000508.jsonl", 
    "type": "ScholarlyArticle", 
    "url": "http://link.springer.com/10.1023%2FB%3AMONE.0000034701.73879.cf"
  }
]
 

Download the RDF metadata as:  json-ld nt turtle xml License info

HOW TO GET THIS DATA PROGRAMMATICALLY:

JSON-LD is a popular format for linked data which is fully compatible with JSON.

curl -H 'Accept: application/ld+json' 'https://scigraph.springernature.com/pub.10.1023/b:mone.0000034701.73879.cf'

N-Triples is a line-based linked data format ideal for batch operations.

curl -H 'Accept: application/n-triples' 'https://scigraph.springernature.com/pub.10.1023/b:mone.0000034701.73879.cf'

Turtle is a human-readable linked data format.

curl -H 'Accept: text/turtle' 'https://scigraph.springernature.com/pub.10.1023/b:mone.0000034701.73879.cf'

RDF/XML is a standard XML format for linked data.

curl -H 'Accept: application/rdf+xml' 'https://scigraph.springernature.com/pub.10.1023/b:mone.0000034701.73879.cf'


 

This table displays all metadata directly associated to this object as RDF triples.

85 TRIPLES      21 PREDICATES      32 URIs      19 LITERALS      7 BLANK NODES

Subject Predicate Object
1 sg:pub.10.1023/b:mone.0000034701.73879.cf schema:about anzsrc-for:08
2 anzsrc-for:0806
3 schema:author N7bcd644a2dd34dcf952670a4227de9df
4 schema:citation sg:pub.10.1007/978-3-642-58908-9_15
5 sg:pub.10.1007/bf00119339
6 https://doi.org/10.1016/s0306-4379(99)00026-5
7 https://doi.org/10.1142/s0218215792000155
8 https://doi.org/10.7146/dpb.v19i338.6569
9 schema:datePublished 2004-10
10 schema:datePublishedReg 2004-10-01
11 schema:description Current workflow management systems have several limitations that need to be addressed by the research community. This paper deals with two of them: the lack of flexibility necessary in a changing business environment, and the lack of transactional guarantees for workflow applications. To handle the dynamic character of current business environments and processes, we have proposed the Migrating Workflow Model. A migrating workflow transfers its code (specification) and its execution state to a site, negotiates a service to be executed on its behalf, receives the results, and moves on. The next place visited by the workflow, and the next service requested, is determined by both the objectives of the process and the results of the current requests. The transactional properties are addressed by merging of the Migrating Workflow Model with a Transactional Workflow Model, in which the workflow designer has the ability of specifying, independently, the task coordination requirements, the failure atomicity requirements, and the execution atomicity requirements. The result, described in this paper, is a migrating workflow model endowed with transactional properties that guarantee the correct execution of workflow applications in the presence of failures and in the presence of concurrent access to shared data.
12 schema:genre research_article
13 schema:inLanguage en
14 schema:isAccessibleForFree false
15 schema:isPartOf Nb8a99d42c199426e8cfc09d3819db22a
16 Nc96be9649f454b2190dca49f4ef119ba
17 sg:journal.1136741
18 schema:name Providing Transactional Properties for Migrating Workflows
19 schema:pagination 473-480
20 schema:productId Nbbe49cbe94af457685847bbdaf32186c
21 Nbed2ff140c1d47b7b6537635fef4ef33
22 Nc08cf178311248cbab798797a01ac2ec
23 schema:sameAs https://app.dimensions.ai/details/publication/pub.1051270669
24 https://doi.org/10.1023/b:mone.0000034701.73879.cf
25 schema:sdDatePublished 2019-04-10T22:30
26 schema:sdLicense https://scigraph.springernature.com/explorer/license/
27 schema:sdPublisher N92ca3015a8e441f09ff9bdd916b941d6
28 schema:url http://link.springer.com/10.1023%2FB%3AMONE.0000034701.73879.cf
29 sgo:license sg:explorer/license/
30 sgo:sdDataset articles
31 rdf:type schema:ScholarlyArticle
32 N5bf0dc16a3294a838526df8db9b624c8 rdf:first sg:person.015306104725.95
33 rdf:rest rdf:nil
34 N7bcd644a2dd34dcf952670a4227de9df rdf:first sg:person.0620441046.64
35 rdf:rest N5bf0dc16a3294a838526df8db9b624c8
36 N92ca3015a8e441f09ff9bdd916b941d6 schema:name Springer Nature - SN SciGraph project
37 rdf:type schema:Organization
38 Nb8a99d42c199426e8cfc09d3819db22a schema:volumeNumber 9
39 rdf:type schema:PublicationVolume
40 Nbbe49cbe94af457685847bbdaf32186c schema:name dimensions_id
41 schema:value pub.1051270669
42 rdf:type schema:PropertyValue
43 Nbed2ff140c1d47b7b6537635fef4ef33 schema:name readcube_id
44 schema:value f43b6aaccc74b714f1075ff919573647c2c0a1749e6bc68b88695c3dbe13d1a5
45 rdf:type schema:PropertyValue
46 Nc08cf178311248cbab798797a01ac2ec schema:name doi
47 schema:value 10.1023/b:mone.0000034701.73879.cf
48 rdf:type schema:PropertyValue
49 Nc96be9649f454b2190dca49f4ef119ba schema:issueNumber 5
50 rdf:type schema:PublicationIssue
51 anzsrc-for:08 schema:inDefinedTermSet anzsrc-for:
52 schema:name Information and Computing Sciences
53 rdf:type schema:DefinedTerm
54 anzsrc-for:0806 schema:inDefinedTermSet anzsrc-for:
55 schema:name Information Systems
56 rdf:type schema:DefinedTerm
57 sg:journal.1136741 schema:issn 1383-469X
58 1572-8153
59 schema:name Mobile Networks and Applications
60 rdf:type schema:Periodical
61 sg:person.015306104725.95 schema:affiliation https://www.grid.ac/institutes/grid.432790.b
62 schema:familyName Rusinkiewicz
63 schema:givenName Marek
64 schema:sameAs https://app.dimensions.ai/discover/publication?and_facet_researcher=ur.015306104725.95
65 rdf:type schema:Person
66 sg:person.0620441046.64 schema:affiliation https://www.grid.ac/institutes/grid.432790.b
67 schema:familyName Cichocki
68 schema:givenName Andrzej
69 schema:sameAs https://app.dimensions.ai/discover/publication?and_facet_researcher=ur.0620441046.64
70 rdf:type schema:Person
71 sg:pub.10.1007/978-3-642-58908-9_15 schema:sameAs https://app.dimensions.ai/details/publication/pub.1019381722
72 https://doi.org/10.1007/978-3-642-58908-9_15
73 rdf:type schema:CreativeWork
74 sg:pub.10.1007/bf00119339 schema:sameAs https://app.dimensions.ai/details/publication/pub.1024666070
75 https://doi.org/10.1007/bf00119339
76 rdf:type schema:CreativeWork
77 https://doi.org/10.1016/s0306-4379(99)00026-5 schema:sameAs https://app.dimensions.ai/details/publication/pub.1006585768
78 rdf:type schema:CreativeWork
79 https://doi.org/10.1142/s0218215792000155 schema:sameAs https://app.dimensions.ai/details/publication/pub.1062965327
80 rdf:type schema:CreativeWork
81 https://doi.org/10.7146/dpb.v19i338.6569 schema:sameAs https://app.dimensions.ai/details/publication/pub.1073611135
82 rdf:type schema:CreativeWork
83 https://www.grid.ac/institutes/grid.432790.b schema:alternateName Ericsson (United States)
84 schema:name Information and Computer Sciences Research Laboratory, Telcordia Technologies, USA
85 rdf:type schema:Organization
 




Preview window. Press ESC to close (or click here)


...