2007
DOI: 10.1007/978-3-540-74974-5_8
|View full text |Cite
|
Sign up to set email alerts
|

Bite: Workflow Composition for the Web

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
32
0

Year Published

2008
2008
2016
2016

Publication Types

Select...
6
3

Relationship

2
7

Authors

Journals

citations
Cited by 50 publications
(32 citation statements)
references
References 5 publications
0
32
0
Order By: Relevance
“…The Bite language however only partially addresses the requirements we have identified in Sect. 3, as it lacks support for content-type negotiation and provides only limited compliance with the uniform interface principle (PUT is not supported [29]). In [30], the state transition logic of a RESTful service has been designed using a Petri-net formalism, which could also potentially be used for composition purposes.…”
Section: Discussionmentioning
confidence: 99%
“…The Bite language however only partially addresses the requirements we have identified in Sect. 3, as it lacks support for content-type negotiation and provides only limited compliance with the uniform interface principle (PUT is not supported [29]). In [30], the state transition logic of a RESTful service has been designed using a Petri-net formalism, which could also potentially be used for composition purposes.…”
Section: Discussionmentioning
confidence: 99%
“…The idea of a RESTful Web service API to access the state of workflow instances has been also described in [28], where an ad-hoc solution based on client callback URIs was proposed to deal with the problem of push notifications. The feature of hypermedia-based discovery of the active tasks of a workflow was also featured in the Bite [5] project. In our architecture we introduce a more general design based on hierarchically nested feeds.…”
Section: Related Workmentioning
confidence: 99%
“…We follow a similar, but less generic, approach, when we propose a specific set of resource-oriented activities to natively support the composition of RESTful Web services. Bite [47] (or the IBM Project Zero assembly flow language) can be seen as a simplified variant of BPEL with a reduced set of activities specifically targeting the development of collaborative Web application workflows [48]. Similar to BPEL for REST, the language supports the invocation of RESTful Web services and the corresponding runtime allows to automatically publish processes as resources.…”
Section: Related Workmentioning
confidence: 99%