the epnk: ideas and concepts · ekkart kindler the epnk: ideas and concepts 32 extension mechanisms...

The ePNK: Ideas and concepts

Ekkart Kindler

Ekkart Kindler

2 The ePNK: Ideas and concepts

Motivation

Ekkart Kindler


Motivation

:Place

:Transition

:Arc

:Transition

:Place

:Arc

:Arc

source

target source

target

target source

:Arc source target

:Petrinet

:Token

Place Transition

1 source

1 target

Arc

*

PetriNet

Token *

Node

Object

concrete syntax abstract syntax

Place

Transition

Arc

Token

generate an editor

Ekkart Kindler


Motivation

Ekkart Kindler


Real world issues

Many more features:

Pages, reference nodes, ...

Need to define specific XML syntax (PNML)

Different versions of Petri nets

(each would need a separate GMF-editor)

Definition of new versions of Petri net types

(without touching the existing tool,

without programming at all?)

Ekkart Kindler


Outline

Motivation

ePNK & PNML

Overview

Core model

Type model

Mapping to XML

ePNK: Extension mechanisms

Ekkart Kindler


PNML in a nutshell

The Petri Net Markup Language (PNML) is an XML-based

transfer format for “all kinds” of Petri nets.

PNML is now an International Standard: ISO/IEC-15909-2

Part 2: focus on high-level nets

Part 3: different extensions

modularity

type and feature definitions

particular versions of Petri nets

…

Ekkart Kindler


But ...

Ekkart Kindler


PNML and XML

The Petri Net Markup Language (PNML) is an XML-based

transfer format for “all kinds” of Petri nets.

For exchanging, PNML between different tools, the XML

syntax is important; but that’s a technical issue.

The interesting stuff are the concepts of PNML.

Ekkart Kindler


Challenges

many versions and variants of Petri nets

with many common features,

but also with many variations,

some fundamental differences,

and many different combinations of the same or similar features

Ekkart Kindler


Objective

PNML should enable the exchange of all

kinds of Petri nets, and, ultimately,

alleviate exchanging between Petri net tools

that support different versions of Petri nets

without loosing too much information.

Ekkart Kindler


A first example

<place id="p1"/>

<arc id="a1" source="p1" target="t1"/>

<transition id="t1"/>

<arc id="a2" source="t1" target="p2"/>

<place id="p2"/>

Ekkart Kindler


A first example

<pnml xmlns="http://www.pnml.org/...">

<net id="n1" type="...">

...

<place id="p1"/>

<arc id="a1" source="p1" target="t1"/>


<arc id="a2" source="t1" target="p2"/>

<place id="p2"/>

...

</net>

</pnml>

Ekkart Kindler


A first example

...

<place id="p1">

<name>

<text>i</text>

</name>

<initialMarking>

<text>1</text>

</initialMarking>

</place>

...

i action o

1

Label

2

Ekkart Kindler


Basic Idea

„All kinds“ of Petri nets can be represented by

places

transitions, and

arcs

along with some

labels

PNML Core Model

Petri Net Type

Definition

«merge»

Ekkart Kindler


Outline

Motivation

ePNK & PNML

Overview

Core model

Type model

Mapping to XML


Ekkart Kindler


Core Model (overview)

Transition Place

source

target Node Arc

Label

*

*

i action o

Object

1 5

PNML Core Model

PetriNet

label

Ekkart Kindler



Transition Place

source

target Node Arc

Object Label

*

*

PetriNet

label

Ekkart Kindler



Transition Place

source

target Node Arc Annotation Attribute

Label Object

*

* *

i o 2 1

1

PetriNet

label

Ekkart Kindler


Name


Transition Place

source

target Node Arc Annotation Attribute

Label Object

*

* *

name

{redefines label}

label

PetriNet

Ekkart Kindler


PNML Core Model

pages and

reference

nodes

graphical

information

Tool specific

information

Ekkart Kindler


Tool specific information

<initialMarking>

<text>3</text>

<toolspecific tool="org.pnml.tool"

version="1.0">

<tokengraphics>

<tokenposition x="-2" y="-2" />

<tokenposition x="2" y="0" />

<tokenposition x="-2" y="2" />

</tokengraphics>

</toolspecific>

</initialMarking>

Ekkart Kindler


Outline

Motivation

ePNK & PNML

Overview

Core model

Type model

Mapping to XML


Ekkart Kindler


Type Definition: PT-Net

initialMarking

Arc

PTMarking Place

XML_Schema::

NonNegativeInteger XML_Schema::

PositiveInteger

inscription

text text

{redefines label}

{redefines label}

3 2

Annotation

PTInscription

Petri Net Type

Definition

Ekkart Kindler


Type Definition: PT-Net

initialMarking

Arc

Place

XML_Schema::

NonNegativeInteger XML_Schema::

PositiveInteger

inscription

text text

{redefines label}

{redefines label}

context Arc inv:

( self.source.isKindOf(Place) and

self.target.isKindOf(Transition) ) or

( self.source.isKindOf(Transition) and

self.target.isKindOf(Place) )

Annotation

PTInscription

PTMarking

Ekkart Kindler


Type Definition: HLPNG (overview)

Ekkart Kindler


Outline

Motivation

ePNK & PNML

Overview

Core model

Type model

Mapping to XML


Ekkart Kindler


Core Model in XML

<pnml xmlns="http:...">

<net id="n1" type="...">

<place id="p1"/>

<arc id="a1" source="p1"

target="t1"/>


<arc id="a2" source="t1"

target="p2"/>

<place id="p2"/>

</net>

</pnml>

Transition Place

source

target Node Arc

Object

*

PetriNet

Ekkart Kindler


XML::

PCDATA

text

Labels in XML

...

<place id="p1">

<name>

<text>i</text>

</name>

<initialMarking>

<text>1</text>

</initialMarking>

</place>

...

Name name

XML_Schema::

NonNegativeInteger

initialMarking

text

PTMarking

PNML Core Model

PT-Net

Node

Place

Ekkart Kindler


In general

How can this be defined in general?

Core model: Just implement it

Petri net type: Just implement it, if standard mapping is not good enough.

Ekkart Kindler


Outline

Motivation

ePNK & PNML

Overview

Core model

Type model

Mapping to XML


Ekkart Kindler


Extension mechanisms

Net-types plug-in: A EMF-model plus a factory for producing all the extended elements

PNML-Mapping for new elements (if necessary)

Separate constraints for syntactical constraints (batch and live)

For structured net types: Interface for parsing and linking (in concrete type used Xtext worked surprisingly smooth for parsing and surprisingly bad for serialization)

Extension of graphical appearance of nets elements (dependent on attributes)

PNML-Mapping:

extended mapping that is flexible enough for all our needs (and some more)

hooked into the existing XMI-serialization ( when there is no mapping defined in the ePNK, XMI is used as default, XMI deals with cross-references even when no id’s exist)

Ekkart Kindler


The ePNK

the epnk: ideas and concepts · ekkart kindler the epnk: ideas and concepts 32 extension mechanisms...

Documents