The Petri Net Markup Language: Concepts, Technology, and Tools

Billington, Jonathan; Christensen, Søren; Hee, Kees van; Kindler, Ekkart; Kummer, Olaf; Petrucci, Laure; Post, R.; Stehno, Christian; Weber, M.

doi:10.1007/3-540-44919-1_31

Cited by 230 publications

(125 citation statements)

References 1 publication

(2 reference statements)

Supporting

Mentioning

115

Contrasting

Unclassified

Order By: Relevance

“…SARN Editor and SARN Simulator understand a common XML schema which provides a framework of communication. The XML format follows the Petri Net Markup Language (PNML) standards [3]. The simulator takes the XML generated by the editor as input to perform the simulation.…”

Section: Sarn Editor Sarn Editor Is Composed Of Process Definition Edmentioning

confidence: 99%

Self-adapting recovery nets for policy-driven exception handling in business processes

Hamadi

Benatallah

Medjahed

2007

Distrib Parallel Databases

View full text Add to dashboard Cite

In this paper, we propose Self-Adapting Recovery Net (SARN), an extended Petri net model, for specifying exceptional behavior in business processes. SARN adapts the structure of the underlying Petri net at run time to handle exceptions while keeping the Petri net design easy. The proposed framework caters for the specification of high-level recovery policies that are incorporated either with a single task or a set of tasks, called a Recovery Region. These recovery policies are generic directives that model exceptions at design time together with a set of primitive operations used at run time to handle the occurrence of exceptions. We identified a set of recovery policies that are useful and commonly needed in many practical situations. A tool has been developed to illustrate the viability of the proposed exception handling technique.

show abstract

Section: Sarn Editor Sarn Editor Is Composed Of Process Definition Edmentioning

confidence: 99%

Self-adapting recovery nets for policy-driven exception handling in business processes

Hamadi

Benatallah

Medjahed

2007

Distrib Parallel Databases

View full text Add to dashboard Cite

show abstract

“…The objective of part 2 is to define an interchange format for Petri nets called PNML (Petri Net Markup Language) [3]. This interchange format relies on XML technology.…”

Section: Partmentioning

confidence: 99%

PN Standardisation: A Survey

Hillah

Kordon

Petrucci

et al. 2006

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Petri Nets formalism requires standardisation to facilitate the work of researchers in this field and to enable the data exchange between different Petri Nets tools through a common format. Following this, a three-part International Standard (ISO/IEC 15909) has been developed. Part 1 is devoted to terms and definitions for Place/Transition Nets and High-Level Petri Nets. It is now completed (published as a standard) but will include an addendum on Symmetric Nets. Part 2 aims at providing a transfer format for High-level Petri Nets, called PNML, based on XML. Work on part 3 which deals with extensions has not started yet. In this paper the first two parts of the standard are presented. Then, to support part 2, an implementation of PNML, through an API framework to be integrated into Petri Net tools, is proposed. It allows for the translation of any Petri Net, designed by a given tool in a dedicated format, into PNML. The Challenge of PN StandardisationPetri Nets [4,8,26,28] are a mathematically defined formalism and may thus be used to provide unambiguous specifications and descriptions of applications. They are especially dedicated to specify and design discrete event systems and this technique is particularly suited to parallel and distributed systems development as it supports concurrency. The technique allows for specification of systems at a level which is independent of the implementation choices (i.e., by software, hardware -electronic and/or mechanical -or humans, or a combination of these) and has been widely used to describe telecommunication systems, protocols, microprocessor architectures,... since their invention in 1962. They also constitute an executable technique, allowing specification prototypes to be developed to test ideas at the earliest and cheapest opportunity. Specifications written in the technique may be subject to analysis methods to prove properties about the specifications, before implementation commences, thus saving on A problem with Petri nets is the explosion of the huge number of elements when described in their graphical form, for specification of complex systems. were developed to overcome this problem by introducing higher-level concepts, such as the use of complex structured data carried by tokens, and using algebraic expressions to annotate net elements. The use of high-level concepts within this Petri net framework is analogous to the use of those in high-level programming languages (as opposed to assembly languages). In the Petri nets community the term High-level net is generally used to refer to nets using such concepts.Two Standardisation of the technique has been seen as an opportunity to obtain a better organisation of the work in the Petri Net community. It has several issues:-to enable the stakeholder -researchers, as well as engineers using Petri nets -to use the same terminology; -to develop future extensions on a stable common basis, e.g., P/T nets or High-level nets; -to provide a reference implementation that will facilitate the data exchange between...

show abstract

“…(Mendling and Nuettgens, 2004), (EPML, 2004), offers an XML-based interchange format especially for Event-driven Process Chains. An XML-based interchange language for various types of Petri nets is given by PNML (Petri net Markup Language) (PNML, 2004), (Billington et al, 2003).…”

Section: Related Workmentioning

confidence: 99%

Using GXL for exchanging business process models

Winter

Simon

2005

ISeB

View full text Add to dashboard Cite

The GXL Graph eXchange Language is an XML-based standard exchange language for sharing graph data between tools. GXL can be customized to exchange application specific types of graphs. This is done by exchanging both, the instance graph, representing the data itself, and the schema, representing the graph structure.Business process models are usually depicted in a graph-like form. This paper describes a novel application of GXL to the exchange of business process models. It is shown, how to customize GXL to exchange business process models depicted as Event-driven Process Chains and Workflow nets as examples for the control flow part of business process models. Each level of modeling is exemplarily demonstrated from the metaschemas down to instances of graphs.

show abstract

The Petri Net Markup Language: Concepts, Technology, and Tools

Cited by 230 publications

References 1 publication

Self-adapting recovery nets for policy-driven exception handling in business processes

Self-adapting recovery nets for policy-driven exception handling in business processes

PN Standardisation: A Survey

Using GXL for exchanging business process models

Contact Info

Product

Resources

About